DNS record lookup for any domain via x402 micropayment — $0.01 per query on Base.
What it does
The `/domain/dns` endpoint on domain.hugen.tokyo returns DNS records for a given domain name. It is part of a broader Domain Intelligence API that offers 7 checks (WHOIS, DNS, SSL, tech stack, security headers, subdomains, redirects), each available individually or combined via `/domain/full`. This specific endpoint accepts a `domain` query parameter and returns structured JSON with DNS record data including A records, MX records, SPF information, and resolver inconsistency checks.
The endpoint is gated by the x402 payment protocol, requiring $0.01 USDC on the Base network per request. The 402 challenge response includes a sample of the actual output format, showing fields like `exists`, `records` (with A and MX arrays), `spf` (with raw SPF string), and `resolver_inconsistencies`. Alternative access methods are available: an MCP gateway at mcp.hugen.tokyo, API key-based access via discovery.hugen.tokyo, or the `x402-pay` Python SDK.
The API is documented via an OpenAPI 3.1 spec and a Swagger UI at `/docs`. Response schemas for the DNS endpoint are not fully specified in the OpenAPI definition (empty schema objects), but the x402 challenge sample provides a concrete example of the output structure. The service runs on Base network for payment settlement.
Capabilities
Use cases
- —Automated DNS auditing for domain portfolios
- —Verifying DNS propagation and record correctness
- —Security assessments checking SPF and mail records
- —Agent-driven domain reconnaissance workflows
- —Monitoring DNS changes for specific domains
Fit
Best for
- —Quick single-domain DNS lookups at low cost
- —AI agents needing structured DNS data without tooling setup
- —Developers wanting pay-per-call DNS intelligence without subscriptions
Not for
- —Bulk DNS enumeration of thousands of domains (per-call pricing adds up)
- —Real-time DNS monitoring requiring sub-second polling
- —Authoritative DNS hosting or zone management
Quick start
pip install x402-pay
import x402_pay
r = x402_pay.get('https://domain.hugen.tokyo/domain/dns?domain=example.com')
print(r.json())Example
Response
{
"spf": {
"raw": "v=spf1 -all"
},
"exists": true,
"records": {
"A": [
"93.184.216.34"
],
"MX": [
"0 ."
]
},
"resolver_inconsistencies": null
}Endpoint
Quality
The endpoint is live (402 challenge confirmed) with a valid OpenAPI 3.1 spec and working Swagger docs. However, the response schema is empty in the OpenAPI definition — the only concrete output example comes from the x402 challenge sample. No dedicated documentation pages, pricing page, or README were found. Price is clear from the challenge notice.
Warnings
- —Response schema is not defined in the OpenAPI spec (empty schema object); output structure is inferred from the x402 challenge sample only.
- —No dedicated documentation beyond the Swagger UI at /docs; /pricing, /README, and /api all return 404.
- —Root URL returns 404 — no landing page for the service.
Citations
- —The API is described as '7 domain intelligence checks in one API — WHOIS, DNS, SSL, tech stack, security headers, subdomains, redirects'https://domain.hugen.tokyo/docs
- —The /domain/dns endpoint accepts a required 'domain' query parameter of type stringhttps://domain.hugen.tokyo/openapi.json
- —Payment required is $0.01 USDC on Base per requesthttps://domain.hugen.tokyo/domain/dns
- —x402 challenge sample shows fields: exists, records (A, MX), spf, resolver_inconsistencieshttps://domain.hugen.tokyo/domain/dns
- —Alternative access via MCP gateway at mcp.hugen.tokyo, API keys via discovery.hugen.tokyo, or x402-pay Python SDKhttps://domain.hugen.tokyo/domain/dns