blueprotocol-fan.com

Observed Aug 16, 2026, 08:19 UTC (1d ago). Every field below was attested with an Ed25519 signature at scan time.

This reading of blueprotocol-fan.com was taken 1d ago

blueprotocol-fan.com is on the survey sweep, which works its way across the whole catalog rather than returning to one name on a schedule. Putting blueprotocol-fan.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 blueprotocol-fan.com Watching a domain needs a DRM3 account. The reading above stays free and public either way.
Up right now
Runs onXserver
Secured byLet's Encrypt
Registered withXServer, Inc.
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 blueprotocol-fan.com 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 blueprotocol-fan.com actually stands on - every host below is a signed observation
blueprotocol-fan.com
A / AAAA
85.131.213.126
Xserverserves the site
NS
ns3.xserver.jpns2.xserver.jpns4.xserver.jpns5.xserver.jp+1 more
xserver.jpanswers its DNS
TLS
www.blueprotocol-fan.com
Let's Encryptissued its certificate

DNS Records

A 1

  • 85.131.213.126

TXT 1

  • v=spf1 +a:sv17005.xserver.jp +a:blueprotocol-fan.com +mx include:spf.sender.xserver.jp ~all

NS 5

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

SOA 1

  • ns1.xserver.jp root.xserver.jp

TLS Certificates (3)

Common NameIssuerExpires
www.blueprotocol-fan.com C=US, O=Let's Encrypt, CN=YR1 Sat, 31 Oct 2026 06:02:51 +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_1bff9bd9383a6f4b
Output Hash
3a586956e7f7ef2f12866b3adddc0b3ae2c5e6363352ba2e5e86f3e7f4b8a76c
Signature
ed25519:8e4ff8efeab874fd2e4508864e11483d3d71c5846264fcfe145fde269e6fc7ab5c661250a4b38855196299664a9796c88fec05ab8bf6bddd37fa23a2e2a30406
Public Key
ed25519:4859bb613d650e12dd7478cc307c73a8712fabc115a9dc59f65534ed3c09a8f9
Parent
(genesis)
Plane
fast
Verify this in your browser
CONTINUOUS INTERNET TELEMETRY24H DRIFT42,736 material changesacross 40,484 domains · 24h to ~85m ago · +3,496 vs yesterdayROTATION78 domains moved DNS from kirklanddc.com to magpiedns.com, 75 moved backa rotation loop, not a migration · 24hEMAIL DRIFT7 domains switched email provider24hNOW495 curated domains not reachable-96 vs yesterdaySITE ERRORS33,670 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 116,854 sites429 rate-limit / 403 bot-block, a posture signal