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

https://rubicon.mainnet.romeprotocol.xyz

Rome Rubicon Mainnetevmromeprotocol.xyz· rubicon.mainnetcompare ↔
Posture score
83
Speed score
86
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
classical
PQ class
Classical only
ALPN
http/1.1
Cert expires in
24d
Session resumed
yes
TLS handshake
117ms
Resumption
109ms
TTFB
634ms
RPC block height
455,134,376
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPNhttp/1.1
PQ classClassical only
Handshake117ms
Resumed?yes · 109ms
OCSP stapledno
SCTs presentno
Certificate chain
Subject*.mainnet.romeprotocol.xyz
IssuerYE1
Key typeECDSA-P-256
Chain length4
SANs*.mainnet.romeprotocol.xyz, mainnet.romeprotocol.xyz
Not before2026-08-05
Not after2026-11-03
Days to expiry24d
Chain SHA-256e048f2c27136aa9e…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
B83
Speed
B86
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://rubicon.mainnet.romeprotocol.xyz
Host
Chain ID
7531
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_AES_256_GCM_SHA384
Last seen
2026-10-10T05:08:47.794084656Z
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://rubicon.mainnet.romeprotocol.xyz' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:59:59.020Z
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.