kaplansmarine.com

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

This reading of kaplansmarine.com was taken 6d ago

kaplansmarine.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting kaplansmarine.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 kaplansmarine.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Guarded by a firewall
Secured byLet's Encrypt
Registered withGoDaddy.com, LLC
1 subdomain · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
EVIDENCE OF WILDCARD DNSobserved 2026-08-15 20:44 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 kaplansmarine.com actually stands on - every host below is a signed observation
kaplansmarine.com
A / AAAA
183.111.183.64
unattributedserves the site
NS
ns2.cafe24.co.krns2.cafe24.comns1.cafe24.comns1.cafe24.co.kr
cafe24.co.kr + cafe24.comanswers its DNS
MX
mw-002.cafe24.com
cafe24.comreceives its email
TLS
kaplansmarine.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 183.111.183.64

MX 1

  • 10mw-002.cafe24.com

TXT 1

  • v=spf1 ip4:183.111.183.64 ~all

NS 4

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

SOA 1

  • kaplansmarine.com postmaster.kaplansmarine.com

MCP_RECORDS 1

  • v=spf1 ip4:183.111.183.64 ~all

DMARC_RECORDS 1

  • v=spf1 ip4:183.111.183.64 ~all

BIMI_RECORDS 1

  • v=spf1 ip4:183.111.183.64 ~all

MTA_STS_RECORDS 1

  • v=spf1 ip4:183.111.183.64 ~all

TLS Certificates (3)

Common NameIssuerExpires
kaplansmarine.com C=US, O=Let's Encrypt, CN=YR1 Tue, 15 Sep 2026 15:43:49 +0000
YR1 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_e57556cd1ec84f8f
Output Hash
910371291d68d6d7eea373e70629e31da25832a5f6a0f93085a44c096ba81a21
Signature
ed25519:284f47ec2d8a80be244e390fbe2a3badbac6e533606b02ad29f1b81683c825e6be6a6536b09d7cb2d2d11dc5d18f069bab956f5cf5740b3aaacf99c6b031450c
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT42,924 material changesacross 40,713 domains · 24h to ~40m ago · +1,365 vs yesterdayROTATION67 domains moved DNS from magpiedns.com to koaladns.com, 63 moved backa rotation loop, not a migration · 24hEMAIL DRIFT3 domains switched email provider24hNOW589 curated domains not reachable+94 vs yesterdaySITE ERRORS36,075 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,370 sites429 rate-limit / 403 bot-block, a posture signal