Resolve ENS on Ethereum mainnet from a full node
Resolve ENS on Ethereum mainnet from a full node: name to address (e.g. vitalik.eth) or address to primary name (reverse record, verified forward). Use it to turn human-readable names into payment addresses and to label addresses. Give either name or address.
Answeringour last check, 2026-10-18
1 of 1checks answered this week
730 msmedian answer time
$0.001listed price per call
$0.001price it asked us
Paid test badge: not yet. The checks above are free: we call the tool without paying and read the payment request it sends back. The Verified badge needs paid calls whose answers match the promised output, and nobody can buy a badge.
Endpoint
GET https://402rpc.com/v1/eth/ens
| Category | Market data |
|---|---|
| Provider host | 402rpc.com |
| Networks | eip155:137, eip155:42161, eip155:8453 |
| Payment schemes | exact |
| Self-reported calls, 30 days | 2 from 2 payers (the provider's figure, not ours) |
Our checks, last 30 days
| Day | Result | HTTP | Asked | Time |
|---|---|---|---|---|
| 2026-10-18 | valid payment request | 402 | $0.001 | 730 ms |
Example input (from the provider)
{
"method": "GET",
"queryParams": {
"name": "vitalik.eth"
},
"type": "http"
}
Promised output schema (from the provider)
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"input": {
"additionalProperties": false,
"properties": {
"method": {
"enum": [
"GET"
],
"type": "string"
},
"queryParams": {
"properties": {
"address": {
"description": "Address for reverse lookup.",
"pattern": "^0x[a-fA-F0-9]{40}$",
"type": "string"
},
"name": {
"description": "ENS name, e.g. vitalik.eth.",
"pattern": "^[^\\s]{3,255}\\.[a-z]{2,}$",
"type": "string"
}
},
"type": "object"
},
"type": {
"const": "http",
"type": "string"
}
},
"required": [
"type",
"method"
],
"type": "object"
},
"output": {
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}
},
"required": [
"input"
],
"type": "object"
}