CONTINUOUS INTERNET TELEMETRY24H DRIFT43,836 material changesacross 42,208 domains · 24h to ~6h ago · -18,240 vs yesterdayROTATION55 domains moved DNS from kirklanddc.com to koaladns.com, 53 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW532 curated domains not reachablelast probe, steadySITE ERRORS33,888 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,377 sites429 rate-limit / 403 bot-block, a posture signal

leadoma.com

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

This reading of leadoma.com was taken 4d ago

leadoma.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting leadoma.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 leadoma.com 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-06 08:38 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 leadoma.com actually stands on - every host below is a signed observation
leadoma.com
A / AAAA
76.223.54.14613.248.169.48
unattributedserves the site
NS
ns1.afternic.comns2.afternic.com
afternic.comanswers its DNS
TLS
leadoma.com
GoDaddy.comissued its certificate

DNS Records

A 2

  • 76.223.54.146
  • 13.248.169.48

MX 1

  • 0

TXT 1

  • v=spf1 -all

NS 2

  • ns1.afternic.com
  • ns2.afternic.com

SOA 1

  • ns2.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
leadoma.com C=US, O=GoDaddy.com, CN=GoDaddy TLS Intermediate CA DV - R1v1 Thu, 28 Jan 2027 23:59:11 +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_0085a7edd8a0c207
Output Hash
0d81ccc20fecd55a724a0aada194f8f6d345144a345f516db30272fb2ffdc896
Signature
ed25519:fbd5b23afdcd2617fd59dbaf3afc45cb3c2c66e83507be81bc51d97fd1aadc5e53d02ccb4307e01b1f62a8b8f08c1bb8e28e4ac3b94660e14d7fb104fd8f530a
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser