biffbampop.com

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

This reading of biffbampop.com was taken 14d ago

biffbampop.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting biffbampop.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 biffbampop.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onAutomattic
Secured byGoogle Trust Services
Registered withGoDaddy.com, LLC
1 subdomain · majestic
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-15 07:36 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 biffbampop.com actually stands on - every host below is a signed observation
biffbampop.com
A / AAAA
192.0.78.153192.0.78.228
Automatticserves the site
NS
ns3.wordpress.comns2.wordpress.comns1.wordpress.com
wordpress.comanswers its DNS
TLS
tls.automattic.com
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 192.0.78.153
  • 192.0.78.228

TXT 1

  • v=spf1 include:_spf.wpcloud.com ~all

NS 3

  • ns3.wordpress.com
  • ns2.wordpress.com
  • ns1.wordpress.com

SOA 1

  • ns1.wordpress.com hostmaster.wordpress.com

MCP_RECORDS 1

  • v=spf1 include:_spf.wpcloud.com ~all

DMARC_RECORDS 1

  • v=DMARC1;p=none;

BIMI_RECORDS 1

  • v=spf1 include:_spf.wpcloud.com ~all

MTA_STS_RECORDS 1

  • v=spf1 include:_spf.wpcloud.com ~all

TLS Certificates (3)

Common NameIssuerExpires
tls.automattic.com C=US, O=Google Trust Services, CN=WR1 Thu, 03 Sep 2026 06:36:49 +0000
WR1 C=US, O=Google Trust Services LLC, CN=GTS Root R1 Tue, 20 Feb 2029 14:00:00 +0000
GTS Root R1 C=BE, O=GlobalSign nv-sa, 2.5.4.11=Root CA, CN=GlobalSign Root CA Fri, 28 Jan 2028 00:00:42 +0000

Subdomains (1)

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_9dc73538e47fc360
Output Hash
9dfc76a1a465f10c25aa1daaf77147ef2290745d68c38ec3b57330354430c876
Signature
ed25519:cd3b6fa1e583043ee2584df4c3e5c44cf3b4b9ff08ef470d896fb32c71686d04bf569fcf5e829a571a1f040c95e7a5512eeda6c5cc830b00ffa8d4c6e2c94403
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT41,169 material changesacross 39,364 domains · 24h to ~70m ago · -390 vs yesterdayROTATION57 domains moved DNS from koaladns.com to magpiedns.com, 55 moved backa rotation loop, not a migration · 24hEMAIL DRIFT3 domains switched email providertop destination alltheemails.comNOW540 curated domains not reachable+45 vs yesterdaySITE ERRORS36,471 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,655 sites429 rate-limit / 403 bot-block, a posture signal