CONTINUOUS INTERNET TELEMETRY24H DRIFT48,392 material changesacross 43,424 domains · 24h to ~2h ago · +13,986 vs yesterdayROTATION55 domains moved DNS from koaladns.com to magpiedns.com, 53 moved backa rotation loop, not a migration · 24hNOW608 curated domains not reachablelast probe, steadySITE ERRORS34,173 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,832 sites429 rate-limit / 403 bot-block, a posture signal

dotfinder.xyz

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

This reading of dotfinder.xyz was taken 7d ago

dotfinder.xyz is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting dotfinder.xyz 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 dotfinder.xyz Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byGoDaddy.com
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-09 17:54 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 dotfinder.xyz actually stands on - every host below is a signed observation
dotfinder.xyz
A / AAAA
13.248.169.4876.223.54.146
unattributedserves the site
NS
ns5.afternic.comns6.afternic.com
afternic.comanswers its DNS
TLS
dotfinder.xyz
GoDaddy.comissued its certificate

DNS Records

A 2

  • 13.248.169.48
  • 76.223.54.146

MX 1

  • 0

TXT 1

  • v=spf1 -all

NS 2

  • ns5.afternic.com
  • ns6.afternic.com

SOA 1

  • ns5.afternic.com dns.jomax.net

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=spf1 -all

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=spf1 -all

TLS Certificates (4)

Common NameIssuerExpires
dotfinder.xyz C=US, O=GoDaddy.com, CN=GoDaddy TLS Intermediate CA DV - R1v1 Fri, 04 Dec 2026 07:36:19 +0000
GoDaddy TLS Intermediate CA DV - R1v1 C=US, O=GoDaddy.com, CN=GoDaddy TLS Root CA - R1 Fri, 24 Aug 2040 11:59:59 +0000
GoDaddy TLS Root CA - R1 C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Thu, 31 Dec 2037 23:59:59 +0000
Go Daddy Root Certificate Authority - G2 C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Thu, 31 Dec 2037 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_618a76aead9e5c18
Output Hash
a64f1653a27b857c0f034188308c2c71558086425707e1f9df55b2b09c9666f3
Signature
ed25519:7b8b412cececb17dad4a2fe15dc389849636fa7f0e363a07355a727a2c91c9724b211e39f483471d8c4e35774c87bcc4d5c1df8b0747dd1008890522b4924b01
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser