CONTINUOUS INTERNET TELEMETRY24H DRIFT34,698 material changesacross 32,925 domains · 24h to ~3h agoROTATION55 domains moved DNS from koaladns.com to kirklanddc.com, 50 moved backa rotation loop, not a migration · 24hNOW594 curated domains not reachablelast probe, steadySITE ERRORS33,540 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,506 sites429 rate-limit / 403 bot-block, a posture signal

lissa.fr

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

This reading of lissa.fr was taken 5d ago

lissa.fr is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lissa.fr 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 lissa.fr 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
Signed observation on record.
IPv6 · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 06:49 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 lissa.fr actually stands on - every host below is a signed observation
lissa.fr
A / AAAA
152.89.172.5681.92.95.5581.92.94.542a01:c8:100::54+2 more
2a01 + 2a09serves the site
NS
nsb.perf1.comnsa.perf1.frnsc.perf1.com
perf1.com + perf1.franswers its DNS

DNS Records

A 3

  • 152.89.172.56
  • 81.92.95.55
  • 81.92.94.54

AAAA 3

  • 2a01:c8:100::54
  • 2a09:35c0:102::56
  • 2a01:c8:101::55

TXT 1

  • v=spf1 -all

NS 3

  • nsb.perf1.com
  • nsa.perf1.fr
  • nsc.perf1.com

SOA 1

  • nsa.perf1.fr technical.nameshield.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 (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_e9cb62a444a22ee2
Output Hash
3c72f54f29909137b72fd029bece2f4076bba4e078bfffc13cf5c9cbb1609480
Signature
ed25519:b100c8575508fea1dce317d8b880ced6a91c87f576eed265fc24a616dcbc4fb353bf6d9911b21223d17bc4da252c9f0b01e5c2fa7a8152feb67a47ebe1ab8d03
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser