CONTINUOUS INTERNET TELEMETRY24H DRIFT28,782 material changesacross 26,712 domains · last 24hROTATION56 domains moved DNS from koaladns.com to kirklanddc.com, 53 moved backa rotation loop, not a migration · 24hNOW598 curated domains not reachablelast probe, steadySITE ERRORS33,529 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 118,415 sites429 rate-limit / 403 bot-block, a posture signal

zkkm.pl

Observed Jul 25, 2026, 19:47 UTC (13d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of zkkm.pl was taken 13d ago

zkkm.pl is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zkkm.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 zkkm.pl Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byhome.pl S.A.
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-07 03:25 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 zkkm.pl actually stands on - every host below is a signed observation
zkkm.pl
A / AAAA
79.96.156.107
unattributedserves the site
NS
dns3.home.pldns2.home.pldns.home.pl
home.planswers its DNS
MX
zkkm.pl
zkkm.plreceives its email
TLS
zkkm.pl
home.pl S.A.issued its certificate

DNS Records

A 1

  • 79.96.156.107

MX 1

  • 10zkkm.pl

TXT 5

  • v=spf1 mx a ip4:79.96.156.107 -all
  • v=DMARC1; p=reject;rua=mailto:biuro@zkkm.pl
  • v=spf1 mx a ip4:79.96.156.107 -all
  • v=spf1 mx a ip4:79.96.156.107 -all
  • v=spf1 mx a ip4:79.96.156.107 -all

NS 3

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

SOA 1

  • dns.home.pl admin.home.pl

TLS Certificates (4)

Common NameIssuerExpires
zkkm.pl C=PL, O=home.pl S.A., CN=home pl DV TLS G2 R35 CA Fri, 02 Oct 2026 00:00:00 +0000
home pl DV TLS G2 R35 CA C=PL, O=Asseco Data Systems S.A., 2.5.4.11=Certum Certification Authority, CN=Certum Trusted Root CA Wed, 16 May 2035 07:45:35 +0000
Certum Trusted Root CA C=PL, O=Unizeto Technologies S.A., 2.5.4.11=Certum Certification Authority, CN=Certum Trusted Network CA Tue, 19 Sep 2028 10:00:00 +0000
Certum Trusted Network CA C=PL, O=Unizeto Technologies S.A., 2.5.4.11=Certum Certification Authority, CN=Certum Trusted Network CA Mon, 31 Dec 2029 12:07:37 +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_e9f0a0639f0041c0
Output Hash
60dbd55a674a812152a860e8706e8626ea3e190c31a260c058fd264e3dcaf50f
Signature
ed25519:1ef18cfc1f1fb7776b5f8f963cc5e272efce365416b54d4b7d17c455fe971e9d4adc23facdb362f4e32e7bc9f799a228190651935efec87c62fc61c4813d850b
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser