Skip to content

Can Proton Mail Be Traced? What Email Evidence Can Reveal

Proton Mail headers can reveal delivery evidence, but usually not a sender’s personal IP. Here is what to preserve, examine and corroborate.

By Sourabh12 min read

When a suspicious email arrives from a Proton Mail address, it may say very little about the person who sent it. There may be no recognizable name, no useful signature, and no obvious connection to someone you know.

Can the email be traced? Would its headers reveal an IP address? Could investigators identify the person behind the account?

A Proton Mail message can provide evidence about its delivery, timing and associated files. However, messages sent through Proton’s web and mobile apps do not include the user’s personal IP address in their outgoing headers.

The distinction matters because tracing a message’s delivery is different from identifying the person who sent it. The first may be possible from the received email. The second usually requires additional evidence.

What Can a Proton Mail Email Reveal?

An email contains more than the words displayed in the inbox. It also carries technical information used to deliver and process the message. This information is commonly described as email metadata.

Sender and recipient addresses, timestamps, message identifiers and mail-server details can help explain how a message reached its destination. They do not all have the same evidential value.

For example, a name in the From field is something the message presents. A delivery connection recorded by a trustworthy receiving server is an observation made by that system. Neither finding, by itself, establishes a person’s identity.

A received email can provide addresses, delivery-server details and timestamps. Connecting those records to a person requires additional evidence. Teaching illustration.

Proton’s encryption also needs to be understood in this context. Its Mail Privacy Policy describes accessible delivery metadata, while stating that encrypted message content is not accessible to the provider.

That does not mean every email uses identical protections. Messages exchanged between Proton users and ordinary unencrypted messages exchanged with external services have different encryption arrangements.

Preserving the Original Email

Before examining a suspicious message, preserve what you received.

A screenshot can record the appearance of an email, but it usually leaves out the full headers, message structure and attachment bytes. Forwarding the message normally can add a new delivery wrapper. Neither should be the only copy retained.

Keep the message in the mailbox wherever possible and save an original-message export supported by your receiving service. Record the source mailbox, collection time and time zone, export method and original filename.

For an email in a Proton Mail account you are authorized to access, open the message on the web and use the three-dot More menu beneath the sender details. Select Export and save the EML file.

If a Proton sender’s message arrived in another service, use that receiving service’s original-message download or export. You do not need access to the sender’s mailbox to preserve your own received copy.

Keep a preserved copy and examine a separate working copy. The export records what was acquired from the mailbox; it should not automatically be treated as a complete, independently authenticated record of everything held on the provider’s servers.

A SHA-256 hash can help detect later changes to the saved file. On macOS:

bash
shasum -a 256 suspicious-email.eml

On Windows PowerShell:

powershell
Get-FileHash .\suspicious-email.eml -Algorithm SHA256

Record the result with the collection notes. A later matching hash supports that the saved bytes have not changed since hashing. It does not establish who sent the message or whether its contents are true.

The wider principles of documenting and protecting digital evidence are covered in our digital first response lesson.

Examining the Full Email Headers

Most email applications display a simplified view of a message. Full headers provide the delivery and processing information behind that view.

In Proton Mail’s web app, open the message and select More → View headers. The header window also offers a text download. That text file contains headers; it is not the same acquisition as a full EML message with its body and attachments.

Several fields are particularly useful:

  • From and Reply-To show the presented sender and requested reply destination. These values can be misleading or forged. A difference between them needs context, rather than an automatic conclusion of fraud.
  • To shows the recipient named in the message. It does not identify every actual delivery recipient, including recipients omitted from that displayed field.
  • Date records the stated message time and offset. Sending software can supply this value, so compare it with trusted server timestamps.
  • Message-ID can help correlate copies or records. Its format is not an identity certificate, and the value can be copied or fabricated.
  • Received records server handoffs where the system adding the entry is trustworthy. Authentication-Results reports checks by an identified receiving system; the reporting source also needs to be trusted.

Our email header analysis lesson explains these fields in greater detail. For a Proton Mail investigation, the important question is what each field actually establishes about this particular message.

Inside the Message Headers Window

Proton’s official header guide includes the genuine interface example below. It shows the Message headers window and the Download control for saving the displayed headers.

This is Proton’s published example of an internal Proton message, dated June 2022. It demonstrates the interface, rather than evidence collected for this article. The fields in your own message will differ.

Screenshot: Proton support. The pictured message is dated June 2022. This is a published interface example, not a message collected for this article.

For an authorized working copy, this Python 3 example reads selected fields and calculates the file hash without opening attachments or fetching remote email content:

python
from pathlib import Path
from email import policy
from email.parser import BytesParser
import hashlib

raw = Path("suspicious-email.eml").read_bytes()
message = BytesParser(policy=policy.default).parsebytes(raw)
print("SHA-256:", hashlib.sha256(raw).hexdigest())
for field in ("From", "To", "Date", "Message-ID",
              "Received", "Authentication-Results"):
    for value in message.get_all(field, []):
        print(f"{field}: {value}")

Save the script as inspect_email.py and run python3 inspect_email.py in the folder containing suspicious-email.eml. Keep the raw file alongside the report.

The parser makes stored values easier to read. It does not decide whether those values are genuine.

Local inspection also avoids sending an unredacted message to an online header analyzer. Such uploads may disclose addresses, subjects, identifiers and routing details to another service.

Does Proton Mail Reveal the Sender’s IP Address?

Finding an IP address in an email header does not necessarily mean you have found the sender’s connection.

Email passes through mail servers before reaching the recipient. A trustworthy receiving server may record the address of the server that connected to it. That address can explain part of the delivery route without identifying the sender’s computer or phone.

Proton’s explanation of email tracing states that messages sent through its web and mobile apps exclude the user’s IP address from outgoing headers. Keep that scope when interpreting the claim. Other clients, forwarding services and sending configurations need their own examination.

Conceptual delivery diagram, not a capture of a real message. Trusted receiving records may identify a sending mail server; that does not identify the person operating the account.

An IP lookup may identify the operator of a visible mail-server address or suggest where that infrastructure is located. It does not turn the location of a server into the location of the person using the account.

There is also a question of which header entries deserve trust.

Receiving servers prepend Received fields, so the apparent chronological route runs from bottom to top. However, an attacker can insert header text before a trusted receiver handles the message. The lowest entry is not automatically the most reliable.

Begin with the receiving infrastructure you can establish as trustworthy, then assess which earlier details can be corroborated. A plausible server name alone is not sufficient.

What Do Email Authentication Results Prove?

Before attributing a message to the claimed service, examine the receiving provider’s authentication results. These checks help evaluate domains and delivery infrastructure, but they answer different questions.

  • SPF checks whether a connecting host is authorized for the SMTP envelope-sender domain, or the HELO identity where applicable. It does not directly authenticate the visible From address.
  • DKIM checks a domain’s cryptographic signature over specified message data. It concerns the signing domain and covered data, rather than the personal identity of a user.
  • DMARC checks whether the visible From domain aligns with a passing SPF or DKIM result. All three mechanisms do not have to pass for DMARC to pass.

These distinctions are explained in our lesson on email protocols, headers and spoofed messages.

The source of the reported result matters as much as the word pass. Anyone can write an Authentication-Results line into a file. A parser displaying it has not independently verified the message.

Even a genuine authentication pass does not establish that the named account holder personally sent the email. A compromised account or an account deliberately used for fraud can send authenticated messages.

The reverse also needs care. Forwarding or message modification can complicate legitimate authentication results, so a failure alone does not prove fraud.

Finding Connections Beyond the Email Headers

Sometimes the more useful lead comes from a connection outside the message.

An email address may appear on a public contact page, in a document or on a forum. Such a reference can help an investigator develop a hypothesis about the account’s use.

