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

https://api-boba-mainnet.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c

Boba Networkevmdwellir.com· api-boba-mainnet.ncompare ↔
Posture score
83
Speed score
64
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
57d
Session resumed
yes
TLS handshake
173ms
Resumption
138ms
TTFB
1.43s
RPC block height
40,303,213
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake173ms
Resumed?yes · 138ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectapi-boba-mainnet.n.dwellir.com
IssuerZeroSSL ECC DV SSL CA 2
Key typeECDSA-P-256
Chain length3
SANsapi-boba-mainnet.n.dwellir.com
Not before2026-09-07
Not after2026-12-06
Days to expiry57d
Chain SHA-25656726161c9100079…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
B83
Speed
D64
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://api-boba-mainnet.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c
Host
Chain ID
288
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:47:46.476467895Z
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://api-boba-mainnet.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:49:52.335Z
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.