CONTINUOUS INTERNET TELEMETRY24H DRIFT48,392 material changesacross 43,424 domains · 24h to ~2h ago · +13,986 vs yesterdayROTATION55 domains moved DNS from koaladns.com to magpiedns.com, 53 moved backa rotation loop, not a migration · 24hNOW611 curated domains not reachablelast probe, steadySITE ERRORS34,180 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,835 sites429 rate-limit / 403 bot-block, a posture signal

regiocanons.nl

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

This reading of regiocanons.nl was taken 7d ago

regiocanons.nl is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting regiocanons.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 regiocanons.nl Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Verify this receipt yourself + Watch this domain
Up right now
Secured byLet's Encrypt
IPv6 · 1 subdomain · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-09 07:33 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 regiocanons.nl actually stands on - every host below is a signed observation
regiocanons.nl
A / AAAA
83.98.140.232001:16f8:4::23
2001serves the site
NS
ns1.driebit.nlns2.driebit.nl
driebit.nlanswers its DNS
TLS
www.regiocanons.nl
Let's Encryptissued its certificate

DNS Records

A 1

  • 83.98.140.23

AAAA 1

  • 2001:16f8:4::23

NS 2

  • ns1.driebit.nl
  • ns2.driebit.nl

SOA 1

  • ns1.driebit.nl hosting\@driebit.nl

MCP_RECORDS 1

  • v=spf1 redirect=_spf.driebit.net

DMARC_RECORDS 1

  • v=spf1 redirect=_spf.driebit.net

BIMI_RECORDS 1

  • v=spf1 redirect=_spf.driebit.net

MTA_STS_RECORDS 1

  • v=spf1 redirect=_spf.driebit.net

TLS Certificates (4)

Common NameIssuerExpires
www.regiocanons.nl C=US, O=Let's Encrypt, CN=YE1 Mon, 12 Oct 2026 01:09:22 +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 (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_d1b083e47dc42543
Output Hash
d55573247e3ce5a000a8f818b63077f443eb57ed7cafc9982d755c45373daabe
Signature
ed25519:05652e172b8f505b44d79ae48f03ba60d7fe5f6f95e3bc9e7d2ab3eadc30ea19b79f7898480c0807089cc9e9faea76fee316deac694e11899da6dd8965eb5b01
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser