Fixing DNS verification
When a record doesn't verify, Porters shows what it found and what to change. Each message below has the longer explanation.
What the statuses mean
- Verified: the record is there and correct.
- Missing: nothing is published at that name. Add the record.
- Mismatch: something is published, but it isn't what Porters needs. Porters lists what it found under "What we found". Change it, don't add a second one.
- Pending: Porters couldn't get an answer, usually because the change hasn't spread yet. Wait and check again.
How long DNS changes take
Most changes appear within a few minutes. Some DNS hosts, and anyone who had the old record cached, take an hour or more; allow up to a day. The time is set by the old record's "TTL" (how long others may remember it). Porters keeps checking, so you can leave the page. If a record is still wrong after a day, the status is no longer a waiting problem, so look at what Porters found.
No MX record found
Add an MX record on the domain itself (host @) pointing to the mail server shown on your domain's setup page, priority 10. See the guide for your DNS host.
Mail still goes to the old provider first or equally
Your Porters MX record is there, but another one ties or wins. Mail goes to the MX with the lowest number first. Delete the old provider's MX records, or give them a number higher than 10.
Mail goes to another provider
Your domain's MX records point to a different email service. Delete them and add the Porters one. Only do this when you're ready to move: from that moment new mail arrives in Porters. Copy any mail you want to keep first; see moving from another provider.
Cloudflare Email Routing is on
Email Routing publishes its own MX records, which take the mail. Turn it off, delete its records, then add the Porters one. The Cloudflare guide has the steps.
No SPF record found
Add a TXT record on the domain itself (host @) with the SPF value from your Porters domain page. It starts v=spf1 and includes the include shown on your domain's setup page.
More than one SPF record
A domain may have exactly one SPF record. With two, receivers ignore both, and your mail can be marked as spam.
- Find every TXT record on
@that startsv=spf1. - Combine them into one: a single
v=spf1, then everyinclude:andip4:entry from all of them (once each), including the include shown on your domain's setup page, ending with one~all. - Delete the other records.
Your SPF record doesn't allow Porters
Edit the SPF record you have: add include: followed by the include shown on your domain's setup page before the final ~all or -all. Don't create a second record.
SPF needs too many lookups
SPF allows ten DNS lookups; every include: costs at least one, and the services inside them cost more. Past ten, receivers reject the whole record. Remove services you no longer send from. For services you keep, ask them for their IP ranges and list those as ip4: entries, which cost nothing.
SPF points at a name with no SPF record
One of your include: entries names something that publishes no SPF record, which receivers treat as an error. Remove that entry, or ask the service that gave it to you for the right name.
No signing key found
Add the DKIM TXT record at exactly the host shown on your domain page (it ends ._domainkey), with the value shown.
The signing key is the wrong one
A record exists at that name but with a different key. Replace its value with the one on your domain page. Paste it whole: some DNS hosts cut long values short or add quotation marks of their own, so compare what you saved with what Porters shows.
No DMARC record found
Add a TXT record with host _dmarc and the value from your domain page. If you already have a DMARC record from another service, keep it: a domain has just one.
DMARC has no valid policy
Your DMARC record needs a policy: p=none, p=quarantine or p=reject. For example v=DMARC1; p=quarantine.
Your domain doesn't ask senders to require encryption
Mail between servers is usually encrypted, but someone in the path can quietly turn that off. MTA-STS tells senders such as Gmail and Outlook to deliver to you only over an encrypted connection. Add the two records shown on your Email health page: a CNAME with host mta-sts, and a TXT record with host _mta-sts. If your DNS host offers a proxy (Cloudflare's orange cloud), leave it off for the CNAME.
More than one _mta-sts record
Senders ignore MTA-STS when a domain has two _mta-sts TXT records. Keep one and delete the rest.
Senders can't read your MTA-STS policy
Your _mta-sts record is there, but the policy it refers to couldn't be fetched from mta-sts. on your domain, so senders ignore it. Check that the mta-sts CNAME points exactly where your Email health page says, with no proxy. After you add it, Porters sets up the certificate for that name within about an hour.
Your MTA-STS policy isn't valid
Something answers at mta-sts. on your domain, but it isn't a valid policy. Point the mta-sts CNAME at the name your Email health page shows, and Porters serves the policy for you.
Your MTA-STS policy is for another mail server
The policy at your domain lists a different mail server, often one left over from your previous provider. In enforce mode, senders that follow it refuse to deliver to Porters, so fix this first: point the mta-sts CNAME at the name your Email health page shows. If you host the policy yourself, add Porters' mail server to it as an mx: line.
No delivery reports requested
A TXT record with host _smtp._tls asks senders to send a daily report when they couldn't deliver to you securely. Porters reads those reports and shows them on your Email health page. Add the record shown there.
Records that were fine can break later, for example when someone changes DNS or a service renews its records. Porters checks verified domains once a day and emails the account owner if something stops matching. You can also open Email health on your domain page at any time.