What email headers tell you
Every server that handles an email adds a Received line to the top of its headers, so reading them from the bottom up gives the route the message took and the time it reached each server. The receiving mail server also records whether the message passed SPF (was it sent from a server the domain allows?), DKIM (was it signed by the domain and not changed?) and DMARC (did either of those match the address in the From line?). Microsoft and most hosting companies add spam scores too.
When an email lands in junk, it's usually one of three things: DMARC failing because the email service signs with its own domain rather than yours, a high spam score from the content, or a sending server with a poor reputation. The headers tell you which.
Questions agencies ask
Start from the bottom of the Received lines and work up: each one is a server the message passed through, with the time it arrived. The gaps between them show where it was delayed. Then look for Authentication-Results, which says whether SPF, DKIM and DMARC passed. This analyser lays all of that out for you.
The most common reason is DMARC failing: the email service (Mailchimp, SendGrid, your website's mail plugin) signs with its own domain instead of yours, so nothing proves the email really came from you. Other reasons are a high spam score from the content or links, a missing unsubscribe link on bulk mail, or a sending server with a bad reputation.
SPF lists the servers allowed to send for a domain. DKIM adds a signature proving the email came from the domain and wasn't changed. DMARC checks that at least one of them matches the address people see in the From line, and tells receivers what to do if not. Since 2024, Google and Yahoo expect all three from bulk senders.
Yes. The analysis runs entirely in your browser and nothing is sent to this server. Headers can include email addresses and server names, so the usual care applies before sharing them anywhere else.
Each server stamps its own clock, and some are a few seconds out. Small negative gaps are shown as zero. Big delays at one hop are usually a queue, greylisting (where a server asks the sender to try again later) or a slow spam filter.
The email was signed by the sending service's domain, such as sendgrid.net, rather than yours. DKIM passes, but DMARC needs the signature to match your From domain. The fix is to set up domain authentication (sometimes called a custom sending domain) in the email service.
Client emails going to junk?
Order confirmations, contact form notifications and newsletters landing in spam is a regular fix for me: SPF, DKIM and DMARC set up properly for WooCommerce, Laravel and every service the client sends through.
- White-label, under your brand, or alongside your team
- Laravel, WordPress, WooCommerce, integrations and tracking
- Inherited and half-finished sites taken over and stabilised
- UK based, straight to the developer, no account managers