IPv6
Measured 2026-11-14 02:38 UTC · aaaa.botWorks over IPv6, with one gap: its mail servers lack IPv6.
the.hosting has 2 IPv6 addresses and answers on every one we tested.
- ✓ the.hosting answers (2 of 2 addresses)
- ✗ Mail: 0 of 1 servers have IPv6
- ✓ Nameservers: 2 of 2 have IPv6
Details: published addresses and what answered
Loads over IPv6 with a valid certificate after 1 redirect: HTTP 200.
| Name | Published address (AAAA) | Answers when we connect |
|---|---|---|
| the.hosting | Published2606:4700:3037::6815:4eee2606:4700:3037::ac43:8a6e | Answers when we connect✓ answers on 443✓ answers on 443 |
Publishedmail.the.hosting | Answers when we connect✗ no IPv6 | |
| Nameservers | Publishedtara.ns.cloudflare.comyew.ns.cloudflare.com | Answers when we connect✓ has IPv6✓ has IPv6 |
See where it lives on the IPv4 map →
Lineage
Our records: Feb 4, 2016 → Nov 15, 2026Oldest registry snapshot we hold: 2018 · 1 renewal on record · DNS at Cloudflare · 5 nameserver changes seen. These dates are when our records begin, not when the domain was registered.
Registrar
- PDR Ltd.Feb 2018
- Namecheaplast seen Sep 2025Mar – Sep 2025
DNS provider
- toughdomains.comFeb 2018
- uniregistrymarket.linkApr 2018
- pq.hostingMar 2025
- CloudflareNOWSeen from Jun 2026
- the.hostingSep 2025 – May 2026
IPv6
- IPv6published, and answeringFirst measured Nov 2026
What changed
- IPv6 first measured: published, and answering on Nov 4, 2026the.hosting has 2 IPv6 addresses. Grade B. Measured by aaaa.bot, 2026-11-04 01:51 UTC. No earlier IPv6 record is held, so this is not a "gained" date.
- DNS moved to Cloudflare between May 12, 2026 and Jun 13, 2026ns1.the.hosting, ns2.the.hosting → tara.ns.cloudflare.com, yew.ns.cloudflare.com. Old set last seen in WHOIS on 2026-05-12; new set first seen in WHOIS on 2026-06-13.
- DNS moved to the.hosting between Aug 3, 2025 and Sep 7, 2025anna.ns.cloudflare.com, cleo.ns.cloudflare.com → ns1.the.hosting, ns2.the.hosting. Old set last seen in WHOIS on 2025-08-03; new set first seen in WHOIS on 2025-09-07.
- Renewed +1 year between Aug 3, 2025 and Sep 7, 2025Expiry moved from 2026-01-05 to 2027-01-05, at Namecheap.
- DNS moved to Cloudflare between Mar 16, 2025 and May 28, 2025ns1.pq.hosting, ns2.pq.hosting → anna.ns.cloudflare.com, cleo.ns.cloudflare.com. Old set last seen in WHOIS on 2025-03-16; new set first seen in WHOIS on 2025-05-28.
- DNS moved to pq.hosting between Apr 17, 2018 and Mar 16, 2025ns1.uniregistrymarket.link, ns2.uniregistrymarket.link → ns1.pq.hosting, ns2.pq.hosting. Old set last in the registry zone file on 2018-04-17; new set first seen in WHOIS on 2025-03-16.
- Re-registered between Feb 19, 2018 and Mar 16, 2025The name lapsed and was registered again through Namecheap. Expiry moved from 2019-01-18 to 2026-01-05.
- DNS moved to uniregistrymarket.link between Feb 19, 2018 and Apr 3, 2018ns1.toughdomains.com, ns2.toughdomains.com → ns1.uniregistrymarket.link, ns2.uniregistrymarket.link. Old set last seen in WHOIS on 2018-02-19; new set first in the registry zone file on 2018-04-03.
Solid bar: the stretch we observed that name. Dot: a single sighting. Dotted line: no record between sightings of the same name. Nothing is drawn between different names.
Registrar and renewals: 28 WHOIS/RDAP snapshots, 2018-02-19 to 2026-05-12 (ledger built 2026-09-27). Every renewal
DNS provider, registry zone files: 162 .hosting zone-file snapshots held, 2016-02-04 to 2026-11-15.
DNS provider, WHOIS snapshots: 16 WHOIS/RDAP snapshots that listed nameservers, 2018-02-19 to 2026-06-13 (who.is archive). Both sources feed one row per provider (hover a bar to see which); a change is placed between the nearest observations on either side, and where the two sources disagree, both are listed under What changed.
Want to know when the.hosting changes?
Monitor it free — 5 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.
Explore related
Registered in 2025 — the same year as yccdn.ru, edgcdn.net and share.google.