For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
contact@agentmail.ccDiscord
DocumentationAPI ReferenceKnowledge BaseChangelog
DocumentationAPI ReferenceKnowledge BaseChangelog
    • Introduction
  • Getting Started
    • What is AgentMail?
    • What can I do with an inbox?
    • Creating your first inbox
    • Getting your API key
  • Agent Patterns
    • Handling inbound emails
    • Allowlists & blocklists
    • Managing threaded conversations
    • Human-in-the-loop workflows
    • Pods for multi-tenant email
    • Using labels to track state
  • Domains & Deliverability
    • Custom domain setup
    • SPF, DKIM, and DMARC setup
    • Emails going to spam
    • Warming Up
    • MX record conflicts
  • Troubleshooting
    • API 403 error
    • Rate limits
    • Preventing duplicate sends
    • Domain not verifying
    • Emails bouncing
    • Why are my emails not showing up?
  • DNS Guides
    • Cloudflare
    • GoDaddy
    • Route 53 (AWS)
    • Namecheap
LogoLogo
contact@agentmail.ccDiscord
On this page
  • Steps
  • Adding a TXT Record (SPF)
  • Adding a CNAME Record (DKIM)
  • Adding an MX Record (Receiving)
  • Verification
  • Common Cloudflare Issues
DNS Guides

DNS Guide: Cloudflare

Step-by-step instructions for adding AgentMail DNS records in Cloudflare.

Was this page helpful?
Edit this page
Previous

DNS Guide: GoDaddy

Step-by-step instructions for adding AgentMail DNS records in GoDaddy.

Next
Built with

Steps

  1. Log in to the Cloudflare dashboard
  2. Select your domain
  3. Go to DNS, then click Records
  4. Click Add Record for each record AgentMail requires

Adding a TXT Record (SPF)

FieldValue
TypeTXT
Name@ (or your subdomain)
ContentThe SPF value from AgentMail (e.g., v=spf1 include:agentmail.to ~all)
TTLAuto

If you already have an SPF record for your domain, do not create a second one. Instead, add include:agentmail.to to your existing SPF record. Having multiple SPF records on the same domain will cause authentication failures.

Adding a CNAME Record (DKIM)

FieldValue
TypeCNAME
NameThe DKIM selector from AgentMail (e.g., agentmail._domainkey)
TargetThe DKIM target from AgentMail
Proxy statusDNS only (grey cloud)
TTLAuto

DKIM CNAME records must have Cloudflare proxy disabled (grey cloud icon). If the orange cloud proxy is enabled, Cloudflare replaces the CNAME with its own proxy addresses, which prevents email servers from looking up your DKIM public key. This will cause DKIM verification to fail. If you see Error 1004 when saving, confirm that proxy is set to DNS only.

Cloudflare automatically strips your domain from the Name field. Enter only the subdomain portion (e.g., agentmail._domainkey), not the full agentmail._domainkey.yourdomain.com.

Adding an MX Record (Receiving)

FieldValue
TypeMX
Name@ (or your subdomain)
Mail serverThe MX target from AgentMail
Priority10
TTLAuto

If you want to receive emails on a subdomain to avoid conflicts with your existing email provider, enter the subdomain instead of @ in the Name field.

Verification

After adding all records, go back to the AgentMail Console and click Verify Domain.

Cloudflare DNS typically propagates within 1 to 5 minutes, making it one of the fastest providers for DNS updates.

Common Cloudflare Issues

  • Proxy must be off for CNAME records: The orange cloud (Proxied) means traffic goes through Cloudflare’s reverse proxy, which only handles HTTP/HTTPS. Email-related CNAME records like DKIM need direct DNS resolution and must be set to DNS only (grey cloud). If you forget, DKIM verification will silently fail.

  • CNAME flattening at root: Cloudflare automatically flattens CNAME records at the zone apex (root domain), returning A/AAAA records instead of the CNAME. This generally does not affect DKIM setup since the selector (e.g., agentmail._domainkey) is a subdomain. However, if you encounter unexpected behavior, consider using a subdomain for sending.

  • Existing SPF record: If you already have a TXT record starting with v=spf1, add include:agentmail.to before the ~all or -all in that existing record. Do not create a second SPF TXT record.

  • Error 1004 when adding CNAME: This error typically means the record cannot be proxied. Switch the proxy status to DNS only (grey cloud) and try saving again.

  • Name field auto-strips domain: Cloudflare removes the domain portion from the Name field automatically. If your DKIM selector is agentmail._domainkey, enter just that. Do not enter agentmail._domainkey.yourdomain.com, or the record will be created incorrectly.