Job template · Email and SMS
Job template: set up SPF, DKIM and DMARC for a sending domain
By The Microployed teamUpdated 2 min read
The short answer
Use this scope when Gmail or Yahoo starts sending your mail to spam, or before you send marketing email from your own domain. An email or DNS pro finds every service that sends as your domain, publishes one SPF record and DKIM keys for each service, adds a DMARC record at p=none with reporting, and confirms all three pass. Most jobs take 45 to 120 minutes of work.
Ready-to-post scope
Set up SPF, DKIM and DMARC so our email stops going to spam
Typical time for a pro: 45 minutes to 2 hours
We send email from our domain through several services and some of it is landing in spam. List every service that sends as our domain, publish one SPF record that covers them all, turn on DKIM in each service, and add a DMARC record at p=none with a reporting address. Confirm each service passes with a test email.
Check first
- List every tool that sends email from your domain, including your store, help desk and invoicing software
- Find out where your domain's DNS is managed, such as your registrar, Cloudflare or your web host
- Choose an address or mailbox that will receive DMARC reports
Access to give
- A user invite or delegated access on your DNS provider with permission to edit records
- A team member account on your email platform with access to its domain authentication settings
- Admin access to your mailbox provider's email authentication settings, such as a delegated admin in the Google Workspace Admin console
Done when
- The domain has exactly one SPF record, ending in ~all, with no more than 10 DNS lookups
- A test email from each sending service shows SPF or DKIM passing and DMARC passing
- A DMARC record at p=none with a rua reporting address is published
- A short note lists every sending service and the DNS records added for it
When to use this template
Post this job when mail from your domain starts landing in spam at Gmail or Yahoo, when your email platform warns that your domain isn't authenticated, or before you start sending newsletters from your own address. Google and Yahoo both require SPF or DKIM from every sender, and Google requires anyone sending 5,000 or more messages a day to personal Gmail accounts to have SPF, DKIM and a DMARC record, with the From domain aligned to SPF or DKIM. Yahoo sets the same minimum DMARC policy of p=none for its bulk senders. Even if you send far less than that, having all three set up properly is the simplest way to keep receipts, invoices and newsletters out of spam folders.
What the pro will do
The pro starts by listing every service that sends mail as your domain, which usually includes your mailbox provider, your email marketing platform, your store or booking system, and any help desk or invoicing tool. They then build a single SPF record that includes each of those services, because a domain can have only one SPF record and the SPF standard allows at most 10 DNS lookups across all its includes. Next they turn on DKIM signing in each service and publish the keys it provides, using 2048-bit keys where the service offers them, since Google recommends that length. Once SPF and DKIM have been live for at least 48 hours, which is the gap Google suggests, they add a DMARC record at p=none with a reporting address so you can see every server that sends mail using your name.
How to review the work
Ask for a short list of every sending service and whether it now passes SPF, DKIM or both. Then send a test email from each service to a Gmail address, open it, click the More icon next to Reply, choose Show original, and check that the SPF, DKIM and DMARC lines near the top say PASS. Within a few days you should also start receiving DMARC aggregate reports at the address in the record, which confirms that receiving servers can read your policy.
Things that commonly trip this job up
The most frequent mistake is adding a second SPF record for a new tool instead of adding its include to the existing one, which causes SPF to fail for everything. Long include chains can also push the record past 10 lookups without anyone noticing, so the pro should count them and drop services you no longer use. Google recommends ending the record with ~all rather than -all, because the stricter setting can block legitimate mail from a service that was missed. Finally, resist jumping straight to p=quarantine or p=reject. Google's recommended rollout keeps p=none for about a week while someone reads the reports daily, then applies quarantine to a small percentage of mail and raises it in stages. If your setup involves more than this scope covers, you can adjust it in the job scope builder before posting.
The next level up
Move DMARC to enforcement so nobody can send mail as your domain
A policy of p=none only reports on mail that pretends to come from you. Once a week or two of reports show every real sender passing, moving to p=quarantine sends failing mail to spam, which protects your customers from spoofed emails. Google recommends making that move gradually, starting with a small percentage of mail.
Post the DMARC enforcement jobQuestions people ask
Do I need DMARC if I only send a few emails a day?
Google and Yahoo require SPF or DKIM from all senders and DMARC from bulk senders. A DMARC record at p=none still costs nothing, doesn't change delivery, and shows you who is sending mail as your domain.
Will our email stop working while this is set up?
It shouldn't, as long as the pro adds every service to one SPF record, ends it with ~all, and starts DMARC at p=none, which tells receiving servers to deliver mail as usual.
Do I need to give the pro my domain registrar password?
No. Most DNS providers let you invite a user or delegate access, and email platforms let you add a team member. Remove that access once you've approved the work.
What does p=none actually do?
It asks receiving servers to deliver your mail normally and send you reports about it. Google recommends starting there for about a week before moving to quarantine.
Sources
Checked against these pages on .
- Email sender guidelines (Gmail Help) (opens in a new tab)
- Sender best practices (Yahoo Sender Hub) (opens in a new tab)
- Recommended DMARC rollout (Google Workspace Admin Help) (opens in a new tab)
- Troubleshoot SPF issues (Google Workspace Admin Help) (opens in a new tab)
- Trace an email with its full header (Gmail Help) (opens in a new tab)