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

https://rpc.hoodi.mantle.xyz

Mantle Hoodi Testnetevmmantle.xyz· rpc.hoodicompare ↔● fastest right now● PQ hybrid
Posture score
97
Speed score
70
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
143d
Session resumed
no
TLS handshake
46ms
Resumption
65ms
TTFB
1.01s
RPC block height
7,463,290
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake46ms
Resumed?no
OCSP stapledyes
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectmantle.xyz
IssuerAmazon RSA 2048 M04
Key typeRSA-2048
Chain length3
SANsmantle.xyz, *.hoodi.mantle.xyz, *.mantle.xyz
Not before2026-09-23
Not after2027-04-08
Days to expiry143d
Chain SHA-25645a6806c0930dc24…
Modern posture
HSTSno header
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECzone signed (DNSKEY present)
CAA recordsnone published
Must-staplenot declared
Grades
Posture
A+97
Speed
C70
Certificate
100
TLS profile
98
Post-quantum
90
RPC reachability
100
Misconfigurations
● No issues detected.

Endpoint identity

URL
https://rpc.hoodi.mantle.xyz
Host
Chain ID
50002
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-11-16T22:16:43.729112952Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
YES
Fastest p50 latency
1.01s
Latest block height
-
Current fastest URL
https://rpc.hoodi.mantle.xyz

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 'https://rpc.hoodi.mantle.xyz' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-11-16T22:27:35.200Z
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.