CONTINUOUS INTERNET TELEMETRY24H DRIFTat least 64,140 material changesacross 60,105+ domains · last 24h · a floor, 24h of 24 walkedROTATION56 domains moved DNS from magpiedns.com to koaladns.com, 56 moved backa rotation loop, not a migration · 24hNOW537 curated domains not reachablelast probe, steadySITE ERRORS33,826 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 133,434 sites429 rate-limit / 403 bot-block, a posture signal

yeezy-slides.org

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

This reading of yeezy-slides.org was taken 3d ago

yeezy-slides.org is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting yeezy-slides.org 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 yeezy-slides.org Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Signed observation on record.
Also usesGoogle Search Console
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 11:33 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 yeezy-slides.org actually stands on - every host below is a signed observation
yeezy-slides.org
A / AAAA
103.224.182.250
unattributedserves the site
NS
ns1.abovedomains.comns2.abovedomains.com
abovedomains.comanswers its DNS
TLS
ancfxlmrxvirexeirafp.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 103.224.182.250

TXT 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

NS 2

  • ns1.abovedomains.com
  • ns2.abovedomains.com

SOA 1

  • ns1.abovedomains.com hostmaster.trellian.com

MCP_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

DMARC_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

BIMI_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

MTA_STS_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

TLS Certificates (3)

Common NameIssuerExpires
ancfxlmrxvirexeirafp.com C=US, O=Let's Encrypt, CN=YR2 Tue, 27 Oct 2026 12:57:15 +0000
YR2 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR 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_c4bdf121b79ec4d9
Output Hash
f64b144a759561703394442cbbca4d0e7f8cfe484c5efa74ddcc81fb99b310e6
Signature
ed25519:79b58788a449d70f9584d76ec712de7ae412c70fad0d19c643584b0d7ea2991de8ee038c3fdb3ca5a6d434412a09395f561a57c2341adb808e9ad319be271502
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser