SSL

Certificate expiration check in Really Simple SSL pro

There’s something strange with uptime robots: they don’t detect expired certificates. So even though you don’t get any messages that your site is down, it might be if your SSL certificate has expired… All browsers will block your site, or give scary warnings to users.

This happens because technically, your site is not down. It’s just that there’s no browser that will show your site without giving a lot of scary warnings.

If you have visitors on your site, they will go away quickly. You will drop from Google. So how to handle this? As of 1.0.27, Really Simple SSL pro has a certificate expiration warning option, that will send you an email when your certificate is expiring within two weeks. Every week your certificate is checked, and the valid to date is registered.

This way, you will get an email when your certificate is expiring soon, so you can take appropriate action. Already have Really Simple SSL pro? Then you can just update the plugin, and you will get this option automatically added to your settings. To enable this feature you only have to click the checkbox, save, and you’re done!

7

Related Articles

  • Really Simple SSL entered the hot 100

    This morning I saw several Twitter messages, mentioning that Really Simple SSL is now included in the hot 100 from godaddy. https://garage.godaddy.com/wordpress-hot-100/ This sounds pretty cool, though to be honest...
  • Really Simple SSL 2.5.18 beta release

    2.5.18 is in beta, and can be tested! Please test this new version and let us know your experiences! Removed JetPack SSL fix, as it is now incorporated in JetPack....
  • Security review of Really Simple SSL

    I recently was asked on the WordPress support forums if Really Simple SSL is securely built. I always thoroughly check the code for possible security issues, and secure all posts...
  • Version 2.2 released

    Yesterday the new version was released. With support for per site activation on WordPress multisite, easy uninstall option, and even less overhead on the front-end, which was pretty good already...