When accessing any of the Mailfence services, the transmission of data between your device program and our servers in Brussels-Belgium is always encrypted and protected by SSL/TLS – for which each website has a (Public Key) Certificate that is verified by a trusted Certificate Authority (CA).
![](https://blog.mailfence.com/wp-content/uploads/2024/07/image-3.png)
A modern browser should automatically check the validity of the Mailfence SSL/TLS certificate and alert you if it detects something untrustworthy. In case an adversary succeeds in spoofing Mailfence (using a rogue SSL/TLS certificate), you will still be able to detect such an (AiTM) attack by manually checking Mailfence SSL/TLS certificate fingerprints.
The Mailfence SSL/TLS certificate fingerprints [valid until August 22nd, 2024, 12:41 PM (Central European Summer Time)] are:
SHA1 fingerprint:
34:D2:C2:9A:00:EB:C3:E0:A3:DB:C1:97:E0:F8:B7:16:E0:88:FD:1C
SHA-256 fingerprint:
2B:AD:FA:CB:C0:FD:BB:6A:3A:31:A5:09:36:CB:4A:17:C2:74:9F:0B:84:2C:9C:53:21:75:67:7B:A9:E8:38:80
If this matches what you see in your browser, then you know you are communicating with the right Mailfence website/service and using the correct public key to encrypt your sensitive information and only Mailfence can decrypt it.
Last updated: July 2024
Next update date: August 2024
Guidelines:
- For Chrome:
- Click on the green padlock in the address bar.
- Click on the Certificate.
- In General, verify that the Fingerprints (SHA1 & SHA-256) matches the one’s above.
- For Firefox:
- Click on the lock button in front of the URL and click on the Arrow on the right side of the dropdown.
- Click on Connection Secure.
- Click on More Information.
- Go to Security and click on View Certificate.
- Verify that the Fingerprints (SHA1 & SHA-256) matches the one’s above.
- For Safari:
- Click on the lock button in front of the URL.
- Select Show Certificate, in Details scroll to the bottom of the page.
- Verify that the Fingerprints (SHA1 & SHA-256) matches the one’s above.
Note: Make sure, in your browser, you are looking at the leaf certificate (mailfence.com, *.mailfence.com). This certificate does not cover blog.mailfence.com and kb.mailfence.com domain names.
For further assistance, feel free to drop us an email at support@mailfence.com
At Mailfence – a secure and private email service, we believe in following good security practices, to contribute in providing you a secure and private email solution. Learn more about who we are.