curl · Python · JavaScript · any language · REST API

The DNSai REST API

No AI needed. Call DNSai from your own code, scripts, data pipelines or servers with an API key and get JSON back: your domains with email gateway, SPF, DKIM and DMARC, full DNS scan results, WHOIS, website technologies, subdomains, Deep Scan reports and a filtered feed of every DNS change. Every endpoint is described in an OpenAPI 3.1 spec.

What you can do with the REST API

Example answers use made-up domains.

“GET /api/v1/domains/?email_gateway=Mimecast&limit=5000”

Up to 5,000 of your domains that use Mimecast, each with DMARC policy, SPF summary and last scan time.

“GET /api/v1/changes/?since_id=123456”

Every DNS change since the last one you processed, oldest first, with next_since_id to store for the next poll.

“POST /api/v1/domains/lookup/ with {"domains": ["adatum.example", "litware.example"]}”

A compact profile of each domain in one call: email gateway, DMARC, SPF, nameservers and website platform.

Connect in 3 steps (about 5 minutes)

Create an API key under Settings > API Keys and keep it in an environment variable.
Send it as "Authorization: Bearer <key>" on any request to /api/v1/.
Page through results with limit and offset, or poll the change feed with since_id.

Signed-in Enterprise customers get the exact click-by-click steps and ready-to-paste configuration for REST API, a one-click API key for it, and a live connection check.

REST API requirements: Any HTTPS client. DNSai Enterprise plan.

Good for

Nightly sync of your domains into a data warehouse or CRM
Alerting when a monitored company switches email provider
Bulk enrichment of a lead list with email gateway and DMARC policy
Feeding DNS changes into a SIEM or ticketing system

Security

Requests use HTTPS with an API key in the Authorization header. Give each system its own key with an expiry, and an IP allowlist for your own servers.
Account and organization owners can make API keys and assistants read-only, so they can read your data but never change it or start scans.
Starting a credit-spending Deep Scan always needs an estimate and your explicit confirmation.
DNSai data comes from public DNS and web records. Your watchlists, notes and tags stay private to your account and are only shared with an AI tool you connect yourself.

Questions

Do I need an AI tool to use DNSai data?

No. The REST API is a standard HTTPS and JSON API that works from any language or tool. The MCP server for AI assistants uses the same data and the same limits.

Is there an OpenAPI spec?

Yes, an OpenAPI 3.1 spec at /api/v1/openapi.json describes every API-key endpoint, so you can generate a client in your language or import it into Postman.

Connect REST API to DNSai

The API and AI connectors are included with DNSai Enterprise plans. Every member of your organization shares one set of limits, and every call counts from the first one.

Other integrations

Last checked 2026-10-30.