CONTINUOUS INTERNET TELEMETRY24H DRIFT7,850 material changesacross 7,302 domains · 24h to ~3h ago · -913 vs yesterdayNOW560 curated domains not reachablelast probe, steadySITE ERRORS34,304 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,289 sites429 rate-limit / 403 bot-block, a posture signalMOVERokta.comNo mail routes in the latest observation

van-essen.nl

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

This reading of van-essen.nl was taken 1d ago

van-essen.nl is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting van-essen.nl 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 van-essen.nl 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-02 08:07 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 van-essen.nl actually stands on - every host below is a signed observation
van-essen.nl
A / AAAA
31.7.2.151
unattributedserves the site
NS
ns1.oxilion.nlns2.oxilion.nlns3.oxilion.net
oxilion.nl + oxilion.netanswers its DNS
MX
mx1.mail-scanner.eumx2.mail-scanner.eu
mail-scanner.eureceives its email
TLS
van-essen.nl
Let's Encryptissued its certificate

DNS Records

A 1

  • 31.7.2.151

MX 2

  • 10mx1.mail-scanner.eu
  • 20mx2.mail-scanner.eu

TXT 2

  • google-site-verification=cuzKnrtylc4bo1HAj3NAu5-LBlTEZhuhihGc4AYMfGo
  • v=spf1 a mx include:_spf.shockmedia.nl a:SMTP.mail3000.nl include:spf.antispamcloud.com ~all

NS 3

  • ns1.oxilion.nl
  • ns2.oxilion.nl
  • ns3.oxilion.net

SOA 1

  • ns1.oxilion.nl postmaster.oxilion.nl

MCP_RECORDS 2

  • google-site-verification=cuzKnrtylc4bo1HAj3NAu5-LBlTEZhuhihGc4AYMfGo
  • v=spf1 a mx include:_spf.shockmedia.nl a:SMTP.mail3000.nl include:spf.antispamcloud.com ~all

DMARC_RECORDS 2

  • google-site-verification=cuzKnrtylc4bo1HAj3NAu5-LBlTEZhuhihGc4AYMfGo
  • v=spf1 a mx include:_spf.shockmedia.nl a:SMTP.mail3000.nl include:spf.antispamcloud.com ~all

BIMI_RECORDS 2

  • google-site-verification=cuzKnrtylc4bo1HAj3NAu5-LBlTEZhuhihGc4AYMfGo
  • v=spf1 a mx include:_spf.shockmedia.nl a:SMTP.mail3000.nl include:spf.antispamcloud.com ~all

MTA_STS_RECORDS 2

  • google-site-verification=cuzKnrtylc4bo1HAj3NAu5-LBlTEZhuhihGc4AYMfGo
  • v=spf1 a mx include:_spf.shockmedia.nl a:SMTP.mail3000.nl include:spf.antispamcloud.com ~all

TLS Certificates (4)

Common NameIssuerExpires
van-essen.nl C=US, O=Let's Encrypt, CN=YE2 Fri, 18 Sep 2026 15:31:24 +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; nothing leaves your machine.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_f69b9f3f964e678d
Output Hash
33dd47b311e3f0eb908afb9fc51170d6fe9f5a97e17331a98afeda717b6e2c86
Signature
ed25519:08f0737f186989c3a173db6b3edf608257aa4760bfc9803a8135567940f7d5b488d3fa47369073888b3d6f0cd71446ee4ee2fb5ef71a7b640a532785887bc508
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser