boulder-dash.com

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

This reading of boulder-dash.com was taken 2d ago

boulder-dash.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting boulder-dash.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 boulder-dash.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onnetcup
Secured byLet's Encrypt
Registered withInterNetX GmbH
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-13 05:02 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 boulder-dash.com actually stands on - every host below is a signed observation
boulder-dash.com
A / AAAA
202.61.233.1262a03:4000:6d:d82::24:1699
netcupserves the site
NS
d.ns14.netb.ns14.neta.ns14.netc.ns14.net
ns14.netanswers its DNS
MX
mail.boulder-dash.com
boulder-dash.comreceives its email
TLS
boulder-dash.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 202.61.233.126

AAAA 1

  • 2a03:4000:6d:d82::24:1699

MX 1

  • 10mail.boulder-dash.com

TXT 1

  • 201bf978-aa64-463e-9ae5-c4e649506e81

NS 4

  • d.ns14.net
  • b.ns14.net
  • a.ns14.net
  • c.ns14.net

SOA 1

  • a.ns14.net stb.bbg-entertainment.com

MCP_RECORDS 1

  • 201bf978-aa64-463e-9ae5-c4e649506e81

DMARC_RECORDS 1

  • 201bf978-aa64-463e-9ae5-c4e649506e81

BIMI_RECORDS 1

  • 201bf978-aa64-463e-9ae5-c4e649506e81

MTA_STS_RECORDS 1

  • 201bf978-aa64-463e-9ae5-c4e649506e81

TLS Certificates (3)

Common NameIssuerExpires
boulder-dash.com C=US, O=Let's Encrypt, CN=YR2 Sun, 08 Nov 2026 08:44:46 +0000
YR2 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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_be14e1a24459bc4e
Output Hash
7c4dce8bc1ae380ca806f83000248fbc0a95eb881cca60c2a1d2352c0a8ef103
Signature
ed25519:6964c60842441d2e6fc6a386c65c234b5b899e1e14d679bb7c42432fd4e259cd01ca8d41967df1f7412496a8c2c31935b4dd6b064b10c48bac7a777fb1a71a02
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT42,850 material changesacross 40,964 domains · 24h to ~2h ago · -1,232 vs yesterdayROTATION55 domains moved DNS from koaladns.com to magpiedns.com, 54 moved backa rotation loop, not a migration · 24hNOW490 curated domains not reachablelast probe, steadySITE ERRORS36,405 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 115,579 sites429 rate-limit / 403 bot-block, a posture signal