Skip to content
Free AI visibility check: does your brand show up in ChatGPT and Gemini answers?Apply →
Lead generation4 min read

What are DMARC, SPF and DKIM? Why your emails land in spam

The three layers of email authentication, Gmail and Yahoo's sender rules, and a step-by-step setup.

AuthorMahmud FiloğluReviewed byLast updated: View as Markdown
What are DMARC, SPF and DKIM: cover with the Gmail logo

SPF, DKIM and DMARC are three DNS records that prove to a receiving server that an email really comes from your domain. SPF lists the servers allowed to send on behalf of your domain. DKIM adds a digital signature to the message. DMARC tells receivers what to do with messages that fail the first two, and sends you reports. If all three are not fully in place, even the best-written email can end up in the spam folder.

Why are they mandatory now?

From February 2024, Google and Yahoo tightened authentication rules for email senders. Bulk senders that send close to 5,000 or more messages a day to Gmail addresses must set up SPF, DKIM and DMARC together, align the From address domain with these checks, and offer one-click unsubscribe in marketing messages. Smaller senders still need SPF or DKIM. Microsoft followed: from May 5, 2025, it requires SPF, DKIM and DMARC from domains sending more than 5,000 messages a day to Outlook.com, Hotmail and Live addresses, and non-compliant messages are first routed to the Junk folder.

In other words, DMARC is no longer a "best practice". It is a baseline requirement for B2B email and outbound.

SPF: who can send?

SPF (Sender Policy Framework) is a TXT record added to your domain's DNS. It lists the servers or services allowed to send email on behalf of your domain.

v=spf1 include:_spf.google.com include:servers.mcsv.net ~all

Two rules matter: a domain has only one SPF record, and evaluating that record may take at most 10 DNS lookups. Companies that use many sending services often exceed this limit, and SPF quietly fails.

DKIM: was the message changed?

DKIM (DomainKeys Identified Mail) means the sending server adds a digital signature to every message using a private key. The public key needed to verify the signature lives in your domain's DNS, in a record of the form selector._domainkey.yourdomain.com. The receiving server checks the signature; if the message was altered in transit or sent from somewhere else, the signature does not match.

DKIM has to be enabled separately for each sending service (Google Workspace, Microsoft 365, your email marketing tool, your outbound tool).

DMARC: what happens to messages that fail?

DMARC (Domain-based Message Authentication, Reporting and Conformance) is a TXT record at _dmarc.yourdomain.com. It does two jobs: it tells receivers what to do with messages that fail SPF or DKIM and are not aligned with the From address, and it sends you authentication reports.

v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com

PolicyWhat happensWhen
p=noneThe message is delivered normally and only reportedStart and monitoring phase
p=quarantineThe message goes to the spam folderOnce legitimate sources are fixed
p=rejectThe message is rejectedWhen every source passes authentication

Step-by-step setup

  1. List your sending sources. Who sends email on behalf of your domain? Corporate email, marketing tool, CRM, support desk, billing system, outbound tool.
  2. Merge SPF into one record. Add every source to a single record and check the lookup count.
  3. Enable DKIM for each source. Add the DKIM record each service gives you to DNS and turn signing on.
  4. Publish DMARC with p=none. Set a reporting address and use a DMARC report tool to read the reports.
  5. Read the reports. Over a few weeks, see which sources fail authentication and fix them.
  6. Tighten the policy. First quarantine, then reject.
  7. Monitor your reputation. Check your spam complaint rate and domain reputation regularly in Google Postmaster Tools.

Extra notes for cold email

Outbound teams usually protect the main domain by sending from a separate domain, warming the new domain up with low volume and capping daily sends per mailbox. The authentication records must be fully set up for that domain too. In Turkey, commercial electronic messages are governed by Law No. 6563 on the Regulation of Electronic Commerce and its regulation; the rules and İYS (Turkey's commercial message consent registry) obligations differ depending on whether the recipient is a business or a consumer, so get legal advice before a campaign. For recipients in Europe, GDPR must be assessed as well.

To pinpoint email delivery problems, our email deliverability entry product audits your domain's authentication and reputation. The full lead generation process, outbound included, is on our B2B lead generation agency page.

Frequently asked questions

Who counts as a bulk sender under Gmail's rules?

Since February 2024, Google treats anyone sending close to 5,000 or more messages a day to Gmail addresses as a bulk sender. Bulk senders must set up SPF, DKIM and DMARC, and marketing messages must offer one-click unsubscribe. Smaller senders still need SPF or DKIM.

Should I set DMARC to p=reject right away?

No. Start with p=none and watch the reports for a few weeks to see who sends email on behalf of your domain and which sources fail authentication. Once every legitimate source is fixed, move to quarantine, then to reject.

Can a domain have more than one SPF record?

No. A domain should have exactly one SPF record; multiple records make SPF fail. Merge all your sending services into a single record and keep an eye on the 10 DNS lookup limit.

Should I use my main domain for cold email?

Sending high-volume cold email from your main domain can hurt delivery of the company's everyday email if complaint and spam rates rise. Many teams use a separate, properly configured domain for outbound. Either way, SPF, DKIM and DMARC must be fully set up.

Sources

  1. 1Yahoo Sender Hub, Best practices, 2024
  2. 2Microsoft Tech Community, Outlook's new requirements for high-volume senders, 2025
  3. 3RFC 7208, Sender Policy Framework (SPF), 2014
  4. 4RFC 6376, DomainKeys Identified Mail (DKIM) Signatures, 2011
  5. 5RFC 7489, Domain-based Message Authentication, Reporting, and Conformance (DMARC), 2015
  6. 6Google Workspace Admin Help, Email sender guidelines, 2024
  7. 7Law No. 6563 on the Regulation of Electronic Commerce (Turkey), 2014

About the author

Senior Software Engineer & Tech Lead

Semih Bayindir , with advanced technical expertise, strong experience in software architecture and modern development technologies Senior Software Engineer & Tech Lead is. Scalable systems demonstrate high competence in code quality, performance optimization and technical strategy determination.

All their posts

The service this post relates toEmail deliverabilityA fixed-scope email deliverability audit: SPF, DKIM, DMARC, domain reputation, list hygiene and a prioritized fix list.

More posts

All Lead generation posts

Let’s put what you read to work for you.

In a 30-minute intro we look at your account and tell you which step should come first.