WHOIS lookup for any domain via x402 micropayment — $0.01 per query on Base (USDC).
What it does
The `/domain/whois` endpoint on domain.hugen.tokyo returns WHOIS registration data for a given domain name. It is one of eight paid endpoints in the Domain Intelligence API, which also offers DNS records, SSL certificate analysis, tech-stack detection, security header auditing, subdomain discovery, redirect tracing, and a combined full-report endpoint. All endpoints run in parallel and are individually addressable.
This specific endpoint accepts a `domain` query parameter (e.g., `example.com`) via HTTP GET and returns JSON containing registration details such as registrar name, creation date, and domain age. Payment is handled via the x402 protocol: an unauthenticated request returns HTTP 402 with a USDC payment challenge on the Base network. The price is $0.01 per call (10,000 base units at 6 decimals). Alternative access methods include an MCP gateway at mcp.hugen.tokyo, a free API-key trial via discovery.hugen.tokyo, and the `x402-pay` Python SDK.
The API is documented with an OpenAPI 3.1 spec, though response schemas for the paid endpoints are not fully specified (empty schema objects). The x402 challenge was captured live and includes a sample WHOIS response showing fields like `exists`, `registrar`, `creation_date`, and `domain_age_days`.
Capabilities
Use cases
- —Checking domain registration details (registrar, creation date, age) before purchasing or partnering
- —Automated due-diligence pipelines that need WHOIS data for domains encountered in the wild
- —AI agents verifying domain legitimacy as part of phishing or fraud detection workflows
- —Enriching threat-intelligence feeds with domain registration metadata
Fit
Best for
- —Quick single-domain WHOIS lookups at very low cost ($0.01)
- —Agent-driven workflows that can pay per call via x402 or API key
- —Developers who want WHOIS data without managing WHOIS client libraries or rate limits
Not for
- —Bulk WHOIS enumeration of thousands of domains (per-call pricing adds up; no batch endpoint)
- —Scenarios requiring full raw WHOIS text output (response appears to be structured/parsed fields only)
- —Users who need free, unlimited WHOIS lookups
Quick start
pip install x402-pay
import x402_pay
r = x402_pay.get('https://domain.hugen.tokyo/domain/whois?domain=example.com')
print(r.json())Example
Response
{
"exists": true,
"registrar": "Cloudflare, Inc.",
"creation_date": "2010-01-01T00:00:00",
"domain_age_days": 5500
}Endpoint
Quality
The endpoint is live (402 challenge captured) with an OpenAPI spec and clear pricing. However, the response schema is empty in the spec, and the only example response comes from the x402 challenge sample, which may not be exhaustive. No dedicated docs page or detailed field descriptions exist.
Warnings
- —Response schema is not defined in the OpenAPI spec (empty schema object); actual response fields are inferred from the x402 challenge sample only.
- —No dedicated pricing page found; price ($0.01 USDC on Base) is derived solely from the x402 challenge notice.
- —Root URL returns 404; no landing page or README available.
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/whois endpoint accepts a required 'domain' query parameter via GEThttps://domain.hugen.tokyo/docs
- —Payment required is $0.01 USDC on Base per the x402 challengehttps://domain.hugen.tokyo/domain/whois
- —Alternative access via MCP gateway at mcp.hugen.tokyo, API key via discovery.hugen.tokyo, and x402-pay Python SDKhttps://domain.hugen.tokyo/domain/whois
- —Sample WHOIS response includes exists, registrar, creation_date, domain_age_days fieldshttps://domain.hugen.tokyo/domain/whois