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

wss://parachain-rpc.origin-trail.network

NeuroWebevmorigin-trail.network· parachain-rpccompare ↔
Posture score
80
Speed score
91
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
-
Cert expires in
78d
Session resumed
no
TLS handshake
-
Resumption
118ms
TTFB
-
RPC block height
15,612,814
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPN-
PQ classClassical only
Handshake-
Resumed?no
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectorigin-trail.network
IssuerYE1
Key typeECDSA-P-256
Chain length4
SANsorigin-trail.network, parachain-rpc.origin-trail.network
Not before2026-11-04
Not after2027-02-02
Days to expiry78d
Chain SHA-256dc354a6c0e435eca…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
B80
Speed
A91
Certificate
100
TLS profile
80
Post-quantum
40
RPC reachability
100
Misconfigurations
  • ALPN not negotiatedno_alpn
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
wss://parachain-rpc.origin-trail.network
Host
Chain ID
2043
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_AES_128_GCM_SHA256
Last seen
2026-11-16T20:20:52.989334476Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
642ms
Latest block height
-

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 'wss://parachain-rpc.origin-trail.network' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T23:01:13.695Z
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.