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.emzy.de/testnet4/api

Bitcoin Testnet4bitcoin_rpcemzy.de· mempoolcompare ↔
Posture score
84
Speed score
80
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
http/1.1
Cert expires in
62d
Session resumed
yes
TLS handshake
145ms
Resumption
146ms
TTFB
1.00s
RPC block height
162,337
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNhttp/1.1
PQ classClassical only
Handshake145ms
Resumed?yes · 146ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectmempool.emzy.de
IssuerYE2
Key typeECDSA-P-256
Chain length4
SANsmempool.emzy.de
Not before2026-10-23
Not after2027-01-21
Days to expiry62d
Chain SHA-25694a395fb3b21f656…
Modern posture
HSTSyes · max-age 730d
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECzone signed (DNSKEY present)
CAA recordsissue:letsencrypt.org
Must-staplenot declared
Grades
Posture
B84
Speed
B80
Certificate
100
TLS profile
97
Post-quantum
40
RPC reachability
100
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://mempool.emzy.de/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-20T02:26:37.330649982Z
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.emzy.de/testnet4/api'
Scan reportschema rpcscan-report · captured 2026-11-20T05:48:35.956Z
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.