RPCScan
5,016 networks tracked8,091 RPC URLsRequestStatus
Companion site:ExplorerScan ↗Block explorer directory with per-provider drill-downs and TLS posture per host
Bitcoin Testnet4

https://mempool.ninja/testnet4/api

Bitcoin Testnet4bitcoin_rpcmempool.ninjacompare ↔
Posture score
83
Speed score
84
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
137d
Session resumed
no
TLS handshake
19ms
Resumption
11ms
TTFB
1.41s
RPC block height
162,319
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake19ms
Resumed?no
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectmempool.space
IssuerSectigo Public Server Authentication CA OV R36
Key typeRSA-2048
Chain length3
SANsmempool.space, *.es1.mempool.space, *.fra.mempool.space +15
Not before2026-09-20
Not after2027-04-06
Days to expiry137d
Chain SHA-256256cece59fe295ed…
Modern posture
HSTSyes · max-age 730d
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsissue:sectigo.com
Must-staplenot declared
Grades
Posture
B83
Speed
B84
Certificate
100
TLS profile
94
Post-quantum
40
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://mempool.ninja/testnet4/api
Host
Chain ID
-
VM
bitcoin_rpc
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-20T00:55:34.68549895Z
History (30 days)
no history

Chain peer ranking

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

Using this RPC

tabs auto-fill the URL
Generic JSON-RPC ping. Adjust the method to whatever the chain expects.
curl 'https://mempool.ninja/testnet4/api'
Scan reportschema rpcscan-report · captured 2026-11-20T05:48:34.569Z
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.