CONTINUOUS INTERNET TELEMETRY24H DRIFT48,244 material changesacross 46,548 domains · 24h to ~6h ago · +13,627 vs yesterdayROTATION56 domains moved DNS from magpiedns.com to koaladns.com, 56 moved backa rotation loop, not a migration · 24hNOW536 curated domains not reachablelast probe, steadySITE ERRORS33,814 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 134,598 sites429 rate-limit / 403 bot-block, a posture signal

yourlocalfling.com

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

This reading of yourlocalfling.com was taken 3d ago

yourlocalfling.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting yourlocalfling.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 yourlocalfling.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byGoogle Trust Services
4 subdomains · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 21:00 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 yourlocalfling.com actually stands on - every host below is a signed observation
yourlocalfling.com
A / AAAA
34.111.186.84
unattributedserves the site
NS
ns1.dnsimple-edge.comns2.dnsimple-edge.netns3.dnsimple-edge.ions4.dnsimple-edge.org
dnsimple-edge.com + dnsimple-edge.net + moreanswers its DNS
MX
mx1.smashtic.com
smashtic.comreceives its email
TLS
yourlocalfling.com
Google Trust Servicesissued its certificate

DNS Records

A 1

  • 34.111.186.84

MX 1

  • 10mx1.smashtic.com

TXT 2

  • v=spf1 include:136224628.spf2.netcorecloud.net include:spf.smashtic.com -all
  • yahoo-verification-key=RUSKtHFthv23i9jSBa7//HnXDBhMBu+d3Fy4gyPW2KU=

NS 4

  • ns1.dnsimple-edge.com
  • ns2.dnsimple-edge.net
  • ns3.dnsimple-edge.io
  • ns4.dnsimple-edge.org

SOA 1

  • ns1.dnsimple-edge.com admin.dnsimple.com

MCP_RECORDS 2

  • v=spf1 include:136224628.spf2.netcorecloud.net include:spf.smashtic.com -all
  • yahoo-verification-key=RUSKtHFthv23i9jSBa7//HnXDBhMBu+d3Fy4gyPW2KU=

DMARC_RECORDS 1

  • v=DMARC1; p=reject; sp=reject; pct=100; fo=1; ri=3600; rua=mailto:dmarcrecord@gmail.com; ruf=mailto:dmarcrecord@gmail.com;

BIMI_RECORDS 2

  • v=spf1 include:136224628.spf2.netcorecloud.net include:spf.smashtic.com -all
  • yahoo-verification-key=RUSKtHFthv23i9jSBa7//HnXDBhMBu+d3Fy4gyPW2KU=

MTA_STS_RECORDS 2

  • v=spf1 include:136224628.spf2.netcorecloud.net include:spf.smashtic.com -all
  • yahoo-verification-key=RUSKtHFthv23i9jSBa7//HnXDBhMBu+d3Fy4gyPW2KU=

TLS Certificates (3)

Common NameIssuerExpires
yourlocalfling.com C=US, O=Google Trust Services, CN=WR3 Mon, 12 Oct 2026 02:17:09 +0000
WR3 C=US, O=Google Trust Services LLC, CN=GTS Root R1 Tue, 20 Feb 2029 14:00:00 +0000
GTS Root R1 C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA Fri, 28 Jan 2028 00:00:42 +0000

Subdomains (4)

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_be1c536bb3a8c006
Output Hash
5634e8bfd91eabf28bfe6219b47d1a8a137315e2fd0f4ecc9e8785376c343573
Signature
ed25519:720ca5e7dc31e93d16cf010bcc4deee0882427810dbcb0b5660c0b6e28a7828c26cfd6f5772f470d362de43333edb8dd52d3f62e73dab6fcee93befbda80da08
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser