Discovery pages
The discovery screens: sources (scan configuration and run-now), source detail with scan history, the inventory of discovered certificates with PQC badges, the servers and a page per server, security findings with acknowledge/suppress, tag rules, and the manage wizard that turns a discovered certificate into a managed one. Concepts and scanner behaviour live in the Discovery section — this page is the screen tour.
Open it from the sidebar: Certificates → Discovery. All discovery pages are project-scoped. A tab bar across the top of every discovery page leads to each area, in four groups separated by a thin line: Overview · Activity | Inventory · Servers · Findings · Target candidates | Insights · Quantum readiness | Tag rules · Sources. On a narrow screen the bar scrolls sideways: the current area is scrolled into view, and a fade at an edge shows that more tabs are hidden on that side.
Overview
The landing page (/discovery) is the Overview: totals, a 13-week expiry calendar, management coverage with the not-managed certificates that need attention first, the CA / key type / lowest TLS version breakdowns, the last 7 days of activity, the most common risk reasons, the certificates with the widest reach and the sources needing attention. Every number opens the list it counts. With no source yet it offers Add source.
Insights
Discovery → Insights has five views, switched at the top: Issuers, Domains (by domain or by network), Teams (tags and owners), Risk and Reach. See Insights.
Sources
The Sources tab (/discovery/sources) lists your discovery sources. The header has a search box, Refresh, and Add source. When open critical, high or medium findings exist, a clickable Open Findings banner shows the critical/high/medium/low counts and jumps to the Findings page.
| Column | Content |
|---|---|
| Name | Source name. Sortable. |
| Type | HOSTNAME · CIDR · AXFR (DNS zone transfer) · Cloud DNS (provider API) · Targets (certificates stored on your SSH, WinRM, IIS and Exchange targets). |
| Records | Number of scan records (or configured resolvers for AXFR). |
| Health | The scan health verdict; the tooltip lists its reasons. |
| Schedule | Scan cadence: an interval (24h) or a day+time recurrence (Mon,Wed 02:30). |
| Last Run | Relative time, coloured by outcome (green completed, red failed). Never-run sources show Never. |
| Status | active or paused. |
| Actions | Pause/Resume, Scan Now (active sources only), Edit (opens the source's edit page), Delete (removes the source and its endpoints and run history). |
Clicking a row opens the source detail.
Adding a source
Add source opens the Add discovery source page. Its fields are grouped into cards — General, What to scan, Schedule and Checks — with the scan limits, SNI and cipher settings under a collapsed Advanced section (it opens by itself when the estimate exceeds Max Targets); Create source and Cancel stay at the bottom of the page:
- Name, optional Description.
- Type — Hostname (FQDN), CIDR / IP, DNS Zone Transfer (AXFR), Cloud DNS Provider, or Targets (the existing SSH / WinRM / IIS / Exchange targets and target groups to read — see Server certificate scan).
- Type-specific fields:
- Hostname / CIDR — a list of records, each a value (
example.comor10.0.0.0/24) plus comma-separated ports (default443); Paste a list adds many at once — values one per line or separated by commas, trimmed, each given the same ports; Max Targets caps how many addresses × ports the whole source may scan (default 512, at most 65,536); a source whose estimate is larger cannot be saved. CIDR shows an authorization warning, and public IP ranges are skipped unless you enable Allow Public IP Scan. - AXFR — one or more AXFR Resolvers (configured under Settings → Discovery → AXFR Resolvers; the create button is disabled until at least one exists) plus the Ports to probe on each resolved host (comma-separated, default
443). The scan transfers your internal DNS zones and probes every host with its own name as SNI — the authoritative way to find certificates behind SNI-routed frontends. Allow zone transfers from the scanner IP on those DNS servers. - Cloud DNS Provider — a DNS Provider Connection (Settings → Discovery), optional Zones, the Ports to probe, and Proxied records — where a proxied (orange-cloud) Cloudflare record is scanned: Edge and origin (default), Edge only or Origin only. See Cloud DNS discovery.
- Hostname / CIDR — a list of records, each a value (
- Schedule — how the source is scanned automatically, two modes:
- Every N hours (interval, default) — a fixed interval measured from the last completion, minimum 24 hours.
- Days & time (scheduled) — runs at a fixed start time (
HH:mm) in a chosen timezone on the selected weekdays (leave all unchecked = every day). Ideal for off-peak (night) scans when the network is quiet. Automatic runs are checked hourly, so a scan set for02:00starts at or shortly after02:00. An existing source's schedule can be changed later from the source detail page ("Schedule → Edit").
- Cipher Suite Enumeration (network/hostname/AXFR sources) — actively probe which cipher suites the server accepts, not just the one it negotiates: Off, Vulnerable only (recommended default), Selected suites (a red-tagged multi-select), or All (full inventory). See cipher-suite enumeration.
Scanner behaviour, SSRF protection, and scheduling: Sources.
Source detail
Header: source name, status tag, Sources (back to the source list). A Scan health card shows the health verdict with its reasons, the share of endpoints the last scan reached, the average scan time, the share reached per recent scan and how the last scan found its endpoints. A summary card shows the full configuration — type, schedule, concurrency, timeout, max targets, SNI mode, public-scan flag, records (or configured resolvers for AXFR), next scan time, and a red Consecutive Errors counter if recent runs failed — plus a Scan Now button. Triggering a scan navigates straight to the resulting job.
Tabs:
- Certificates — certificates discovered by this source (subject, issuer, expiry, key, Managed / Older version / Not managed status, number of servers serving it); rows open the inventory detail.
- Servers — the server list limited to what this source saw: each address and port once, with its certificate, names, TLS, key exchange and status. Click a server to open its page. The tab and the summary count servers, not rows. CT-log sources have no Servers tab.
- Scan History — one row per run: started (relative), status (completed / running / failed / skipped), total/success/failed target counts, New Certs, Changed, Disappeared, duration, and who triggered it. Rows with a linked job open the job detail.
- Access — who may see, use and manage this source when resource grants restrict a user to some sources. Shown only to an admin of the source.
Inventory
Discovery → Inventory aggregates everything discovered across sources. The summary card on top shows Certificates and Servers answering (each address and port once, without the servers that failed at the last scan — the same number as the Servers tab; hover it for the total), a Managed by CertAutoPilot bar (Managed, Not managed, and Older managed version when there are any) and a Validity bar. Beside it (below it on a narrow screen), a Quantum readiness panel shows two bars: Certificate keys — Vulnerable (weak keys — upgrade first), Transition (standard crypto — migrate later), Ready (post-quantum keys: ML-DSA, SLH-DSA) and Unknown (an algorithm the classifier does not bucket, DSA for example) — and Key exchange on servers (Quantum-safe or Classical); Details opens the Quantum readiness page — see PQC readiness.
Two tabs:
Certificates tab
Search (subject, issuer, SANs) and the inventory filters sit above the table, with Views to save and reapply a set of filters (saved views).
| Column | Content |
|---|---|
| Certificate | Certificate subject. |
| Issuer | Issuer string. |
| Expires | Relative time — red expired, orange expiring within 30 days. |
| Key | Algorithm + size, e.g. RSA 2048. |
| PQC | The post-quantum readiness of the key: Vulnerable, Transition, Ready or Unknown (hover for the explanation). |
| Risk | Stored risk level. |
| Servers | How many servers (address and port) serve this certificate now. |
| Tags · owner | Tags typed by hand, tags from tag rules in blue, and the owner. |
| Status | Managed (green, links to the managed certificate), Older version (an earlier version of a certificate CertAutoPilot manages, still served somewhere; links to the managed certificate) or Not managed. |
| Actions | Manage — opens the manage wizard for a certificate that is not managed. |
Rows open the fingerprint detail.
Servers tab
The server list of the whole project — the same table as the Servers page.
Quantum readiness
Discovery → Quantum readiness (a tab of the Discovery bar) brings the key exchange of every server (host:port, counted once by its weakest endpoint row) and the certificate keys together: two share bars, what the results ask for, the servers by key exchange with a TLS 1.2 or older filter (each opens its server page, with the groups it supports when the source probes them and its history), the groups negotiated, the recent key-exchange changes, a per-source table and the last 90 days. See the Quantum readiness page.
Servers
Discovery → Servers lists each address and port discovery reached once, whatever names and sources saw it: server (with an edge tag for a CDN or proxy edge), the certificate served without a name (+N when other names get other certificates), its expiry, the number of names, the oldest TLS version, the weakest key exchange, status (Managed / Not managed / Failed), the sources that saw it and when it was last seen. Above the table: a search (address or any name), Status, Source, TLS (older than 1.3) and Key exchange filters, a Show failed switch, Columns (optional columns, remembered in this browser), Export (endpoint CSV or JSON) and Views (saved views). 10, 20, 50 or 100 rows per page; search, filters, sort and page are in the page address. The rows do not expand: click one for its page. See Servers.
Server page
/discovery/servers/<address:port>: the Certificate card, the TLS card (version, cipher, key exchange and supported groups when probed, chain, older versions accepted, OCSP staple, HSTS), Names on this server (searchable: each name with its certificate, expiry, how it was found, status and the sources that saw it; a Name mismatch tag when the certificate does not cover the name), Open findings and the History of everything it served.
Discovered certificate detail
Each inventory row opens /discovery/inventory/<fingerprint>:
- Header: the name the certificate is known by, its subject beneath, and tags for the risk level and score (or No risk found), Managed by CertAutoPilot / Earlier version of a managed certificate / Not managed, the key, and Wildcard, Self-signed and CA certificate where they apply. Buttons: Labels explained, Target candidates (the candidates list filtered to this certificate), Import with private key (when it is not managed and the scan kept its PEM; needs the admin role) and Manage with CertAutoPilot — or, when it is managed, Open managed certificate (Open the current version for an earlier version).
- Facts: Issued by, Valid (with a validity bar), Signature, Seen (N servers under M names), Serial number and SHA-256 fingerprint. When no server serving it has answered for a while, a notice says since when.
- Panels: Chain the server sends, Names (the Subject Alternative Names), Risk (weighted risk factors and signals), Open findings for this certificate, and Quantum readiness (with a replacement hint for vulnerable keys).
- Tags and owner — typed tags and owner, and under From tag rules what the tag rules gave.
- Where it can go — its target candidates, switched between Candidates, Added and Removed with counts, a search and 10 per page. Shown only while the certificate is not managed.
- Where it's served — the server list filtered to this certificate; each server opens its page with the TLS details.
- Timeline — one line per server: when each served this certificate, when it was replaced and by what, and whether it is still served, gone or not answering.
- Change history — replacements detected on servers that served this fingerprint, and TLS-settings changes while it was served, with change tags (
key rotated,issuer changed, …) and old → new fingerprints. See drift detection.
Findings
Discovery → Findings lists security findings raised by scans; Views saves and reapplies a set of filters (saved views). Clickable severity tiles (critical / high / medium / low / info) filter the table. Above it: a search box (title, certificate, endpoint), status (default shows open + acknowledged; options All, Open, Acknowledged, Suppressed, Resolved, Resolved (auto)), Severity, Type, Source, Certificate tag and Certificate owner filters, and Export (CSV or JSON).
| Column | Content |
|---|---|
| Severity | CRITICAL / HIGH / MEDIUM / LOW / INFO tag. |
| Title | Finding title; for a certificate finding, the certificate's name and one server it is on (+N for more). Suppressed findings that are still being detected carry a still detected tag. |
| Type | The finding type in words. |
| Status | open · acknowledged · suppressed · resolved · resolved auto. |
| Affected | Number of distinct affected servers (host:port). The expanded row lists every entry — one per SNI name, labelled host:port [sni]. |
| Last Seen | Relative time, hover for exact. |
| Actions | The status changes allowed from the finding's status (operators and up): open → Ack, Resolve, Suppress; acknowledged → Resolve, Suppress, Reopen; suppressed → Resolve, Reopen; resolved → Suppress, Reopen; resolved auto → none. |
- Ack — marks the finding acknowledged; an optional note is stored.
- Suppress — hides the finding from the default view; a reason is required. The finding keeps its still detected tag while scans keep seeing it.
- Resolve — closes the finding as fixed; an optional note is stored. It reopens automatically if a later scan detects the issue again.
- Reopen — sets the finding back to open.
resolved autois set by the scanner itself once the underlying condition disappears.
Expand a row for the description, remediation, affected endpoints and the finding's History: when it was opened, resolved (by a scan or by hand), reopened, acknowledged or suppressed, its severity changes, who made each change and the note (history).
Clicking a row opens the affected certificate's detail page when the finding is about a certificate, and the server page when it is about a server. Finding types, severities, and remediation hints: Findings.
Tag rules
Discovery → Tag rules lists the rules that tag discovered certificates (and set their owner) on their own, in run order: the arrows change the order, each row shows its conditions in words, tags and owner, how many certificates it matched at the last apply (a link to the inventory filtered by its first tag), an on/off switch, Edit and Delete. New rule opens a form with condition rows and a live Matches now count with example certificates; with no rules, one-click examples add External, Internal, Wildcard or Self-signed. Editing needs the project admin role. See Tag rules.
Manage wizard
Manage (from the inventory, the findings shortcut, or the cert detail) starts the adoption flow at /discovery/manage/<fingerprint> — a five-step wizard: Review → Configure → Zone & Domains → Options → Confirm.
- Review — the discovered certificate: subject, issuer, expiry, key, its SANs, the endpoints it's deployed on, and the suggested domains derived from them.
- Configure — certificate name (pre-derived from the primary domain), description, owner and Issue from: ACME or Microsoft AD CS (only what the certificate policy allows). For ACME: the ACME Account (the list respects policy restrictions), organization for OV/EV accounts, and the validation method (automatic DNS, manual DNS, or HTTP). For AD CS: the AD CS connection and Certificate template.
- Zone & Domains (titled just Domains for AD CS, manual DNS and HTTP validation) — the domain list, pre-filled from the suggested domains, with the names grouped by the zone that validates them (as on the issue form); for automatic DNS every name needs a zone with a DNS credential. Policy SAN violations are shown as blocking errors.
- Options — key type (pre-mapped from the discovered certificate's key), auto-renew (locked off for manual DNS, locked on when policy requires it), renewal threshold, key rotation policy.
- Confirm — summary, then Issue Certificate. Issuance may detour to the approval workflow; otherwise you land on the new certificate's detail page, and the discovered fingerprint is linked so the inventory row flips to Managed once the replacement is picked up.
What adoption changes, prerequisites, and troubleshooting: Manage wizard.
See also
Video tutorial
Short, hands-on videos showing this feature working for real. English audio, English and Turkish subtitles. All video tutorials →