Email authentication inspector

Turn dense headers into readable signals.

Open an EML or MSG, preserve the raw header view, and summarize the authentication results that survived in the saved file.

Workspace status

Ready · Local browser memory

Drop an email to inspect its safety signals

Open it once. Reader, safety, headers, route, redaction, and export reuse the same in-memory source.

.EML
.MSG
.EMLX
winmail.dat
Processed locally. Files and filenames stay on this device.
Workflow

From source file to finished result

Runs locally
  1. Step 1

    Choose the email file

  2. Step 2

    Review authentication results

  3. Step 3

    Compare the summary with the raw headers

What this workspace preserves

SPF, DKIM, DMARC, and ARC summary

Raw values remain available

Missing results are never treated as automatic failure

Questions about this workflow

Why might authentication results be missing?

Some MSG files, exports, and forwarding workflows do not preserve the original internet headers.

Can a pass prove the sender is legitimate?

No. Authentication can show that a sending domain authorized a message, but it does not establish that the sender or content is trustworthy.