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

https://api.popdex.xyz/api/v1/web3/rpc

Morph Tachyonevmpopdex.xyz· apicompare ↔● fastest right now● PQ hybrid
Posture score
97
Speed score
100
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
188d
Session resumed
yes
TLS handshake
16ms
Resumption
9ms
TTFB
317ms
RPC block height
66,996,158
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake16ms
Resumed?yes · 9ms
OCSP stapledyes
SCTs presentyes
Certificate chain
Subjectpopdex.xyz
IssuerCloudflare TLS Issuing ECC CA 3
Key typeECDSA-P-256
Chain length4
SANspopdex.xyz, *.popdex.xyz
Not before2026-09-28
Not after2027-04-15
Days to expiry188d
Chain SHA-256577c62e59354dc3a…
Misconfigurations
● No issues detected.
Grades
Posture
A+97
Speed
A+100
Certificate
100
TLS profile
100
Post-quantum
90
RPC reachability
100
Endpoint identity
URL
https://api.popdex.xyz/api/v1/web3/rpc
Host
Chain ID
2184
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
PQ hybrid
Key exchange
X25519MLKEM768
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-09T13:08:23.389097718Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
317ms
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://api.popdex.xyz/api/v1/web3/rpc' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T11:34:20.977Z
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.