Monday morning, your invoices go out from your new company domain. By lunch, two clients say they found them in spam. Then your newsletter to Outlook.com readers bounces with a blunt reply: 550 5.7.515 Access denied, sending domain does not meet the required authentication level. Nothing changed in your copy. What changed is that Gmail, Yahoo and Microsoft now check three DNS records, SPF, DKIM and DMARC, before they trust your mail.
Here’s the short version. If those records are missing, broken or misaligned, your email looks like it could be forged, so filters send it to spam or refuse it outright. The good news is that all three are free text records you add once at your domain host. Below you’ll find why emails go to spam, what each record does in plain English, how to set up SPF, DKIM and DMARC for Google Workspace, Microsoft 365, GoDaddy and Namecheap, and a free checker and record generator you can use right on this page.
SPF, DKIM and DMARC are three DNS records that prove your email really comes from your domain. SPF lists the servers allowed to send for you. DKIM signs each message. DMARC tells inboxes what to do when those checks fail. Gmail, Yahoo and Outlook.com require all three from bulk senders, and missing them is a top reason email lands in spam.
Why Are My Emails Going to Spam?
Most emails go to spam for one of five reasons: missing or broken SPF, DKIM and DMARC records, too many spam complaints, a new or damaged sender reputation, poor list quality, or content that looks like spam. Since 2024, authentication is checked first. If it fails, nothing else you do will get the message into the inbox.
Mailbox providers can’t see who you are. They only see a message that claims to come from your domain. Authentication records are how you prove that claim. Without them, your real invoice looks exactly like a phishing email that copied your logo. So the filter plays it safe and sends it to spam.
| Cause | What you’ll notice | Where to look first |
|---|---|---|
| SPF, DKIM or DMARC missing or failing | Mail to Gmail or Outlook.com goes to spam or bounces with a 5.7.x error | Run the checker below |
| Spam complaints too high | Spam placement grows over days or weeks | Google Postmaster Tools spam rate |
| New domain or new sending tool | Mail worked from your old address, not the new one | SPF and DKIM for the new tool |
| Old or bought contact list | Many bounces, few opens | Bounce report in your email platform |
| Spam-like content | Only some campaigns land in spam | Links, images, subject line, sending domain mismatch |
| Forwarded or mailing list mail | Mail fails only after passing through a list | DKIM signature and DMARC reports |
Why is my email suddenly going to spam?
If mail that used to work now lands in spam, look at dates. Microsoft started rejecting non-compliant bulk mail to Outlook.com, Hotmail and Live addresses on May 5, 2025 (Microsoft Tech Community, April 2025). Google’s sender FAQ says that starting November 2025, Gmail is ramping up enforcement, with temporary and permanent rejections for mail that fails its rules. A setup that slipped through in 2024 can fail now without you touching anything.
Other sudden triggers are more ordinary. You added a new tool, such as a CRM or invoicing app, that sends as your domain but isn’t in your SPF record. Someone edited DNS and created a second SPF record. Or one campaign drew a burst of spam complaints. Check authentication first, then complaints, then recent changes to your tools.
Why do my emails go to spam in Gmail?
Gmail blocks or filters mail that fails its sender rules. Every sender must use SPF or DKIM, send over TLS, have valid forward and reverse DNS, and keep its spam rate below 0.3%. Anyone sending close to 5,000 messages a day to personal Gmail accounts needs SPF, DKIM and DMARC, plus one-click unsubscribe (Google email sender guidelines). Google recommends staying below a 0.1% spam rate, not just below 0.3%.
What Are SPF, DKIM and DMARC? Explained in Simple Terms
SPF, DKIM and DMARC are email authentication standards stored as TXT records in your domain’s DNS. SPF says which servers may send your email. DKIM signs each message so receivers can tell it wasn’t changed. DMARC checks that SPF or DKIM passed for the same domain shown in the From line, then tells receivers what to do if not.
Think of a company mailroom. SPF is the list of couriers allowed to carry your packages. DKIM is a tamper-proof seal on each package. DMARC is the note on the door that says, “If a package shows up without our seal or from a courier not on the list, return it.” One alone helps. All three together stop strangers from mailing things in your name.
What is SPF in cyber security?
SPF stands for Sender Policy Framework. It’s a single TXT record at your root domain that starts with v=spf1 and lists the services allowed to send email for you, such as Google Workspace or Microsoft 365. When a message arrives, the receiving server checks whether the sending server is on that list. SPF is used to stop spammers from using your domain on their own servers.
SPF has a weak spot. It checks the hidden “envelope” sender address, not the From address people see. So a message can pass SPF for a vendor’s domain while showing your name in the From line. DMARC closes that gap.
What is DKIM in cyber security?
DKIM stands for DomainKeys Identified Mail. Your email service signs every outgoing message with a private key it keeps secret. You publish the matching public key in DNS under a name called a selector, such as google._domainkey.yourdomain.com. Receivers use that public key to confirm the signature. If anyone changes the message on the way, the check fails.
What does DMARC stand for, and where does it live?
DMARC stands for Domain-based Message Authentication, Reporting and Conformance. The record always lives at _dmarc.yourdomain.com, so the “DMARC location” people search for is that _dmarc host name. The current standard is RFC 9989, published in May 2026, which replaced the original 2015 specification, RFC 7489 (RFC 9989).
DMARC does two jobs. First, it sets your policy: none to only monitor, quarantine to send failures to spam, or reject to block them. Second, it asks receivers to send you reports, which show every server that sends mail using your domain. That second job is why people start getting strange DMARC emails after setup, which we cover below.
Difference between SPF, DKIM and DMARC
| SPF | DKIM | DMARC | |
|---|---|---|---|
| What it proves | The sending server is allowed | The message wasn’t changed and was signed by a domain | SPF or DKIM passed for the From domain |
| DNS record name | Your domain (@) | selector._domainkey | _dmarc |
| Starts with | v=spf1 | v=DKIM1 | v=DMARC1 |
| Survives forwarding? | Usually not | Usually yes | Yes, if DKIM survives |
| Gives you reports? | No | No | Yes |
| Tells receivers what to do? | Weakly, with ~all or -all | No | Yes, with none, quarantine or reject |
DKIM vs DMARC
DKIM and DMARC aren’t alternatives. DKIM is a signature on each message. DMARC is a policy that reads the DKIM and SPF results and checks they match your From domain. You can have DKIM without DMARC, but then nobody knows what you want done with failures. You can’t really have DMARC without DKIM, since forwarded mail often breaks SPF and DKIM is what keeps it passing.
Do You Need SPF, DKIM and DMARC in 2026?
Yes, if you send any business email. Every sender to Gmail and Yahoo needs SPF or DKIM. Anyone sending about 5,000 or more messages a day to Gmail, Yahoo or Outlook.com addresses needs all three, with DMARC at p=none or stricter. Smaller senders aren’t forced to use DMARC yet, but without it, anyone can spoof your domain.
| Requirement | Gmail | Yahoo | Outlook.com |
|---|---|---|---|
| SPF or DKIM for all senders | Required | Required | Not stated (rules target 5,000+ a day) |
| SPF and DKIM for bulk senders | Required | Required | Required |
| DMARC for bulk senders | Required, p=none minimum | Required, p=none minimum | Required, p=none minimum |
| From domain aligned with SPF or DKIM | Required | Required | Required |
| One-click unsubscribe | Required for marketing mail | Required, RFC 8058 recommended | Working unsubscribe link recommended |
| Spam rate limit | Below 0.3%, aim for under 0.1% | Below 0.3% | Not published |
| What happens if you fail | Temporary or permanent rejection since November 2025 | Not detailed on its Sender Hub | Rejection with 550 5.7.515 since May 5, 2025 |
Google treats a sender as bulk once it sends close to 5,000 messages to personal Gmail accounts in 24 hours, and says that status is permanent. Yahoo publishes the same core rules on its Sender Hub, including honoring unsubscribes within two days. Microsoft added one detail that surprises people: a recipient’s Safe Senders list won’t override its authentication enforcement.
Is DMARC really necessary?
For bulk senders, it’s mandatory. For everyone else, it’s the only thing that stops someone else from sending email that shows your exact domain in the From line. SPF and DKIM prove good mail is real. Only DMARC with quarantine or reject tells inboxes to refuse fake mail.
The cost of skipping it is real. The FBI’s Internet Crime Complaint Center logged 24,768 business email compromise complaints with $3.046 billion in losses in 2025 (FBI IC3 2025 Internet Crime Report, April 2026). Not every one of those used a spoofed domain, but domain spoofing is the cheapest trick in that playbook. US federal agencies have had to use DMARC at p=reject since CISA’s Binding Operational Directive 18-01, which set an October 2018 deadline.
What happens if I don’t have a DMARC record?
Three things. Bulk mail to Gmail, Yahoo and Outlook.com can be filtered or rejected. Anyone can send mail that shows your domain, and you won’t see it happening. And you lose access to reports that would show which of your own tools are failing. Even a basic p=none record with a reporting address fixes the first and third problems on day one.
How to Set Up SPF, DKIM and DMARC Step by Step
To set up SPF, DKIM and DMARC, list every service that sends email as your domain, publish one SPF record that includes them, turn on DKIM signing in each service and add its DNS record, then publish a DMARC record at p=none with a reporting address. After two to four weeks of clean reports, move DMARC to quarantine, then reject.
- List every sender. Your mailbox provider, newsletter tool, CRM, help desk, invoicing app, website contact form and any server that sends alerts.
- Publish one SPF record. Add a TXT record at @ that starts with v=spf1, includes each sender and ends with ~all or -all.
- Turn on DKIM in each service. Each service gives you a selector and a TXT or CNAME record to add. Then switch signing on.
- Publish DMARC at p=none. Add a TXT record at _dmarc with a rua= address for reports.
- Read reports for two to four weeks. Fix any real sender that fails SPF and DKIM alignment.
- Tighten to quarantine, then reject. Move one step at a time and keep watching the reports.
Step 1: Find every service that sends as your domain
This is the step people skip, and it’s why DMARC breaks real mail later. Ask each team what tools send email. Check your email platform, CRM, billing system, support desk and website forms. If you already have a DMARC record with reporting, the reports list every server that sent mail as you, including ones nobody remembered.
Step 2: Create your SPF record (SPF record example)
A good SPF record is one TXT record at your root domain, under the 10-DNS-lookup limit, that ends with ~all or -all. Here’s an SPF record example for a business using Google Workspace for staff mail and Mailchimp for newsletters:
Type: TXT
Host: @
Value: v=spf1 include:_spf.google.com include:servers.mcsv.net ~all Each include: points to the provider’s own list of servers. The ending matters. Google recommends ~all, a soft fail. Microsoft recommends -all, a hard fail, for Microsoft 365 domains that also use DKIM and DMARC (Microsoft Learn, SPF setup). Both work with DMARC. Never use +all, which allows any server on the internet to send as you.
Two rules break SPF more than anything else. First, a domain can have only one SPF record. Two records cause a permanent error, and SPF fails for every message. Second, SPF allows at most 10 DNS lookups. Each include:, a, mx, exists and redirect counts, and so do the includes nested inside them. Go over 10 and SPF fails.
Step 3: Turn on DKIM signing (DKIM record example)
You don’t write DKIM keys by hand for hosted email. Your provider creates them. You copy the record it shows you into DNS, then switch signing on. A DKIM record example looks like this, with the long key shortened:
Type: TXT
Host: google._domainkey
Value: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA... The part before ._domainkey is the DKIM selector. It’s just a label that tells receivers which key to fetch, so one domain can hold several keys for different services. Google Workspace uses google by default. Microsoft 365 uses selector1 and selector2. Use 2048-bit keys when your provider allows it. Gmail accepts 1024-bit keys but recommends 2048.
Step 4: Publish your DMARC record (DMARC record example)
Start every new DMARC record at p=none with a reporting address. That way you see who sends as your domain before you block anything. Here’s a starter DMARC record example:
Type: TXT
Host: _dmarc
Value: v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com | Tag | What it does | Example |
|---|---|---|
| v | Version. Must come first. | v=DMARC1 |
| p | Policy for your domain: none, quarantine or reject | p=quarantine |
| sp | Policy for subdomains, if different | sp=reject |
| rua | Where to send daily aggregate reports | rua=mailto:dmarc@yourdomain.com |
| ruf | Where to send failure reports (rarely sent today) | ruf=mailto:dmarc@yourdomain.com |
| adkim / aspf | Alignment mode, r for relaxed (default) or s for strict | adkim=s |
| t | Testing flag added in RFC 9989. t=y asks receivers to go easier on failures | t=y |
| np | Policy for subdomains that don’t exist, added in RFC 9989 | np=reject |
Step 5: Move from none to quarantine to reject
Read your reports for two to four weeks. When every real sender passes, change p=none to p=quarantine. Watch for another few weeks, then change it to p=reject. That’s the setting that actually stops spoofing.
Here’s a correction to a lot of guides you’ll find. Many still tell you to ramp up with pct=10, then pct=50, then pct=100. The May 2026 DMARC standard removed the pct tag (RFC 9989, Appendix A.6). Receivers may still read it on older records, but don’t build a rollout plan on it. Use the new t=y testing flag, or apply the stricter policy to a subdomain first with sp=.
Setup Guides for Google Workspace, Microsoft 365, GoDaddy and Namecheap
Setup follows the same pattern everywhere: get the values from your email provider, then add them as DNS records wherever your domain’s DNS is hosted. Your email provider and your DNS host can be different companies. For example, you might use Google Workspace for mail but manage DNS at GoDaddy or Namecheap.
How to set up SPF, DKIM and DMARC in Google Workspace
For SPF, Google’s recommended record is v=spf1 include:_spf.google.com ~all. For DKIM, a super administrator opens the Admin console and goes to Apps, Google Workspace, Gmail, then Authenticate email. Pick your domain, choose a 2048-bit key if your DNS host supports it, and click Generate new record (Google Workspace Admin Help).
- Copy the host name, which is google._domainkey by default, and the TXT value that starts with v=DKIM1.
- Add them as a TXT record at your DNS host.
- Wait for DNS to update. Google says DKIM can take up to 48 hours to start working.
- Go back to Authenticate email and click Start authentication.
- Send a test to a Gmail address you don’t own and check the message header for dkim=pass.
Google also says to wait 24 to 72 hours after turning on Gmail before generating the key. Starting earlier can trigger a “DKIM record was not created” error. Add DMARC last, at _dmarc, once SPF and DKIM pass.
How do I add SPF to Gmail with a free Gmail address?
You can’t. SPF, DKIM and DMARC belong to a domain you own. A free @gmail.com address uses Google’s own records, which Google manages. To control authentication, you need your own domain, such as yourname.com, connected to Google Workspace or another email host.
How to set up SPF, DKIM and DMARC in Office 365 (Microsoft 365)
For a domain that sends only through Microsoft 365, Microsoft’s SPF record is v=spf1 include:spf.protection.outlook.com -all. To update an existing SPF record in Office 365, edit the one TXT record at your DNS host and add that include. Don’t create a second record (Microsoft Learn).
For DKIM, open the Microsoft Defender portal, then Email & collaboration, Policies & rules, Threat policies, Email authentication settings, and the DKIM tab (Microsoft Learn, DKIM setup). Select your domain to see two CNAME records for selector1._domainkey and selector2._domainkey. Add both at your DNS host, then turn on signing.
Two details catch people. Since May 2025, new custom domains get CNAME targets ending in dkim.mail.microsoft, while older domains point to onmicrosoft.com. Copy whatever the portal shows. And Microsoft’s default DKIM key size is 1024 bits. To move to 2048 bits, rotate the keys, which Microsoft says takes four days to take effect.
How to add an SPF record in GoDaddy
Sign in to your GoDaddy Domain Portfolio, select the domain, then select DNS. Choose Add New Record, set Type to TXT, Name to @, and paste your SPF value. If you use Microsoft 365 bought from GoDaddy, GoDaddy’s help page gives the value v=spf1 include:secureserver.net -all. GoDaddy says changes usually work within an hour but can take up to 48 hours.
SPF, DKIM and DMARC at GoDaddy all use the same Add New Record screen. DMARC goes in a TXT record named _dmarc. DKIM goes in whatever name your email provider gives you, such as google._domainkey. If an SPF record already exists, edit it instead of adding a new one, since GoDaddy also warns your domain can only have one.
How to add an SPF record in Namecheap
Go to Domain List, click Manage next to your domain, and open the Advanced DNS tab. Click Add New Record and pick TXT Record, even for SPF, DKIM and DMARC. Set Host to @ for SPF, _dmarc for DMARC, or the selector name for DKIM, paste the value and save. Namecheap says new records usually work within about 30 minutes.
Namecheap’s one gotcha: don’t type your domain into the Host field. Write _dmarc, not _dmarc.yourdomain.com, or you’ll end up with _dmarc.yourdomain.com.yourdomain.com. This applies only when your domain uses Namecheap BasicDNS, PremiumDNS or FreeDNS. If it points to Namecheap hosting, add the records in cPanel instead.
How to add SPF to DNS at any other host
Every DNS host, from Cloudflare to Squarespace, uses the same three fields: type, host or name, and value. Pick TXT, use @ for the root domain, and paste the record. Some hosts want the full name, such as yourdomain.com instead of @. If a record doesn’t show up in the checker after an hour, look at the exact host name it saved.
Free SPF, DKIM and DMARC Checker and Record Generator
Type your domain below to check your SPF, DKIM and DMARC records in one go. The checker counts SPF lookups, flags duplicate records, estimates your DKIM key size and reads your DMARC policy. The other tabs build an SPF record, a DMARC record or a DKIM key pair you can copy straight into DNS.
How to read your results
Green means the record exists and looks healthy. Amber means it works but leaves you exposed, such as DMARC at p=none or a 1024-bit DKIM key. Red means it’s failing right now, such as two SPF records or more than 10 lookups. Fix red items first, because they affect every message you send.
If DKIM shows “not found,” don’t panic. The checker tries common selectors only. Open a message you sent, view the original or source, find the DKIM-Signature header, and look for s= followed by a word. That word is your selector. Type it into the selector box and check again.
How to Check Your Email Authentication Records Online
You can check SPF, DKIM and DMARC records three ways: run a DNS checker like the one above, read the Authentication-Results header on a message you sent, or query DNS from your computer. The header test is the most honest, because it shows what a real inbox decided, not just what your DNS says.
Check the message header in Gmail
Send an email from your domain to a Gmail address you can open. In Gmail, open the message, click the three-dot menu and choose Show original. The top of the page lists SPF, DKIM and DMARC with PASS or FAIL next to each. If all three say PASS, your setup works for Gmail.
Check from the command line
On Windows, Mac or Linux, nslookup reads TXT records. Replace yourdomain.com and the selector with your own:
nslookup -type=TXT yourdomain.com
nslookup -type=TXT _dmarc.yourdomain.com
nslookup -type=TXT google._domainkey.yourdomain.com MxToolbox and other DKIM checkers
MxToolbox is a popular free option for SPF, DKIM and DMARC lookups, and it’s where many people run an MxToolbox DKIM check. It needs the selector too. Any tool that asks only for a domain is guessing selectors, the same way our checker does. A message header is still the final word on whether DKIM passed.
Common Email Authentication Errors and How to Fix Them
Most authentication failures come from a short list of mistakes: no SPF record, two SPF records, too many SPF lookups, a sending tool that isn’t authorized, DKIM that was never switched on, and DMARC alignment failures. Each one has a specific fix, and the table below pairs the symptom with it.
| Problem | What it means | Fix |
|---|---|---|
| No SPF record | Receivers can’t tell which servers may send for you | Add one TXT record at @ starting with v=spf1 |
| Two SPF records | SPF returns a permanent error for every message | Merge them into one record |
| SPF permerror: too many DNS lookups | More than 10 lookups, counting nested includes | Remove unused includes or move a sender to a subdomain |
| DKIM not found | Signing is off, or the selector name is wrong | Turn on signing and copy the record exactly |
| DKIM fails after forwarding | A mailing list changed the message | Normal for some lists. DMARC reports will show it |
| DMARC fail with SPF and DKIM passing | The passing domain doesn’t match your From domain | Set up DKIM with your own domain in your sending tool |
| 550 5.7.515 from Outlook.com | Bulk mail missing SPF, DKIM or DMARC | Publish all three and make one align |
| Gmail 5.7.26 unauthenticated bounce | Message failed Gmail’s authentication checks | Fix SPF and DKIM, then add DMARC |
No SPF record found
A “no SPF record” warning means receivers have no list of approved senders, so they guess. Add a single TXT record at @ that includes every service you send through. If the domain never sends email at all, publish v=spf1 -all instead. That tells everyone the domain sends nothing, which stops spammers from borrowing it.
What is a DMARC fail?
A DMARC fail means neither SPF nor DKIM passed for a domain that matches the one in the From line. This is called alignment. The classic case is a newsletter tool that passes SPF for its own domain, like mail.vendor.com, while the From line shows yours. Fix it by setting up DKIM inside that tool so it signs with your domain.
Why am I getting DMARC emails?
If you added rua= to your DMARC record, mailbox providers email you daily aggregate reports. They usually arrive as zipped XML files from Google, Microsoft, Yahoo and others. They aren’t spam and they aren’t errors. They list every server that sent mail using your domain and whether it passed. If they flood your inbox, point rua= to a separate mailbox or a DMARC report service.
How to Stop Emails From Going to Spam After Authentication
Once SPF, DKIM and DMARC pass, inbox placement depends on how people react to your mail. Keep spam complaints under 0.1%, make unsubscribing one click, remove addresses that bounce or never engage, and send only to people who asked to hear from you. Authentication gets you through the door. Reputation keeps you in the inbox.
Watch your spam rate in Postmaster Tools
Google Postmaster Tools is free and shows the spam rate Gmail users report for your domain. Google calculates it daily. Google recommends keeping it under 0.1% and says bulk senders at 0.3% or higher lose eligibility for help with delivery problems. Microsoft’s equivalent for Outlook.com is SNDS, the Smart Network Data Services portal.
One update to older advice: according to Twilio’s summary of Google’s notice, Gmail retired the old Postmaster Tools on September 30, 2025 and removed the domain and IP reputation scores. Many guides still tell you to watch a “High” or “Bad” reputation rating. That rating is gone. Watch spam rate and the compliance status dashboard instead.
Make unsubscribing easy
Google and Yahoo require one-click unsubscribe on marketing mail from bulk senders. Your email platform adds this through a List-Unsubscribe header, so check it’s switched on. Yahoo says to honor requests within two days, and Google recommends 48 hours. A hard-to-find unsubscribe link pushes people to click Report spam instead, which hurts you far more.
The same consent logic applies outside email. If you also text customers, our guide to US texting rules on consent and opt-outs covers the opt-out rules that trip up small businesses.
Clean your list
Remove hard bounces after every send. Stop mailing people who haven’t opened or clicked in months, or send them one re-engagement message first. Never buy a list. Bought lists contain old and trap addresses that spike bounces and complaints within days, and the damage outlasts the campaign.
Cold email and spam checker tools
Cold email is the hardest case, because recipients never asked for it. Use a separate subdomain for outreach so problems don’t hit your main domain’s mail. Set up SPF, DKIM and DMARC on that subdomain too. Send low volumes, personalize each message and avoid link-heavy templates.
An email spam checker, such as Mail-Tester or GlockApps, sends a test message through spam filters and scores it. These tools are useful for catching broken authentication, blocklist hits and risky content. They can’t predict how real recipients will react, so treat a good score as a minimum, not a promise of inbox placement.
Branded logos with BIMI and Apple Branded Mail
Once DMARC is at quarantine or reject, you can show your logo next to your emails in some inboxes through BIMI. Apple has its own version called Branded Mail, managed in Apple Business, which also asks you to verify your domain first. Our guide to Apple Business and Branded Mail explains where that setting now lives.
How to Stop Incoming Emails Going to Spam in Gmail and Outlook
If good emails you receive keep landing in spam, mark them as not spam and add the sender to your contacts. In Gmail, open Spam, select the message and click Not spam. In Outlook.com, open Junk Email, select the message and click It’s not junk. Then add the sender as a contact or safe sender so future mail stays in your inbox.
How do I unspam my mail in Gmail?
- Open Gmail on a computer.
- In the left menu, click More, then Spam.
- Check the box next to the email.
- Click Not spam at the top. If the message shows an unconfirmed sender warning, click Report not spam.
To keep that sender out of spam, save them as a contact or create a filter for their address. Google says that if real mail still lands in spam after both steps, the sender likely has an authentication problem only they can fix.
How to stop incoming emails going to spam in Outlook
In Outlook.com, open the Junk Email folder, select the message and choose It’s not junk. Then add the sender to your Safe senders list. In Outlook on the web, that list is under Settings, Mail, then Block or allow. You can add a full address or a whole domain.
One limit to know: Microsoft says a Safe Senders list won’t override its authentication enforcement for bulk mail. If a newsletter you want is being rejected, the sender has to fix their SPF, DKIM and DMARC. Nothing in your settings can force it through.
Email Authentication FAQ
Why use SPF, DKIM and DMARC?
You use them to prove your email is real and to stop others from faking it. SPF and DKIM show inboxes that a message came from an approved server and wasn’t altered. DMARC tells inboxes to quarantine or reject mail that fails, and sends you reports. Gmail, Yahoo and Outlook.com require all three from bulk senders, so skipping them also hurts deliverability.
How can I check my SPF, DKIM and DMARC records?
Use the free checker on this page, which looks up all three records and flags problems. For DKIM, enter your selector, which you can find in the s= value of a sent message’s DKIM-Signature header. To see what a real inbox decided, send yourself a message at Gmail, open it, choose Show original, and look for SPF, DKIM and DMARC marked PASS.
What is a good SPF record?
A good SPF record is a single TXT record at your root domain that starts with v=spf1, lists every service that sends mail for you, stays under 10 DNS lookups and ends with ~all or -all. For example, v=spf1 include:_spf.google.com ~all works for a business that sends only through Google Workspace. Avoid +all, ptr and duplicate records. Run the checker after publishing to confirm the real lookup count, since includes can contain more includes.
How do I add DMARC to my email?
Add a TXT record at your DNS host with the host name _dmarc and a value such as v=DMARC1; p=none; rua=mailto:you@yourdomain.com. Make sure SPF and DKIM already pass first. After a few weeks of clean reports, change p=none to p=quarantine, then to p=reject. The DMARC generator tab on this page builds the record for you, and the checker confirms it went live.
How long do SPF, DKIM and DMARC changes take to work?
Most DNS changes work within an hour. GoDaddy says up to 48 hours, Namecheap says about 30 minutes, and Google says DKIM can take up to 48 hours to start working in Workspace. Microsoft says rotating DKIM keys takes four days. If a record still doesn’t appear after a day, check the host name you saved for typos. A common mistake is adding your domain twice, as in _dmarc.yourdomain.com.yourdomain.com.
Can I have two SPF records?
No. A domain or subdomain can have only one SPF record. If receivers find two TXT records starting with v=spf1, SPF returns a permanent error and fails for every message. Merge all your senders into one record instead. Other TXT records, such as Google site verification codes, are fine to keep alongside it. If you switch email providers, edit the include in your existing record rather than adding a new one.
What is a DKIM selector?
A DKIM selector is the label before ._domainkey in a DKIM record, such as google in google._domainkey.yourdomain.com. It tells receivers which public key to fetch, so one domain can hold separate keys for different services. Your email provider picks it. Google Workspace uses google by default, and Microsoft 365 uses selector1 and selector2. To find yours, look for s= in the DKIM-Signature header of a message you sent.
Do I need DMARC if I only send a few emails?
Gmail, Yahoo and Outlook.com don’t require DMARC from small senders yet, but you should still add it. A p=none record with a reporting address takes five minutes and shows you who sends mail as your domain. Without DMARC, scammers can send phishing emails with your exact domain in the From line, and you’d never know. Small businesses are easy targets because customers trust their name.
Is SPF or DKIM better?
Neither replaces the other. SPF is easy to set up but usually breaks when mail is forwarded. DKIM survives forwarding and proves the message wasn’t changed, but each sending service needs its own key. DMARC only needs one of them to pass and align, and DKIM is usually the one that keeps passing. Set up both. Bulk senders to Gmail, Yahoo and Outlook.com must have both anyway.
What should a parked domain’s records look like?
A domain that never sends email should say so. Publish v=spf1 -all as its SPF record and v=DMARC1; p=reject as its DMARC record. Microsoft recommends the same SPF approach for parked domains. This stops scammers from sending mail that uses a domain you own but don’t use for email. It takes two minutes per domain, and it’s one of the most skipped steps in email security.
Conclusion
Back to those invoices in spam and that 550 bounce from Outlook.com. Neither one meant your business looked shady. They meant your domain couldn’t prove it was you. SPF, DKIM and DMARC are how you prove it, and since Microsoft’s May 2025 rules and Gmail’s November 2025 enforcement push, inboxes act on that proof.
Start with the checker above and fix anything red. Get SPF down to one record under 10 lookups. Turn on DKIM with a 2048-bit key in every tool that sends as you. Add DMARC at p=none, read the reports, then move to quarantine and reject. After that, inbox placement comes down to sending mail people want, keeping complaints low and making it easy to leave. None of this is a one-time job, because every new tool you add needs to be authorized too. Your domain is the return address on every message you send. When did you last check who else is using it?