Why one method is never enough
You cannot renew a certificate you do not know about, and the certificates nobody knows about cause most expiry outages, as we explain in how to stop certificate expiry outages. Discovery is the step that finds them.
Each discovery method sees a different part of your estate. Public logs see what public CAs issued. Network scans see what is served. Host checks see what is stored. Cloud APIs see what is held in cloud services. A complete inventory combines all four.
Certificate Transparency logs
Public CAs record every certificate they issue in public Certificate Transparency (CT) logs. Searching those logs for your domains lists every public certificate issued for them, including ones a team or vendor ordered without telling you.
What CT logs miss:
- Certificates from internal CAs, which are not logged.
- Where a certificate is installed, or whether it is installed at all.
- Which of several certificates for the same name a server actually uses.
Treat CT as the list of what exists publicly, then find where each one lives.
Network scans
A scan connects to addresses and ports and records the certificate each service presents. It sees what clients see, which makes it the best check of what is really in use.
Scan more than port 443. Certificates are also used on, for example, 8443 and other alternative HTTPS ports, 636 (LDAPS), 993 (IMAPS), 995 (POP3S), 465 (SMTP submission over TLS), 3389 (RDP) and 5986 (WinRM over HTTPS). Mail on ports 25 and 587 and many databases start in plain text and switch to TLS with STARTTLS, so the scanner must speak that protocol to see the certificate.
What scans miss:
- Names. Many servers choose a certificate from the hostname the client sends (Server Name Indication). A scan by IP address alone may see only a default certificate. Scan by hostname too, using the names from CT logs and DNS.
- Unreachable places. A scan sees only networks it can reach. Run scanners inside each network segment, with permission from whoever owns it.
- Stored but unused certificates. A certificate that is waiting on disk is invisible until it is served.
Host and file checks
On the servers themselves, certificates live in files and stores: PEM and DER files, PKCS#12 (PFX) bundles, Java keystores and the Windows certificate store. Checking these finds certificates before they are served, and shows which application uses which file.
Do this with an agent or a configuration management tool that already has access to the host. Read only the certificates, never copy private keys off the host for an inventory.
Cloud and platform APIs
Cloud services hold certificates that neither a host check nor many scans will see. For example, AWS Certificate Manager, Azure Key Vault and Google Cloud Certificate Manager each have APIs to list certificates. Kubernetes keeps TLS certificates in Secrets of type kubernetes.io/tls. Content delivery networks and hosting platforms have their own lists. Each needs read-only credentials to list.
Combining the results
- Merge the results by certificate fingerprint, so the same certificate found by CT, a scan and a host check becomes one record with three locations.
- Give every record a team owner. Unowned certificates are the ones that will expire unnoticed.
- Flag anything surprising: certificates from CAs you do not use, names you do not recognise, expired certificates still being served.
- Run discovery continuously, not once. New services appear every week, and a one-off scan is out of date as quickly as a spreadsheet, a problem we cover in why certificate tracking spreadsheets fail.
Where clm.mt fits
We make clm.mt, so weigh this accordingly. Its discovery by network scan from agents inside your networks and by Certificate Transparency search is in preview: it has passed our local tests, not yet a customer’s network. Certificates you then manage through clm.mt are tracked with owners, and each deployment is checked against what the endpoint serves.
See the integrations page for what is supported and in preview, the docs for setup and pricing for the plans.
Sources
- IETF, RFC 6962: Certificate Transparency.
- Kubernetes, Secrets, including the
kubernetes.io/tlstype.