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

https://bscrpc.com

BNB Smart Chain Mainnetevmbscrpc.comcompare ↔● PQ hybrid
Posture score
78
Speed score
6
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
X25519MLKEM768
PQ class
PQ hybrid
ALPN
h2
Cert expires in
86d
Session resumed
yes
TLS handshake
1.26s
Resumption
891ms
TTFB
6.37s
RPC block height
-
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupX25519MLKEM768
ALPNh2
PQ classPQ hybrid
Handshake1.26s
Resumed?yes · 891ms
OCSP stapledno
SCTs (CT log)none in TLS ext
PQ strict?no (classical tolerated)
Certificate chain
Subjectenterprise.onerpc.com
IssuerWR1
Key typeRSA-2048
Chain length3
SANsenterprise.onerpc.com, lat-nyc1-01.enterprise.onerpc.com, optimism.onerpc.com +45
Not before2026-10-22
Not after2027-01-20
Days to expiry86d
Chain SHA-256d553caac0b84f7e4…
Modern posture
HSTSyes · max-age 365d
HTTP/3 (ALPN hint)no
ECH offeredno
DNSSECunsigned
CAA recordsnone published
Must-staplenot declared
Grades
Posture
C78
Speed
F6
Certificate
100
TLS profile
94
Post-quantum
90
RPC reachability
30
Misconfigurations
  • OCSP stapling not enabledno_ocsp_staple

Endpoint identity

URL
https://bscrpc.com
Host
Chain ID
56
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
PQ hybrid
Key exchange
X25519MLKEM768
Cipher
TLS_AES_256_GCM_SHA384
Last seen
2026-10-26T03:43:38.552027194Z
History (30 days)
no history

Chain peer ranking

This URL is fastest right now
no
Fastest p50 latency
1.07s
Latest block height
-

Using this RPC

tabs 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://bscrpc.com' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-27T11:30:55.617Z
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.