bourgy.com

Observed Aug 16, 2026, 17:22 UTC (14h 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 withGoDaddy.com, LLC
domcop
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

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

DNS Records

A 2

  • 13.248.169.48
  • 76.223.54.146

TXT 1

  • v=spf1 -all

NS 2

  • ns1.namefind.com
  • ns2.namefind.com

SOA 1

  • ns1.namefind.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 (4)

Common NameIssuerExpires
bourgy.com C=US, O=GoDaddy.com, CN=GoDaddy TLS Intermediate CA DV - R1v1 Tue, 12 Jan 2027 16:49:52 +0000
GoDaddy TLS Intermediate CA DV - R1v1 C=US, O=GoDaddy.com, CN=GoDaddy TLS Root CA - R1 Fri, 24 Aug 2040 11:59:59 +0000
GoDaddy TLS Root CA - R1 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
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 17:22 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_cdd1a7b1b17dd6e3
Output Hash
1096c0c3f50c8f4a54a39c1be436600f6420dedbe928a482ccc700eb2c179eb2
Signature
ed25519:b15d8403825c9ee982cc766b4c3d0beda147e449118613eda303e869a5490fc601e28a53e39a10944d774fa0987b352d80e0d92d70d5d7ad98fffe5c99823d0b
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT40,911 material changesacross 38,996 domains · 24h to ~85m ago · +1,671 vs yesterdayROTATION62 domains moved DNS from koaladns.com to magpiedns.com, 61 moved backa rotation loop, not a migration · 24hEMAIL DRIFT6 domains switched email providertop destination h-email.netNOW540 curated domains not reachable-51 vs yesterdaySITE ERRORS34,284 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,612 sites429 rate-limit / 403 bot-block, a posture signal