CONTINUOUS INTERNET TELEMETRY24H DRIFT30,429 material changesacross 29,264 domains · 24h to ~3h agoSHIFT26 domains moved DNS from brainydns.com to koaladns.coma coordinated move · 24hNOW564 curated domains not reachablelast probe, steadySITE ERRORS34,078 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 156,336 sites429 rate-limit / 403 bot-block, a posture signal

v554.casino

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

This reading of v554.casino was taken 2d ago

v554.casino is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting v554.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 v554.casino Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Runs onCloudflare
Secured byLet's Encrypt
IPv6 · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-04 00:17 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 v554.casino actually stands on - every host below is a signed observation
v554.casino
A / AAAA
104.21.68.15172.67.184.2192606:4700:3035::ac43:b8db2606:4700:3030::6815:440f
Cloudflareserves the site
NS
josh.ns.cloudflare.commaeve.ns.cloudflare.com
cloudflare.comanswers its DNS
TLS
v554.casino
Let's Encryptissued its certificate

DNS Records

A 2

  • 104.21.68.15
  • 172.67.184.219

AAAA 2

  • 2606:4700:3035::ac43:b8db
  • 2606:4700:3030::6815:440f

TXT 2

  • v=spf1 -all
  • yandex-verification: 7d17bb17e1ef43fa

NS 2

  • josh.ns.cloudflare.com
  • maeve.ns.cloudflare.com

SOA 1

  • josh.ns.cloudflare.com dns.cloudflare.com

MCP_RECORDS 1

  • yandex-verification: 7d17bb17e1ef43fa

DMARC_RECORDS 1

  • v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s;

BIMI_RECORDS 1

  • yandex-verification: 7d17bb17e1ef43fa

MTA_STS_RECORDS 1

  • yandex-verification: 7d17bb17e1ef43fa

TLS Certificates (4)

Common NameIssuerExpires
v554.casino C=US, O=Let's Encrypt, CN=YE1 Wed, 23 Sep 2026 22:35:44 +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 (0)

None observed.

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_26cf0c0c97581bd7
Output Hash
23407fa8662df5ef067102e771bd430d4220de95919c9f425c285b66c98c84ad
Signature
ed25519:095972e02ceeb786284343581edb6bb208cf23751760668ffab911294f4a4602855140da8107b565abd1bb23cf1b44b25a9f40f9dba80d41f2fc80b83425b40a
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser