Home / Acmefyer / Certificate discovery
Find expiring SSL certificates in your network.
The certificate that causes trouble is the one nobody remembered: on the old reporting server, the management interface or the service on port 8443. Acmefyer finds the certificates in your network, with agents on the servers and a network scan from the server, shows issuer and expiry date and tells you for each one whether it is already renewed automatically.
How to check a certificate’s expiry date by hand.
For a single service one line with OpenSSL is enough. It shows name, issuer and expiry date of the certificate the port serves:
openssl s_client -connect intranet.example.com:443 -servername intranet.example.com </dev/null | openssl x509 -noout -subject -issuer -enddate
For a whole network this turns into a spreadsheet someone has to maintain: every server, every port, every expiry date. It is accurate exactly until the next server nobody enters.
- Unknown services
- Only what is on the list gets checked. The forgotten service is not on it.
- Used several times
- The same wildcard certificate often sits on many systems. For a replacement you have to know all of them.
- Warning only
- Monitoring reports the approaching expiry. A person still has to do the replacement.
- How often
- From 2029 public certificates are valid for only 47 days. Every gap in the inventory then shows up roughly every month.
Found certificates: agent scan and network scan in one list.
Every Acmefyer agent searches its system for applications that serve TLS: web servers, mail servers, databases, Java services and every other port that speaks TLS. In addition the Acmefyer server can search address ranges itself, also where no agent runs.
The page “Found certificates” brings both together. Every certificate appears there once, with names, issuer, expiry date and all systems and ports that serve it. What is still missing you take over with one click: Acmefyer adds the domain and, where an agent runs, the matching deployment.
- Agent scan
- Detects IIS, Exchange, NGINX, Apache, Traefik, HAProxy, Tomcat, Remote Desktop, SQL Server, Postfix, Dovecot and PostgreSQL among others, after start and then daily. It only reads configuration files and certificates, never private keys.
- Network scan
- Addresses, host names or ranges such as 192.168.16.0/24, optionally with a port, once a day. The server only opens a TLS connection and reads the certificate presented. It signs in nowhere and changes nothing.
- Missing in Acmefyer
- No domain covers the names. One click adds it with the certificate’s public names.
- Domain exists
- Acmefyer has a matching certificate, but the application still serves another one. One click adds the deployment.
- From Acmefyer
- The application already uses a certificate from Acmefyer. Nothing is left to do here.
- Internal
- Self-signed certificates and those with internal names only. They are hidden and can be shown.
- 01
Enter the ranges
Under “Network scan”, name your own networks, one line per address or range.
- 02
Roll out agents
On the servers whose certificates Acmefyer is to replace itself later.
- 03
Go through the list
“Found certificates” shows what is missing, with expiry date and every place it was found.
- 04
Take over
Add domain and deployment with one click. From then on Acmefyer renews by itself.
