PUBLIC · READ-ONLY · NO API KEY
Email DNS API
Use standard HTTP GET requests to inspect public email DNS configuration. The API returns JSON, runs on Cloudflare Workers, and requires no account or API key.
Endpoints
/api/analyze?domain=example.com— combined report/api/spf?domain=example.com— SPF records/api/dmarc?domain=example.com— DMARC records/api/mx?domain=example.com— MX hosts and priorities/api/dkim?domain=example.com&selector=google— DKIM TXT lookup (selector required)/api/mta-sts?domain=example.com— MTA-STS DNS and HTTPS policy/api/tls-rpt?domain=example.com— TLS reporting records/api/bimi?domain=example.com— BIMI record (optional selector)
All URLs are relative to https://howto.email. For combined analysis, optionally provide dkim_selector to include one known DKIM selector.
Try a request
curl "https://howto.email/api/analyze?domain=google.com"Response and limitations
Responses include the queried domain, records, and whether matching records were found. Combined analysis also provides informational findings. Failed upstream checks are identified separately. HTTP 400 indicates invalid input, 429 indicates rate limiting, and 502 indicates an upstream lookup failure.
Results are public DNS observations, not an email security certification. DKIM requires a known selector. MX lookups do not test SMTP connectivity, and BIMI checks do not validate images or certificates.
Use with AI assistants
An AI assistant that can fetch arbitrary web URLs may be able to read an API response directly. Merely pasting a URL into a chat does not guarantee that its web tools can access or call the API. For native tool access, see the MCP server.
Usage
Responses support cross-origin GET requests. Successful responses may be cached for five minutes. Requests share the MCP Worker's per-client rate limit. The service is offered without availability guarantees; do not submit sensitive information in query parameters.