Explain what each of the three authentication records does, and add them to your domain using your email tool's instructions.
Your email lands more reliably when your domain publishes three records in its settings: SPF, DKIM and DMARC. Inbox providers now expect senders to prove who they are, and these records are the proof. Each one answers a simple question about a message that says it comes from you.
They exist because email has the same weakness as a paper envelope, where anyone can write any sender name they like. With no further checks in place, a scammer could send a message that claims to be from your business, and the inbox receiving it would have no means of telling it apart from your genuine newsletter. Much phishing relies on exactly this gap. Adding the records is covered in Lesson 3.5. What follows explains what each one does.
Mei Ling owns a bakery, and her website and her email address both use the same name, her own domain. A domain is the name that appears in your website and your email address. Behind it sits a group of public settings known as DNS records, which tell the internet things such as where your website can be found and where email for you should be delivered.
You change these settings at your domain registrar or DNS host, meaning either the company that sold you the domain or a service you later pointed the domain to. SPF, DKIM and DMARC each sit in DNS as a text record. They are public by design, so anyone can look them up. Whenever an inbox gets a message that says it is from your domain, it fetches your records and compares the message with what they say.
SPF is short for Sender Policy Framework. Your SPF record lists the servers that are permitted to send email on behalf of your domain, much like a guest list kept at a door. If a message comes from a server missing from that list, it fails the SPF check. Mei Ling uses an email tool for her newsletter and Google Workspace for day-to-day messages, so both services appear in her SPF record.
Each domain can have just one SPF record. If you take on a new sending service later, open the SPF record you already have and add the new service to it, and leave it as a single record. The instructions from your email tool tell you the exact text to add.
DKIM is short for DomainKeys Identified Mail, and it places a digital signature on every email you send. The email tool signs each message using a private key that stays with the tool. You put the matching public key in your DNS, and the receiving server uses it to test the signature. When the signature matches, the receiver knows the message was genuinely signed for your domain and was not altered along the way. Any tampering with the content in transit breaks the match.
You can leave the cryptography to the tool. Your email tool creates the DKIM key and displays the record for you to add, and your only job is to copy it into DNS character for character.
SPF and DKIM hand the receiving server facts about a message, yet neither tells it how to treat a message that fails. DMARC covers that. Your DMARC record instructs receivers on what to do when mail claiming to be from your domain fails the checks, and gives an address where they should send reports.
DMARC also runs a check of its own, called alignment. It confirms that the domain shown to the reader in the From line lines up with a domain that passed SPF or DKIM. The DMARC specification published by the IETF (RFC 7489) sets out exactly how closely the two must match. Without this alignment check, someone could pass SPF or DKIM using a domain they own while presenting themselves as you.
The policy in a DMARC record can be set at three levels:
Monitoring, written p=none, where receivers take no special action and simply send you reports. Quarantine, where receivers treat mail that fails as suspicious, which usually means putting it in spam. Reject, where receivers turn failing mail away completely.
Start at p=none and include an address for reports, then read what comes back. The reports list every service that sends mail as your domain, and they often uncover one you had stopped thinking about, for example an online shop sending order confirmations or an accounting tool sending invoices. Get each of those services passing first. After that, change the policy to quarantine, and move to reject at a later stage. Going directly to reject can block legitimate mail you sent yourself.
In their raw form, DMARC reports are difficult to read. A number of free and paid services convert them into a readable summary, and some email tools handle this for you.
A lot of small businesses send their newsletter from a Gmail or Yahoo address using a marketing tool, and that setup undoes everything described above. You have no way to add SPF, DKIM or DMARC records to gmail.com, because you do not own it. Google and Yahoo each publish their own DMARC policies for their consumer domains. When mail says it is from a Gmail or Yahoo address but is actually sent through a different service, it fails the checks, and inboxes may file it in spam or refuse it.
Fixing this needs a domain that you own. If you have a website domain already, send from an address on it. Priya runs a centre with its own website domain, so she would send from priya@ followed by that domain. If you have no domain yet, buying one costs little next to what poor delivery costs you. Once you have it, your email tool guides you through authenticating it.
In the activity below you will log in to your registrar or DNS host and look at what is already set. Note any SPF, DKIM or DMARC records that exist, and which of the three are missing.
Log in to your domain registrar or DNS host. List the SPF, DKIM and DMARC records set for your domain now, and note any that are missing.
Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).