CONTINUOUS INTERNET TELEMETRY24H DRIFT64,140 material changesacross 60,105 domains · last 24h · +29,523 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW537 curated domains not reachablelast probe, steadySITE ERRORS33,826 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 133,434 sites429 rate-limit / 403 bot-block, a posture signal

zapisyterroru.pl

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

This reading of zapisyterroru.pl was taken 3d ago

zapisyterroru.pl is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zapisyterroru.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 zapisyterroru.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-05 02:13 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 zapisyterroru.pl actually stands on - every host below is a signed observation
zapisyterroru.pl
A / AAAA
150.254.186.36
unattributedserves the site
NS
dns.home.pldns2.home.pldns3.home.pl
home.planswers its DNS
MX
serwer1670890.home.pl
home.plreceives its email
TLS
zapisyterroru.pl
Let's Encryptissued its certificate

DNS Records

A 1

  • 150.254.186.36

MX 1

  • 10serwer1670890.home.pl

TXT 1

  • v=spf1 a mx ~all

NS 3

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

SOA 1

  • dns.home.pl admin.home.pl

MCP_RECORDS 1

  • v=spf1 a mx ~all

DMARC_RECORDS 1

  • v=spf1 a mx ~all

BIMI_RECORDS 1

  • v=spf1 a mx ~all

MTA_STS_RECORDS 1

  • v=spf1 a mx ~all

TLS Certificates (2)

Common NameIssuerExpires
zapisyterroru.pl C=US, O=Let's Encrypt, CN=E7 Tue, 25 Aug 2026 10:12:35 +0000
E7 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Fri, 12 Mar 2027 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_70b7242565609d66
Output Hash
f87d31c27a44f1e0566947d7aba025c6ea651f4191725d22f3fee31c0564bfd3
Signature
ed25519:598ed661583711247dbe2aef0d5105a14cadd9cbd3b0d9b58446bca8871cd30cb7b46d77d53b01ba1b02b5d6a0855379ab08e8ee7064a7b20974e55ad42a1608
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser