https://api.bie.ai
Posture score
66
Speed score
70
TLS version
TLS 1.3
Cipher
TLS_AES_256_GCM_SHA384
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
21d
Session resumed
yes
TLS handshake
87ms
Resumption
83ms
TTFB
1.10s
RPC block height
-
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake87ms
Resumed?yes · 83ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectbie.ai
IssuerYR1
Key typeRSA-2048
Chain length4
SANs*.bie.ai, bie.ai
Not before2026-07-31
Not after2026-10-29
Days to expiry21d
Chain SHA-256dd823202a29a68fc…
Misconfigurations
- OCSP stapling not enabled
no_ocsp_staple
Probes attempted
-
Successful
-
Success rate
-
Median p50
-
Median p95
-
Latest bucket
-
Class
Classical only
Key exchange
-
Cipher
TLS_AES_256_GCM_SHA384
Last seen
2026-10-07T23:58:09.217801852Z
History (30 days)
no history
This URL is fastest right now
-
Fastest p50 latency
-
Latest block height
-
Current fastest URL
-JSON-RPC eth_chainId, which verifies the endpoint is alive and reports the chain ID.
curl -X POST 'https://api.bie.ai' \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'Scan reportschema rpcscan-report · captured 2026-10-10T05:55:54.414Z
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.