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 Namecheap Issues
DNS Guides

DNS Guide: Namecheap

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

Was this page helpful?
Edit this page
Previous

Changelog

Next
Built with

Steps

  1. Log in to your Namecheap account
  2. Go to Domain List → click Manage next to your domain
  3. Select the Advanced DNS tab
  4. Click Add New Record for each record AgentMail requires

Make sure your domain is using Namecheap BasicDNS or Namecheap PremiumDNS as its nameserver. If you’ve pointed your nameservers to another provider (e.g., Cloudflare), you’ll need to add records there instead.

Adding a TXT Record (SPF)

FieldValue
TypeTXT Record
Host@ (or your subdomain)
ValueThe SPF value from AgentMail (e.g., v=spf1 include:agentmail.to ~all)
TTLAutomatic

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 will cause validation failures.

Adding a CNAME Record (DKIM)

FieldValue
TypeCNAME Record
HostThe DKIM selector from AgentMail (e.g., agentmail._domainkey)
ValueThe DKIM target from AgentMail
TTLAutomatic

Namecheap automatically appends your domain to the Host field. Enter only the subdomain portion. For example, enter agentmail._domainkey, not agentmail._domainkey.yourdomain.com.

Adding an MX Record (Receiving)

FieldValue
TypeMX Record
Host@ (or your subdomain)
ValueThe MX target from AgentMail
Priority10
TTLAutomatic

If you want to receive emails on a subdomain to avoid conflicts with your existing email provider, use the subdomain (e.g., mail) instead of @ in the Host field.

Verification

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

Namecheap DNS typically propagates within 15 to 30 minutes, but in some cases it can take up to a few hours. If verification doesn’t succeed immediately, wait and try again.

Common Namecheap Issues

  • Host field auto-appends domain: Namecheap adds your domain automatically. If your DKIM selector is agentmail._domainkey, enter just that, not the full agentmail._domainkey.yourdomain.com. If you enter the full value, the actual record will end up as agentmail._domainkey.yourdomain.com.yourdomain.com.

  • 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.

  • Wrong nameserver: If your domain uses Custom DNS nameservers (e.g., pointing to Cloudflare or Route 53), records added in the Namecheap Advanced DNS panel will have no effect. Add your records at the provider that controls your nameservers instead.

  • Propagation delays: Unlike some providers, Namecheap propagation can take 15 to 30 minutes. If verification fails, wait and retry before troubleshooting further.