bluecode.com

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

This reading of bluecode.com was taken 5d ago

bluecode.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting bluecode.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 bluecode.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Email byMicrosoft 365
Secured byLet's Encrypt
Also uses1PasswordZoomAnthropicAtlassianGoogle Search ConsoleLinearMixpanel
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-15 02:14 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 bluecode.com actually stands on - every host below is a signed observation
bluecode.com
A / AAAA
216.150.1.1
unattributedserves the site
NS
ns-1301.awsdns-34.orgns-1759.awsdns-27.co.ukns-248.awsdns-31.comns-765.awsdns-31.net
awsdns-34.org + awsdns-27.co.uk + moreanswers its DNS
MX
bluecode-com.mail.protection.outlook.com
Microsoft 365receives its email
TLS
bluecode.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 216.150.1.1

MX 1

  • 0bluecode-com.mail.protection.outlook.com

TXT 13

  • 1password-site-verification=LEICPLHNEZE7DJOYTPH73IO25E
  • MS=ms24534049
  • ZOOM_verify_xR8KRM-8SjeHwKSozZnhog
  • _s6d564ljq7ynarhvf2ndnzf47m5ivbg
  • anthropic-domain-verification-5ysgtz=8bc2gDmD3hknP1caq7AynPpYr
  • atlassian-domain-verification=qdn52UWiSuLS0a3NMrvdacnT8uSJzupiCjTksuituoan4mphsSgCf0IIaiyg08Fm
  • google-site-verification=1_47zG5xPqFFsBNXDRDFjarQMdPZF-EL_PnJ3fO1l_s
  • google-site-verification=AzVa9c0Yqo6QULxn9XP5DgXmnGEQsEISdAUpYGLWFsI
  • google-site-verification=ky-endkzToE14epBWqbwJcmffJtnzIpvOo1I7uHOeDA
  • linear-domain-verification=2ba7uf3532v6

NS 4

  • ns-1301.awsdns-34.org
  • ns-1759.awsdns-27.co.uk
  • ns-248.awsdns-31.com
  • ns-765.awsdns-31.net

SOA 1

  • ns-1301.awsdns-34.org awsdns-hostmaster.amazon.com

MCP_RECORDS 1

  • heritage=external-dns,external-dns/owner=extdns-eks-bcx-prod-growing-unicorn-dnsrecordadmin,external-dns/resource=ingress/acquibase-fpscbhsy/acquibase-main-846onmgs

DMARC_RECORDS 1

  • v=DMARC1; p=none; rua=mailto:dmarc@groups.bluecode.com

BIMI_RECORDS 1

  • heritage=external-dns,external-dns/owner=extdns-eks-bcx-prod-growing-unicorn-dnsrecordadmin,external-dns/resource=ingress/acquibase-fpscbhsy/acquibase-main-846onmgs

MTA_STS_RECORDS 1

  • heritage=external-dns,external-dns/owner=extdns-eks-bcx-prod-growing-unicorn-dnsrecordadmin,external-dns/resource=ingress/acquibase-fpscbhsy/acquibase-main-846onmgs

TLS Certificates (3)

Common NameIssuerExpires
bluecode.com C=US, O=Let's Encrypt, CN=YR1 Fri, 11 Sep 2026 06:37:32 +0000
YR1 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_03deeccff29da785
Output Hash
bf01aceebdcc584fcbcb224cfa860364a6004a7c06f05a7b927d002d380cc54e
Signature
ed25519:b0b61665e14e3358af5d5d1f291093d5729ddc74896404c837bb4cc7ab5ac4eddec7fbdeb4bf637a1436a256d8d2c63933e1c7e847cc6fff03bcae205378d40b
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT39,968 material changesacross 38,480 domains · 24h to ~3h ago · -3,539 vs yesterdayROTATION62 domains moved DNS from magpiedns.com to koaladns.com, 58 moved backa rotation loop, not a migration · 24hNOW496 curated domains not reachablelast probe, steadySITE ERRORS36,306 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,290 sites429 rate-limit / 403 bot-block, a posture signal