CONTINUOUS INTERNET TELEMETRY24H DRIFT63,733 material changesacross 59,883 domains · 24h to ~2h ago · +29,116 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW536 curated domains not reachablelast probe, steadySITE ERRORS33,804 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 130,707 sites429 rate-limit / 403 bot-block, a posture signal

zithromax.cyou

Observed Jul 26, 2026, 10:02 UTC (10d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of zithromax.cyou was taken 10d ago

zithromax.cyou is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zithromax.cyou 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 zithromax.cyou Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byDigiCert
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 04:43 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 zithromax.cyou actually stands on - every host below is a signed observation
zithromax.cyou
A / AAAA
64.190.63.222
unattributedserves the site
NS
ns2.sedoparking.comns1.sedoparking.com
sedoparking.comanswers its DNS
MX
localhost
localhostreceives its email
TLS
zithromax.cyou
DigiCert Incissued its certificate

DNS Records

A 1

  • 64.190.63.222

MX 1

  • 0localhost

TXT 5

  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all
  • v=spf1 -all

NS 2

  • ns2.sedoparking.com
  • ns1.sedoparking.com

SOA 1

  • ns1.sedoparking.com hostmaster.sedo.de

TLS Certificates (2)

Common NameIssuerExpires
zithromax.cyou C=US, O=DigiCert Inc, 2.5.4.11=www.digicert.com, CN=Encryption Everywhere DV TLS CA - G2 Sun, 09 Aug 2026 23:59:59 +0000
Encryption Everywhere DV TLS CA - G2 C=US, O=DigiCert Inc, 2.5.4.11=www.digicert.com, CN=DigiCert Global Root G2 Sat, 27 Nov 2027 12:46:40 +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_4033a54d70b92e79
Output Hash
33f41c6b845ad651ea67d78dbca593c62fc39b99ce32d4a293ea2442312d0da8
Signature
ed25519:f15309159dbdf1c41d1acff4be1f68636f1fc2ce856ccda1670a476acdb1e8bcc25054c264d0c9f4231d32a438dc1ecc6023f10640ab98b830e495434530be0e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser