CONTINUOUS INTERNET TELEMETRY24H DRIFT23,583 material changesacross 21,757 domains · 24h to ~3h agoROTATION57 domains moved DNS from koaladns.com to kirklanddc.com, 56 moved backa rotation loop, not a migration · 24hEMAIL DRIFT1 domain switched email providertop destination ~NOW603 curated domains not reachablelast probe, steadySITE ERRORS33,520 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,157 sites429 rate-limit / 403 bot-block, a posture signal

lchclearnet.com

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

This reading of lchclearnet.com was taken 5d ago

lchclearnet.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lchclearnet.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 lchclearnet.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Not responding
Email byMimecast
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 22:25 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 lchclearnet.com actually stands on - every host below is a signed observation
lchclearnet.com
NS
kayleigh.ns.cloudflare.compiers.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
eu-smtp-inbound-1.mimecast.comeu-smtp-inbound-2.mimecast.com
Mimecastreceives its email

DNS Records

MX 2

  • 10eu-smtp-inbound-1.mimecast.com
  • 20eu-smtp-inbound-2.mimecast.com

TXT 5

  • MS=ms77252351
  • T0H0E12995
  • k2cOnpwGZyLFte6DzQ8DRLZjPHKRER2Fyhi0ZtXjUNpj83SF8/mnp3aoZoYepzwxV8Upw2K239Dqgnzc7/a3Rg==
  • v=spf1 ip4:205.132.94.50 ip4:205.132.94.51 include:eu._netblocks.mimecast.com include:spf.messagelabs.com -all
  • wxgl6lpf9pqynng3jxxsd4hlyp50r7vy

NS 2

  • kayleigh.ns.cloudflare.com
  • piers.ns.cloudflare.com

SOA 1

  • kayleigh.ns.cloudflare.com dns.cloudflare.com

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=DMARC1; p=reject; rua=mailto:rua@lseg.com; ruf=mailto:ruf@lseg.com; fo=1

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=spf1 -all

TLS Certificates (0)

None.

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_bc5ebcea88bbf4b5
Output Hash
2cb39490cd3d1b822560c9f78c3d134319a8a4ce0543ad9a16c6cbaf0a040cc8
Signature
ed25519:92b3030be96f1cd05847f97f54f6372d265c151807f422385583559b2713272972fc843f021e675595da8c212a292e393d92d05d2a6fcd3fb15417ea031b5305
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser