Does Proton Mail Work in China?

Proton Mail in China may be disrupted, and a working app or an open login page does not prove the entire email workflow works. Check web access, app connection, sign-in, message delivery, and attachments separately. Proton's alternative routing can help supported apps reach its services, but it is not a website feature or an availability guarantee.［1］

Key Takeaways:

• Webmail, the mobile app, sign-in, and email delivery have different failure points.
• Alternative routing belongs to Proton apps and can still fail.
• A connection change does not restore passwords, recovery materials, or recipient acceptance.
• Confirm a harmless send-and-receive task before relying on the mailbox abroad.
• Preserve authenticated sessions and prepare recovery through independent channels.

What evidence supports the Proton Mail in China answer?

GreatFire's current mail.proton.me page, checked on October 5, 2026, labels the address blocked with a last test on July 25, 2026 and only one conclusive test in the displayed window. That is a limited observation about an exact web address. It is not a representative survey of every carrier, the mobile app, or the complete mail transaction.［4］

Do not substitute older protonmail.com observations for measurements of today's web address. A legacy domain, a marketing page, an account page, and an API endpoint may behave differently. Report the address you actually used and avoid concluding that the whole service is available or unavailable from one page.

Proton's own alternative-routing documentation explains the purpose and limits of another path to its servers. The feature is activated when the app suspects interference, is not available for its websites, and does not always succeed.［1］ This supports trying the supported app as a separate branch, not promising that it will work in China.

Our China travel connectivity overview covers broader preparation. If unrelated services also fail, start with the general mainland service diagnostic before changing your mailbox or password.

Which email stage is failing?

Email is a chain of tasks, not a single “works” switch. Opening the inbox proves more than opening a homepage, but it still does not prove that a newly sent message reached its recipient. An attachment may require a separate transfer after the message body has loaded.

Observation	Likely investigation	Evidence worth preserving
Webmail address does not open	Connection or web endpoint	Exact address, network, time, visible error
App cannot refresh an existing inbox	App connection or session	App version and whether older messages remain visible
Sign-in rejects credentials	Account or authentication	Redacted error, not the password or recovery code
Message remains in drafts or outbox	Submission did not complete	Whether the sender view confirms a sent message
Sender shows sent, recipient sees nothing	Delivery or recipient filtering	Delivery notice and recipient's spam-folder check
Message opens, attachment fails	Transfer or attachment-specific issue	File type, size, and error without confidential content

These branches help decide who can resolve the problem. A network operator may explain a local connectivity fault.

Proton support may explain an account error. The recipient or their mail administrator may need to investigate filtering. Reinstalling a browser is not a useful response to every row.

Use a harmless test message with a clear subject and ask the recipient to confirm it through another permitted channel. Check both directions if you depend on replies. Do not send a confidential document merely to establish connectivity, and do not treat the absence of a bounce as proof of delivery.

Can alternative routing help the app when webmail fails?

Proton describes alternative routing as an app-level fallback when its services appear blocked. It can use third-party infrastructure for the connection; the provider may see your IP address and that you are connecting to Proton, while the content remains encrypted. Consult the current app controls if you want to opt out.［1］

The important distinction is between a Proton Mail connection feature and a general VPN connection. Having the Mail app installed does not mean every application on the device uses its route. Conversely, installing a separate VPN does not add Proton's alternative routing to your browser.

Compare outcomes cautiously. If the app refreshes while webmail does not, you have evidence that one client path worked at that time. You do not have evidence that all account pages, large attachments, or future connections will work. Keep the supported client updated through official channels rather than looking for unofficial replacement login pages.

If both clients fail, return to a normal connectivity comparison and check for an official service incident using an available trusted channel. Do not disable certificate checks, install an unknown certificate, or give recovery material to a person offering to “unlock” the inbox. Those actions introduce new risks without establishing the original cause.

How should you prepare a separate network path?

Before departure, test your ordinary mailbox on the device you will carry. Keep a supported app installed, verify that you can receive authentication messages, and record an approved fallback contact method. If your employer controls the device or mailbox, obtain its permitted travel workflow rather than changing security controls yourself.

For the network-connection substep, AethoVPN can be set up on Windows or Android using the official package, then connected to a currently available app location before refreshing Proton Mail. If you use an iPhone, iPad, or Mac, follow the website configuration guide with Pro or Premium. Compare the same harmless inbox refresh on the original path and the connected path before diagnosing the result.

The connection test should verify that the tunnel is active and then test the mail action itself. A public IP observation describes an exit address; it does not prove how every DNS query traveled. Our DNS leak explanation shows why resolver identity and actual routing are different evidence, without asserting an undocumented protection feature for this product.

