Help Domains and sending
DNS records
Every sending domain needs a few DNS records. They let Amazon SES verify the domain and let mailbox providers trust its email. This page lists each record and what it is for. It also covers how to publish them (with Cloudflare, by hand or through your DNS admin), how SendForever checks them, and how it handles DMARC policy and reports.
The records a domain needs
Open the domain's Settings and its DNS records tab. Each record shows its type, its name and its full value, each with a copy button. Records are grouped under the check that says whether the DNS publishes them. An MX record shows its Priority on a separate line, because most DNS providers ask for it separately from the mail server. The examples below use example.com. The region is the one your AWS account is connected in.
| Record | Type | Name | Value |
|---|---|---|---|
| DKIM (three records) | CNAME | <token>._domainkey.example.com |
<token>.dkim.amazonses.com |
| MAIL FROM | MX | mail.example.com |
10 feedback-smtp.<region>.amazonses.com |
| SPF | TXT | mail.example.com |
v=spf1 include:amazonses.com ~all |
| DMARC | TXT | _dmarc.example.com |
v=DMARC1; p=none; rua=mailto:<address>; adkim=s; |
| SPF (domain) | TXT | example.com |
Only once you choose who sends as the domain |
| BIMI | TXT | default._bimi.example.com |
Only once you upload a brand logo |
| Links host certificate | CNAME | Given by Certificate Manager | Only while setting up a links host |
| Links host | CNAME | Your links host, such as links.example.com |
The CloudFront endpoint in your AWS account |
A domain that already had a custom MAIL FROM domain in Amazon SES keeps it, so its MAIL FROM records use that name instead of mail.example.com.
DKIM
The three CNAME records point at the keys Amazon SES holds for the domain (Easy DKIM, 2048-bit). Amazon SES signs every email with these keys, which proves the email came from your domain. The DKIM signing check waits until Amazon SES finds the records. It fails if Amazon SES cannot find them, usually because a value does not match exactly or the domain was added to the name twice.
If you use your own DKIM key in Amazon SES instead, there are no CNAME records to add. Publish the public key as a TXT record at your selector followed by ._domainkey. The check reads that selector.
MAIL FROM and its SPF
The MX and TXT records on mail.example.com make it the domain that bounces return to. They also authorize Amazon SES to send for it. This is what makes SPF align with your domain for DMARC. Until Amazon SES finds the MX record, emails fall back to amazonses.com and SPF does not align. The Custom MAIL FROM (SPF alignment) check tracks both records.
The SPF record on mail.example.com ends in ~all (soft fail) on purpose, as Amazon SES documents it. Only Amazon SES sends from that domain, and DMARC is what stops anyone else from using your domain, so -all would add no protection there. Some checkers flag ~all on mail.example.com as a warning because they read the record on its own. You can leave it as it is. The SPF record SendForever prepares for the domain itself, once you choose its senders, does end in -all.
DMARC
The TXT record at _dmarc.example.com tells mailbox providers what to do with email that claims to come from your domain but fails DKIM and SPF. It also says where to send reports about that email. Gmail and Yahoo require one for bulk senders. The record SendForever prepares holds only the policy (p=), the report address (rua=) and strict DKIM alignment (adkim=s). The DMARC section below explains the choices.
A subdomain such as news.example.com with no DMARC record of its own is covered by its parent's record, through the parent's sp= or else its p=. SendForever then prepares no record for the subdomain and says which policy applies. If you set up DMARC for the subdomain anyway, the policy starts no weaker than the parent's.
SPF on the domain itself
Amazon SES never needs an SPF record on example.com, because its SPF is on the MAIL FROM domain. But without one, anyone can use your domain as a bounce address. Click Choose senders under SPF on the domain itself and pick one of these:
- I am not sure yet: SendForever prepares no record.
- Only Amazon SES sends email as this domain: the record is
v=spf1 -all, which allows no other service. If DMARC is at p=none, this choice also moves it to p=quarantine. That is safe when Amazon SES is the only sender. - Other services also send as this domain: add each service's SPF domain under SPF domain of each service, one per line. Enter it as it appears after
include:in the service's DNS setup guide (for examplespf.migadu.comfor Migadu or_spf.google.comfor Google Workspace). The record lists each one as aninclude:and ends in-all, so the list must be complete. Email from a service you leave out lands in spam.
Under What changes, the dialog shows Today beside Once published. Both list the SPF record, who else may send and the DMARC policy, with the changes marked. Below them, the dialog says what this means for your email. With other services, the box starts with what the domain already publishes. Nothing changes in your DNS until you save and publish.
If the domain receives mail through Cloudflare Email Routing, or you set up forwarding, the record also includes _spf.mx.cloudflare.net. The check passes when the domain has exactly one SPF record. It fails with two or more, because receivers treat that as no SPF at all.
If receivers cannot read the domain's one SPF record (for example because of the dot in -all.), the check needs attention. This does not stop the domain from sending, because the SPF of emails sent through Amazon SES is on the MAIL FROM domain. But email from anything else that sends as the domain can land in spam. If stray punctuation is the only problem, the card shows the corrected record to replace it with, and publishes it to Cloudflare if SendForever is authorized there. Otherwise the card names the problem, and you fix it at your DNS provider or by choosing the senders.
Receivers also give up on an SPF record that takes more than 10 DNS lookups to check. Each include:, a, mx, ptr, exists and redirect= counts as one, and so do those inside each include. Google Workspace or Microsoft 365 alone take several. Past 10, the check needs attention, with the same effect as above. Remove the services that no longer send as the domain under Choose senders, or at your DNS provider.
Receiving mail (MX)
Domain can receive replies passes when the domain has an MX record. Without one, replies and mail to postmaster@ bounce, and some filters hold that against you. You can use your own mailbox. Or click Set up forwarding, choose Forward with Cloudflare Email Routing and enter the mailbox in Forward to. Then pick Only the essential ones (postmaster@, abuse@, the address you send from, and the DMARC report address if it is on this domain) or Everything (catch-all). Cloudflare adds its own MX records. When the records are added to Cloudflare, SendForever turns routing on and adds the rules. Cloudflare emails the destination once to confirm it. Forwarding needs the domain's DNS on Cloudflare. If you later choose I handle inbound mail myself, the existing rules in Cloudflare stay as they are.
Brand logo (BIMI)
The Brand logo (BIMI) check appears once DMARC is at p=quarantine or p=reject. Click Upload logo and pick a square SVG Tiny PS file under 32 KB. Its svg element declares version="1.2" and baseProfile="tiny-ps", and has a title with your brand name and a viewBox (or a width and height). The file has no stylesheets (style elements or attributes), scripts, links to other files or embedded images. If a file breaks one of these rules, SendForever refuses it and says what to change. The BIMI Group's guide explains how to make the file, and its SVG Assistant checks and fixes one you already have. SendForever hosts the logo in your AWS account, served by CloudFront, and adds the BIMI record that points at it. Gmail and Apple Mail also require a Verified Mark Certificate (a=) before they show a BIMI logo, and the record SendForever prepares has none. Without one, Yahoo shows the logo to senders with a good reputation, and Apple Mail can show a logo through Branded Mail instead (see below). Remove logo deletes the file and its record. When SendForever is authorized on Cloudflare, the record is removed from Cloudflare at once. Otherwise it is marked for removal. If your stack is too old to host logos, the check says to update it.
Links host
When you set up a links host (see Domains), Certificate Manager asks for the Links host certificate CNAME to prove the domain is yours. The Links host CNAME points the host at CloudFront. Once the host setup starts, the DNS records tab lists both under Links host. Add records to Cloudflare publishes both, and Copy all, Download zone file and Send to your DNS admin include them.
Publish the records
With Cloudflare
If the domain is on Cloudflare, the DNS records tab offers Add the records automatically with Cloudflare while there are records to add or change.
- Click Add records to Cloudflare.
- Choose how long the connection lasts: For one hour or Until you disconnect, then click Connect.
- Cloudflare asks you to allow SendForever to read and edit DNS (and Email Routing) on the accounts you choose. Approve it.
- Back on the domain's page, SendForever adds the records right away. A message says how many were added or updated.
SendForever finds the Cloudflare zone of the domain or of a parent domain. It adds missing records, updates wrong ones and leaves correct ones alone. It only matches a TXT record with one of the same kind (SPF, DMARC, BIMI), so it never touches a site verification TXT on the same name. If you already publish a DMARC record, SendForever replaces it with its own once the domain has DMARC choices. SendForever takes those choices from your record the first time it reads the domain: your policy, and your report address (or SendForever's, if you have none). Other tags in your record are not kept. Records SendForever adds carry the comment "Managed by SendForever" and use Cloudflare's automatic TTL. Its CNAMEs are set to DNS only.
The authorization belongs to the team. While it is live, every choice you save that changes a record is published at once. You can revoke it from your Cloudflare profile, or with Disconnect Cloudflare in the team's Settings. There you also see how long the authorization lasts.
- For one hour: SendForever keeps nothing that could renew it, so after it expires Cloudflare asks you to confirm again.
- Until you disconnect: SendForever keeps an encrypted refresh token that renews the authorization by itself. Anyone who can manage the team's domains can then change DNS through it at any time, on the Cloudflare accounts you allowed.
To avoid the authorization, click Use an API token instead:
- In Cloudflare, go to "My Profile" → "API Tokens" and choose "Create Token".
- Use the "Edit zone DNS" template and, under "Zone Resources", pick only your domain.
- Paste the token in Cloudflare API token and click Add records to Cloudflare. SendForever uses the token once and never stores it.
At another DNS provider
SendForever reads the domain's name servers and names the provider. For known providers it adds a link such as Open GoDaddy. The known providers are GoDaddy, Namecheap, Amazon Route 53, Squarespace, Google Cloud DNS, OVHcloud, DigitalOcean, Vercel, Hostinger, Porkbun, Gandi, IONOS, Name.com, DNSimple, Azure DNS, Hetzner and Akamai Linode. Add each record there with the copy buttons. That includes a domain in Route 53: SendForever never changes records there, even in the AWS account you connected. If your provider adds the domain to names automatically, leave .example.com off the name. Once the last check finds every record in the DNS, the tab says the records are published.
While there are records left to add, Copy all copies every record as a BIND zone file. Download zone file saves it as a .zone file for providers that can import one.
Send the records to your DNS admin
While there are records left to add, click Send to your DNS admin to get a link for whoever runs your DNS. The link needs no account and works for a week. Its page shows only the domain's records, what the last check found for each, and the changes still to make. For a wrong record, it also shows what the DNS publishes instead. Copy link copies the link so you can send it however you like. The page also has Copy all as a zone file.
How SendForever checks the records
Amazon SES only says whether DKIM and MAIL FROM verified. So SendForever also looks up every record itself, through Cloudflare's public DNS resolver over HTTPS. That resolver does not keep reporting a record as missing after you add it. Each record shows one of these:
- Verified: the DNS publishes the expected value. Case, spacing and a trailing dot or semicolon do not matter.
- Wrong value: something else is published. Under the record, Published now: shows what the DNS has, one record per line. A record marked Change shows it too, so you see what to replace.
- Not found: nothing is published at that name.
- Unknown: the resolver could not answer, so SendForever assumes nothing. It looks the record up again at the next check.
A wrong record also says the likely reason:
- A different value is published: replace it with the value shown.
- Two or more SPF records on the same name: keep only one.
- The record was published with the domain added twice, such as
mail.example.com.example.com: enter the name without the domain at the end. - A CNAME proxied by Cloudflare (orange cloud) hides its target from Amazon SES: switch it to DNS only (grey cloud).
SendForever's DMARC record holds only p=, rua= and adkim=s. So a DMARC record with other tags shows Wrong value, even when the DMARC policy check passes. Publishing SendForever's record replaces it.
If SendForever cannot reach the resolver at all, the page says We could not check this domain just now and gives the reason. It keeps showing the checks from last time.
Propagation and verification
Amazon SES usually finds new records within a few minutes, and within 72 hours at most. While a check is waiting, the domain's page checks again every 30 seconds as long as it is open. Check again asks Amazon SES to look right away. Right after a publish to Cloudflare, the DNS can show the old record for a while. For an hour after the publish, the DMARC policy check says a stricter policy was published while the DNS still shows the old one.
After 72 hours without finding the records, Amazon SES stops looking and the domain shows Failed. Fix the records, then click Restart verification. A domain on Easy DKIM can get new DKIM records when verification restarts. With a live Cloudflare authorization, they are published at once. Otherwise they are listed as changes to make.
Changes waiting to be published
Several things can change the records a domain needs: a DMARC, senders or forwarding choice, a brand logo, a links host, a restarted verification, or a DMARC step SendForever prepared. SendForever saves each change first. With a live Cloudflare authorization, a change you make on the domain's page is published at once, but a DMARC step SendForever prepared waits for you. Otherwise the tab shows DNS changes waiting to be published and marks each record Add, Change or Remove. Only two records are ever marked for removal: a brand logo's, and the Links host record of a host you stopped using.
A change stops waiting once it is published to Cloudflare. Records changed by hand also stop waiting once the DNS shows them. While a Cloudflare authorization is live, a removal waits for the next publish to Cloudflare.
DMARC
Where reports go
Click Set up DMARC (or Change DMARC) under DMARC policy. Under Where should reports go?, choose:
- SendForever (recommended): reports go to a private address for the domain at
dmarc.sendforever.net. SendForever reads them, shows who sends as the domain, and tells you when a stricter policy is safe. - A reporting service already set up in DNS: for example Cloudflare DMARC Management. SendForever keeps the address that service published and only manages the policy. It refuses this choice until a report address is published.
- An email address: enter it in Send reports to. Expect about one XML report per mailbox provider per day.
When SendForever first reads a new domain that publishes no report address, it prepares a DMARC record that sends the reports to SendForever. That record keeps the policy already published (or p=none), and Prepare a stricter policy when it is safe is turned on. If the domain already publishes a report address, SendForever keeps it, with its policy. A domain that is removed and added again gets back the SendForever address it still publishes. That inbox accepts reports for any domain, so you do not need to publish an extra record to allow them.
Policy
Under Policy, choose Monitor only (p=none), Send failures to spam (p=quarantine) or Reject failures (p=reject). The one to pick today is marked (recommended). If Amazon SES is the only sender, that is the next step. Otherwise it is the policy the domain is on now. If you pick a weaker policy than the saved one, the dialog explains it and Save asks you to confirm it.
The DMARC policy check:
- Fails with no DMARC record, or one without a valid
p=. - Is a recommendation when there is no report address, at p=none, or once p=quarantine has held for 30 days with Amazon SES aligned and the only sender (move to p=reject). Its text starts with what to do now. At p=none with Prepare a stricter policy when it is safe on, it passes instead, because there is nothing to do until SendForever emails the next step.
- Passes with p=quarantine or p=reject and a report address.
With Prepare a stricter policy when it is safe on, SendForever looks at the last 30 days each time a report arrives. It prepares the next step (none → quarantine → reject) once the current policy has been in your DNS for 30 days and at least 99% of the reported mail passes. That needs at least 20 messages reported, and the 99% must also hold in every report of 20 messages or more. SendForever then emails the team's owners and admins the record with a Publish it now link. Nothing changes in your DNS until you publish it, with Add records to Cloudflare or at your provider. The 30 days only count while the DNS shows the policy the domain is on. To stop the steps, open Change DMARC and untick the option.
DMARC reports
When reports go to SendForever, the domain's Reputation tab shows Who sends as your domain over the last 30 days. It shows the share of messages that pass, and each sending source by name (such as Amazon SES or Google Workspace, taken from its reverse DNS). Each source has its message count and Aligned, Partly aligned or Failing. Providers send reports once a day, so the first ones arrive within 24 to 48 hours after the record is published. Reports are kept for 45 days. SendForever does not open a report flagged as spam or malware.
When there is no report to show, the card says why:
- Your DNS sends these reports elsewhere: the DMARC record in your DNS does not list the domain's SendForever address under
rua. Publish the DMARC record shown in DNS records. - Reports cannot reach SendForever yet: mailbox providers check that SendForever's inbox accepts reports for the domain, and the inbox does not answer for the domain yet. The problem is on SendForever's side, and SendForever is notified.
- Otherwise the record and the inbox are both set up. Providers only report on days they receive email from the domain, so reports start once the domain sends email.
If a failing source is yours, add its SPF domain under Choose senders and set up DKIM in that service. If it is not, a quarantine or reject policy stops it. When reports go to a mailbox on your own domain, the tab offers to let SendForever collect them instead.
Common questions
My domain will not verify. What should I check?
Open the DNS records tab and look for records marked Not found or Wrong value. The usual causes are a value that does not match exactly, the domain added to the name twice, or a DKIM CNAME proxied by Cloudflare. Once every DKIM and MAIL FROM record shows Verified, click Check again. If the domain shows Failed, click Restart verification.
A record shows Wrong value but I copied it exactly. Why?
Look at Published now: under the record. Often there is a second record of the same kind at that name, such as two SPF or two DMARC records. Receivers then use neither, so the DMARC check fails until only one is left. Or your provider added the domain to the name. A DMARC record with tags SendForever does not use also shows Wrong value.
Should my DKIM CNAMEs be proxied on Cloudflare?
No. A proxied CNAME (orange cloud) hides its target from Amazon SES. Set it to DNS only (grey cloud). Records SendForever adds to Cloudflare are DNS only.
My domain already has an SPF record. Will SendForever replace it?
SendForever prepares no SPF record for the domain itself until you choose who sends as it. After you choose, the record it prepares for the domain itself lists only the includes you entered, so enter every service that sends as the domain. Amazon SES's include stays on mail. plus your domain. Publishing to Cloudflare updates your existing SPF record instead of adding a second one.
How long does the link for my DNS admin work?
A week. It shows only the domain's records and what the last check found.
Cloudflare asks me to authorize SendForever again. Why?
The authorization lasts about an hour and is never renewed. Click Add records to Cloudflare again and confirm it, or use an API token.
Does SendForever change my DNS on its own?
Only through a Cloudflare authorization you gave, while it is live. It changes DNS when you add a domain, click Add records to Cloudflare, save a change on the domain's page that changes a record, or delete a domain with its records. DMARC steps prepared from the reports always wait for you to publish them.
Why did SendForever not move my DMARC policy to quarantine?
A step needs all of these: Prepare a stricter policy when it is safe turned on, reports sent to SendForever, the current policy in your DNS for 30 days, and at least 99% of reported mail passing. The 99% must also hold in every report of 20 messages or more. A step already prepared waits until you publish it.
My emails land in spam. Which records matter?
Make sure DKIM, MAIL FROM and DMARC all pass, that the domain can receive replies, and that the DMARC reports show no failing source of your own. Gmail and Yahoo require DMARC for bulk senders. Send marketing from a subdomain.
My brand logo does not show in Gmail. Why?
Gmail only shows a BIMI logo with a Verified Mark Certificate or a Common Mark Certificate. The record SendForever prepares includes neither. Both are paid certificates from a certificate authority such as DigiCert, GlobalSign, SSL.com or Sectigo. The logo also needs DMARC at p=quarantine or p=reject. Yahoo shows the logo without a certificate to senders with a good reputation.
How do I show my logo in Apple Mail without a certificate?
Register it with Branded Mail in Apple Business Connect, which is free and separate from BIMI:
- Make sure the domain's DMARC is at p=quarantine or p=reject, applied to all mail (no
pctbelow 100). The DMARC policy check on the domain's page tells you when that is safe. Amazon SES signs every email with DKIM, which Apple requires. - Sign in to Apple Business Connect with an Apple Account, and add your company with its legal name, address and company registration number.
- Open Branded Mail, add your brand name and website, and upload a square logo of at least 1024 × 1024 pixels (PNG, HEIF or JPEG).
- Add the domain, or a subdomain you send from. A subdomain without a logo of its own shows the domain's.
- Publish the TXT record Apple gives you to prove the domain is yours. Add it at your DNS provider, or in Cloudflare if that is where the domain's DNS is.
- Wait for Apple to review it, which can take up to seven business days. Apple emails you once the logo is approved.
The logo then shows in Apple Mail on recent versions of iOS, iPadOS and macOS. Other mailbox providers and older versions of Apple Mail do not show it.
Still stuck?