1sadf2qw.cfd
IPv6
Measured 2026-10-31 10:33 UTC · aaaa.botWebsite, mail and DNS all work over IPv6.
Both published IPv6 addresses accepted a connection when we tried them.
- ✓ 1sadf2qw.cfd answers (2 of 2 addresses)
- ✓ Mail: has IPv6
- ✓ Nameservers: 2 of 2 have IPv6
Details: published addresses and what answered
Loads over IPv6 with a valid certificate: HTTP 404.
| Name | Published address (AAAA) | Answers when we connect |
|---|---|---|
| 1sadf2qw.cfd | Published2606:4700:3030::ac43:a5ca2606:4700:3035::6815:49c1 | Answers when we connect✓ answers on 443✓ answers on 443 |
PublishedNo MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record. | Answers when we connecthas IPv6 | |
| Nameservers | Publishedhattie.ns.cloudflare.comwilson.ns.cloudflare.com | Answers when we connect✓ has IPv6✓ has IPv6 |
Lineage
Our records: Jan 19, 2016 → Nov 1, 2026DNS at Cloudflare · 1 nameserver change seen. These dates are when our records begin, not when the domain was registered.
What changed
- IPv6 first measured: published, and answering on Oct 31, 20261sadf2qw.cfd has 2 IPv6 addresses. Grade A. Measured by aaaa.bot, 2026-10-31 10:32 UTC. No earlier IPv6 record is held, so this is not a "gained" date.
- DNS moved to Cloudflare between Oct 23, 2026 and Oct 24, 2026ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com → hattie.ns.cloudflare.com, wilson.ns.cloudflare.com.
Nameservers, registry zone files: 166 .cfd zone-file snapshots held, 2016-01-19 to 2026-11-01.
Hatched = the span we hold records for. A coloured bar runs only between observations that named the same registrar or operator; nothing is assumed in between.
Each mark sits at the first observation of the new state; its bracket runs back to the last observation of the old one.
Want to know when 1sadf2qw.cfd changes?
Monitor it free — 50 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.