archerage.to
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403SafeSSL: 49 days left9 years oldTranco #249381
70
archerage.to was registered on 29 Dec 2016 via Tonic and the registry expiry is 29 Dec 2026. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/archerage.to.
archerage.to publishes 2 nameservers. DNSSEC is not signed.
archerage.to has 2 IPv4 addresses (104.21.88.252, 172.67.155.49). The geolocation database places 104.21.88.252 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 49 days left (TLS 1.3).
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for archerage.to in the checks that ran.
Domain · RDAP/WHOIS
archerage.to was registered on 29 Dec 2016 via Tonic. The registry returned 1 status value and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/archerage.to.
| Registered | since 29 Dec 2016 |
|---|---|
| Created | 29 December 2016 |
| Updated | 6 July 2026 |
| Expires | 29 December 2026 |
| Registrar | Tonic |
| Status | active |
| Nameservers | alex.ns.cloudflare.com, kira.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.tonicregistry.to/rdap/domain/archerage.to |
Nameserver alex.ns.cloudflare.com is published for archerage.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/archerage.to.
Nameserver kira.ns.cloudflare.com is published for archerage.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/archerage.to.
DNS
archerage.to has 2 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.88.252, 172.67.155.49 |
|---|---|
| AAAA | — |
| NS | alex.ns.cloudflare.com, kira.ns.cloudflare.com |
| MX | mx.mail.archerage.to (10) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at archerage.to is "v=spf1 a mx include:spf.mail.archerage.to -all".
The DMARC text record at _dmarc.archerage.to is "v=DMARC1; p=quarantine; pct=100; adkim=r; aspf=r; rua=mailto:[email protected]".
IPv4 address 104.21.88.252 answers for archerage.to at resolver 1.1.1.1:53.
IPv4 address 172.67.155.49 answers for archerage.to at resolver 1.1.1.1:53.
Mail exchanger mx.mail.archerage.to has preference 10.
Hosting and geo
archerage.to is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.88.252 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for archerage.to is valid, with 49 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | archerage.to |
| Valid from | 20 September 2026 |
| Valid until | 19 December 2026 |
| Days left | 49 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.archerage.to, archerage.to.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 403 in 29 ms. The target title is 16 characters and the page has 0 H1 headings.
| Status | 403 |
|---|---|
| TTFB | 29 ms |
| Title length | 16 yes |
| Quoted title | "Just a moment..." |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | noindex,nofollow |
| Canonical | — |
| Language | en-US |
| Links | 0 |
| Images | 0 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for archerage.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 | yes |
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 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 10 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 archerage.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 archerage.to?
archerage.to is placed in Toronto, Canada.
When does archerage.to expire?
archerage.to expires on 29 December 2026 according to https://rdap.tonicregistry.to/rdap/domain/archerage.to.
Who owns archerage.to?
The registry did not return a person or a company for archerage.to. RDAP often redacts the registrant. The registrar on file is Tonic.
Sources
- RDAP source https://rdap.tonicregistry.to/rdap/domain/archerage.to at 2026-10-30T15:15:21Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:15:21Z
- TLS source tls:443 at 2026-10-30T15:15:21Z
- HTTP source https://archerage.to/ at 2026-10-30T15:15:21Z
- Tech source wappalyzergo at 2026-10-30T15:15:21Z
- Geo source db-ip at 2026-10-30T15:15:21Z
- Safety source family DNS and local lists at 2026-10-30T15:15:21Z
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.