bood.com

Observed Aug 16, 2026, 15:10 UTC (22h ago). Every field below was attested with an Ed25519 signature at scan time. Catalog observation, re-checked on rotation - watch it for 5-minute checks.

Verify this receipt yourself + Watch this domain
Up right now
Runs onAmazon
Secured byGoDaddy.com
Registered withDynadot Inc
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for bood.com 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 bood.com actually stands on - every host below is a signed observation
bood.com
A / AAAA
76.223.54.14613.248.169.48
Amazonserves the site
NS
ns1.afternic.comns2.afternic.com
afternic.comanswers its DNS
TLS
bood.com
GoDaddy.comissued its certificate

DNS Records

A 2

  • 76.223.54.146
  • 13.248.169.48

MX 1

  • 0

TXT 1

  • v=spf1 -all

NS 2

  • ns1.afternic.com
  • ns2.afternic.com

SOA 1

  • ns1.afternic.com dns.jomax.net

MCP_RECORDS 1

  • v=spf1 -all

DMARC_RECORDS 1

  • v=spf1 -all

BIMI_RECORDS 1

  • v=spf1 -all

MTA_STS_RECORDS 1

  • v=spf1 -all

TLS Certificates (3)

Common NameIssuerExpires
bood.com C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., 2.5.4.11=http://certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2 Thu, 20 Aug 2026 07:32:44 +0000
Go Daddy Secure Certificate Authority - G2 C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Sat, 03 May 2031 07:00:00 +0000
Go Daddy Root Certificate Authority - G2 C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Thu, 31 Dec 2037 23:59:59 +0000

Subdomains (0)

None observed.

WILDCARD DNSobserved 2026-08-16 15:10 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_f3bc86d3d77f532f
Output Hash
b2b75ade2bbeb632df7217dc325c14a44eae8ee59f0241a42866a815a291fbfe
Signature
ed25519:43495b6eb2c345ef9145ec583cc9f0e23506ba1e87b8b88e7a5ba28400bbd66e3be179a4bdb1f59337eb55164f6dc3ce8cb88753a6afa75c1bcb3b1aa02a9901
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT43,944 material changesacross 41,887 domains · 24h to ~40m ago · +4,704 vs yesterdayDNS DRIFT92 domains changed DNS providertop destination koaladns.com · +5 vs yesterdayEMAIL DRIFT7 domains switched email providertop destination h-email.netNOW506 curated domains not reachable-85 vs yesterdaySITE ERRORS33,753 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,800 sites429 rate-limit / 403 bot-block, a posture signal