Email Deliverability 101: SPF, DKIM and DMARC Explained
You write a clear message, attach the right files, hit Send, and it still lands in the spam folder. The problem is rarely the content. It is the sender’s reputation, and more specifically how well your domain proves to receiving mail servers that the message really came from you.
Email deliverability is the measure of how often your messages reach the inbox instead of the junk folder. Three DNS-based authentication standards control most of that outcome:
- SPF
- DKIM
- DMARC
They are not optional extras for business email. They are the difference between being read and being filtered. This guide explains what each one does and how to set them up correctly.
What Is Email Deliverability?
Email deliverability is the percentage of your outgoing messages that receiving servers accept and place in the inbox. It is not the same as email delivery. A message can be delivered and still sit unread in the spam folder, and for marketing or sales outreach an unread message is the same as a lost one.
Receiving servers score every message against three groups of signals.
The first is sender reputation, which mailboxes build from complaint rates, bounce rates and sending volume.
The second is content, including spam-trigger words and image-to-text ratios.
The third is authentication and whether the message passes SPF, DKIM and DMARC checks. A failure on any one of those checks is enough to push an otherwise clean message into the junk folder, and repeated failures train the receiving server to distrust your whole domain.
For a business, the cost is direct. A professional address on your own domain is the base layer, and the Personal Email and Professional Email plans from Midphase start at $0.50 and $1.00 per month for the first year. The authentication records described below are what keep those messages credible.
SPF Explained
SPF stands for Sender Policy Framework, and it answers one question, which mail servers are allowed to send email on behalf of your domain? You answer it by publishing a TXT record in your domain’s DNS that lists the IP addresses and hostnames authorized to send. A typical record reads v=spf1 include:_spf.example.com ~all. The include mechanism pulls in the sending infrastructure of your provider or web host, and ~all tells receivers to soft-fail anything not listed. Switch to -all for a hard failure once you are confident the list is complete.
SPF matters because email was built without identity checks, and anyone could claim to be any sender.
SPF closes that hole for the sending path, but it has limits. It only verifies the MAIL FROM domain in the envelope, not the From address the recipient actually sees, and forwarded messages often fail because the forwarding server is not in the original record. That is why SPF alone is not enough when it comes to email deliverability.
DKIM Explained
DKIM stands for DomainKeys Identified Mail. Where SPF authorizes servers, DKIM signs the message itself. When you send, your mail server creates a hash of the message content, encrypts it with a private key, and attaches the result as a DKIM-Signature header. The matching public key lives in DNS. The receiving server fetches it and recomputes the hash; if the values match and the content has not been altered in transit and the message genuinely came from a server holding your domain’s private key.

DKIM stands for DomainKeys Identified Mail. Where SPF authorizes servers, DKIM signs the message itself. When you send, your mail server creates a hash of the message content, encrypts it with a private key, and attaches the result as a DKIM-Signature header. The matching public key lives in DNS. The receiving server fetches it and recomputes the hash; if the values match and the content has not been altered in transit and the message genuinely came from a server holding your domain’s private key.
Three fields in the signature matter most. d= is the signing domain. s= is the selector, and it tells the receiver which DNS record to query, usually selector._domainkey.yourdomain.com. And the signature covers the headers plus the body, so any change in transit breaks verification.
Like SPF, DKIM requires a real domain you control. If you register your domain through Midphase, you manage those DNS records directly and can publish the public keys yourself.
DMARC Explained
DMARC stands for Domain-based Message Authentication, Reporting, and Conformance. It builds on SPF and DKIM and adds two things they lack, a policy and a reporting loop. The policy is published as a TXT record at _dmarc.yourdomain.com and has three levels. p=none asks receivers to take no action on failures but still send you reports. p=quarantine sends failures to the spam folder. p=reject bounces the message outright.
DMARC also checks identifier alignment. SPF can pass on one domain while the visible From address shows another, and DKIM can sign with a different domain than the one recipients recognize. DMARC requires the domain that passes to align with the From domain, in relaxed or strict mode, before the overall check passes. Failures land in the aggregate reports you request with the rua= tag, which lets you see exactly who is sending on your behalf and who is trying to impersonate you.
DMARC policy enforcement is the final step in email deliverability, but the whole system works best on infrastructure that mailboxes recognize. Midphase email hosting handles the sending side with supported protocols and spam and virus protection, while you keep control of the DNS records that authenticate your domain.
How SPF, DKIM and DMARC Work Together
Each standard fills a gap the others leave open. SPF authorizes the sending servers. DKIM proves the message is intact and genuinely signed by your domain. DMARC tells receiving servers what to do when either check fails, and it is the record that connects the two so a lookup happens in a predictable order.
In practice, a message passes DMARC when it passes SPF with aligned domains, or DKIM with aligned domains, or both. Alignment means the domain that passed the check matches the From address the recipient sees.
When SPF and DKIM both fail, DMARC applies your policy, which at p=reject stops spoofed mail from ever reaching a customer’s inbox. That protection is why brands treat the three records as a single deployment rather than separate to-dos.
There is a practical trade-off to know. Enforcing DMARC makes every unauthenticated message fail, so every legitimate service that sends as your domain, from your website contact forms to your transactional mail provider, must appear in your SPF record or sign with DKIM first. Roll DMARC out gradually and keep the reports on.

Email Deliverability Best Practices
Publish all three records for every domain that can send email, including the one your website uses. Keep SPF under the 10 DNS lookup limit by using include statements instead of listing many IPs one by one. Start DMARC at p=none, study the aggregate reports for a few weeks, then tighten to p=quarantine and finally p=reject.
Send from the domain your recipients know, because alignment is easiest when the From address matches the domain that passes authentication. Warm up new sending infrastructure by increasing the volume gradually instead of blasting on day one. Keep lists clean with a double opt-in, remove hard bounces and inactive addresses, and keep an eye on complaint rates and blacklist status month to month.
Finally, use business email rather than free webmail accounts, which carry shared reputation. Midphase website hosting includes the mail services you need to get started, and adding email hosting to a domain you already own takes minutes.
Authentication is not a one-time setup either. Recheck your records whenever you change providers or add a new sending service.
Frequently Asked Questions
Q: What is the difference between DMARC policies p=none, p=quarantine and p=reject?
A: p=none tells receiving servers to take no action on failed messages but still send you reports, which makes it the safe starting point. p=quarantine sends failures to the spam or junk folder. p=reject instructs servers to bounce the message outright, which is the strongest protection against spoofing and should be your end goal once reports confirm all legitimate senders.
Q: How do I check whether SPF, DKIM and DMARC are already set up for my domain?
A: Use a DNS lookup tool or the dig command. dig TXT yourdomain.com shows your SPF record, dig TXT selector._domainkey.yourdomain.com shows your DKIM public key, and dig TXT _dmarc.yourdomain.com shows your DMARC record. You can also paste your sending address into a free email authentication checker, which tests all three records at once.
Q: Can DMARC alone stop email spoofing?
A: No. DMARC only works when SPF or DKIM is publishing and passing. It evaluates the other two checks, applies your policy to failures, and gives you reports. Without valid SPF and DKIM records in place, a DMARC record has nothing to evaluate and cannot protect your domain. Deploy all three together.
Q: How long do DNS changes for SPF, DKIM and DMARC take to apply?
A: Most DNS providers propagate TXT records within minutes to a few hours, but the TTL (time to live) value you set on the record controls how long receiving servers cache the old value. A TTL of 300 seconds propagates quickly and is fine for testing. Expect any change to be fully visible worldwide within 24 hours.
Ready to put email deliverability into practice? Sign up for Midphase email hosting today and get Personal Email at $0.50 per month and Professional Email at $1.00 per month for the first year, or register a new domain if you are just getting started.
Popular This Week
Recent posts
-
How to Migrate Your Website to a New Host Without Losing Traffic
-
How to Speed Up Your WordPress Website: 12 Practical Tips
-
VPS Hosting Explained: What It Is, What It Costs and Who Needs It
-
How to Set Up a Professional Business Email Address in 2026
-
WordPress Hosting vs Website Builder: Which Should You Use?