Rank #4,958Updated November 10, 2026
solo.to
solo.to is registered with Spaceship, Inc. since February 23, 2025 (1.7 years). The registration expires on February 15, 2031. Its email security grade is B. Its SSL certificate is issued by Google Trust Services and is valid for 50 more days.
- Domain age
- 1.7 yrs
- Technologies
- —
- Email security
- B
- SSL days left
- 50
Registration
| Registrar | Spaceship, Inc. |
|---|---|
| IANA ID | 3862 |
| Registered | February 23, 2025 |
| Expires | February 15, 2031 |
| Updated | February 23, 2025 |
| Status | active |
| Name servers | kyree.ns.cloudflare.com, nena.ns.cloudflare.com |
| DNSSEC | Not signed |
DNS records
| Type | Value | TTL |
|---|---|---|
| A | 172.66.167.234 | 264 |
| A | 104.20.19.133 | 264 |
| MX | mx.zoho.com 10 | 300 |
| MX | mx2.zoho.com 20 | 300 |
| MX | mx3.zoho.com 50 | 300 |
| NS | kyree.ns.cloudflare.com | 86400 |
| NS | nena.ns.cloudflare.com | 86400 |
| CAA | issue 0 comodoca.com | 3600 |
| CAA | issue 0 digicert.com; cansignhttpexchanges=yes | 3600 |
| CAA | issue 0 letsencrypt.org | 3600 |
| CAA | issue 0 pki.goog; cansignhttpexchanges=yes | 3600 |
| CAA | issue 0 ssl.com | 3600 |
| CAA | issuewild 0 comodoca.com | 3600 |
| CAA | issuewild 0 digicert.com; cansignhttpexchanges=yes | 3600 |
| CAA | issuewild 0 letsencrypt.org | 3600 |
| CAA | issuewild 0 pki.goog; cansignhttpexchanges=yes | 3600 |
| CAA | issuewild 0 ssl.com | 3600 |
| TXT | apple-domain-verification=dkr5ZQOqnrYMcTYc0MfNgnLbKdSGJaQG63lCMNdfOXE | 300 |
| TXT | globalsign-domain-verification=9IMSKrOIyOZEp9IwI7vfoPl5APLsdGT4FzZxyyQf-J | 300 |
| TXT | google-site-verification=JClQ-yACFd82BSZIHoKrrvrogkVWs7FfBioJ-sG297A | 300 |
| TXT | v=spf1 include:mailgun.org include:zoho.com -all | 300 |
| AAAA | 2606:4700:10::ac42:a7ea | 42 |
| AAAA | 2606:4700:10::6814:1385 | 42 |
SSL certificate
| Valid | Valid |
|---|---|
| Issuer | US, WE1, Google Trust Services |
| Expires | December 30, 2026 |
| Days remaining | 50 |
| Protocol | TLSv1.3 |
| Names | solo.to, *.solo.to |
Email security
BScore 84/100 across SPF, DMARC, DKIM, MTA-STS and BIMI.
- warnSPF uses 10 of the 10 allowed DNS lookups. Adding another service may break it.
- warnDKIM key found (selector: zoho) but it is only 1024 bits; 2048 is recommended.
- warnNo MTA-STS: mail sent to you can be downgraded to an unencrypted connection.
- warnNo TLS-RPT record, so you won't hear about failed encrypted deliveries.
- goodSPF record found.
- goodSPF ends with -all: servers you have not listed are rejected (hard fail).
- goodDMARC policy is reject: mail that fails authentication is blocked.
- goodDMARC aggregate reports are sent to mailto:[email protected], mailto:[email protected].
- good3 MX record(s) found. Mail is handled by Zoho Mail.
- goodBIMI record found: supporting inboxes can show your brand logo.
About solo.to
Who is the registrar of solo.to?
solo.to is registered with Spaceship, Inc. (IANA ID 3862).
When does solo.to expire?
The current registration of solo.to expires on February 15, 2031. It was first registered on February 23, 2025.
Does solo.to protect its email with SPF and DMARC?
solo.to scores 84/100 (grade B) for email security. SPF uses 10 of the 10 allowed DNS lookups. Adding another service may break it. DKIM key found (selector: zoho) but it is only 1024 bits; 2048 is recommended.
What are the name servers of solo.to?
solo.to uses kyree.ns.cloudflare.com, nena.ns.cloudflare.com.