sgnow.to
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 66 days left6 years old
50
sgnow.to was registered on 22 Oct 2020 via Tonic and the registry expiry is 27 Nov 2026. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/sgnow.to.
sgnow.to publishes 2 nameservers. DNSSEC is not signed.
sgnow.to has 2 IPv4 addresses (104.21.61.119, 172.67.210.69) and 2 IPv6 addresses (2606:4700:3035::ac43:d245, 2606:4700:3037::6815:3d77). The geolocation database places 104.21.61.119 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 66 days left (TLS 1.3).
No safety warning was recorded for sgnow.to in the checks that ran.
Domain · RDAP/WHOIS
sgnow.to was registered on 22 Oct 2020 via Tonic. The registry returned 1 status value and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/sgnow.to.
| Registered | since 22 Oct 2020 |
|---|---|
| Created | 22 October 2020 |
| Updated | 11 January 2026 |
| Expires | 27 November 2026 |
| Registrar | Tonic |
| Status | active |
| Nameservers | cora.ns.cloudflare.com, joel.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.tonicregistry.to/rdap/domain/sgnow.to |
Nameserver cora.ns.cloudflare.com is published for sgnow.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/sgnow.to.
Nameserver joel.ns.cloudflare.com is published for sgnow.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/sgnow.to.
DNS
sgnow.to has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.61.119, 172.67.210.69 |
|---|---|
| AAAA | 2606:4700:3035::ac43:d245, 2606:4700:3037::6815:3d77 |
| NS | cora.ns.cloudflare.com, joel.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.61.119 answers for sgnow.to at resolver 1.1.1.1:53.
IPv4 address 172.67.210.69 answers for sgnow.to at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::ac43:d245 answers for sgnow.to at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3037::6815:3d77 answers for sgnow.to at resolver 1.1.1.1:53.
Hosting and geo
sgnow.to is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.61.119 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for sgnow.to is valid, with 66 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | sgnow.to |
| Valid from | 7 October 2026 |
| Valid until | 5 January 2027 |
| Days left | 66 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.sgnow.to, sgnow.to.
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
context deadline exceeded
Security
Family DNS for sgnow.to is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
First checked on 30 October 2026; changes will appear here.
Questions
Is sgnow.to safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts sgnow.to?
sgnow.to is placed in Toronto, Canada.
When does sgnow.to expire?
sgnow.to expires on 27 November 2026 according to https://rdap.tonicregistry.to/rdap/domain/sgnow.to.
Who owns sgnow.to?
The registry did not return a person or a company for sgnow.to. RDAP often redacts the registrant. The registrar on file is Tonic.
Sources
- RDAP source https://rdap.tonicregistry.to/rdap/domain/sgnow.to at 2026-10-30T15:17:59Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:17:59Z
- TLS source tls:443 at 2026-10-30T15:17:59Z
- HTTP source https://sgnow.to/ at 2026-10-30T15:17:59Z
- Tech source not available at 2026-10-30T15:17:59Z
- Geo source db-ip at 2026-10-30T15:17:59Z
- Safety source family DNS and local lists at 2026-10-30T15:17:59Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.