Verify your sending domain to keep email out of spam.
Authenticate your sending domains with DKIM, SPF alignment on a custom return-path, DMARC, and branded tracking links so password resets, receipts, and campaigns reach the inbox instead of the spam folder. Register domains in the dashboard or onboard multi-tenant customer domains via API, with automated DNS checks that verify in minutes.
news.example.com
Sending identity
Ready to send
Verified
Sign your messages
Verified
Return-path
Align your SPF identity
Verified
Check the domain policy
Configured
From: Fieldnotes
Example domain. Add the records Bird generates for your own domain.
Stop losing emails to unaligned DNS records.
Mailbox providers like Gmail, Outlook, and Yahoo filter or reject messages when your sending domain lacks aligned SPF, DKIM, and DMARC records. On the Bird Email API, registering a domain generates the exact DNS records to publish, signs outbound mail automatically, and monitors your configuration so broken records are caught before deliverability drops.
Built to protect sender reputation across domains and brands.
Generate the required DNS records, isolate traffic by subdomain, and automate domain onboarding without manual DNS polling.
- 01
Verify DNS records automatically in minutes.
Copy the generated hostnames and values into Cloudflare, Route 53, or your registrar. Bird checks propagation automatically on a backoff schedule and enables sending as soon as your records resolve.
- 02
Align DKIM, SPF return-path, and DMARC without touching your root SPF.
Bird signs outbound mail with a unique DKIM key, verifies your DMARC policy, and aligns SPF through a custom return-path CNAME so you stay clear of the 10-lookup SPF limit on your root domain.
- 03
Separate transactional, marketing, and corporate reputation.
Send from dedicated subdomains so promotional campaigns, transactional receipts, and your team’s corporate email each maintain an independent sender reputation.
- 04
Onboard multi-tenant customer domains via API.
Building a platform that sends email on behalf of your customers? Register domains programmatically, return the generated DNS records in your own settings UI, and trigger or forward verification instructions by API.
- 05
Inspect live DNS records and DMARC reports.
Audit a domain’s live DMARC, SPF, DKIM, BIMI, and MX records to see what fails and why, or paste raw DMARC aggregate XML reports to translate authentication failures into plain language.
Register a domain and get ready-to-paste DNS records in one call.
Create a sending domain from the dashboard, CLI, or REST API when setting up your own app or onboarding a customer’s domain inside your product. Bird returns the exact DNS records to publish: an organization-specific DKIM key, a custom return-path CNAME that handles bounces and SPF alignment, a DMARC policy record, and an optional CNAME for branded tracking links.
$ bird email domains create mail.acme.com \
| jq -c '.status, (.dns_records[] | {purpose, type, host})'
"pending"
{"purpose":"dkim","type":"TXT","host":"bird1._domainkey.mail.acme.com"}
{"purpose":"return_path","type":"CNAME","host":"send.mail.acme.com"}
{"purpose":"dmarc","type":"TXT","host":"_dmarc.mail.acme.com"}
{"purpose":"tracking","type":"CNAME","host":"links.mail.acme.com"}
# Publish them, then check: bird email domains verify <domain-id>
Track opens and clicks on your own branded domain.
Shared tracking domains can trigger spam filters and look suspicious when recipients hover over a link. Publish the optional tracking CNAME to serve open pixels and rewritten click URLs over HTTPS under your own hostname so link reputation stays with your brand.
Tracking readiness stays separate from your ability to send. Your domain can deliver email as soon as DKIM, the return-path CNAME, and DMARC verify, and you can enable open and click tracking later once the tracking CNAME is in place.
Because rewritten URLs add a redirect hop and change the address shown on hover, tracking remains opt-in per domain. Enable it on marketing and lifecycle subdomains where engagement metrics matter, and leave it off on transactional subdomains that send password resets or security codes.
Continuous DNS monitoring that tolerates transient blips.
You do not need to build a polling loop to find out when a DNS record propagates or when a teammate accidentally edits a zone file. Bird checks new domains within minutes of registration, steps down to hourly checks over the first three days, and re-verifies active domains daily. If a verified record fails a check, Bird places the domain in a 24-hour warning grace period, alerts your workspace, and retries hourly so a brief DNS outage does not interrupt production sending.
Explore the domain authentication guides.
Follow the sending domains guide to register domains via API, configure custom return-path and tracking hostnames, or share DNS records with your IT team, and read the DKIM, SPF & DMARC guide for record formats and registrar setup steps.
Questions about sending domains
What records do I need to verify a domain, and how long does it take?
What does the DMARC record actually do?
Can I send from a subdomain, or use more than one domain?
From authentication to delivery
Scale without
losing control.
Organize teams in workspaces, control API access, and trace changes through audit logs.