This assumes you have created one or more certificates using Certbot. If not, check out my articles:

• Create standalone public private key pair using Certbot
• Create wildcard public private key pair using GoDaddy and Certbot

Let's say you have have something like this.

~]$ sudo ls -l /etc/letsencrypt/live/example.com/
lrwxrwxrwx 1 root root  34 Jul 17 10:34 cert.pem -> ../../archive/example.com/cert.pem
lrwxrwxrwx 1 root root  35 Jul 17 10:34 chain.pem -> ../../archive/example.com/chain.pem
lrwxrwxrwx 1 root root  39 Jul 17 10:34 fullchain.pem -> ../../archive/example.com/fullchain.pem
lrwxrwxrwx 1 root root  37 Jul 17 10:34 privkey.pem -> ../../archive/example.com/privkey.pem

The certbot certificates command can be used to get a brief summary of each of your Certbot certificates.

~]$ sudo certbot certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Found the following certs:
  Certificate Name: example.com
    Serial Number: 123456789abcdefghi123456789abdefghi
    Key Type: ECDSA
    Domains: example.com *.example.com
    Expiry Date: 2023-10-15 14:34:41+00:00 (VALID: 80 days)
    Certificate Path: /etc/letsencrypt/live/example.com/fullchain.pem
    Private Key Path: /etc/letsencrypt/live/example.com/privkey.pem
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -