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

https://jp.enirpc.com

ENI Mainnetevmenirpc.com· jpcompare ↔● PQ hybrid
Posture score
97
Speed score
67
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
66d
Session resumed
yes
TLS handshake
123ms
Resumption
161ms
TTFB
1.18s
RPC block height
41,040,332
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake123ms
Resumed?yes · 161ms
OCSP stapledyes
SCTs presentno
Certificate chain
Subjectenirpc.com
IssuerAmazon RSA 2048 M04
Key typeRSA-2048
Chain length3
SANsenirpc.com, *.enirpc.com
Not before2025-11-13
Not after2026-12-12
Days to expiry66d
Chain SHA-25639477d53245a64c7…
Misconfigurations
● No issues detected.
Grades
Posture
A+97
Speed
D67
Certificate
100
TLS profile
100
Post-quantum
90
RPC reachability
100
Endpoint identity
URL
https://jp.enirpc.com
Host
Chain ID
173
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-07T23:57:42.16064587Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
no
Fastest p50 latency
933ms
Latest block height
-
Current fastest URL
https://rpc.eniac.network
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://jp.enirpc.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T07:33:13.166Z
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.