Anthropic · Sign in with OAuth

DNSai for Claude

Add DNSai to Claude as a custom connector and ask about your domains in plain English: email providers, SPF, DKIM and DMARC posture, what changed in DNS this week, and Deep Scan findings across a company's subdomains. Claude signs in with OAuth, so there is no key to paste.

What you can ask Claude

Example answers use made-up domains.

“Which of my domains switched email gateway in the last 7 days?”

Three did: northwind.example moved from Proofpoint to Microsoft 365 on Oct 24, tailspin.example from Google Workspace to Mimecast on Oct 26, and fabrikam.example dropped its MX records entirely on Oct 27.

“Is contoso.example safe to send mail from?”

Mostly. SPF ends in -all with 6 of 10 lookups used, DKIM is published for two selectors, but DMARC is p=none, so spoofed mail is still delivered. Moving to quarantine is the next step.

“Summarise the latest Deep Scan of woodgrove.example.”

214 subdomains found, 181 live. Two findings matter: dev.woodgrove.example serves an expired certificate, and four hosts point at a cloud provider the main domain no longer uses.

Connect in 3 steps (about 2 minutes)

In Claude, open Customize (or Settings) and choose Connectors, then Add custom connector.
Paste the DNSai MCP server address and add it.
Click Connect, sign in to DNSai and approve access.

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

Claude requirements: Any Claude plan (Free allows one custom connector). On Team and Enterprise an owner adds it under Organization settings first. DNSai Enterprise plan.

Good for

Weekly briefings on DNS and email-gateway changes across your portfolio
Auditing a domain's SPF, DKIM and DMARC before a migration
Summarising an Organization Deep Scan for a security review

Security

Claude signs in with OAuth 2.1 and PKCE. You approve the connection in DNSai and can revoke it at any time; no key is pasted anywhere.
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 API key for Claude?

No. Claude connects with OAuth: you sign in to DNSai and approve access, and you can disconnect at any time.

Does it work in the Claude mobile app?

Yes. Connectors added on the web or in Claude Desktop are available in the mobile apps.

Can Claude change anything in my account?

Only if you allow it. Account owners can make AI assistants read-only, and starting a Deep Scan always needs a cost estimate and your confirmation.

Connect Claude 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-29.