saikami.jp

Observed Aug 10, 2026, 03:49 UTC (4d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of saikami.jp was taken 4d ago

saikami.jp is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting saikami.jp 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 saikami.jp Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Email byHubSpot
Also usesGoogle Search Console
tranco
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat saikami.jp actually stands on - every host below is a signed observation
saikami.jp
A / AAAA
202.254.239.158
unattributedserves the site
NS
ns1.xserver.jpns2.xserver.jpns3.xserver.jpns5.xserver.jp+1 more
xserver.jpanswers its DNS
MX
saikami.jp
HubSpotreceives its email
TLS
www.saikami.jp
Let's Encryptissued its certificate

DNS Records

A 1

  • 202.254.239.158

MX 1

  • 0saikami.jp

TXT 3

  • google-site-verification=LZgz8xe06h-ThLcM4PFB4Kl5zTszSe3ewq3mAVZsE4s
  • google-site-verification=u-C-VW_dGWCuU_5F6yZXrboeK0TcvI0DxLzv5YHp0bI
  • v=spf1 +a:sv7477.xserver.jp +a:saikami.jp +mx include:spf.sender.xserver.jp include:spf.besender.jp include:242391817.spf02.hubspotemail.net ~all

NS 5

  • ns1.xserver.jp
  • ns2.xserver.jp
  • ns3.xserver.jp
  • ns5.xserver.jp
  • ns4.xserver.jp

SOA 1

  • ns1.xserver.jp root.xserver.jp

DMARC_RECORDS 1

  • v=DMARC1; p=none; ruf=mailto:link@saikami.jp

TLS Certificates (3)

Common NameIssuerExpires
www.saikami.jp C=US, O=Let's Encrypt, CN=YR1 Thu, 29 Oct 2026 23:18:39 +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_5ae87fc26937f4f4
Output Hash
5a5b4b5561371c25bd267eef4334193ebb6b0bf48869c568a63079f696b0465a
Signature
ed25519:ffe368e2df24710f7788bee2b35f0df32892d80650c1eb7d9c99359c469c59d1a2a2069c44d51c71620786ef221c0348e86b3bc1d8f952eb97f78693f3af2f05
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT41,773 material changesacross 39,917 domains · 24h to ~2h ago · -2,309 vs yesterdayROTATION59 domains moved DNS from koaladns.com to magpiedns.com, 54 moved backa rotation loop, not a migration · 24hNOW490 curated domains not reachablelast probe, steadySITE ERRORS36,526 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 115,984 sites429 rate-limit / 403 bot-block, a posture signal