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

https://mainnet.basedaibridge.com/rpc

BasedAIevmbasedaibridge.com· mainnetcompare ↔
Posture score
73
Speed score
71
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
-
PQ class
Unknown
ALPN
h2
Cert expires in
32d
Session resumed
yes
TLS handshake
236ms
Resumption
201ms
TTFB
618ms
RPC block height
4,797,085
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX group-
ALPNh2
PQ classUnknown
Handshake236ms
Resumed?yes · 201ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectmainnet.basedaibridge.com
IssuerYE1
Key typeECDSA-P-256
Chain length4
SANsmainnet.basedaibridge.com
Not before2026-08-13
Not after2026-11-11
Days to expiry32d
Chain SHA-2564df870cba7e241f1…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
C73
Speed
C71
Certificate
100
TLS profile
95
Post-quantum
0
RPC reachability
100
Endpoint identity
URL
https://mainnet.basedaibridge.com/rpc
Host
Chain
Chain ID
32323
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
Unknown
Key exchange
-
Cipher
TLS_AES_128_GCM_SHA256
Last seen
2026-10-10T05:53:53.084840104Z
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://mainnet.basedaibridge.com/rpc' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T05:57:41.830Z
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.