Whois x402 REST usage
WHOIS registration lookup — registrar, creation/expiry/updated dates, domain age in days, name servers, DNSSEC, registrant country/org, EPP status codes. All TLDs (.com .net .org .io .dev .ai ccTLDs gTLDs). Per-field err...
domain.hugen.tokyo · 8 listed services · provider site
WHOIS registration lookup — registrar, creation/expiry/updated dates, domain age in days, name servers, DNSSEC, registrant country/org, EPP status codes. All TLDs (.com .net .org .io .dev .ai ccTLDs gTLDs). Per-field err...
DNS lookup across 3 independent resolvers in parallel — A, AAAA, MX, TXT, NS, CNAME, SOA records. SPF mechanism parsing, DMARC policy extraction, resolver inconsistency detection (DNS hijacking/BGP leak signal). One call...
Redirect chain analysis — follows up to 10 hops (301/302/303/307/308) with per-hop timing, status codes, TLS status. Detects HTTPS-to-HTTP TLS downgrade, redirect loops, excessive chains. A-F grade. SSRF-safe. Accepts US...
Technology stack detection (1000+ signatures) — web servers, CMS, JS frameworks, CDN, analytics. Identifies Nginx, Apache, WordPress, Shopify, React, Vue, Next.js, Cloudflare, and hundreds more. No pattern database maint...
Security header audit — 10 headers checked: CSP, HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy, X-XSS-Protection, CORP, COEP, COOP. Information leakage detection via Server/X-Powered-...
SSL/TLS certificate analysis — issuer, SAN list, serial number, validity period, days until expiry. TLS 1.0/1.1/1.2/1.3 individual probing. Automated A-F security grade. No SSL library setup or certificate parsing needed...
Complete domain intelligence in one call — WHOIS, multi-resolver DNS, SSL/TLS, tech stack, security headers, subdomain discovery, redirect chain. All 7 run in parallel with individual timeouts. Partial results on compone...
Subdomain discovery via certificate database — finds all subdomains with issued SSL certificates. Discovers API endpoints, staging servers, mail servers, and forgotten infrastructure. Deduplication and wildcard handling...
Provider identity is derived from the domain or repository in the source record. If two vendors share a host, they appear together here — that is a limitation of the data, not a statement about ownership.