RPCScan
- networks tracked- RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host

https://rpc.softnote.com/

Tectum Emission Tokenevmsoftnote.com· rpccompare ↔
Posture score
61
Speed score
83
TLS version
TLS 1.2
Cipher
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
81d
Session resumed
no
TLS handshake
214ms
Resumption
217ms
TTFB
566ms
RPC block height
-
TLS handshake
VersionTLS 1.2
CipherTLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake214ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subjectrpc.softnote.com
IssuerYE1
Key typeECDSA-P-256
Chain length4
SANsrpc.softnote.com
Not before2026-09-29
Not after2026-12-28
Days to expiry81d
Chain SHA-2565856b6bc6ea55a36…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
D61
Speed
B83
Certificate
100
TLS profile
75
Post-quantum
40
RPC reachability
30
Endpoint identity
URL
https://rpc.softnote.com/
Host
Chain ID
1003
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_ECDSA_WITH_AES_128_GCM_SHA256
Last seen
2026-10-07T23:58:03.070130186Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
107ms
Latest block height
-
Using this RPCtabs 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://rpc.softnote.com/' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T07:31:48.313Z
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.