bitsocket.org

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

This reading of bitsocket.org was taken 10d ago

bitsocket.org is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting bitsocket.org 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 bitsocket.org Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onTrellian Pty. Limited
Secured byLet's Encrypt
Registered withSav.com, LLC - 42
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-12 10:13 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 bitsocket.org actually stands on - every host below is a signed observation
bitsocket.org
A / AAAA
103.224.182.253
Trellian Pty. Limitedserves the site
NS
ns1.abovedomains.comns2.abovedomains.com
abovedomains.comanswers its DNS
MX
alltheemails.com
alltheemails.comreceives its email
TLS
foesters.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 103.224.182.253

MX 1

  • 10alltheemails.com

TXT 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

NS 2

  • ns1.abovedomains.com
  • ns2.abovedomains.com

SOA 1

  • ns1.abovedomains.com hostmaster.trellian.com

MCP_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

DMARC_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

BIMI_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

MTA_STS_RECORDS 1

  • v=spf1 ip6:fdcf:abda:4154::/48 -all

TLS Certificates (3)

Common NameIssuerExpires
foesters.com C=US, O=Let's Encrypt, CN=YR2 Tue, 06 Oct 2026 05:24:58 +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 (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; the only network request the check makes is for the published public keys.

Verify this receipt

Ed25519 Receipt

Receipt ID
rcpt_d7c2f3fdc7b7aa8f
Output Hash
137cb794c00e9fb0f7fe493d6e92552bf273f73245f365380575e1de296e7690
Signature
ed25519:347a30fda38eef245d61ce7883f433e36b0c58092d9bd7c550ae3dc3c76d549c403d0b6463aeeaeaf5493c83170a0b2303bade202988fcfa507bdb5d668cb607
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT44,280 material changesacross 42,213 domains · 24h to ~3h ago · +32,482 vs yesterdayROTATION64 domains moved DNS from magpiedns.com to koaladns.com, 60 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT2 changed registrar24hNOW499 curated domains not reachablelast probe, steadySITE ERRORS36,652 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,322 sites429 rate-limit / 403 bot-block, a posture signal