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

https://node1.amechain.io

AME Chain Mainnetevmamechain.io· node1compare ↔● fastest right now
Posture score
83
Speed score
49
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
14d
Session resumed
yes
TLS handshake
307ms
Resumption
251ms
TTFB
1.61s
RPC block height
27,940,467
TLS handshake
VersionTLS 1.3
CipherTLS_AES_256_GCM_SHA384
KEX groupclassical
ALPNhttp/1.1
PQ classClassical only
Handshake307ms
Resumed?yes · 251ms
OCSP stapledno
SCTs presentno
Certificate chain
Subjectnode1.amechain.io
IssuerYR2
Key typeRSA-2048
Chain length3
SANsnode1.amechain.io
Not before2026-07-24
Not after2026-10-22
Days to expiry14d
Chain SHA-256b7a62caaeac75f3e…
Misconfigurations
  • OCSP stapling not enabled no_ocsp_staple
Grades
Posture
B83
Speed
F49
Certificate
100
TLS profile
95
Post-quantum
40
RPC reachability
100
Endpoint identity
URL
https://node1.amechain.io
Host
Chain ID
180
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-07T23:57:42.591042613Z
History (30 days)
no history
Chain peer ranking
This URL is fastest right now
YES
Fastest p50 latency
1.61s
Latest block height
-
Current fastest URL
https://node1.amechain.io
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://node1.amechain.io' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
Scan reportschema rpcscan-report · captured 2026-10-10T06:56:11.052Z
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.