SPF, DKIM and DMARC in plain words: the 30-minute fix that stops people sending email as you
What the three email records do, why Gmail and Outlook now reject mail without them, and the safe order to switch them on without losing real email.
Anyone on the internet can send an email that says it comes from accounts@yourcompany.gr. Nothing in the email system stops them by default. Three DNS records are how your domain tells receiving mail servers which messages are really yours: SPF, DKIM and DMARC.
They cost nothing, take about half an hour to set up, and they are the most common gap we see when we check small and mid-sized companies. They also carry 15% of a VelonGrade, under Email.
Why this matters now
- Invoice fraud. The classic attack is an email "from" a supplier or your own finance team asking a customer to pay into a new IBAN. Without DMARC, receiving servers have no instruction to reject the fake.
- Your real email gets lost. Since February 2024 Google and Yahoo require senders to authenticate their mail, and anyone sending more than 5,000 messages a day to Gmail must also publish a DMARC record (Google's sender guidelines). Microsoft announced similar rules for Outlook.com in 2025. Unauthenticated mail is increasingly filtered or rejected.
- Insurers ask about it. Email authentication is a standard question on cyber insurance proposal forms, because business email compromise is one of the most frequent claim types.
What each record does
| Record | Question it answers | Lives at |
|---|---|---|
| SPF | Which servers may send mail for this domain? | TXT on yourcompany.gr |
| DKIM | Was this message signed by the domain and left unchanged? | TXT on selector._domainkey.yourcompany.gr |
| DMARC | What should a receiver do when a message fails, and where should it send reports? | TXT on _dmarc.yourcompany.gr |
SPF and DKIM prove a message is legitimate. DMARC ties them to the address people actually see in the From line and tells receivers what to do with failures. Without DMARC, the other two leave a gap.
The safe order to switch them on
1. List everything that sends email as you
Your mailbox provider (Microsoft 365 or Google Workspace), plus newsletter tools, invoicing software, the website contact form, the CRM, the booking engine. Forgetting one is the only real risk in this whole process.
2. Publish one SPF record
One record per domain, listing each sender. For a company on Microsoft 365 that also uses a newsletter tool, it looks something like:
v=spf1 include:spf.protection.outlook.com include:servers.mcsv.net -all
Each provider documents the exact include: to use. Keep it under 10 DNS lookups. Two SPF records on the same domain is an error, and so is +all.
3. Turn on DKIM at every sender
In Microsoft 365 and Google Workspace this is a switch in the admin console plus one or two DNS records they give you. Most newsletter and invoicing tools have the same option under "domain authentication".
4. Start DMARC in monitoring mode
v=DMARC1; p=none; rua=mailto:dmarc@yourcompany.gr
p=none changes nothing about delivery. It only asks receivers to send you daily reports of who is sending as your domain. Read them for two to four weeks (a free DMARC report viewer helps) and fix any legitimate sender that fails.
5. Tighten to quarantine, then reject
Move to p=quarantine once your real senders pass, then to p=reject. Only quarantine or reject actually stops spoofed email. A DMARC record stuck at p=none for years protects nobody.
Common mistakes we see
- DMARC at
p=noneforever. It's the most common finding. It's a starting point, not the goal. - Two SPF records after switching provider. Receivers treat the result as an error.
- Forgetting parked domains. A domain that never sends email should say so:
v=spf1 -allandv=DMARC1; p=reject;. Otherwise attackers use it, because nobody is watching it. - Reports sent to a mailbox nobody reads.
How to check your own domain
Run a free check on Velontech. It reads only public DNS and tells you which of the three records are missing or weak, with the exact fix. If you'd rather check by hand, any DNS lookup tool will show the TXT records at the addresses in the table above.
For the full technical definition, DMARC is specified in RFC 7489.
What does your company look like from outside?
Free check, public information only, results in about a minute.