CONTINUOUS INTERNET TELEMETRY24H DRIFT25,547 material changesacross 22,819 domains · 24h to ~35m agoROTATION56 domains moved DNS from koaladns.com to kirklanddc.com, 55 moved backa rotation loop, not a migration · 24hEMAIL DRIFT1 domain switched email providertop destination ~NOW605 curated domains not reachablelast probe, steadySITE ERRORS33,530 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,011 sites429 rate-limit / 403 bot-block, a posture signal

lidasogram.xyz

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

This reading of lidasogram.xyz was taken 5d ago

lidasogram.xyz is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lidasogram.xyz 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 lidasogram.xyz Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byGoDaddy.com
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 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 lidasogram.xyz actually stands on - every host below is a signed observation
lidasogram.xyz
A / AAAA
13.248.169.4876.223.54.146
unattributedserves the site
NS
ns5.afternic.comns6.afternic.com
afternic.comanswers its DNS
TLS
lidasogram.xyz
GoDaddy.comissued its certificate

DNS Records

A 2

  • 13.248.169.48
  • 76.223.54.146

MX 1

  • 0

TXT 1

  • v=spf1 -all

NS 2

  • ns5.afternic.com
  • ns6.afternic.com

SOA 1

  • ns5.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 (3)

Common NameIssuerExpires
lidasogram.xyz C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., 2.5.4.11=http://certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2 Sun, 09 Aug 2026 06:28:56 +0000
Go Daddy Secure Certificate Authority - G2 C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Sat, 03 May 2031 07:00:00 +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_113c191227ab4da7
Output Hash
8548f5f4e9b1144ba925640dc58d2826beded75103d988b5480f5c5f77365cfe
Signature
ed25519:a7644e77e78db4af5b3257762423c3053fad2231092c33cf08b4fb7e3fe10f9c92494af3f1cc7dda08b5e4c13067b5b8434056a1ff5ec54a85709d515a178d0e
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser