betscore.app

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

This reading of betscore.app was taken 2d ago

betscore.app is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting betscore.app 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 betscore.app Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onLiquid Web
Secured byLet's Encrypt
Registered withPDR Ltd. d/b/a PublicDomainRegistry.com
Also usesGoogle Search Console
7 subdomains · domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-13 02:15 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 betscore.app actually stands on - every host below is a signed observation
betscore.app
A / AAAA
67.227.166.94
Liquid Webserves the site
NS
ns.liquidweb.comns1.liquidweb.com
liquidweb.comanswers its DNS
MX
betscore.app
betscore.appreceives its email
TLS
cpanel.betscore.app
Let's Encryptissued its certificate

DNS Records

A 1

  • 67.227.166.94

MX 1

  • 10betscore.app

TXT 1

  • google-site-verification=PczkxWltqe2s3xTku8bSyzx80G284GM71mG2galNvOo

NS 2

  • ns.liquidweb.com
  • ns1.liquidweb.com

SOA 1

  • ns.liquidweb.com admin.liquidweb.com

MCP_RECORDS 1

  • google-site-verification=PczkxWltqe2s3xTku8bSyzx80G284GM71mG2galNvOo

DMARC_RECORDS 1

  • google-site-verification=PczkxWltqe2s3xTku8bSyzx80G284GM71mG2galNvOo

BIMI_RECORDS 1

  • google-site-verification=PczkxWltqe2s3xTku8bSyzx80G284GM71mG2galNvOo

MTA_STS_RECORDS 1

  • google-site-verification=PczkxWltqe2s3xTku8bSyzx80G284GM71mG2galNvOo

TLS Certificates (3)

Common NameIssuerExpires
cpanel.betscore.app C=US, O=Let's Encrypt, CN=YR2 Tue, 06 Oct 2026 08:55:39 +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 (7)

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_0efdcdd1357b08a9
Output Hash
e90e342285f9ee309de9abc298859669fd1e9cc5640524cd36018718e1a86095
Signature
ed25519:c2a54fd6561007240b792cef47f7a19c569ec808f663656e52edef80413c27b0573f95f54f80153dd42b587edfc08cae2825d516ea487ccf0314b55725d8760c
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT48,390 material changesacross 46,168 domains · 24h to ~30m ago · +2,520 vs yesterdayROTATION58 domains moved DNS from magpiedns.com to koaladns.com, 58 moved backa rotation loop, not a migration · 24hCERT DRIFT1 domains switched issuing CA24hREGISTRAR DRIFT2 changed registrar24hNOW498 curated domains not reachablelast probe, steadySITE ERRORS36,464 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 115,883 sites429 rate-limit / 403 bot-block, a posture signal