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

veterix.cz

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

This reading of veterix.cz was taken 3d ago

veterix.cz is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting veterix.cz 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 veterix.cz Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Email byGoogle Workspace
Also usesFacebook/MetaGoogle Search Console
IPv6 · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 22:39 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 veterix.cz actually stands on - every host below is a signed observation
veterix.cz
A / AAAA
95.168.219.1752a01:28:ca:107::1:175
2a01serves the site
NS
ns.forpsi.czns.forpsi.itns.forpsi.net
forpsi.cz + forpsi.it + moreanswers its DNS
MX
smtp.google.com
Google Workspacereceives its email
TLS
veterix.cz
Let's Encryptissued its certificate

DNS Records

A 1

  • 95.168.219.175

AAAA 1

  • 2a01:28:ca:107::1:175

MX 1

  • 1smtp.google.com

TXT 3

  • v=spf1 include:_spf.google.com ~all
  • facebook-domain-verification=1a66re18pq4h8qr7iq5u3tsq9cjp4b
  • google-site-verification=JDF-L6X9cXn4q_oomS8roN4SlrcGIwWrOqCIZL_e5-M

NS 3

  • ns.forpsi.cz
  • ns.forpsi.it
  • ns.forpsi.net

SOA 1

  • ns.forpsi.net admin.forpsi.com

MCP_RECORDS 3

  • v=spf1 include:_spf.google.com ~all
  • facebook-domain-verification=1a66re18pq4h8qr7iq5u3tsq9cjp4b
  • google-site-verification=JDF-L6X9cXn4q_oomS8roN4SlrcGIwWrOqCIZL_e5-M

DMARC_RECORDS 1

  • v=DMARC1; p=none; rua=mailto:admin@veterix.cz

BIMI_RECORDS 3

  • v=spf1 include:_spf.google.com ~all
  • facebook-domain-verification=1a66re18pq4h8qr7iq5u3tsq9cjp4b
  • google-site-verification=JDF-L6X9cXn4q_oomS8roN4SlrcGIwWrOqCIZL_e5-M

MTA_STS_RECORDS 3

  • v=spf1 include:_spf.google.com ~all
  • facebook-domain-verification=1a66re18pq4h8qr7iq5u3tsq9cjp4b
  • google-site-verification=JDF-L6X9cXn4q_oomS8roN4SlrcGIwWrOqCIZL_e5-M

TLS Certificates (4)

Common NameIssuerExpires
veterix.cz C=US, O=Let's Encrypt, CN=YE1 Sat, 10 Oct 2026 00:09:04 +0000
YE1 C=US, O=ISRG, CN=Root YE Sat, 02 Sep 2028 23:59:59 +0000
Root YE C=US, O=Internet Security Research Group, CN=ISRG Root X2 Thu, 02 Sep 2032 23:59:59 +0000
ISRG Root X2 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +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_d15088c43c5ed817
Output Hash
2a08767312f9bd835b10c1eb7afd6ab4c02d07d4ed3aa0a84d122d71fb9bc01a
Signature
ed25519:be9d8870128bd7eb902c4d0c6ef73dff06cad04d92998310aa9c599fff7cef6920166a4b402f323f3bfd2d171886cc93f51ae1a9a62b44651251c5ad8cf99009
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser