letsgoeat.pl

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

This reading of letsgoeat.pl was taken 3d ago

letsgoeat.pl is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting letsgoeat.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 letsgoeat.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 · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-13 23:31 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 letsgoeat.pl actually stands on - every host below is a signed observation
letsgoeat.pl
A / AAAA
213.25.153.251
unattributedserves the site
NS
ns2.domeny.hostns1.domeny.host
domeny.hostanswers its DNS
MX
mx-1.letsgoeat.pl
letsgoeat.plreceives its email
TLS
letsgoeat.pl
Let's Encryptissued its certificate

DNS Records

A 1

  • 213.25.153.251

MX 1

  • 10mx-1.letsgoeat.pl

TXT 2

  • 39869e89ae0c748cf1702242101854e3742d5d12dff4992e16e6b414849a1b3
  • v=spf1 a mx include:spf.tld.pl -all

NS 2

  • ns2.domeny.host
  • ns1.domeny.host

SOA 1

  • ns1.domeny.host admin.domeny.host

MCP_RECORDS 1

  • v=spf1 a mx include:spf.tld.pl -all

DMARC_RECORDS 1

  • v=DMARC1; p=none; sp=none

BIMI_RECORDS 1

  • v=spf1 a mx include:spf.tld.pl -all

MTA_STS_RECORDS 1

  • v=spf1 a mx include:spf.tld.pl -all

TLS Certificates (4)

Common NameIssuerExpires
letsgoeat.pl C=US, O=Let's Encrypt, CN=YE2 Thu, 22 Oct 2026 15:12:48 +0000
YE2 C=US, O=ISRG, CN=Root YE Sat, 02 Sep 2028 23:59:59 +0000
Root YE C=US, O=Internet Security Research Group, CN=ISRG Root X2 Thu, 02 Sep 2032 23:59:59 +0000
ISRG Root X2 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 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_44593b0e8359c6a5
Output Hash
88a11cc6796ee8d35197d3220fbf6f1072b21cd8c9e8c5a89904ac0ae0a6e536
Signature
ed25519:40952f279666dbb8c28a2147b56fec8074201bcc8aa1aaeed5ba577102c5d7039a4775f819c09ff2b4486e1a437e9a22187807bc1024b5fb0786a9ab83b46f0f
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT47,493 material changesacross 45,291 domains · 24h to ~40m ago · +3,411 vs yesterdayROTATION58 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW492 curated domains not reachablelast probe, steadySITE ERRORS36,357 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 115,561 sites429 rate-limit / 403 bot-block, a posture signal