CONTINUOUS INTERNET TELEMETRY24H DRIFT38,088 material changesacross 34,280 domains · 24h to ~45m agoDNS DRIFT52 domains changed DNS providertop destination koaladns.com · +30 vs yesterdayNOW543 curated domains not reachablelast probe, steadySITE ERRORS33,703 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 157,225 sites429 rate-limit / 403 bot-block, a posture signal

zaglebie.org

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

This reading of zaglebie.org was taken 2d ago

zaglebie.org is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zaglebie.org 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 zaglebie.org Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
2 subdomains · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 17:24 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 zaglebie.org actually stands on - every host below is a signed observation
zaglebie.org
A / AAAA
188.210.221.84
unattributedserves the site
NS
ns05.domaincontrol.comns06.domaincontrol.com
domaincontrol.comanswers its DNS
MX
mail.zaglebie.org
zaglebie.orgreceives its email
TLS
mail.zaglebie.org
Let's Encryptissued its certificate

DNS Records

A 1

  • 188.210.221.84

MX 1

  • 1mail.zaglebie.org

TXT 2

  • v=spf1 redirect=_spf-h24.microhost.pl
  • D1423036

NS 2

  • ns05.domaincontrol.com
  • ns06.domaincontrol.com

SOA 1

  • ns05.domaincontrol.com dns.jomax.net

MCP_RECORDS 2

  • v=spf1 redirect=_spf-h24.microhost.pl
  • D1423036

DMARC_RECORDS 1

  • v=DMARC1; p=none; sp=none; rua=mailto:spam-reports@microhost.pl

BIMI_RECORDS 2

  • v=spf1 redirect=_spf-h24.microhost.pl
  • D1423036

MTA_STS_RECORDS 2

  • v=spf1 redirect=_spf-h24.microhost.pl
  • D1423036

TLS Certificates (2)

Common NameIssuerExpires
mail.zaglebie.org C=US, O=Let's Encrypt, CN=E8 Mon, 24 Aug 2026 06:44:12 +0000
E8 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Fri, 12 Mar 2027 23:59:59 +0000

Subdomains (2)

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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_709bd863bc16142a
Output Hash
056e7d60e68f7061a38e2adaa4fa66d1efcb5849171647ed12527fb4e82b68d7
Signature
ed25519:a10c8f384c7939fabf158bbe69993f376a6918896d35fb617bf20faa24117ca047f919c35746bd97b3bb8d0109870c955062a40967b2695c30f351bef901a702
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser