jasmy.co.jp

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

This reading of jasmy.co.jp was taken 6d ago

jasmy.co.jp is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting jasmy.co.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 jasmy.co.jp Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Email byMicrosoft 365
Secured byCybertrust Japan Co.
Also usesGoogle Search Console
5 subdomains · tranco
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat jasmy.co.jp actually stands on - every host below is a signed observation
jasmy.co.jp
A / AAAA
52.223.35.120
unattributedserves the site
NS
ns2.dns.ne.jpns1.dns.ne.jp
ne.jpanswers its DNS
MX
jasmy-co-jp.mail.protection.outlook.com
Microsoft 365receives its email
TLS
*.jasmy.co.jp
Cybertrust Japan Co.issued its certificate

DNS Records

A 1

  • 52.223.35.120

MX 1

  • 0jasmy-co-jp.mail.protection.outlook.com

TXT 3

  • google-site-verification=rerQJwSCFfButHBAKXS28TFfqz5siPfHhsIOWSIdP0I
  • v=spf1 include:spf.protection.outlook.com include:spf.form.run include:webcas.net +ip4:210.175.7.1 ~all
  • google-site-verification=yOCicPxfjx3IAwpLbAlgCSPZHUTOk1U63TrwOGpHP40

NS 2

  • ns2.dns.ne.jp
  • ns1.dns.ne.jp

SOA 1

  • master.dns.ne.jp tech.sakura.ad.jp

DMARC_RECORDS 1

  • v=DMARC1; p=none; rua=mailto:dmarcreports@jasmy.co.jp; ri=86400

TLS Certificates (2)

Common NameIssuerExpires
*.jasmy.co.jp C=JP, O=Cybertrust Japan Co., Ltd., CN=Cybertrust Japan SureServer CA G4 Sun, 25 Oct 2026 14:59:00 +0000
Cybertrust Japan SureServer CA G4 C=JP, O=SECOM Trust Systems CO.,LTD., 2.5.4.11=Security Communication RootCA2 Tue, 29 May 2029 05:00:39 +0000

Subdomains (5)

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_d2a222a3155d722f
Output Hash
54bf0be42a11433b700e829d82463b1979686e04e0ec84230a7d96b4d2da7f1d
Signature
ed25519:8b1b3b7342f6be3c86799be877b3d8e36752a646176d7c2002e60230a49fbb4fd05d9462e303c598ab9839c861c80cdd97b389f9c0596faf0de1bf712688030c
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT37,166 material changesacross 35,271 domains · 24h to ~2h ago · -4,393 vs yesterdayROTATION66 domains moved DNS from magpiedns.com to koaladns.com, 65 moved backa rotation loop, not a migration · 24hEMAIL DRIFT3 domains switched email provider24hNOW594 curated domains not reachable+99 vs yesterdaySITE ERRORS35,748 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,264 sites429 rate-limit / 403 bot-block, a posture signal