CONTINUOUS INTERNET TELEMETRY24H DRIFT68,088 material changesacross 64,935 domains · 24h to ~2h ago · +33,471 vs yesterdayROTATION56 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW538 curated domains not reachablelast probe, steadySITE ERRORS33,857 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 123,111 sites429 rate-limit / 403 bot-block, a posture signal

zirkonzahn.com

Observed Aug 2, 2026, 11:35 UTC (3d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of zirkonzahn.com was taken 3d ago

zirkonzahn.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zirkonzahn.com under watch moves it to the fast lane, where DomainDrift re-checks it about every 5 minutes and signs each reading, so a change becomes a dated event within minutes instead of waiting for the sweep to come round.

Watch zirkonzahn.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onCloudflare
Email byMicrosoft 365
Secured byLet's Encrypt
IPv6 · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-05 20:04 UTC

DomainDrift asked this domain for a TXT record at a name nobody registers, and got an answer back. A domain that answers a name that was never created is answering names in general, and that is wildcard DNS.

Wildcard DNS clusters around domain parking, dynamic DNS and catch-all hosting. It is also a real attack surface: if every invented hostname resolves, then a hostname an attacker invents resolves too, which is the ground state for subdomain takeover and for phishing hosted under a name that looks legitimate.

This is evidence of wildcard behaviour, not a proven fact. It rests on one control name: a domain could legitimately serve a TXT record at exactly that name for an unrelated reason, and a wildcard that answers address records but not TXT records would not be caught here at all. What this reading is and is not.

INFRASTRUCTURE MAPwhat zirkonzahn.com actually stands on - every host below is a signed observation
zirkonzahn.com
A / AAAA
172.67.68.27104.26.14.111104.26.15.1112606:4700:20::ac43:441b+2 more
Cloudflareserves the site
NS
rob.ns.cloudflare.comtess.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
zirkonzahn-com.mail.protection.outlook.com
Microsoft 365receives its email
TLS
zirkonzahn.com
Let's Encryptissued its certificate

DNS Records

A 3

  • 172.67.68.27
  • 104.26.14.111
  • 104.26.15.111

AAAA 3

  • 2606:4700:20::ac43:441b
  • 2606:4700:20::681a:f6f
  • 2606:4700:20::681a:e6f

MX 1

  • 10zirkonzahn-com.mail.protection.outlook.com

TXT 2

  • u56grdaijkjc1c5ejhfnrh4gg8
  • v=spf1 include:spf.protection.outlook.com include:spf.zirkonzahn.com ip4:31.207.122.152/29 ip4:31.207.122.48/29 ip4:3.126.7.233 ip4:176.9.15.255 -all

NS 2

  • rob.ns.cloudflare.com
  • tess.ns.cloudflare.com

SOA 1

  • rob.ns.cloudflare.com dns.cloudflare.com

MCP_RECORDS 1

  • v=spf1 include:zirkonzahn.com -all

DMARC_RECORDS 1

  • v=DMARC1; p=reject; rua=mailto:c2e5a1cd47104190bb5540f88538945a@dmarc-reports.cloudflare.net,mailto:dmarc@zirkonzahn.com; fo=s; aspf=s

BIMI_RECORDS 1

  • v=spf1 include:zirkonzahn.com -all

MTA_STS_RECORDS 1

  • v=spf1 include:zirkonzahn.com -all

TLS Certificates (4)

Common NameIssuerExpires
zirkonzahn.com C=US, O=Let's Encrypt, CN=YE2 Sun, 11 Oct 2026 10:14:55 +0000
YE2 C=US, O=ISRG, CN=Root YE Sat, 02 Sep 2028 23:59:59 +0000
Root YE C=US, O=Internet Security Research Group, CN=ISRG Root X2 Thu, 02 Sep 2032 23:59:59 +0000
ISRG Root X2 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (0)

None observed.

The proof

Signed at scan time. Check the math yourself. Every line above is part of one signed observation. Re-hash it and check the Ed25519 signature in your own browser; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_4ba5c7468245f50c
Output Hash
5434a9686b7a36d61e346a4bf6fcdb0ef1f3b663d1ae53dae33902dd237adcae
Signature
ed25519:9cb7f7b9d60c674c0256484edde21eeb3aeece9930eeb64d5d03e2b2b6c68bf6ce72b845c59197c0fe54973bc7586b5080608ef319fc8d4463959c53fd8ea104
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser