CONTINUOUS INTERNET TELEMETRY24H DRIFT37,653 material changesacross 34,127 domains · 24h to ~25m agoDNS DRIFT55 domains changed DNS providertop destination koaladns.com · +33 vs yesterdayNOW556 curated domains not reachablelast probe, steadySITE ERRORS33,351 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,386 sites429 rate-limit / 403 bot-block, a posture signal

vhu.sk

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

This reading of vhu.sk was taken 2d ago

vhu.sk is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting vhu.sk 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 vhu.sk Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Secured byLet's Encrypt
Also usesGoogle Search Console
1 subdomain · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 12:10 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 vhu.sk actually stands on - every host below is a signed observation
vhu.sk
A / AAAA
93.184.79.35
unattributedserves the site
NS
ns.forpsi.czns.forpsi.itns.forpsi.net
forpsi.cz + forpsi.it + moreanswers its DNS
MX
jason.aglo.eu
aglo.eureceives its email
TLS
vhu.sk
Let's Encryptissued its certificate

DNS Records

A 1

  • 93.184.79.35

MX 1

  • 10jason.aglo.eu

TXT 2

  • v=spf1 ptr:aglo.eu -all
  • google-site-verification=en8yhbu6-huSKp73rjV9KtVr1ixzREl7ba-YIe690Qc

NS 3

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

SOA 1

  • ns.forpsi.net admin.forpsi.com

MCP_RECORDS 2

  • v=spf1 ptr:aglo.eu -all
  • google-site-verification=en8yhbu6-huSKp73rjV9KtVr1ixzREl7ba-YIe690Qc

DMARC_RECORDS 2

  • v=spf1 ptr:aglo.eu -all
  • google-site-verification=en8yhbu6-huSKp73rjV9KtVr1ixzREl7ba-YIe690Qc

BIMI_RECORDS 2

  • v=spf1 ptr:aglo.eu -all
  • google-site-verification=en8yhbu6-huSKp73rjV9KtVr1ixzREl7ba-YIe690Qc

MTA_STS_RECORDS 2

  • v=spf1 ptr:aglo.eu -all
  • google-site-verification=en8yhbu6-huSKp73rjV9KtVr1ixzREl7ba-YIe690Qc

TLS Certificates (3)

Common NameIssuerExpires
vhu.sk C=US, O=Let's Encrypt, CN=YR1 Fri, 02 Oct 2026 02:56:29 +0000
YR1 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 (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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_8e9ae395c2d0263a
Output Hash
abd132aece9e159c0ddb173fa8df84f4efb8d4591331e97c1d40eaa2a8953e09
Signature
ed25519:c6d43ef68239d4ee7b48de4b20420b94f0d036ce088f37fc64829ef5eae2ccb341a41a791d0f441dded2ebef63bdff86359c7de76499b795c9cb85ec1cecbf0c
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser