🔒 Privacy Policy

Last updated: January 2025. SecurityAnalysts.org is a free community service. We take your privacy seriously — especially on a security site.

What we collect

If you accept cookies, we use Google Analytics to collect anonymous usage data (pages visited, time on site, country). IP addresses are anonymised. We collect no names, emails, or personal details from analytics.

If you submit the contact form or a site suggestion, we receive the information you type. This is stored securely via Formspree and used only to respond to you.

What we never do

Cookies

We use one category of cookies: analytics cookies (Google Analytics), only if you consent. These are used to understand how many people visit and which guides are most helpful. You can withdraw consent at any time by clicking "Decline" below.

We also use a sessionStorage item (not a cookie) to remember language preferences and consent state within your visit.

Advertising

This site displays adverts served by Google AdSense. Google may use cookies to serve ads based on your prior visits to this and other websites. You can opt out via Google's Ad Settings.

Your rights (GDPR)

If you are in the EU/EEA, you have the right to access, correct, or delete any personal data we hold about you. Contact us at [email protected] for any data requests.

Contact

Questions about this policy: [email protected]

Home/Email Header Analyzer

Email Header Analyzer

Paste raw email headers from a suspicious message and inspect authentication clues such as SPF, DKIM, DMARC, Reply-To, and mail path.

Advertisement

Paste the full headers from a suspicious email. We'll break them down and flag anything that looks wrong.

How to get headers: Gmail: open email → ⋮ menu → Show original · Outlook: File → Properties → Internet headers · Apple Mail: View → Message → All Headers

What we look for:

✅ SPF — did the email come from an authorised server?
✅ DKIM — is the email's content verified and unaltered?
✅ DMARC — does the domain enforce anti-spoofing?
🔍 From vs Reply-To — do they match? Mismatch = suspicious
🔍 Sender IP — where did the email actually originate?
🔍 Mail path — how many servers did it pass through?
How to use this

Look for mismatches

Failed SPF, DKIM, or DMARC checks do not automatically prove a message is malicious, but combined with urgency, payment requests, or a mismatched Reply-To address, they are strong warning signs.

Advertisement