blogpost.com

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

This reading of blogpost.com was taken 3d ago

blogpost.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting blogpost.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 blogpost.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Not responding
Runs onAkamai Connected Cloud
Registered withABOVE.COM PTY LTD.
IPv6 · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-13 10:29 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 blogpost.com actually stands on - every host below is a signed observation
blogpost.com
A / AAAA
45.33.83.10045.79.167.18066.175.209.17996.126.111.165+4 more
Akamai Connected Cloudserves the site
NS
anan.ns.giantpanda.compo.ns.giantpanda.com
giantpanda.comanswers its DNS
MX
mail.mailerhost.net
mailerhost.netreceives its email

DNS Records

A 4

  • 45.33.83.100
  • 45.79.167.180
  • 66.175.209.179
  • 96.126.111.165

AAAA 4

  • 2600:3c03::f03c:95ff:fe91:5d52
  • 2600:3c03::f03c:95ff:fe00:29ca
  • 2600:3c03::f03c:95ff:feed:cf2a
  • 2600:3c03::f03c:95ff:feed:4d4f

MX 1

  • 1mail.mailerhost.net

TXT 1

  • v=spf1 ip6:fd43:c0d1:c090::/48 -all

NS 2

  • anan.ns.giantpanda.com
  • po.ns.giantpanda.com

SOA 1

  • anan.ns.giantpanda.com admin.giantpanda.com

MCP_RECORDS 1

  • v=spf1 ip6:fd43:c0d1:c090::/48 -all

DMARC_RECORDS 1

  • v=spf1 ip6:fd43:c0d1:c090::/48 -all

BIMI_RECORDS 1

  • v=spf1 ip6:fd43:c0d1:c090::/48 -all

MTA_STS_RECORDS 1

  • v=spf1 ip6:fd43:c0d1:c090::/48 -all

TLS Certificates (0)

None.

Subdomains (0)

None observed.

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_a48f8dc88fe4f156
Output Hash
177d0e0c51579758f066c4b40e267248249708999d46ded04f086169b0184ab2
Signature
ed25519:3247d8c2d3aca3e47c8057de3136fa282b8647a1d6fc15881e69533d8aec6e185fe177b5c5774e3a84e182e68fafa62f53d3882cb0353da943e20758cc563302
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT44,082 material changesacross 42,116 domains · 24h to ~3h ago · -1,788 vs yesterdayROTATION59 domains moved DNS from magpiedns.com to koaladns.com, 59 moved backa rotation loop, not a migration · 24hNOW492 curated domains not reachablelast probe, steadySITE ERRORS36,326 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 115,558 sites429 rate-limit / 403 bot-block, a posture signal