The Mailfence SSL/TLS Certificate

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).

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 current Mailfence SSL/TLS certificate fingerprints are:

SHA1 fingerprint:

68:F6:D4:6D:70:21:76:BF:1B:58:8B:19:21:A8:6B:90:4E:46:DD:66

SHA-256 fingerprint:

8A:C3:7E:01:60:9D:3C:6D:88:E1:31:50:7D:15:C1:29:12:91:38:6B:AB:94:7E:49:67:18:9B:0C:60:7A:E9:94

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: January 2026
Next update date: April 2026

Guidelines:

• For Chrome:
  1. Click on the green padlock in the address bar.
  2. Click on the Certificate.
  3. In General, verify that the Fingerprints (SHA1 & SHA-256) matches the one’s above.
     
• For Firefox:
  1. Click on the lock button in front of the URL and click on the Arrow on the right side of the dropdown.
  2. Click on Connection Secure.
  3. Click on More Information.
  4. Go to Security and click on View Certificate.
  5. Verify that the Fingerprints (SHA1 & SHA-256) matches the one’s above.
     
• For Safari:
  1. Click on the lock button in front of the URL.
  2. Select Show Certificate, in Details scroll to the bottom of the page.
  3. Verify that the Fingerprints (SHA1 & SHA-256) matches the one’s above.

Note: 1) Make sure, in your browser, you are looking at the leaf certificate (mailfence.com, *.mailfence.com). 2) 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.