wss://ws.memecore.net
Posture score
66
Speed score
64
TLS version
TLS 1.3
Cipher
TLS_AES_128_GCM_SHA256
KEX group
classical
PQ class
Classical only
ALPN
h2
Cert expires in
61d
Session resumed
no
TLS handshake
241ms
Resumption
255ms
TTFB
1.22s
RPC block height
-
TLS handshake
VersionTLS 1.3
CipherTLS_AES_128_GCM_SHA256
KEX groupclassical
ALPNh2
PQ classClassical only
Handshake241ms
Resumed?no
OCSP stapledno
SCTs presentno
Certificate chain
Subjectmemecore.net
IssuerAmazon RSA 2048 M01
Key typeRSA-2048
Chain length3
SANsmemecore.net, *.memecore.net
Not before2025-11-10
Not after2026-12-09
Days to expiry61d
Chain SHA-25667c4a5d18dd84362…
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_128_GCM_SHA256
Last seen
2026-10-09T16:08:35.387784534Z
History (30 days)
no history
This URL is fastest right now
no
Fastest p50 latency
1.30s
Latest block height
-
Current fastest URL
https://rpc.memecore.netJSON-RPC eth_chainId, which verifies the endpoint is alive and reports the chain ID.
curl -X POST 'wss://ws.memecore.net' \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'Scan reportschema rpcscan-report · captured 2026-10-10T06:59:42.606Z
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.