In this guide, I’m going to show you how to display the SSL expiration of any domain in Home Assistant. This setup will create a couple sensors which can then be added to a Lovelace card.

If you own several domains, you know how challenging it can be to monitor their SSL certificates. (Especially if you are using LetsEncrypt and don’t have them setup to renew automatically.)

To set this up, I read a bunch of Community forums posts until I found something that was super easy. You can literally copy and paste the code into your configuration.yaml file, change the domain name, and the expiration dates will show up!

Note: There is a default Home Assistant integration called Certificate Expiry which will fetch the certificate from your Home Assistant server, but for this tutorial – I want to display when the SSL certs from my other domains.

So if you just looking to monitor Home Assistant, add that integration instead.

Let’s get started!

How It Works

The SSL issued date and expiration date is being pulled in from this website:

For this example, I’m going to use my site, This will create two sensors for me to use: sensor.shp_cert_expiry and sensor.shp_cert_issued. Once these are created, you can add them to any Lovelace card. You can optionally create automations to remind you before they expire (example automation at the end of the tutorial).

If you plan on monitoring several domains/subdomains, you will basically duplicate the two sensors below, change the domain, and give them each a unique sensor name.

Create 2 Sensors

First, you need create two sensors by going to File Editor > configuration.yaml from your HA sidebar. Paste these two into your sensors: codeblock.

  1. Create a sensor to get SSL issue date
  2. Create another sensor to start counting down when there is 90 days or less remaining until the renewal date.
  • Blue: Enter the domain you wish to monitor the SSL expiry of
  • Orange: Unique sensor name for your domain
  • Green: The name of your SSL expiry sensor. Make sure to update the sensor name in the 2nd sensor.

Note: I’m using “shp” as the abbreviation for my site so my sensor names are a little shorter. You can of course change this to whatever you want.

1. SSL Cert Issued Sensor

- platform: rest
    name: SHP Cert Issued
    scan_interval: 14400
    value_template: '{{ value_json[0].not_before }}'

2. SSL Cert Expiry

- platform: template
        value_template: '{{ 90 - (( as_timestamp(now()) - as_timestamp(strptime(states.sensor.shp_cert_issued.state, "%Y-%m-%d")) )/ (3600*24)) | round(0) }}'
        unit_of_measurement: Days

Restart Home Assistant

After adding the two new sensors, restart Home Assistant from Configuration > Server Controls.

You can now find these two sensors under your Entities page.

Add SSL Expiry Sensors to Lovelace Dashboard

Now that the sensors have been created, you can use them to any card you’d like.

Just for your reference, here’s a few different ways you could display them in a dashboard. I’ve found that visually displaying these in Lovelace is a great way to be reminded everytime you open the app.

Personally, I like using the gauge cards for this. I’ve added them to a separate “Network” view, but I also added a conditional card to my primary dashboard that only shows up when 0 days are remaining.

Entity Card

Entities Card

Gauge Card

Conditional Card

This card will only displays when there is 0 days remaining. I keep the actual gauge cards that count down the number of days remaining on my Network view, but have this card on my primary dashboard.

type: conditional
  - entity: sensor.shp_cert_expiry
    state: '0'
  type: gauge
  min: 0
  max: 100
  entity: sensor.shp_cert_expiry

Automation To Alert When Domain Expires

If you’d like to create an automation using these new sensors, you can do that too. This automation will notify you once the countdown inches closer to being expired, starting when there is 3 days remaining.

You can change the notification service to your phone, a persistent notification, or whatever method you’d like to use.

  - alias: "SHP Certificate Expiry Notification"
    initial_state: true
      - platform: numeric_state
        entity_id: sensor.shp_cert_expiry
        below: 3
      - service: notify.home_assistant
          title: "SSL Certificate Expire Notification"
          message: >
                    <b>Today is {{ now().strftime( '%B %d, %Y') }} </b> <br>
                    Domain ssl certificate expires in {{ states.sensor.shp_cert_expiry.state }} days. <br>
            images: []

Wrapping Up

All in all, this is a really simple way to display expiration dates of all of your websites. It works with standard domains as well as subdomains.

This is a great way to view the validity of your SSL certs very quickly to help you stay on top of their renewals.

After setting this up, I’m considering installing Home Assistant at my day job just so I can quickly monitor the 30+ domains we use.

I hope this guide helped you out!

My Favorite Home Assistant Devices

Below are some of the Home Assistant-compatible devices I personally use in my home. I highly recommend each of them.

The full list of all Home Assistant compatible & recommended devices I use can be found on my Equipment List page.

Similar Posts


  1. Svetoslav Tolev says:

    Integrated Cert Expiry sensor supports also 3rd party sites – when you configure integration – it asks for host / port.

    1. Oh interesting, that is good to know! The HA doc on Certificate Expiry doesn’t mention that at all so I didn’t even attempt installing it.

  2. nicktheradiovosht says:

    Great idea and very useful. However, from Jan 2022 though, the strptime and as_timestamp methods both require a default value to be added! Zero (0) is a suitable value though changing the logic a bit to detect use of the default is a further step to avoid getting silly large values displayed when the defaults get used.

    A MORE SERIOUS ISSUE is that the behaviour of strptime has changed as well. In the past a partial format pattern could be used to match from the start of the provided time string, hence YYYY-MM-DD or similar was OK. Now, a few tests in Jan 2022 show that the format string has to match every character in the provided string. So you could change the format to something like %Y-%m-%dT%H:%M:%S+00:00 which works for me in UTC time. You cannot use %z to match the time zone +00:00 as it does’nt match the ‘:’ given in e.g. my current timeout of: 2022-04-24T09:47:54+00:00. Yet again, you could do some string manipulation on the provided time before use. This is indeed the solution giving :

    strptime(states((“sensor.shp_cert_issued.state”)[:-15], “%Y-%m-%d”, 0)
    ** note the change to function states, extra speech marks round argument + brackets to force exvaluation of the function result its last 15 characters chopped off fed to strptime so it works now correctly again.

    Which works from Jan 2022 onwards!

Leave a Reply

Your email address will not be published. Required fields are marked *