CONTINUOUS INTERNET TELEMETRY24H DRIFT25,322 material changesacross 24,507 domains · 24h to ~14h ago · -12,700 vs yesterdayROTATION55 domains moved DNS from kirklanddc.com to koaladns.com, 51 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW563 curated domains not reachable+32 vs yesterdaySITE ERRORS33,717 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,858 sites429 rate-limit / 403 bot-block, a posture signal

lem.pl

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

This reading of lem.pl was taken 5d ago

lem.pl is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting lem.pl 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 lem.pl Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
1 subdomain · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-06 19:04 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 lem.pl actually stands on - every host below is a signed observation
lem.pl
A / AAAA
109.95.156.7
unattributedserves the site
NS
ns1.dhosting.plns2.dhosting.pl
dhosting.planswers its DNS
MX
mx-1.dpoczta.plmx-2.dpoczta.pl
dpoczta.plreceives its email
TLS
lem.pl
Let's Encryptissued its certificate

DNS Records

A 1

  • 109.95.156.7

MX 2

  • 10mx-1.dpoczta.pl
  • 10mx-2.dpoczta.pl

TXT 1

  • v=spf1 include:_mail.dhosting.pl -all

NS 2

  • ns1.dhosting.pl
  • ns2.dhosting.pl

SOA 1

  • ns1.dhosting.pl root.lem.pl

SRV 1

  • dpoczta.pl:443 p0

MCP_RECORDS 1

  • v=spf1 include:_mail.dhosting.pl -all

DMARC_RECORDS 1

  • v=DMARC1; p=none; sp=none; rua=mailto:dmarc-raports@dhosting.pl

BIMI_RECORDS 1

  • v=spf1 include:_mail.dhosting.pl -all

MTA_STS_RECORDS 1

  • v=spf1 include:_mail.dhosting.pl -all

TLS Certificates (6)

Common NameIssuerExpires
lem.pl C=US, O=Let's Encrypt, CN=YR2 Mon, 21 Sep 2026 01:22:52 +0000
R12 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Fri, 12 Mar 2027 23:59:59 +0000
R13 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Fri, 12 Mar 2027 23:59:59 +0000
YR1 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
YR2 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000

Subdomains (1)

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_0fffc672aea22ec2
Output Hash
6c750d9f75d40376e43e49a5b048c55e904b5716d51bdbc56d7b13a92a2d786f
Signature
ed25519:cf4e53d117464d70f297db3e44e337bf1c331d8f3fdaa539e46fd4e45413d98b72886ee7059ff5e259ddd67fa0ac8fc5d4caca549b53f4404ce5d1eb98d89e08
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser