javalab.org

Observed Aug 16, 2026, 19:14 UTC (8h 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
Also usesGoogle Search Console
1 subdomain · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
DRIFT

Steady. No change on record for javalab.org 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 javalab.org actually stands on - every host below is a signed observation
javalab.org
A / AAAA
183.111.100.159
unattributedserves the site
NS
ns1.cafe24.co.krns2.cafe24.co.krns1.cafe24.comns2.cafe24.com
cafe24.co.kr + cafe24.comanswers its DNS
MX
ugp8-wpm-003.cafe24.com
cafe24.comreceives its email
TLS
javalab.org
Let's Encryptissued its certificate

DNS Records

A 1

  • 183.111.100.159

MX 1

  • 10ugp8-wpm-003.cafe24.com

TXT 2

  • v=spf1 ip4:183.111.100.159 ~all
  • google-site-verification=o9CYZTWP-Al1lhiXTK5_ZMcpWLcii_IdIbTIai4YI84

NS 4

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

SOA 1

  • javalab.org postmaster.javalab.org

MCP_RECORDS 2

  • v=spf1 ip4:183.111.100.159 ~all
  • google-site-verification=o9CYZTWP-Al1lhiXTK5_ZMcpWLcii_IdIbTIai4YI84

DMARC_RECORDS 2

  • google-site-verification=o9CYZTWP-Al1lhiXTK5_ZMcpWLcii_IdIbTIai4YI84
  • v=spf1 ip4:183.111.100.159 ~all

BIMI_RECORDS 2

  • google-site-verification=o9CYZTWP-Al1lhiXTK5_ZMcpWLcii_IdIbTIai4YI84
  • v=spf1 ip4:183.111.100.159 ~all

MTA_STS_RECORDS 2

  • v=spf1 ip4:183.111.100.159 ~all
  • google-site-verification=o9CYZTWP-Al1lhiXTK5_ZMcpWLcii_IdIbTIai4YI84

TLS Certificates (3)

Common NameIssuerExpires
javalab.org C=US, O=Let's Encrypt, CN=YR2 Wed, 11 Nov 2026 15:13:12 +0000
YR2 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)

WILDCARD DNSobserved 2026-08-16 19: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_6fcdd6ff12cddb52
Output Hash
065936e5e0c783cb97ce4f67ef0739073c5a6e76e180f6df989db239214e86c7
Signature
ed25519:92a3874de3c3a298d5509a5b093d7b051be532d1bc4666fbd34641b84c8f4bc54bac0b72c6e344533a2a8a512654459c316243ef08e0f534fd2b28958981f408
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT42,486 material changesacross 40,435 domains · last 24h · +3,246 vs yesterdayROTATION59 domains moved DNS from koaladns.com to magpiedns.com, 58 moved backa rotation loop, not a migration · 24hEMAIL DRIFT3 domains switched email provider24hNOW594 curated domains not reachablelast probe, steadySITE ERRORS35,150 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,352 sites429 rate-limit / 403 bot-block, a posture signal