CONTINUOUS INTERNET TELEMETRY24H DRIFT41,685 material changesacross 38,305 domains · 24h to ~2h ago · +7,068 vs yesterdaySHIFT42 domains moved DNS from koaladns.com to magpiedns.coma coordinated move · 24hNOW539 curated domains not reachablelast probe, steadySITE ERRORS33,856 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 149,215 sites429 rate-limit / 403 bot-block, a posture signal

urzekajaca.pl

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

This reading of urzekajaca.pl was taken 3d ago

urzekajaca.pl is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting urzekajaca.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 urzekajaca.pl Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Guarded by a firewall
Runs onCloudflare
Secured byhome.pl S.A.
Also usesGoogle Search Console
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:33 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 urzekajaca.pl actually stands on - every host below is a signed observation
urzekajaca.pl
A / AAAA
89.161.202.137
Cloudflareserves the site
NS
dns.home.pldns2.home.pldns3.home.pl
home.planswers its DNS
MX
urzekajaca.pl
urzekajaca.plreceives its email
TLS
*.urzekajaca.pl
home.pl S.A.issued its certificate

DNS Records

A 1

  • 89.161.202.137

MX 1

  • 10urzekajaca.pl

TXT 3

  • lh.pl
  • google-site-verification=TohoyRfWjCfjH7vCX1nFHzM0bTZxWaM8vjzMHW8_DTc
  • v=spf1 mx a ptr ~all

NS 3

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

SOA 1

  • dns.home.pl admin.home.pl

MCP_RECORDS 3

  • google-site-verification=TohoyRfWjCfjH7vCX1nFHzM0bTZxWaM8vjzMHW8_DTc
  • lh.pl
  • v=spf1 mx a ptr ~all

DMARC_RECORDS 1

  • v=DMARC1; p=none;

BIMI_RECORDS 3

  • google-site-verification=TohoyRfWjCfjH7vCX1nFHzM0bTZxWaM8vjzMHW8_DTc
  • v=spf1 mx a ptr ~all
  • lh.pl

MTA_STS_RECORDS 3

  • lh.pl
  • google-site-verification=TohoyRfWjCfjH7vCX1nFHzM0bTZxWaM8vjzMHW8_DTc
  • v=spf1 mx a ptr ~all

TLS Certificates (4)

Common NameIssuerExpires
*.urzekajaca.pl C=PL, O=home.pl S.A., CN=home pl DV TLS G2 R35 CA Thu, 24 Sep 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 (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_e9dfdfc7fb49e7ac
Output Hash
965a705a5b7157d6706d5f491278ae9ce1ee7530aba83b92fe525005aa117774
Signature
ed25519:3acc8cc4f1df3bf57f85a1d73700bb4134239c5f797fdba576c3d2634b185c691ceeffeee091ff85ac135c1332a7735d4cc1904b2882dd702773c0fb8727b703
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser