Every email carries a trail: each server that handled it adds a Received header, and the server that accepted it for you records whether SPF, DKIM and DMARC passed. This tool turns that trail into a table and a verdict, so you can see where a message came from, where it was delayed and why it landed in spam or the inbox.
What you get
- The verdict from your own mail server's Authentication-Results: DMARC passed, failed, wasn't checked, or can't be told because the headers carry no results.
- Every hop, first to last: the name the sending server gave, its address and its reverse DNS name, the server that received it, the protocol, whether the connection was encrypted, and the time it took. Clock problems (a hop stamped before the one before it) and slow hops are marked, and so is the boundary where the message entered your organisation.
- Authentication: the SPF, DKIM, DMARC and ARC results, with the domains each one checked.
- Alignment: whether the From domain matches the Return-Path domain (SPF) and the DKIM signing domains, which is what DMARC actually requires.
- The extras that explain deliverability: the Message-ID domain, the sending software, List-Unsubscribe and one-click unsubscribe, spam scores from SpamAssassin, Microsoft and Rspamd, and any ARC sets added by forwarders and mailing lists.
Pasted mail stays private
What you paste is processed in memory and discarded as soon as the answer is sent. It is never cached, stored, logged, streamed or shared, and it never appears in an error message. The result itself leaves out the Subject, the To and Cc addresses, every name before an @, the recipient part of each Received line and the raw header text. Only domains, addresses of servers and the results remain.
This tool runs entirely on what you paste. It makes no DNS queries and no connections, so the answer is immediate and free, without a daily limit.
Reading the verdict
DMARC passes when SPF or DKIM passes for a domain that matches the From address. If DMARC failed, look at the alignment rows first: often SPF passed for a newsletter service's own bounce domain and DKIM passed for the service's own signing domain, so neither matches yours. The fix is to set up the service to sign with your domain.
A failed SPF result next to a DMARC pass is normal for forwarded mail. A signature that fails while another passes is usually a mailing list footer. A long delay at one hop points to a queue, a greylisting filter or a retry; the hop table shows where it happened.
Spotting a forged message
A forged message usually shows the same pattern: a DMARC failure, SPF failing or soft-failing for a domain that isn't yours, a DKIM signature that fails or names another domain, and a first hop from a home connection or an unknown server. A Reply-To pointing somewhere else is a common sign too. If your own DMARC policy is quarantine or reject, the receiver acted on it; the result tells you whether that happened and why.
Looking up a hop's address
Signed in, each public address in the hop table has a Look up button that runs the IP lookup for that address (1 credit each): its reverse DNS name, whether that name points back, and the registry that allocated it. Only the address is sent; the headers never leave this page.
What we don't do
We don't verify DKIM signatures here: that needs the whole message, including the body. Use the DKIM verifier with the original message for that. We also don't judge whether a message is spam; we show what the receiving servers recorded and what it means.