https://rpc.public-0138.defi-oracle.io

Defi Oracle Meta Mainnetevm

defi-oracle.io· rpc.public-0138 compare ↔● PQ hybrid

Posture score

Speed score

TLS version

TLS 1.3

Cipher

TLS_AES_128_GCM_SHA256

KEX group

X25519MLKEM768

PQ class

PQ hybrid

ALPN

Cert expires in

77d

Session resumed

yes

TLS handshake

269ms

Resumption

213ms

TTFB

2.39s

RPC block height

10,723,150

TLS handshake

VersionTLS 1.3

CipherTLS_AES_128_GCM_SHA256

KEX groupX25519MLKEM768

ALPNh2

PQ classPQ hybrid

Handshake269ms

Resumed?yes · 213ms

OCSP stapledyes

SCTs presentyes

Certificate chain

Subjectdefi-oracle.io

IssuerCloudflare TLS Issuing ECC CA 3

Key typeECDSA-P-256

Chain length4

SANsdefi-oracle.io, *.defi-oracle.io, rpc.public-0138.defi-oracle.io

Not before2026-09-26

Not after2026-12-25

Days to expiry77d

Chain SHA-2569c4588693a914dfc…

Misconfigurations

● No issues detected.

Grades

Posture

A+97

Speed

F38

Certificate

100

TLS profile

100

Post-quantum

RPC reachability

100

Endpoint identity

URL

https://rpc.public-0138.defi-oracle.io

Host

rpc.public-0138.defi-oracle.io

Chain

Defi Oracle Meta Mainnet

Chain ID

138

evm

Platform type

chain

Sibling RPCs

view all on chain page →

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_128_GCM_SHA256

Last seen

2026-10-09T20:27:42.098793491Z

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://rpc.public-0138.defi-oracle.io' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Scan reportschema rpcscan-report · captured 2026-10-10T05:59:55.088Z

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.