blogging.la

Observed Aug 16, 2026, 18:45 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.

Up right now
Runs onAmazon
Secured byGoDaddy.com
majestic
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

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

DNS Records

A 2

  • 76.223.54.146
  • 13.248.169.48

MX 1

  • 0

TXT 1

  • v=spf1 -all

NS 2

  • ns1.afternic.com
  • ns2.afternic.com

SOA 1

  • ns2.afternic.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 (3)

Common NameIssuerExpires
blogging.la C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., 2.5.4.11=http://certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2 Thu, 01 Oct 2026 21:05:07 +0000
Go Daddy Secure Certificate Authority - G2 C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., CN=Go Daddy Root Certificate Authority - G2 Sat, 03 May 2031 07:00:00 +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 18:45 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_0c6ff674458efb90
Output Hash
49bb94ea5d7032649590b1672d25c90fdb1fed6bfe5f6a36d38dd534dfca010f
Signature
ed25519:d9e7794541c142cf981438166ad7d97df668dcde4571294d354e7c89f35b4645045aac68b502a99b0917423a568f1f945b285e746cc308827c4f346e3527ab07
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT38,179 material changesacross 36,363 domains · 24h to ~2h ago · -1,061 vs yesterdayROTATION57 domains moved DNS from magpiedns.com to koaladns.com, 56 moved backa rotation loop, not a migration · 24hEMAIL DRIFT7 domains switched email providertop destination alltheemails.comNOW529 curated domains not reachable-62 vs yesterdaySITE ERRORS34,005 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,663 sites429 rate-limit / 403 bot-block, a posture signal