CONTINUOUS INTERNET TELEMETRY24H DRIFT27,060 material changesacross 26,158 domains · 24h to ~14h ago · -10,962 vs yesterdayROTATION57 domains moved DNS from kirklanddc.com to koaladns.com, 51 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW562 curated domains not reachable+31 vs yesterdaySITE ERRORS33,728 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,775 sites429 rate-limit / 403 bot-block, a posture signal

leadlander.com

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

This reading of leadlander.com was taken 4d ago

leadlander.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting leadlander.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 leadlander.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Up right now
Email byGoogle Workspace
Secured byAmazon
Also usesGoogle Search ConsoleHubSpot
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 14:19 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 leadlander.com actually stands on - every host below is a signed observation
leadlander.com
A / AAAA
184.73.33.7534.199.162.92
unattributedserves the site
NS
ns-1527.awsdns-62.orgns-1787.awsdns-31.co.ukns-269.awsdns-33.comns-546.awsdns-04.net
awsdns-62.org + awsdns-31.co.uk + moreanswers its DNS
MX
aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comalt1.aspmx.l.google.com+1 more
Google Workspacereceives its email
TLS
*.leadlander.com
Amazonissued its certificate

DNS Records

A 2

  • 184.73.33.75
  • 34.199.162.92

MX 5

  • 1aspmx.l.google.com
  • 10alt3.aspmx.l.google.com
  • 10alt4.aspmx.l.google.com
  • 5alt1.aspmx.l.google.com
  • 5alt2.aspmx.l.google.com

TXT 4

  • google-site-verification=Hs9YY18erNXk6uojqXUedDQ6CkcJpDbsWXffACbJ9zY
  • google-site-verification=ctmoYr8SUVPoNto5kLpn0qYOfWTULAj3rOmjw9JAV8w
  • hubspot-developer-verification=NTEyNmMxMjItYmFjOC00YmQzLWExMGUtOTNiMjZlNjkzMWM4
  • v=spf1 ip4:66.151.25.0/24 include:_spf.google.com include:sendgrid.net ip4:34.231.124.222/32 -all

NS 4

  • ns-1527.awsdns-62.org
  • ns-1787.awsdns-31.co.uk
  • ns-269.awsdns-33.com
  • ns-546.awsdns-04.net

SOA 1

  • ns-1787.awsdns-31.co.uk awsdns-hostmaster.amazon.com

MCP_RECORDS 4

  • google-site-verification=Hs9YY18erNXk6uojqXUedDQ6CkcJpDbsWXffACbJ9zY
  • google-site-verification=ctmoYr8SUVPoNto5kLpn0qYOfWTULAj3rOmjw9JAV8w
  • hubspot-developer-verification=NTEyNmMxMjItYmFjOC00YmQzLWExMGUtOTNiMjZlNjkzMWM4
  • v=spf1 ip4:66.151.25.0/24 include:_spf.google.com include:sendgrid.net ip4:34.231.124.222/32 -all

DMARC_RECORDS 1

  • v=DMARC1; p=none; rua=mailto:dmarc@leadlander.com,mailto:33a91480@mxtoolbox.dmarc-report.com; ruf=mailto:dmarc@leadlander.com,mailto:33a91480@forensics.dmarc-report.com; fo=1

BIMI_RECORDS 4

  • google-site-verification=Hs9YY18erNXk6uojqXUedDQ6CkcJpDbsWXffACbJ9zY
  • google-site-verification=ctmoYr8SUVPoNto5kLpn0qYOfWTULAj3rOmjw9JAV8w
  • hubspot-developer-verification=NTEyNmMxMjItYmFjOC00YmQzLWExMGUtOTNiMjZlNjkzMWM4
  • v=spf1 ip4:66.151.25.0/24 include:_spf.google.com include:sendgrid.net ip4:34.231.124.222/32 -all

MTA_STS_RECORDS 4

  • google-site-verification=Hs9YY18erNXk6uojqXUedDQ6CkcJpDbsWXffACbJ9zY
  • google-site-verification=ctmoYr8SUVPoNto5kLpn0qYOfWTULAj3rOmjw9JAV8w
  • hubspot-developer-verification=NTEyNmMxMjItYmFjOC00YmQzLWExMGUtOTNiMjZlNjkzMWM4
  • v=spf1 ip4:66.151.25.0/24 include:_spf.google.com include:sendgrid.net ip4:34.231.124.222/32 -all

TLS Certificates (3)

Common NameIssuerExpires
*.leadlander.com C=US, O=Amazon, CN=Amazon RSA 2048 M01 Mon, 01 Mar 2027 23:59:59 +0000
Amazon RSA 2048 M01 C=US, O=Amazon, CN=Amazon Root CA 1 Fri, 23 Aug 2030 22:21:28 +0000
Amazon Root CA 1 C=US, ST=Arizona, L=Scottsdale, O=Starfield Technologies, Inc., CN=Starfield Services Root Certificate Authority - G2 Thu, 31 Dec 2037 01:00:00 +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_146dc466628b9de4
Output Hash
4fa0646577815c3246a8e2a67be08614d894b359283d10393cb875674448e2fa
Signature
ed25519:1fb6913c6d78743214bde8a62704a5064d8446c4088fd052178140ff49d21dc8c4bccfdd8db940eca4b0a165a3bff9e4bd60ca318c9ce615f8fe61afaf169d09
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser