Skip to content
  • There are no suggestions because the search field is empty.

Is it safe to share email headers?

It's generally safe to share email headers privately with the people diagnosing a delivery problem, after reviewing them for personal and internal details. Headers can expose addresses, server names, IP addresses and recipient-specific links. The safest useful sample is a test message sent to a mailbox you control, with the recipient's headers shared through an authorized support channel rather than posted publicly.

Don't strip out every technical line. The domains, sending IP and authentication results are often the evidence the person helping you needs. Redact a copy, keep the original private, and make clear what you've changed.

What email headers contain

Headers describe a message and its route through mail servers. They can include:

  • Addresses and message details: From, To, Cc, Return-Path, Subject, Date and Message-ID.
  • Routing information: Received: lines with server names and IP addresses for the hops that handled the message.
  • Authentication evidence: Authentication-Results and DKIM-Signature, including signing domains and selectors.
  • Filtering verdicts: extra headers added by the receiving provider.
  • Personal links: unsubscribe or tracking URLs that may identify a recipient.

Headers are separate from the message body, but a raw message or copied source can include both. Check the whole file before sharing it, not just the first screen of text.

For the distinction between the visible From address and the envelope sender, see Envelope From vs Header From.

What's sensitive, and what needs to stay

Personal addresses, internal hostnames, private IP addresses and unique link tokens deserve review before sharing. But a domain or public sending IP can be central to the diagnosis. Removing it may protect privacy at the cost of making the sample unusable.

Header information What to preserve for diagnosis What to review before sharing
Authentication-Results The receiver's results and the domains checked Addresses or identifiers embedded in the line
DKIM-Signature At least the d= signing domain and s= selector Other identifiers; tell support if you alter the signature
Received: The public sending IP and relevant route Internal server names and private IPs
Return-Path and From Domains needed to assess alignment Personal mailbox names before @
Provider filtering headers The verdict fields Recipient or tenant-specific identifiers
Unsubscribe and tracking headers The header's presence, where relevant Personal URLs and tokens

Identifier alignment for SPF and DKIM explains why the domains matter for alignment. If the issue concerns a customer domain you aren't authorized to disclose, use a controlled test instead of publishing an altered customer sample.

A safe way to share headers

  1. Reproduce with a test message. Send it through the affected service to a mailbox you control. Avoid customer addresses, customer subjects and confidential message text.
  2. Use the recipient's copy. Copy its full headers as text. In Gmail, use "Show original"; in Outlook, look for message details or view source. A Sent-folder copy doesn't have the receiving provider's final authentication and filtering results.
  3. Separate the headers from the body. Don't attach an entire raw message without checking whether it includes confidential text or attachments.
  4. Redact a working copy consistently. Replace personal mailbox names with labels such as user1@example.com, keeping the real domain only when authorized and necessary for the problem. Mark changed values so the person helping you doesn't mistake them for the original.
  5. Remove personal tracking and unsubscribe tokens. Don't turn a troubleshooting sample into a usable personal link.
  6. Preserve authentication evidence where possible. Don't casually rewrite Authentication-Results, the DKIM signing domain or selector, or the public sending IP. If any of these must be hidden, tell support what was removed and ask whether a test sample would work better.
  7. Share privately. Use the agreed ticket or support channel and give access only to the people working on the issue. Keep the unedited original private in case they need a more complete sample through an approved channel.

Send text rather than a screenshot. Screenshots often omit long or folded lines and make copying the evidence harder.

Redaction changes what can be checked

A redacted header copy can help someone interpret recorded results. It isn't the same as the original message.

Changing signed headers can prevent a signature from being rechecked. Headers alone also aren't enough to recheck the full DKIM signature: that needs the original message body too. Don't send that body automatically. If support needs the full original, first agree a private transfer method and confirm you're authorized to disclose it.

The goal is a useful sample with the least necessary sensitive data, not a promise that every diagnosis is possible after every identifier has been removed.

When headers aren't enough

One message shows what happened to that message at that receiver. It doesn't tell you whether every sending service for the domain is configured correctly.

For a domain-wide view of reported authentication results, use DMARC aggregate reports. A field-by-field walk-through of a DMARC aggregate report walks through a report, and What visual DMARC analysis should show you explains what a visual view should show. Those reports don't show inbox placement.

For the specific problem behind your sample, see Mail started failing after we published DMARC for mail affected by a DMARC change, Third-party mail fails alignment for third-party alignment issues, DKIM signature not found for missing DKIM records, or Authentication passes, but Outlook still puts mail in Junk when authentication already passes and Outlook still files the mail in Junk.

Free DMARC account

Not sure which sender is failing?

Connect your domain's DMARC reports and see every service that sends as your domain, and whether each one passes SPF, DKIM and DMARC.

  • Every sending source in one dashboard
  • SPF, DKIM and alignment results per sender
  • No XML files to read

Create a free DMARC accountTalk to an expert

FAQ

Can someone get my password from email headers?

Normal email headers don't include your account password. That doesn't make them harmless: they can expose addresses, server details, personal links and, sometimes, tokens in tracking or custom headers. Review the sample and share it privately rather than assuming there's nothing sensitive in it.

Which copy should I share?

The recipient's copy of a controlled test message. It includes the receiving system's results, which the Sent-folder copy doesn't.

Can I post redacted headers in a public forum?

A private support channel is safer. Redaction is easy to get wrong, and removing enough information to protect everyone involved can also remove what makes the sample useful.