RPCScan
4,976 networks tracked8,031 RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host
Atoshi Testnet

https://node2.atoshi.io

Atoshi Testnetevmatoshi.io· node2compare ↔
Posture score
59
Speed score
27
TLS version
TLS 1.2
Cipher
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
40d
Session resumed
no
TLS handshake
492ms
Resumption
471ms
TTFB
2.94s
RPC block height
-
TLS handshake
VersionTLS 1.2
CipherTLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake492ms
Resumed?no
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectatoshi.org
IssuerYR1
Key typeRSA-2048
Chain length3
SANs*.10atoshi.top, *.11atoshi.top, *.4atoshi.top +21
Not before2026-09-28
Not after2026-12-27
Days to expiry40d
Chain SHA-25699d4aa2f13b31e6a…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
F59
Speed
F27
Certificate
100
TLS profile
68
Post-quantum
40
RPC reachability
30
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://node2.atoshi.io
Host
Chain ID
167
VM
evm
Platform type
chain

Live probe (last 24 h)

Probes attempted
-
Successful
-
Success rate
-
Median p50
-
Median p95
-
Latest bucket
-

TLS posture (post-quantum)

full history →
Class
Classical only
Key exchange
-
Cipher
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Last seen
2026-11-16T20:20:17.279839779Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
2.63s
Latest block height
-
Current fastest URL
https://node3.atoshi.io

Using this RPC

tabs auto-fill the URL + chain ID
JSON-RPC eth_chainId, which verifies the endpoint is alive and reports the chain ID.
curl -X POST 'https://node2.atoshi.io' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T22:32:56.945Z
SHA-256 of canonical content
computed in your browser
computing…

The hash covers every field above the JSON serialization with sorted keys. Re-running this computation against the downloaded artifact must produce the same hash; that's how RPCScan's future on-chain proofs (rpcscanchain) will let anyone verify a published snapshot wasn't tampered with.