0034.casino

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

This reading of 0034.casino was taken 14d ago

0034.casino is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting 0034.casino 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 0034.casino Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Runs onSERVERS TECH FZCO
Registered withSpaceship, Inc.
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for 0034.casino in the last day; this reading matches the one before it. The steady record is signed like every other reading. Watch it to catch the next move the moment it lands.

INFRASTRUCTURE MAPwhat 0034.casino actually stands on - every host below is a signed observation
0034.casino
A / AAAA
89.124.81.57
SERVERS TECH FZCOserves the site
NS
launch1.spaceship.netlaunch2.spaceship.net
spaceship.netanswers its DNS

DNS Records

A 1

  • 89.124.81.57

TXT 1

  • yandex-verification: b5377cfb0f78e07e

NS 2

  • launch1.spaceship.net
  • launch2.spaceship.net

SOA 1

  • launch1.spaceship.net support.spaceship.com

MCP_RECORDS 1

  • yandex-verification: b5377cfb0f78e07e

DMARC_RECORDS 1

  • yandex-verification: b5377cfb0f78e07e

BIMI_RECORDS 1

  • yandex-verification: b5377cfb0f78e07e

MTA_STS_RECORDS 1

  • yandex-verification: b5377cfb0f78e07e

TLS Certificates (0)

None.

Subdomains (0)

None observed.

WILDCARD DNSobserved 2026-08-15 19:11 UTC

DomainDrift asked this domain for one hostname that nobody ever registered, and it answered. A domain that answers invented hostnames is running wildcard DNS. It is common and usually deliberate. A SaaS platform gives every customer a subdomain this way. How the check works

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_127891acc4fbf9ce
Output Hash
9556ea1113933639c2465546184619b4cac9b8e85e59da1b9b885d7d73acaeb2
Signature
ed25519:f56382bd69e124a169c8d5b3efa02c79ad181298d9a00c678f4007c0240c90a76ac4c1d84dc8751600ec91345400eeb87620f70242a369924a5bb5fd00adeb04
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT40,911 material changesacross 38,996 domains · 24h to ~2h ago · +1,671 vs yesterdayROTATION58 domains moved DNS from magpiedns.com to koaladns.com, 57 moved backa rotation loop, not a migration · 24hEMAIL DRIFT7 domains switched email providertop destination alltheemails.comNOW534 curated domains not reachable-57 vs yesterdaySITE ERRORS34,126 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,615 sites429 rate-limit / 403 bot-block, a posture signal