CONTINUOUS INTERNET TELEMETRY24H DRIFT2,424 material changesacross 2,190 domains · -974 vs yesterdayDNS DRIFT16 domains changed DNS providertop destination cloudflare.com · -11 vs yesterdayEMAIL DRIFT5 domains switched email providertop destination google.com · -1 vs yesterdayCERT DRIFT5 domains switched issuing CA24h · -2 vs yesterdayNOW3,329 curated domains not answering-6,389 vs yesterdayERRORS10,908 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT2,424 material changesacross 2,190 domains · -974 vs yesterdayDNS DRIFT16 domains changed DNS providertop destination cloudflare.com · -11 vs yesterdayEMAIL DRIFT5 domains switched email providertop destination google.com · -1 vs yesterdayCERT DRIFT5 domains switched issuing CA24h · -2 vs yesterdayNOW3,329 curated domains not answering-6,389 vs yesterdayERRORS10,908 responded with an errorlast probe · 5xx / 404 / 429 / 403

diamond.jp

Observed 2026-07-12T22:40:24.045Z (1d ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Also usesGoogle Search ConsoleFacebook/Meta
4 subdomains · tranco_10k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat diamond.jp actually stands on - every host below is a signed observation
diamond.jp
A / AAAA
210.148.177.240
Cloudflareserves the site
NS
ryleigh.ns.cloudflare.comeugene.ns.cloudflare.com
cloudflare.comanswers its DNS
MX
route2.mx.cloudflare.netroute3.mx.cloudflare.netroute1.mx.cloudflare.net
cloudflare.netreceives its email

HTTPS probe

ok Responding normally (2xx) 200 OK
HTTP status200
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time368 ms
DNS resolutionNOERROR

Every field above is part of the same signed observation as the records below. Blank means not observed, never "none".

DNS Records

A 1

  • 210.148.177.240

MX 3

  • 47route2.mx.cloudflare.net
  • 80route3.mx.cloudflare.net
  • 14route1.mx.cloudflare.net

TXT 6

  • google-site-verification=fISKJQyNGY7KCqL6XF_qn0PoURXchIR45XBpVnSQ5VQ
  • google-site-verification=m71bv9LLHHMI5847dG8uLsnUu0yRjq8_PU30vBm1zDE
  • v=spf1 include:92tghrck6z.powerspf.com ~all
  • google-site-verification=cw47u27nVyRFIWWpPmSthQ0GF7al7BaoARoMy8-i9Ns
  • facebook-domain-verification=35xmukjxwsvp824oum831hkqbxolst
  • v=DMARC1; p=reject; sp=reject; rua=mailto:p4vx7ofdwm@rua.powerdmarc.com; ruf=mailto:p4vx7ofdwm@ruf.powerdmarc.com; fo=1;

NS 2

  • ryleigh.ns.cloudflare.com
  • eugene.ns.cloudflare.com

SOA 1

  • eugene.ns.cloudflare.com dns.cloudflare.com

TLS Certificates (0)

None.

Subdomains (4)

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; nothing leaves your machine.

Verify this receipt

Put the receipt on your own site. A live badge showing what DomainDrift observes and signs for diamond.jp. It updates itself. It attests a signed observation - not that the site is safe.

DomainDrift signed-observation badge for diamond.jp <a href="https://domaindrift.io/t/diamond.jp"> <img src="https://domaindrift.io/badge/diamond.jp.svg" width="300" height="64" alt="DomainDrift signed observations for diamond.jp"> </a>

Ed25519 Receipt

Receipt ID
9d7afa00-0d8c-47eb-a3ba-6b703e7477f6
Output Hash
657d0d1be624c78f3ee36d827b0e860b3bdfaf69d9c921ce9fa23c1ac5d8dde1
Signature
ed25519:cc89ba0ff02f5be6334ce5ac93ed9d15ad1dda5ccc76181efa625c835bb16355925f93a704d8e826e0e5ddc0147cfe8e2cdf35f03d4f098863af1d4f4a740604
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser