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

https://ethnode.primusmoney.com/firenze

Firenze test networkevmprimusmoney.com· ethnodecompare ↔
Posture score
78
Speed score
65
TLS version
TLS 1.2
Cipher
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
KEX group
classical
PQ class
Classical only
ALPN
http/1.1
Cert expires in
37d
Session resumed
no
TLS handshake
265ms
Resumption
-
TTFB
1.13s
RPC block height
13,533,402
TLS handshake
VersionTLS 1.2
CipherTLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
KEX groupclassical
ALPNhttp/1.1
PQ classClassical only
Handshake265ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subject*.primusmoney.com
IssuerCertera RSA DV SSL CA 2
Key typeRSA-2048
Chain length3
SANs*.primusmoney.com, primusmoney.com
Not before2026-05-02
Not after2026-11-16
Days to expiry37d
Chain SHA-2568c7507f7c8c582b9…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C78
Speed
D65
Certificate
100
TLS profile
75
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://ethnode.primusmoney.com/firenze
Host
Chain ID
78110
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
Classical only
Key exchange
-
Cipher
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
Last seen
2026-10-10T05:48:55.047282259Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
-
Fastest p50 latency
-
Latest block height
-
Current fastest URL
-
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://ethnode.primusmoney.com/firenze' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:52:05.740Z
SHA-256 of canonical content
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.