CONTINUOUS INTERNET TELEMETRY24H DRIFT33,450 material changesacross 32,285 domains · 24h to ~10h ago · -4,572 vs yesterdayROTATION56 domains moved DNS from kirklanddc.com to koaladns.com, 53 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW549 curated domains not reachablelast probe, steadySITE ERRORS33,824 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,662 sites429 rate-limit / 403 bot-block, a posture signal

zaltoglas.at

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

This reading of zaltoglas.at was taken 4d ago

zaltoglas.at is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting zaltoglas.at 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 zaltoglas.at Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
8 subdomains · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-07 00: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 zaltoglas.at actually stands on - every host below is a signed observation
zaltoglas.at
A / AAAA
92.205.173.215
unattributedserves the site
NS
ns39.domaincontrol.comns40.domaincontrol.com
domaincontrol.comanswers its DNS
MX
mx1.bon.at
bon.atreceives its email
TLS
webmail.zaltoglas.at
Let's Encryptissued its certificate

DNS Records

A 1

  • 92.205.173.215

MX 1

  • 10mx1.bon.at

TXT 1

  • v=spf1 include:bspf.a1.net include:secureserver.net ~all

NS 2

  • ns39.domaincontrol.com
  • ns40.domaincontrol.com

SOA 1

  • ns39.domaincontrol.com dns.jomax.net

MCP_RECORDS 1

  • v=spf1 include:bspf.a1.net include:secureserver.net ~all

DMARC_RECORDS 1

  • v=DMARC1; p=none; fo=1;

BIMI_RECORDS 1

  • v=spf1 include:bspf.a1.net include:secureserver.net ~all

MTA_STS_RECORDS 1

  • v=spf1 include:bspf.a1.net include:secureserver.net ~all

TLS Certificates (3)

Common NameIssuerExpires
webmail.zaltoglas.at C=US, O=Let's Encrypt, CN=YR2 Wed, 30 Sep 2026 03:37:35 +0000
YR2 C=US, O=ISRG, CN=Root YR Sat, 02 Sep 2028 23:59:59 +0000
Root YR C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (8)

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_3230e9db4374a254
Output Hash
e1ebd29cd6314569c3854bb47b011be0cd78462e07f2e46ccc1a240d226a1ae8
Signature
ed25519:414291d8aef90953e2225657a6d0a7cdb1c4fdc39724f6d173bec5abf923a46ee8ef2dadab3a2bed12b291ad0daa5cb12f1cff299ee71ec330d408414d4dab0a
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser