❯ Email Deliverability for Small Teams: SPF, DKIM, DMARC Without the Hype
by Jonas Reyes — the builder's desk, Side Quest Studios
November 10, 2026
Alright, let's talk email. Not the "AI will write your emails" nonsense, but the actual delivery. The stuff that keeps your transactional emails out of spam folders and your investor updates actually seen. You've got a small team, maybe a couple of services sending mail, and suddenly your "Important Notice" emails are vanishing into the void. You've heard the acronyms: SPF, DKIM, DMARC. Vendors will sell you a five-figure "deliverability audit" for this. Don't bite. This isn't rocket science, and you don't need a consultant. You need to set three DNS records, and maybe check a log or two. We'll nail this down in 15 minutes.
Your email not landing is a business problem. It means your password resets don't arrive, your customer support tickets go unanswered, and your marketing emails are dead on arrival. For a startup, this is existential. Your reputation is tied to this, and email providers are ruthless. One bad sender, and your entire domain gets red-flagged. It's like building a new soda brand with a $2B exit, then forgetting to secure your supply chain Allison Ellsworth, Jetty launch. You built the product, now make sure it gets to the customer.
Forget the "trustworthy AI" whitepapers and the ethical debates in Go games. This is basic infrastructure. It's about telling the world, "Yes, this email actually came from us." Without these three records, you're shouting into a hurricane. Let's make it easy.
SPF: Who's Allowed to Send?
SPF (Sender Policy Framework) is the bouncer for your domain. It tells receiving mail servers which IP addresses are authorized to send email on behalf of your domain. If an email comes from an IP not on your list, it's immediately suspicious.
This is a TXT record you add to your DNS. It looks like this:
v=spf1 include:_spf.google.com include:sendgrid.net -all
Let's break it down:
v=spf1: This just says "this is an SPF record, version 1."include:_spf.google.com: If you use Google Workspace (Gmail for your domain), Google publishes their authorized sender IPs here. You just include it.include:sendgrid.net: If you use SendGrid for transactional emails, they have their own SPF record. Same deal. Add all your legitimate senders here. Common ones includemailgun.org,_spf.mail.intercom.io, etc. Check your mail provider's docs. They all have one.-all: This is critical. It means "any server not listed in this SPF record is NOT authorized to send mail for my domain." This is a hard fail. There's also~all(soft fail), which means "maybe it's authorized, but probably not." For a small team, always use-all. Be definitive. You know who sends your email.
Action: 1. List every single service that sends email on behalf of your domain (Google Workspace, SendGrid, Mailgun, AWS SES, Intercom, whatever). 2. Find their SPF include directive. It'll be in their documentation. 3. Combine them into a single TXT record. 4. Go to your DNS provider (Cloudflare, AWS Route 53, Namecheap, etc.) and add this TXT record for your root domain (yourdomain.com).
One-liner check: Use dig -t TXT yourdomain.com | grep spf to see your current SPF record. If you have multiple v=spf1 records, you've made a mistake. You can only have one. Combine them.
DKIM: Cryptographic Signature for Trust
DKIM (DomainKeys Identified Mail) is like a tamper-proof seal on your emails. When an email is sent, your mail server signs it with a private key. The receiving server then uses a public key (published in your DNS) to verify the signature. If the signature matches, the email hasn't been altered in transit, and it genuinely came from your domain.
This also goes in your DNS as a TXT record. Unlike SPF, you'll have one of these for each sending service, and they'll give you the exact record to publish.
Example for SendGrid (selector s1):
s1._domainkey.yourdomain.com. IN TXT "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDnL/2..."
s1._domainkey: This is the selector. Your mail provider generates this. They might uses2,google,mailgun, etc. It's how the receiving server knows which public key to look up.yourdomain.com: Your domain.- The long string of characters: This is your public key.
Action: 1. For each mail-sending service (Google Workspace, SendGrid, etc.), go into their settings and find the DKIM setup. 2. They will provide you with a CNAME or TXT record to add to your DNS. It usually looks like selector._domainkey.yourdomain.com. 3. Add these records to your DNS provider.
Gotcha: Sometimes, providers give you a CNAME that points to their DKIM record. That's fine. Other times, they give you the raw TXT record containing the public key. Either way, just paste what they give you. Double-check for typos. Seriously. One character off, and it fails.
DMARC: What to Do When SPF/DKIM Fail?
DMARC (Domain-based Message Authentication, Reporting, & Conformance) is the referee. It tells receiving mail servers what to do if an email fails SPF or DKIM, and crucially, it sends you reports on those failures. This is how you gain visibility into who is trying to impersonate your domain.
This is also a TXT record, specifically for _dmarc.yourdomain.com.
v=DMARC1; p=quarantine; fo=1; ruf=mailto:dmarc-reports@yourdomain.com; rua=mailto:dmarc-aggregate@yourdomain.com
Let's break this down:
v=DMARC1: DMARC version 1.p=quarantine: This is your policy.quarantinemeans "put emails that fail SPF/DKIM in the spam folder." Other options arenone(just monitor, don't take action – good for starting out) andreject(delete them immediately – the strongest policy, use this when you're confident). For a small team, start withnonefor a week or two, then move toquarantine.fo=1: Forensic options.1means "generate a report if any authentication mechanism fails."ruf=mailto:dmarc-reports@yourdomain.com: This is where forensic (individual failure) reports get sent. These can be voluminous, so consider a dedicated mailbox.rua=mailto:dmarc-aggregate@yourdomain.com: This is where aggregate (summary) reports get sent. These are XML files, usually sent daily, and they are GOLD. They tell you exactly which IPs are sending mail for your domain, whether SPF/DKIM passed, and how many messages were sent.
Action: 1. Create two new email addresses: dmarc-reports@yourdomain.com and dmarc-aggregate@yourdomain.com. 2. Add the TXT record to your DNS for _dmarc.yourdomain.com with p=none initially. 3. Monitor the dmarc-aggregate@ mailbox for a week. Use a DMARC report parser (there are free online ones, just search "DMARC report parser") to make sense of the XML. This will show you if all your legitimate senders are passing SPF/DKIM. 4. Once you're confident everything legitimate is passing, change p=none to p=quarantine. Give it another week. 5. Finally, change p=quarantine to p=reject. This is your ultimate protection.
This entire DMARC setup provides crucial visibility. You'll see if a compromised account or an old, forgotten service is sending mail as your domain. It’s like getting a daily security audit without hiring anyone. I've seen countless "unexpected" senders show up in these reports — old marketing automation tools, forgotten dev environments, even compromised employee accounts. DMARC tells you.
Practical Workflow and What to Watch For
- Start with SPF: Get your single SPF
TXTrecord right first. Include all current senders. - Add DKIM: Implement DKIM for each sender. This is usually the trickiest part because each service has its own key.
- Deploy DMARC (p=none): Get the DMARC record up, pointing to your new email addresses, with a
nonepolicy. This is the monitoring phase. - Analyze Reports: For at least a week, check those aggregate reports daily. Don't skip this. This is where you find out what you missed. If you see legitimate emails failing, go back and fix your SPF/DKIM for that sender.
- Increase Policy: Once clean, move to
p=quarantine, thenp=reject.
Tools & Tricks: * dig: Your best friend. dig -t TXT yourdomain.com for SPF, dig -t TXT selector._domainkey.yourdomain.com for DKIM, dig -t TXT _dmarc.yourdomain.com for DMARC. * Mail-tester.com: Send an email to the address they provide. It'll give you a score and tell you exactly what's passing and failing. Invaluable. * Google Postmaster Tools: If you send a lot of mail to Gmail, set this up. It gives you domain reputation, spam rates, and DMARC errors directly from Google. Essential.
Don't Overthink It. Just Ship It.
This isn't some abstract AI ethics debate for government engineers AI Trends, Government AI Engineers. This is concrete, actionable infrastructure. You're configuring three DNS records. It will take you 15 minutes of actual work, and maybe a week of monitoring.
The biggest mistake is paralysis. You spend days reading vendor blogs, getting lost in the acronym soup. Don't. Just follow these steps. Get those records in place. Start with p=none on DMARC. Get those reports. Iterate. This stuff works. It keeps your emails out of spam, and it protects your brand. It’s a foundational piece of your digital presence. Implement it, then move on to building something cool.
by Terminal King — the terminal, Side Quest Studios