martmonster.com

Observed Aug 16, 2026, 17:36 UTC (16h 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 byLet's Encrypt
2 subdomains · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for martmonster.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 martmonster.com actually stands on - every host below is a signed observation
martmonster.com
A / AAAA
1.234.79.161
unattributedserves the site
NS
ns1.cafe24.comns1.cafe24.co.krns2.cafe24.comns2.cafe24.co.kr
cafe24.com + cafe24.co.kranswers its DNS
MX
ALT.ASPMX.daum.netASPMX.daum.net
daum.netreceives its email
TLS
martmonster.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 1.234.79.161

MX 2

  • 20ALT.ASPMX.daum.net
  • 10ASPMX.daum.net

TXT 1

  • v=spf1 include:_spf.daum.net ~all

NS 4

  • ns1.cafe24.com
  • ns1.cafe24.co.kr
  • ns2.cafe24.com
  • ns2.cafe24.co.kr

SOA 1

  • martmonster.com postmaster.martmonster.com

MCP_RECORDS 1

  • v=spf1 include:_spf.daum.net ~all

DMARC_RECORDS 1

  • v=spf1 include:_spf.daum.net ~all

BIMI_RECORDS 1

  • v=spf1 include:_spf.daum.net ~all

MTA_STS_RECORDS 1

  • v=spf1 include:_spf.daum.net ~all

TLS Certificates (4)

Common NameIssuerExpires
martmonster.com C=US, O=Let's Encrypt, CN=YE2 Mon, 09 Nov 2026 05:18:32 +0000
YE2 C=US, O=ISRG, CN=Root YE Sat, 02 Sep 2028 23:59:59 +0000
Root YE C=US, O=Internet Security Research Group, CN=ISRG Root X2 Thu, 02 Sep 2032 23:59:59 +0000
ISRG Root X2 C=US, O=Internet Security Research Group, CN=ISRG Root X1 Thu, 02 Sep 2032 23:59:59 +0000

Subdomains (2)

WILDCARD DNSobserved 2026-08-16 17:36 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_6bc9bc5fb14adf8e
Output Hash
845c432dbc1c6451c9b74dd3b59752601f5ce45bab9a9134e72d2fc2c183ed38
Signature
ed25519:76b2f3324c07f30e6cfd47515cbc3ecb934683a556703c79a45ddda75ec68149f643da765c134a3dd9e18632eca1e9194457b2a3aa8ecd38a548e5b2d221ad05
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT43,754 material changesacross 41,714 domains · last 24h · +4,514 vs yesterdayROTATION57 domains moved DNS from magpiedns.com to koaladns.com, 54 moved backa rotation loop, not a migration · 24hEMAIL DRIFT7 domains switched email providertop destination alltheemails.comNOW526 curated domains not reachable-65 vs yesterdaySITE ERRORS33,906 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,773 sites429 rate-limit / 403 bot-block, a posture signal