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

https://evm-rpc-infinite.mschihuahua.org

Infinite Driveevmmschihuahua.org· evm-rpc-infinitecompare ↔● fastest right now
Posture score
73
Speed score
86
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
-
PQ class
Unknown
ALPN
h2
Cert expires in
88d
Session resumed
no
TLS handshake
111ms
Resumption
-
TTFB
430ms
RPC block height
3,861,710
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX group-
ALPNh2
PQ classUnknown
Handshake111ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subjectmschihuahua.org
IssuerWE1
Key typeECDSA-P-256
Chain length3
SANsmschihuahua.org, *.mschihuahua.org
Not before2026-10-08
Not after2027-01-06
Days to expiry88d
Chain SHA-256ce3d689ba600a2e0…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C73
Speed
B86
Certificate
100
TLS profile
95
Post-quantum
0
RPC reachability
100
Endpoint identity
URL
https://evm-rpc-infinite.mschihuahua.org
Host
Chain ID
421018
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
Unknown
Key exchange
-
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-10T09:04:01.987878592Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
430ms
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://evm-rpc-infinite.mschihuahua.org' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T09:08:51.949Z
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.