Target candidates
Discovery → Target candidates lists the places discovery found a certificate, so you can turn them into distribution targets without typing their addresses again.
A candidate is a draft, never a target by itself. Discovery sees where a certificate is served; a target is where CertAutoPilot connects to install it — SSH on port 22, WinRM on 5985/5986, a device's management API, the Cloudflare API. Those are often a different address or port, and they need a credential. So you choose the target type, check the address and pick the credential; nothing is created for you.
What becomes a candidate
- One candidate per host. All ports, server names (SNI) and certificates seen at one address — an IP, or a name for a hostname source — are one candidate. The same host seen by several sources is one candidate that names every source.
- Only places that served a real certificate. Failed rows, and hosts whose only certificate is a placeholder (the Kubernetes ingress fake certificate, the Traefik default certificate), are not candidates.
- Cloudflare edge addresses are never candidates — the edge is updated through the Cloudflare API, not at an address. Proxied names become Cloudflare zone candidates instead: the zone is filled in when the cloud-DNS source lists its zones (the longest matching zone); otherwise you enter it. Origin rows behind Cloudflare are ordinary host candidates.
- The pool is rebuilt by the findings refresh — after a scan (at most once every five minutes per project; a scan inside that window is picked up by the next refresh), every hour and when a source is deleted — from what discovery already stored. It never scans anything itself, so it adds no time to a scan.
- A place discovery no longer sees leaves the list; a removed or added candidate is kept with a not seen any more mark so its state is not lost.
- The same machine can appear twice when one source scans it by IP and another by name: there is no DNS lookup to join them.
Candidates, Added, Removed
| Tab | What it holds |
|---|---|
| Candidates | Places still seen that you have not removed or added. |
| Added | Candidates a target was created from (the target is linked). When the last target made from a candidate is deleted, it goes back to Candidates. |
| Removed | Candidates you removed. No later scan brings them back, even when the host serves a new certificate. From here you can Restore one to Candidates (or to Added if a target was already made from it) or still Add as target. |
Each row shows:
| Column | What it shows |
|---|---|
| Where | The host (or, for a Cloudflare zone candidate, the zone) with tags: Cloudflare zone, managed cert (at least one certificate found there is managed by CertAutoPilot) and not seen any more. |
| Ports and names | One line per port: host:port, a protocol tag for STARTTLS, and up to three server names (+N for more). A host with more than eight ports shows the first eight and a +N more ports link; Show fewer ports folds the list again. |
| Certificates | How many different certificates were found there. |
| Seen by | The discovery sources that saw it. |
| Suggestion | The suggested target type, with the fact it rests on in the tooltip. |
| Targets | Already a target: <name> links to existing targets at that address. |
| Actions | Add as target, and Remove (or Restore under Removed). |
The list shows 20, 50 or 100 candidates per page. A discovered certificate's page has the same three states in its Where it can go card — the candidates where that certificate was seen, with a count per state, a search and 10 per page.
Removing and restoring need the operator role and are audit-logged
(DISCOVERY_TARGET_CANDIDATE_REMOVED / _RESTORED). Anyone who can see the project's discovery
can see the list; a user limited to granted resources sees only the
candidates one of its granted discovery sources saw — and of a host several sources scanned, only
the ports, names, certificates and suggestions its own sources saw. Searching and filtering look
at the same part. Removing and restoring need only the project operator role, not a grant above
viewer on the source (like triaging a finding).
Already a target
A candidate whose host — or one of its names — is exactly the address of an existing target shows Already a target: <name> with a link. The comparison is plain text (case-insensitive) against the address field of SSH, WinRM, IIS, Exchange, F5 BIG-IP, NetScaler, PAN-OS, FortiWeb, FortiGate, A10 Thunder and cPanel targets; there is no DNS resolution. A Cloudflare zone candidate matches a Cloudflare target that names the same zone (a target that names only the zone id is not matched). You can still add another target for the same machine (for example SSH and WinRM).
Suggestions
Some candidates carry a suggestion — never selected for you, always with the fact it rests on:
| Suggestion | When |
|---|---|
| Kubernetes | The host served the Kubernetes ingress default ("fake") certificate or the Traefik default certificate on one of its ports. |
| Windows (WinRM / IIS / Exchange) | Remote Desktop (RDP) answered on the host. |
| Cloudflare | The names are proxied by Cloudflare (seen at the edge). |
They come only from what the scan already read; discovery does not probe hosts further to guess their platform. Device-specific suggestions (F5, NetScaler, FortiGate/FortiWeb, PAN-OS and the like) are not made.
Add as target
- Add as target on a candidate (Candidates or Removed).
- Choose the address the target connects to — the host or one of its names — and which places become validation endpoints. Only ports that speak TLS directly are offered: the post-deploy validation opens TLS at once and does not speak STARTTLS. The endpoints are checked at the address discovery saw (an IP goes into IP, a name into Hostname) with the chosen server name.
- The normal target form opens with the name, the validation endpoints and — once you pick a type — the address filled in, plus what discovery saw and its suggestion. A Cloudflare zone candidate opens as a Cloudflare target with its zone. You pick the type and the credential.
- Save works exactly like any target create: the configuration approval gate (an operator gets an approval request), the licence target limit and your target permissions all apply. A candidate that no longer exists or that you cannot see is refused at once, before any approval request is made. When the target is created — directly or when its approval is executed — the candidate moves to Added.
A target only receives certificates once it is in a distribution module linked to the certificate; adding it from a candidate does not do that for you.
Video tutorials
Short, hands-on videos showing this feature working for real. English audio, English and Turkish subtitles. All video tutorials →