bittersweetblog.com

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

This reading of bittersweetblog.com was taken 1d ago

bittersweetblog.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting bittersweetblog.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 bittersweetblog.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 withBluehost Inc.
1 subdomain · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-12 02:42 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 bittersweetblog.com actually stands on - every host below is a signed observation
bittersweetblog.com
A / AAAA
192.0.78.143192.0.78.200
Automatticserves the site
NS
ns1.wordpress.comns3.wordpress.comns2.wordpress.com
wordpress.comanswers its DNS
MX
smtp-fwd.wordpress.com
wordpress.comreceives its email
TLS
tls.automattic.com
Google Trust Servicesissued its certificate

DNS Records

A 2

  • 192.0.78.143
  • 192.0.78.200

MX 1

  • 0smtp-fwd.wordpress.com

TXT 1

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

NS 3

  • ns1.wordpress.com
  • ns3.wordpress.com
  • ns2.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 Wed, 04 Nov 2026 05:59:09 +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_50b8f9853f4c0029
Output Hash
abc00b830872c0eb66abbc3fa5596c8eb93e3676bcdaa0a5f835f518a9ac362c
Signature
ed25519:750decb651bf7dd42d51ee982bcaa67648193f9ecd0bb0a124f033578b8cef7bcb185d7bbdd5a6ad4e85647c6e42bb40e3ba7286b4afbbfbdcd47c877ce0420b
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT38,886 material changesacross 36,129 domains · 24h to ~70m ago · +27,088 vs yesterdayROTATION63 domains moved DNS from magpiedns.com to koaladns.com, 60 moved backa rotation loop, not a migration · 24hNOW524 curated domains not reachablelast probe, steadySITE ERRORS36,595 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,345 sites429 rate-limit / 403 bot-block, a posture signal