bloggers.com

Observed Aug 10, 2026, 22:23 UTC (4d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of bloggers.com was taken 4d ago

bloggers.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting bloggers.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 bloggers.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onKorea Telecom
Secured byLet's Encrypt
Registered withGabia, Inc.
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-13 18:28 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 bloggers.com actually stands on - every host below is a signed observation
bloggers.com
A / AAAA
112.175.246.86
Korea Telecomserves the site
NS
ns.cafe24.comns0.cafe24.comns1.cafe24.comns2.cafe24.com
cafe24.comanswers its DNS
MX
mw-002.cafe24.com
cafe24.comreceives its email
TLS
bloggers.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 112.175.246.86

MX 1

  • 10mw-002.cafe24.com

TXT 1

  • v=spf1 ip4:112.175.246.86 ~all

NS 4

  • ns.cafe24.com
  • ns0.cafe24.com
  • ns1.cafe24.com
  • ns2.cafe24.com

SOA 1

  • bloggers.com postmaster.bloggers.com

MCP_RECORDS 1

  • v=spf1 ip4:112.175.246.86 ~all

DMARC_RECORDS 1

  • v=spf1 ip4:112.175.246.86 ~all

BIMI_RECORDS 1

  • v=spf1 ip4:112.175.246.86 ~all

MTA_STS_RECORDS 1

  • v=spf1 ip4:112.175.246.86 ~all

TLS Certificates (3)

Common NameIssuerExpires
bloggers.com C=US, O=Let's Encrypt, CN=YR2 Thu, 05 Nov 2026 22:32:02 +0000
YR2 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 (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_392b28ad8a5d05e7
Output Hash
4fa573fe83b9f6715c0a9b9a524bc77bb3bb39a700de249723af25cd311b6e6d
Signature
ed25519:a620aed701c363d08981d6fc9d411bf973e23950c792ceafec83a37c4a8e63bd800d6bb0dd7b28ca9da33e88dddcaca9f3dda941d1f255ea127cbc50c1550d0d
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT44,228 material changesacross 42,540 domains · 24h to ~2h ago · +721 vs yesterdayROTATION54 domains moved DNS from koaladns.com to magpiedns.com, 53 moved backa rotation loop, not a migration · 24hNOW497 curated domains not reachablelast probe, steadySITE ERRORS36,281 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 117,270 sites429 rate-limit / 403 bot-block, a posture signal