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

lante.eu

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

This reading of lante.eu was taken 6d ago

lante.eu is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lante.eu 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 lante.eu 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.
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 17:11 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 lante.eu actually stands on - every host below is a signed observation
lante.eu
A / AAAA
77.55.131.44
unattributedserves the site
NS
dns3.home.pldns.home.pldns2.home.pl
home.planswers its DNS
MX
serwer1860768.home.pl
home.plreceives its email

DNS Records

A 1

  • 77.55.131.44

MX 1

  • 10serwer1860768.home.pl

TXT 1

  • v=spf1 mx a ptr ~all

NS 3

  • dns3.home.pl
  • dns.home.pl
  • dns2.home.pl

SOA 1

  • dns.home.pl admin.home.pl

SRV 2

  • lante.eu:993 p10
  • lante.eu:587 p10

MCP_RECORDS 1

  • v=spf1 mx a ptr ~all

DMARC_RECORDS 1

  • v=spf1 mx a ptr ~all

BIMI_RECORDS 1

  • v=spf1 mx a ptr ~all

MTA_STS_RECORDS 1

  • v=spf1 mx a ptr ~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_6abf68cb308a9bbb
Output Hash
6c338d54a6d8bf84731bdb45d2f4829514d6ac2fe7ffe2e83a42221c95f5ea94
Signature
ed25519:ad496a7226bc923bcd775df1a1eb4767959d59853df2954b080bb83ee6a4cab5d5996b6d0f8418ce05edeab7ddeb32a6b904bee4efa242b73e767072abdf6500
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser