blogspt.com

Observed Aug 16, 2026, 11:14 UTC (19h 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
Secured byZeroSSL GmbH
Registered withPDR Ltd. d/b/a PublicDomainRegistry.com
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for blogspt.com 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 blogspt.com actually stands on - every host below is a signed observation
blogspt.com
A / AAAA
208.91.196.105
unattributedserves the site
NS
sk.s5.cm.ns1.39.ztomy.comsk.s5.cm.ns2.39.ztomy.com
ztomy.comanswers its DNS
MX
\~
unattributedreceives its email
TLS
blogspt.com
ZeroSSL GmbHissued its certificate

DNS Records

A 1

  • 208.91.196.105

MX 1

  • 300\~

TXT 1

  • v=spf1 a -all

NS 2

  • sk.s5.cm.ns1.39.ztomy.com
  • sk.s5.cm.ns2.39.ztomy.com

SOA 1

  • sk.s5.cm.ns1.39.ztomy.com abuse.confluence-networks.com

MCP_RECORDS 1

  • v=spf1 a -all

DMARC_RECORDS 1

  • v=spf1 a -all

BIMI_RECORDS 1

  • v=spf1 a -all

MTA_STS_RECORDS 1

  • v=spf1 a -all

TLS Certificates (3)

Common NameIssuerExpires
blogspt.com C=AT, O=ZeroSSL GmbH, CN=ZeroSSL ECC DV SSL CA 2 Wed, 19 Aug 2026 23:59:59 +0000
ZeroSSL ECC DV SSL CA 2 C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication Root E46 Sun, 23 Sep 2035 23:59:59 +0000
Sectigo Public Server Authentication Root E46 C=US, ST=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust ECC Certification Authority Mon, 18 Jan 2038 23:59:59 +0000

Subdomains (0)

None observed.

WILDCARD DNSobserved 2026-08-16 11:14 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_9ddbf19edffe8117
Output Hash
d6a8f1273680761d9c734c7cbf57a3b8578154210cc80896f89ce3a859498d36
Signature
ed25519:0b609a3f4ae52826dfd31d2e7e44a6cfa614a162634d89b84884dafa272f10dfa76e80d57cc8bd8e119e27d3c5261946cd3eaff11304dcce0631238a80eb4e02
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT38,834 material changesacross 37,036 domains · 24h to ~3h ago · -406 vs yesterdayROTATION58 domains moved DNS from koaladns.com to magpiedns.com, 55 moved backa rotation loop, not a migration · 24hEMAIL DRIFT4 domains switched email providertop destination alltheemails.comNOW559 curated domains not reachable-32 vs yesterdaySITE ERRORS34,687 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,574 sites429 rate-limit / 403 bot-block, a posture signal