DNS & Email Security API
GET /api/dns $0.002 per call
USDC on Base · x402
DNS and domain intelligence: A/AAAA/CNAME, MX (sorted), NS, TXT, SOA records plus email security posture — SPF record, DMARC policy, and DKIM selector probing. For deliverability, security, and research agents. ?domain=example.com
Parameters
| Name | In | Description | |
|---|---|---|---|
domain | query | required | Domain to inspect, e.g. example.com |
Example request
curl "https://api.webbersites.com/api/dns?domain=example.com"
# first call returns 402 + payment requirements; an x402 client pays and retries automaticallyExample response
{
"domain": "example.com",
"resolves": true,
"records": {
"a": [
"93.184.215.14"
],
"mx": [
{
"exchange": "mail.example.com",
"priority": 10
}
],
"ns": [
"a.iana-servers.net"
],
"txt": [
"v=spf1 -all"
]
},
"email": {
"mail_configured": true,
"spf": {
"present": true
},
"dmarc": {
"present": true,
"policy": "reject"
},
"dkim": {
"found_selectors": []
}
}
}MCP tool: get_dns — via npx -y webbersites-x402-mcp (local, key stays on your machine) or the remote endpoint https://api.webbersites.com/mcp.
How payment works
There is no signup and no API key. Call the endpoint; it replies 402 Payment Required with machine-readable payment requirements. Your client signs a USDC transfer authorization (EIP-3009, gasless) and retries with the X-PAYMENT header — @x402/fetch does this automatically. See the overview for a working snippet.