CONTINUOUS INTERNET TELEMETRY24H DRIFT41,157 material changesacross 39,647 domains · 24h to ~7h ago · -20,919 vs yesterdayROTATION57 domains moved DNS from kirklanddc.com to koaladns.com, 54 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW532 curated domains not reachablelast probe, steadySITE ERRORS33,882 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,231 sites429 rate-limit / 403 bot-block, a posture signal

lg-3232.com

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

This reading of lg-3232.com was taken 3d ago

lg-3232.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lg-3232.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 lg-3232.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
Secured byLet's Encrypt
Registered withOldTownDomains.com LLC
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 07:34 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 lg-3232.com actually stands on - every host below is a signed observation
lg-3232.com
A / AAAA
103.224.182.213
unattributedserves the site
NS
ns15.abovedomains.comns16.abovedomains.com
abovedomains.comanswers its DNS
MX
park-mx.above.com
above.comreceives its email
TLS
lg-3232.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 103.224.182.213

MX 1

  • 10park-mx.above.com

TXT 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

NS 2

  • ns15.abovedomains.com
  • ns16.abovedomains.com

SOA 1

  • ns1.abovedomains.com hostmaster.trellian.com

MCP_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

DMARC_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

BIMI_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

MTA_STS_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -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_db324b18eae529a0
Output Hash
092af23d66d41cae884e8a57b5881cde3ca947e427ab79ec1914008a2f0d5067
Signature
ed25519:0eb7c17ccecfe6ae223cb8d8737f0430d5f7e6eeca95f5093bc23e5f74c9413cc81b388d14ca0c59480715657483084b4e7f608099294d1cb758622eeec96a0e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser