Domain verification is required before you can send any emails through AhaSend. Unverified domains cannot send emails and will result in API errors.
Why Domain Setup Matters
Email receivers use multiple authentication methods to verify that emails are legitimate. When you properly configure your domain with AhaSend, you’re telling receiving servers that:- You own the domain and have the rights to send emails from it
- You’ve authorized AhaSend to send emails on behalf of your domain
- Your emails are authentic and not spoofed or malicious
Subdomain recommendation: Use a subdomain like
email.yourcompany.com
instead of your main domain for transactional emails. This isolates your transactional email reputation from marketing campaigns.Prerequisites
Before setting up your domain, make sure you have:- Access to your DNS provider (usually your hosting provider or domain registrar)
- An AhaSend account with verified email address
- The domain or subdomain you want to use for sending emails
Add Your Domain
Start by adding your domain to your AhaSend account:
- Log in to your AhaSend Dashboard
- Navigate to Domains in the sidebar
- Click “Add Domain”
- Enter your domain name (e.g.,
email.yourcompany.com
) - Click “Create Domain”
API Alternative: You can also add domains programmatically using our Domains API.
Configure DNS Records
Add the following DNS records to your domain. All records are provided in your domain details page with exact values for your domain.
SPF Record (Required)
SPF Record (Required)
Sender Policy Framework (SPF) authorizes AhaSend to send emails on your domain’s behalf.Record Type:
TXT
Purpose: Prevents email spoofing by specifying authorized sending serversIf you already have an SPF record, do not create a duplicate. Instead, add
include:_spf.ahasend.com
to your existing SPF record before the final mechanism (~all
or -all
).DKIM Record (Required)
DKIM Record (Required)
DomainKeys Identified Mail (DKIM) cryptographically signs your emails to verify authenticity.Record Type:
TXT
Purpose: Prevents email tampering and confirms sender identityThe exact DKIM record name and value are unique for each domain and provided in your dashboard. Copy them exactly as shown.
DMARC Record (Required)
DMARC Record (Required)
Domain-based Message Authentication, Reporting and Conformance (DMARC) provides policy guidance for email authentication failures.Record Type:
TXT
Purpose: Protects your domain from email spoofing and phishing attacksThis DMARC policy tells receiving servers to quarantine emails that fail authentication and send reports to AhaSend for monitoring.
Return-Path Record (Highly Recommended)
Return-Path Record (Highly Recommended)
Return-Path specifies where bounce messages and delivery notifications should be sent.Record Type:
CNAME
Purpose: Improves deliverability by providing a communication channel for bounce handlingWhile not strictly required, the Return-Path record significantly improves deliverability by allowing AhaSend to properly handle bounces and feedback loops.
Email Tracking Record (Optional)
Email Tracking Record (Optional)
Tracking Domain ensures tracking URLs in your emails come from your domain instead of AhaSend’s.Record Type:
CNAME
Purpose: Improves deliverability and maintains brand consistency for tracked linksEmail tracking is disabled by default and must be explicitly enabled in your account settings, even if you configure the tracking domain.
MX Record (Recommended)
MX Record (Recommended)
Mail Exchanger (MX) specifies the mail server responsible for receiving emails for your domain.Record Type:
MX
Purpose: Required for receiving emails, recommended for better sending reputationWhile not required for sending emails, some receiving servers penalize domains without MX records. Adding this record improves overall deliverability.
Wait for DNS Propagation
DNS changes can take time to propagate across the internet:
- Typical time: 5-30 minutes
- Maximum time: Up to 48 hours
- Check status: Use online DNS checkers to verify your records are live
Pro tip: Use tools like DNS Checker or What’s My DNS to verify your records have propagated globally.
Verify Your Domain
Once your DNS records are live, verify your domain in AhaSend:
- Return to your domain details page in the dashboard
- Click “Check DNS” to run verification
- Wait for confirmation - this usually takes just a few seconds
- Look for the green checkmarks next to each record type
Success! When all records show green checkmarks, your domain is verified and ready to send emails.
If verification fails, double-check that:
- All DNS records are added exactly as shown
- DNS changes have had time to propagate
- You don’t have conflicting DNS records
DNS Provider Guides
Need help adding DNS records? Here are guides for popular providers:Cloudflare
Manage DNS records in Cloudflare dashboard
GoDaddy
Add TXT and CNAME records in GoDaddy
Namecheap
Configure email authentication records
Route 53
AWS Route 53 record management
Google Domains
Add DNS records in Google Domains
Other Providers
Contact support for help with your DNS provider
Manage Domains with API
For programmatic domain management, use our comprehensive Domains API:Create Domain
Add new domains programmatically
List Domains
Retrieve all your configured domains
Get Domain Details
Check domain verification status
Delete Domain
Remove domains from your account
Troubleshooting
DNS Records Not Verifying
DNS Records Not Verifying
Common causes and solutions:
- Wait longer: DNS propagation can take up to 48 hours
- Check record values: Ensure exact copy-paste from dashboard (no extra spaces)
- Verify record type: TXT records for SPF/DKIM/DMARC, CNAME for others
- Remove duplicates: Don’t create multiple SPF records
- Check with DNS tools: Use online DNS checkers to verify records are live
Existing SPF Record Conflicts
Existing SPF Record Conflicts
If you already have an SPF record:
- Don’t create a duplicate - domains can only have one SPF record
- Modify your existing record by adding
include:_spf.ahasend.com
- Place it before the final mechanism (
~all
or-all
)
Subdomain vs Root Domain
Subdomain vs Root Domain
Understanding the difference:
- Root domain:
yourcompany.com
(affects all subdomains) - Subdomain:
email.yourcompany.com
(isolated setup)
Still Having Issues?
Still Having Issues?
We’re here to help:
- Check our status page for any ongoing DNS issues
- Contact support at [email protected]
- Include your domain name and specific error messages
- Attach screenshots of your DNS configuration if helpful
What’s Next?
Once your domain is verified, you’re ready to start sending emails:Send Your First Email
Follow our quickstart guide to send emails via API or SMTP
Create SMTP Credentials
Generate credentials for your applications
Create API Keys
Track email delivery and engagement events
Enable Tracking
Monitor opens and clicks on your emails
Domain setup complete? Your domain is now ready to send emails through AhaSend. Test it out with our quickstart guide to send your first email!