CONTINUOUS INTERNET TELEMETRY24H DRIFT68,088 material changesacross 64,935 domains · 24h to ~3h ago · +33,471 vs yesterdayROTATION56 domains moved DNS from koaladns.com to magpiedns.com, 56 moved backa rotation loop, not a migration · 24hNOW538 curated domains not reachablelast probe, steadySITE ERRORS33,857 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 123,111 sites429 rate-limit / 403 bot-block, a posture signal

vetais.com

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

This reading of vetais.com was taken 3d ago

vetais.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting vetais.com 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 vetais.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
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-05 12:17 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 vetais.com actually stands on - every host below is a signed observation
vetais.com
A / AAAA
5.200.54.125
unattributedserves the site
NS
ns.forpsi.czns.forpsi.itns.forpsi.usns.forpsi.net
forpsi.cz + forpsi.it + moreanswers its DNS
MX
vetais.com
vetais.comreceives its email
TLS
vetais.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 5.200.54.125

MX 1

  • 5vetais.com

TXT 1

  • v=msv1 t=5a93b3784ed04fa54932e82850ddd6

NS 4

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

SOA 1

  • ns.forpsi.net admin.forpsi.com

MCP_RECORDS 1

  • v=msv1 t=5a93b3784ed04fa54932e82850ddd6

DMARC_RECORDS 1

  • v=DMARC1; p=none

BIMI_RECORDS 1

  • v=msv1 t=5a93b3784ed04fa54932e82850ddd6

MTA_STS_RECORDS 1

  • v=msv1 t=5a93b3784ed04fa54932e82850ddd6

TLS Certificates (4)

Common NameIssuerExpires
vetais.com C=US, O=Let's Encrypt, CN=YE2 Tue, 29 Sep 2026 09:34:04 +0000
YE2 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 (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_d0282535839f31c2
Output Hash
acd4b2ce761f132e8be21616a79354d4fd98cbac9dd97c5e34d1fee226fdd5d2
Signature
ed25519:ea837d3c0c4655b02392905841851e4842a5fa7cbdb65a45f9a4a3309022e42183cd4a97fb053d74b81f454a96956ebfb98e1eb584d598ea3f1080a3904f0d0f
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser