The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Email Deliverability Setup
For a client launch, I configured the domain's email authentication using:
SPF
DKIM
DMARC
The goal was to improve email authentication and reduce the likelihood of legitimate transactional emails being treated as suspicious.
It's an easy part of a project to overlook because it isn't visible in the UI.
But a confirmation, verification or notification email is only useful if it actually reaches the user.
Lesson: Shipping a website includes the infrastructure around the interface, not just the interface itself.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Processing incoming PDF attachments and logging key email data manually takes hours of tedious, repetitive work. Every time a new invoice, quote, or report lands in your inbox, you have to manually open the email, download the PDF, read through dense pages to extract important details, format the data, and log it into Google Sheets row by row.
Which one is faster, saves more time, and prevents mistakes?
4 votes
Ends in 1d
Automated is a time saver🔥🔥
"No DKIM record found": usually the checker asked for the wrong selector. How to find the right one in an email header.
A DKIM key has no fixed address. It lives at selector._domainkey.[your domain], and the selector is chosen by whoever signs your mail. DNS has no query that lists every name under a domain, so a checker can only try common ones (google, selector1, s1, k1...).
A real example, from a run of my email-auth-checker today:
• Amazon SES's own domain, common selectors only: no DKIM key found among 33.
• Same domain, with the selector copied from a real Amazon SES email: 1 active key.
SES uses random 32-character selectors, so no list of common names will ever find them. Gmail had already marked that email dkim=pass.
How to find your selector
Step 1: Send yourself an email from the tool you're checking. In Gmail: ⋮ > Show original.
Step 2: Find the DKIM-Signature header. d= is the signing domain, s= is the selector.
Step 3: Look up s._domainkey.d (often a CNAME pointing to your provider's key).
Right selector and still not found?
• Doubled name: you typed the full s1._domainkey.[your domain] in a DNS panel that adds the domain itself, so the record name ends with your domain twice.
• Partial set: Microsoft 365 asks for two CNAMEs (selector1 and selector2), Amazon SES for three.
• Wrong domain: if d= is your provider's domain, DKIM can pass while DMARC fails, because DMARC needs d= to match your From domain.
• Too early: resolvers can keep an earlier "not found" answer cached for a while, so check again later.
Have you checked the s= in a real header, or only the record your DNS panel shows?
It is one of the best projects for website development and is extremely secure.
:Minimal Luxury web UI concept for a high-end cafe experience
