Domain Intel
Domain in, the full public profile out: WHOIS, DNS, mail policy, TLS certificate and subdomains. Every call is paid inside the request over x402. No signup, no API key, no dashboard.
Endpoint
| Route | Price | What it does |
|---|---|---|
POST /domain |
0.003 USDC | Full domain profile: WHOIS, DNS records, mail setup, TLS certificate, subdomains and registrability in one paid call. |
How a call works
curl -s -X POST https://dns.netzhandwerker.de/domain \
-H "Content-Type: application/json" \
-d '{"domain":"example.com","subdomains":true}'
The first call answers with HTTP 402 and the accepted payment terms. An x402 capable client signs the terms and repeats the request; the answer arrives in the same round trip. Any x402 client library, or an MCP client pointed at /mcp, handles this without further setup.
What one answer contains
- WHOIS: registrar, creation, expiry, days remaining, status codes.
- DNS: A, AAAA, CNAME, MX, NS, TXT, CAA, SOA.
- Mail: SPF and DMARC with parsed policy, probed DKIM selectors, MTA-STS, provider.
- TLS: issuer, validity, chain, SAN list, trust result.
- Subdomains from Certificate Transparency.
- Nameserver operator and registrability.
Rules we follow
- Per TLD query budgets are respected; one lane per registry.
- A throttled registry yields
unknownfields with a reason, never a guess. - No invented fields. A silent DKIM selector is not reported as missing DKIM.
- Profiles cached 6 hours, WHOIS 24 hours.
- Public data only. No port scanning, no access control bypass.
Discovery
- /openapi.json
- /.well-known/x402
- /mcp — Model Context Protocol
- /pricing
- /llms.txt
- /health · /readiness
Operational figures
Rolling 30 day window, updated live: 0 requests, 0 of them paid, 0 settlements, 0 USDC volume, 17 profiles in cache.