You can create an account for the three-day Pro trial before traveling, while your verification mailbox is reachable. The trial is available once per user. This prepares a separate connection option; it does not reset a Proton password, supply a missing recovery code, or control the recipient's filtering rules.

Record the observed difference rather than a presumed explanation. “Inbox refresh completed through the second permitted connection” is a useful result. “Email is guaranteed everywhere” is not. If the connection change produces an account warning, stop repeated retries and use the account's official recovery or support process.

What should you do about login and recovery errors?

An explicit credential or two-factor error belongs to the sign-in branch, even if a network issue occurred earlier. Proton's support guidance includes checking the correct username and password, browser requirements, extensions, and device time for authentication problems.［2］ Preserve an existing authenticated session while investigating a second client.

Avoid clearing every device or signing out everywhere as the first repair. That can remove the only usable way to access account settings. Test a clean browser session separately if needed, keeping the known working session intact and protecting any saved credentials.

Account recovery and recovery of encrypted data are not the same outcome. Proton explains that after some password-reset methods you may need a separate data-recovery process.［3］ Before travel, check which recovery methods you have prepared and store sensitive recovery materials securely, separate from routine travel notes.

A recovery channel is weak if accessing it requires the mailbox you are trying to recover. Use the provider's supported alternatives and confirm that you can reach them without that dependency. If you lack the required material, contact official support; a new IP address cannot recreate an absent recovery secret.

How do you verify delivery without confusing it with connectivity?

Distinguish submission from receipt. A message in a draft or outbox has not demonstrated completed submission. A message shown as sent supports a later stage, but recipient filtering or rejection may still prevent it appearing in the expected inbox. Keep any delivery notice rather than repeatedly sending duplicates.

For travel coordination, agree on a second permitted channel before a deadline. If a colleague has not received your email, ask them to check the address and spam folder, then involve their administrator where appropriate. Do not attach sensitive data to multiple retries or ask them to disable security filtering globally.

Attachment trouble also deserves a narrower test. Compare a small, nonconfidential attachment with a plain message, respecting your organization's rules. If the plain message arrives but the attachment does not, investigate size, format, transfer, and recipient policy instead of assuming the whole mail service is blocked.

If you also rely on another mailbox, our Gmail travel-access guide covers its separate dependencies. Two addresses are not an effective fallback when both require the same unavailable recovery channel or untested connection.

Summary

• Evaluate webmail, app connection, sign-in, delivery, and attachments individually.
• Treat alternative routing as a supported app fallback with documented limits.
• Prepare a permitted network option and independent recovery before departure.
• Confirm the recipient's outcome instead of relying only on the sender view.

FAQ

Is Proton Mail always blocked in mainland China?

The available observation for mail.proton.me is too limited to prove an always-blocked nationwide result. Plan for disruption, and test the particular client and mail task you need without generalizing from one web address.［4］

Can I rely on alternative routing for the website?

Alternative routing is documented for Proton's apps, not its websites. A working app therefore does not establish that the browser login or webmail page will work through the same connection.［1］

Is Proton Mail the same product as Proton VPN?

Proton Mail and Proton VPN perform different tasks. A Mail connection feature should not be described as providing a device-wide VPN, and a VPN connection does not supply account recovery or mail delivery guarantees.

Will a VPN recover my Proton account?

A VPN may affect connectivity, but account recovery still requires Proton's supported verification and recovery methods. A missing password, code, or data-recovery secret must be handled through the account process.［3］

Why can I read messages but not open attachments?

Attachments can involve a separate transfer and additional size or policy constraints. Test a harmless small file and preserve the specific error rather than treating readable message text as proof that all transfers work.

Does the sent folder prove my email was received?

The sent folder does not establish that the recipient saw the message. Obtain a recipient confirmation and review delivery notices or filtering when the email matters to a deadline.

What should I prepare before visiting China?

Prepare a supported client, a harmless two-way mail test, secure recovery material, and an independent permitted contact channel. Complete verification and installation while the required mailbox and official download channels are reachable.

Disclaimer: VPN laws differ by country and region and may change. This article is not legal advice. Review and comply with local laws before using a VPN.

Sources:

1. Introducing alternative routing to prevent censorship of Proton apps — https://proton.me/blog/anti-censorship-alternative-routing
2. Troubleshooting sign-in issues — https://proton.me/support/common-login-problems
3. Reset your Proton Account password — https://proton.me/support/reset-password
4. Is https://mail.proton.me blocked in mainland China? — https://en.greatfire.org/https/mail.proton.me

Sources checked 5 October 2026.