Overview
This endpoint retrieves all DNS records that are required for domain verification. It includes both the records that need to be added to your DNS provider and their current verification status.Authentication
Bearer token for API authentication. Format:
Bearer YOUR_API_KEY
Parameters
The unique identifier of the domain to retrieve DNS records for.
Response
The unique identifier of the domain.
The domain name (e.g., “example.com”).
Array of DNS records required for domain verification.
Examples
Request
Response
Error Responses
DNS Record Types
The following DNS record types are commonly used for domain verification:TXT Records
Used for domain verification and AWS SES identity verification.MX Records
Used to route emails to the correct mail servers.SPF Records (TXT)
Used for email authentication to specify which servers can send emails on behalf of your domain.SPF records help prevent email spoofing by specifying authorized mail servers. The
~all
indicates a “soft fail” for unauthorized servers, while -all
would be a “hard fail”.DMARC Records (TXT)
Used for email authentication policy to specify how receiving servers should handle emails that fail SPF or DKIM checks.DMARC records provide reporting and policy instructions. The
p=none
policy is recommended for monitoring, while p=quarantine
or p=reject
provide stronger protection once you’ve verified your email authentication setup.CNAME Records
Sometimes used for specific subdomain configurations.Verification Status
Each DNS record has a verification status that indicates whether it’s properly configured:1
Not Verified (isVerified: false)
The DNS record has not been verified yet or is incorrectly configured.
Check that the record has been added to your DNS provider with the exact name and value.
2
Verified (isVerified: true)
The DNS record has been verified and is correctly configured.
This record is properly set up and contributing to domain verification.
Common DNS Configuration
Here’s how to configure the most common DNS records:Adding TXT Records
- Log into your DNS provider (Cloudflare, GoDaddy, etc.)
- Navigate to DNS management
- Add a new TXT record with the exact name and value provided
- Save the changes
Adding MX Records
- Remove any existing MX records for the domain
- Add the new MX record with the provided hostname and priority
- Ensure no conflicting MX records exist
Important Notes
DNS propagation can take up to 24 hours, but typically completes within 1-2 hours. Check the
lastChecked
timestamp to see when verification was last attempted.Use the domain’s GET endpoint with
check=true
to trigger a real-time verification check of all DNS records.All required DNS records must be verified before the domain can receive emails. Missing or incorrect records will prevent email delivery.
Troubleshooting
If DNS records are not verifying:- Check DNS propagation: Use online DNS lookup tools to verify records are visible
- Verify exact values: Ensure the name and value match exactly (case-sensitive)
- Remove conflicting records: Delete any existing MX or CNAME records that might conflict
- Wait for propagation: DNS changes can take time to propagate globally
Related Endpoints
- Trigger verification check:
GET /api/v2/domains/{id}?check=true
- View domain status:
GET /api/v2/domains/{id}
- List all domains:
GET /api/v2/domains
Notes
- DNS records are automatically created when a domain is added
- The
isVerified
status is updated during verification checks - All required records must be verified for the domain to become active
- DNS records are automatically deleted when a domain is removed
- Record verification happens automatically but can be triggered manually
1.0 - ✅