Certificate discovery
Find the certs you don't know about. Scan IP/CIDR ranges, watch CT logs for new issuances, detect drift, and transition discovered certs to managed lifecycle.
Overview page
The discovery Overview page: expiry calendar, management coverage, CA, key type and TLS version breakdowns, the last 7 days of activity, top risk reasons, widest reach and sources needing attention.
Discovery sources
A discovery source tells CertAutoPilot where to look for unmanaged certificates. Source types: CIDR/IP scan, hostname list, DNS zone transfer (AXFR), cloud DNS provider (Cloudflare, Google Cloud DNS), and CT log monitor. All feed one inventory. Network scans are SNI-aware, so certificates behind SNI-routed frontends are discovered too.
AXFR (DNS zone transfer) discovery
Name-first discovery for SNI-routed frontends. Pull every host from your internal DNS zones via zone transfer (AXFR), then probe each IP with its own hostname as SNI so every distinct certificate behind an ingress, content switch, or virtual-host load balancer is discovered.
Cloud DNS provider discovery
Name-first discovery for DNS you host in the cloud. When AXFR isn't available (Cloudflare and other managed DNS), list a zone's records through the provider API and probe each host with its own name as SNI, so every distinct live certificate is discovered.
Server certificate scan
Find the certificates stored on the servers you already deploy to: files on Linux (SSH targets) and Windows (WinRM, IIS, Exchange targets), and the Windows certificate stores. The scan is read-only: it finds certificates, never takes a private key off a server and changes nothing there.
Discovery inventory
The inventory is the union of every certificate discovered across your configured sources, de-duplicated by SHA-256 fingerprint. Filter, cross-reference with managed certs, and drill into the servers that serve them โ the inventory is where you answer "what certs do we actually have?"
Servers
Every address and port discovery reached, listed once whatever names and sources saw it, with a page per server for its certificates, TLS settings, names, findings and history.
Activity
What changed in the discovered estate over the last day, week, month or quarter: servers that started or stopped answering, new certificates, replaced certificates, TLS settings changes, and findings raised, reopened or resolved.
Insights
The discovered estate grouped by issuing CA, registrable domain or network, tag and owner, risk reason, and reach (servers per certificate).
Tag rules
Rules that tag discovered certificates and set their owner on their own โ by name, issuer, key, trust, source, address or port โ re-applied after scans, every hour and after every change.
Discovery findings
Findings are the actionable output of discovery. Every scan produces zero or more findings per certificate or endpoint: weak ciphers, legacy TLS, expiring certificates, self-signed, PQC vulnerabilities. Each has a severity, a suggested remediation, and a status you can advance (open โ acknowledged / suppressed / resolved).
Manage wizard
Adopt a discovered certificate into full CertAutoPilot management. The wizard creates a new ACME or AD CS certificate for the same names, links it to the discovered record, and starts its issuance โ after which the lifecycle machinery takes over.
Target candidates
Where discovery found certificates, collected as candidates for distribution targets: one per host, kept current by every scan, removed for good on request, and added as a target through the normal target form.
PQC readiness
How ready the discovered inventory is for quantum computers: the key exchange every endpoint negotiates and the key of every discovered certificate, on the Quantum readiness page and in the inventory, risk score and findings.
Certificate Transparency monitoring
Watch public CT logs (via crt.sh) for certificates issued for your domains โ catch shadow IT and rogue issuance, flag certificates from unexpected CAs.