Search the complete address before treating a similar username as a connection. Record where the reference appeared, when it was collected and what the surrounding page actually said.

A matching username is not proof that two accounts belong to the same person. Public pages can be outdated, copied or deliberately misleading. Several websites repeating one source do not provide independent corroboration.

Our web OSINT and digital footprint lesson explains how to evaluate these connections and document their limitations.

Use public information and records you are authorized to examine. Account-recovery probing, deception or unauthorized access is not a substitute for evidence, and a search result should not become a public accusation.

Examining Attachments and Message Content

A suspicious email may contain a PDF, photograph or office document. Depending on how the file was created and processed, it may retain author properties, software identifiers, timestamps or image metadata.

For a supported file, ExifTool can display available metadata using a read-only command:

bash
exiftool suspicious-document.pdf

Our ExifTool metadata guide explains how to interpret that output.

Consider a PDF whose Author property contains a name. That name may belong to its creator, but it may also have been inherited from a template or retained in a document copied from another source.

The property therefore provides a lead. It does not establish who attached the file or sent the email.

Teaching illustration: file metadata supplies leads. A property may be inherited from a reused template and does not establish who sent the email.

The same caution applies to timestamps and image metadata. Software processing can alter them, and missing EXIF does not establish deliberate concealment.

Potentially dangerous attachments should be examined in an appropriate isolated environment. Do not casually open unknown files, enable macros or fetch embedded links while collecting evidence.

Message wording can provide context too. References to a particular event, unusual terminology or information shared by a small group may help organize enquiries.

However, similarities in writing, especially in a short message, are not conclusive evidence of authorship. They need independent support and consideration of alternative explanations.

Can Police Obtain Information From Proton Mail?

The information visible to a recipient and the information a provider may hold are separate questions.

Section 2.5 of Proton’s general Privacy Policy says permanent account IP logging is off by default. It also describes exceptions involving abuse prevention and enabled security logging.

That position does not guarantee that every account has no IP information. It also does not establish that historical login records exist for the message being investigated.

Proton’s law-enforcement guidance states that data disclosure follows Swiss legal processes. If requested data can be supplied, it is transmitted through Swiss authorities. The guidance also addresses inquiries about preserving records.

An ordinary request to support does not give a private individual access to another user’s account records. A lawful investigation must establish the relevant authority and use the appropriate channels.

The available records depend on what was retained, the account’s circumstances and the applicable legal process. Nor does obtaining provider records mean encrypted message content can automatically be decrypted.

These are limits described in the provider’s published policies, rather than advice about the legal procedure for a particular case.

Connecting the Evidence to a Person

Consider a hypothetical investigation in which a trusted receiver records a mail-server connection, a PDF attachment contains an author name, and a public website lists the displayed sender address.

At first, the findings may appear to point to the same person.

But each observation concerns something different: a delivery hop, a file property and a published association. The PDF may be a reused template. The website may be outdated. Another person may have operated the account.

Even an account found on a lawfully examined device does not, by itself, establish who sent a particular message.

Investigators need to compare provenance, timestamps and time zones, test alternative explanations, and identify which sources independently support a conclusion. Collecting several versions of the same weak lead does not make it independent evidence.

The report should distinguish what was observed from what was inferred, including any uncertainty that remains.

What to Do After Receiving a Suspicious Message

Preserve the original message, full headers and relevant context before blocking or reporting it. If there are repeated messages, related payment requests or losses, keep a timeline.

Use the receiving provider’s phishing or abuse reporting route. Proton’s published guidance directs evidence of service abuse to abuse@proton.me. Reporting abuse is different from requesting another person’s private records.

For threats, fraud or an immediate safety concern, contact the relevant local authorities rather than trying to confront a suspected sender.

A Proton Mail investigation may establish useful facts about a message’s delivery and associated evidence while leaving the sender’s identity unresolved. Recognizing that limit is part of a careful examination, rather than a reason to disregard the evidence that is available.