Email header analyser

"Why did our email go to junk?" The answer is almost always in the headers. Paste them in to see the route the message took and how long each step took, whether SPF, DKIM and DMARC passed, what the spam filters scored it, and what to fix. It all runs in your browser, so nothing is sent anywhere.

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.

FOR AGENCIES

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

Related free tools