This is a follow up of last blog post Mailfence launches new blog, and provide details over the SSL/TLS certificate for this blog.

A modern browser should automatically check the validity of the Mailfence blog SSL/TLS certificate and alert you if it detects something untrustworthy. For security conscious users who want to manually check, our blog SSL/TLS certificate fingerprints/thumbprints (valid until 19/November/‎2020) are:

SHA1 fingerprint:

B6:A8:83:A8:B1:03:3E:1D:80:FB:DE:1F:80:C9:F7:BC:AF:E4:77:1B

SHA-256 fingerprint:

DE:92:51:18:04:79:1E:F5:08:65:F0:2F:C6:99:84:D8:94:96:6E:DE:93:F6:E3:C8:78:A5:08:94:85:3A:E8:16

If this matches what you see in your browser, then you know you are communicating with the real Mailfence blog website and using the correct public key to encrypt your sensitive information and only Mailfence blog can decrypt it.

Last updated: Monday, 18th of November 2019

Next update date: Thursday, 19th of November 2020

Guidelines:

For Chrome: Click on the lock button in front of the URL. Click on the Certificate . In Details tab, show All and verify the Thumbprint matches the one above (SHA1).

For Firefox: Click on the lock button in front of the URL and click on More Information . Go to Security and click on View Certificate . In General , verify 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 the Fingerprints (SHA1 & SHA-256) matches the one’s above.



Note: make sure you are looking at the certificate for blog.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.

Get your secure email

Follow us on twitter/reddit and keep yourself posted at all times.

Mailfence Team