MyIPScan

Email Security Tool

Email Header Analyzer

Paste raw email headers to inspect routing and authentication-result signals locally. The pasted text stays in your browser.

Direct answer

Email Header Analyzer: answer first

Analyze pasted email headers locally for routing and authentication result signals. Use the result as an observable public-signal check with stated limitations, not as an absolute guarantee.

Last updated

Analyze headers locally

Paste email headers to start.

What the results mean

Received headers show handoff paths. Authentication-Results can include SPF, DKIM, and DMARC outcomes as seen by a receiving system. Header signals can be useful, but they do not prove whether a message is safe.

How to use this tool

  1. Open the raw original message in your email client.
  2. Copy the headers only.
  3. Paste them here and review routing plus authentication signals.

FAQ

Does this send headers to MyIPScan?

No. The parser is browser-local.

Can headers be forged?

Some headers can be forged or added by different systems. Interpret them with context.

Does this replace mail-provider security tools?

No. Treat it as a local inspection helper, not a complete email investigation.

B2B diagnostic report model

Email domain diagnostics

Email checks connect MX, SPF, DMARC, optional DKIM selector records, PTR/rDNS, sender-IP context, blacklist context, and email-header evidence.

SummaryStart with a plain-language status for the public target.
Top issuesPrioritize the few findings that need attention first.
What passedShow expected public signals without turning them into a certification.
What needs reviewSeparate limited, unavailable, and review-worthy signals.
Why it mattersExplain the business, delivery, crawl, or implementation impact.
Recommended fixesPoint to the DNS, hosting, email, CMS, or SEO owner who can act.
What this tool cannot checkThis does not send mail, inspect private mailboxes, guarantee inbox placement, or certify sender reputation everywhere.
Client-safe copyClient-safe copy should keep authentication findings and fixes while removing email local-parts, raw TXT payloads, raw sender IP details, and private mailbox context.
Monitoring beta (optional)Optional monitoring beta can compare MX, SPF, DKIM selector checks, DMARC policy, PTR/rDNS, and selected blacklist signals for approved domains.

Client-safe report

Share findings without leaking raw technical material

Use Safe Copy or this page's summary when sending results to a client, vendor, developer, or support team. Raw headers, credentials, tokens, cookies, private addresses, email local-parts, and oversized payloads should stay out of client-facing copy.

Review Safe Copy Ask about monitoring beta
Email Deliverability DoctorEmail domain diagnostics follow-up. DMARC CheckerEmail domain diagnostics follow-up. Website Exposure ScannerEmail domain diagnostics follow-up. Domain Intelligence ReportEmail domain diagnostics follow-up. AI/Search Visibility ScannerEmail domain diagnostics follow-up.

Check my email domain

What this checks

Public mail-domain records and pasted email-header signals such as MX, SPF, DMARC, DKIM selector context, and sender-route clues.

Limits

What this cannot check

It cannot guarantee inbox placement, inspect private mailboxes, or certify sender reputation everywhere.

Read results

How to use the output

Treat results as review signals for this browser/session or public target. Re-test after one change, then use Safe Copy or notes that avoid raw identifiers.

Related tools

Continue with the closest checks

Public Exposure ReportFull browser-session report with Safe Copy, issues, fixes, and clear limits. VPN Leak TestCompare visible IP, DNS, WebRTC, IPv6, and browser signals. Email Deliverability DoctorMX, SPF, DMARC, DKIM selector, PTR, sender IP, and blacklist context. Email Security ToolsCategory hub for email authentication and deliverability checks. MethodologyReview how MyIPScan labels signals, limitations, and Safe Copy output.

SEO and AI citation summary

Email Header Analyzer: what this tool does

Parses pasted email headers locally for Received lines, Authentication-Results, SPF, DKIM, and DMARC mentions.

How to use

  1. Enter one public domain, email domain, optional selector, or pasted header depending on the tool.
  2. Review authentication, policy strength, routing, and monitoring signals together.
  3. Apply one DNS or mail-provider change, then retest after propagation.

What the result means

Treat MX, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, PTR, and header findings as email trust signals. They do not guarantee inbox placement or prove sender identity alone.

Limitations

  • This tool reports observable signals only; it is not a guarantee or certification.
  • Client-side parser only.
  • Results can change after VPN reconnects, DNS propagation, browser updates, cache changes, or provider configuration changes.

FAQ

Are pasted email headers uploaded?

No. This analyzer runs locally in the browser and does not send pasted headers to a MyIPScan API.

What does Email Header Analyzer do?

Email Header Analyzer parses pasted email headers locally for Received lines, Authentication-Results, SPF, DKIM, and DMARC mentions. Results are review signals with stated limits.

How should I use Email Header Analyzer results?

Use the result to decide what to review next, make one change at a time, and retest in the same browser, network, domain, or provider context when possible.

What does Email Header Analyzer not prove?

It does not prove anonymity, full security, complete deliverability, full reputation cleanliness, search ranking, or AI citation. It only reports the visible signals available to this tool.

Next checks and references

Email Security ToolsParent hub for this tool category.Email Deliverability DoctorCombined email authentication exposure estimate.SPF CheckerSPF TXT policy check.DMARC CheckerDMARC TXT policy check.MX LookupMail exchanger DNS lookup.Relevant guideBackground reading for interpreting this result.MethodologyHow MyIPScan labels confidence, limits, and safe-copy outputs.