Servers
Discovery → Servers lists every server discovery reached — an address and a port, such as
10.0.0.5:443 or [fd00::1]:8443 — once, however many names it answers for and however many
sources scan it.
Servers and rows
Discovery stores one row per source, address, port and server name (SNI): an ingress that answers for 40 names gives 41 rows (one without a name, one per name), and twice that when two sources scan it. A server is all the rows of one address and port. The names and the sources are inside a server: the server page lists them.
Discovery counts servers wherever it counts places:
- the Servers tile and tab of the inventory,
- the Servers column of the certificate tables (the servers that serve the certificate now),
- the Servers tab and count of a source,
- a discovered certificate's Seen: N servers under M names,
- the server list of the Quantum readiness page.
The API still reports the rows too (total_endpoints beside total_servers, endpoint_count
beside server_count), so totals built on the row counts keep working.
The list
| Column | Content |
|---|---|
| Server | Address and port; an edge tag when the address is a CDN or proxy edge in front of the origin (a proxied cloud-DNS record). |
| Certificate | The certificate served when the client names no host, or else the first answering name's; +N when the server hands out N more certificates depending on the name asked for. No certificate (scan failed) when every scan of it failed. |
| Expires | Expiry of that certificate. |
| Names | How many different server names were answered there. The name-less answer, and the same name seen by another source, are not counted again. |
| TLS | The oldest TLS version any of its names negotiated at a successful scan (shown as a warning when older than 1.3). A name whose last scan failed keeps its old version and is not counted. |
| Key exchange | The weakest key-exchange class among its names that served a certificate (RSA (no PFS), Classical, Unknown, Quantum-safe (hybrid ML-KEM), Quantum-safe (ML-KEM only)). |
| Status | Managed when one of its names serves a certificate managed by CertAutoPilot, Failed when every scan of it failed, otherwise Not managed. |
| Seen by | The sources that found it. |
| Last seen | When a scan last reached it. |
Above the table:
- Search — an address, an address with its port as the list writes it (
10.0.0.5:8443,[fd00::1]:443) or any name answered there (part of it, case-insensitive). A server is listed when any of its names matches, and its counts stay whole. - Status — Managed, Not managed (a name serves a certificate CertAutoPilot does not manage, or an older version of one it does — the server has not received the current one yet) or Failed. A server can be both managed and not managed when its names serve both kinds.
- Source — only what the chosen sources saw (that source's own view of the server).
- TLS — Older than TLS 1.3, or the server's lowest version (TLS 1.0 … TLS 1.3, or not recorded).
- Key exchange — one or more classes, matched against the server's weakest name (the class the column shows), so a server with one quantum-safe and one classical name is listed under Classical only. The export filters its rows by their own class.
- Show failed — servers where every scan failed are hidden unless this is on (or the status filter asks for them).
- Columns — Expires, Key exchange, Seen by and Last seen can be hidden; the choice is kept in this browser only.
- Export — the endpoint export (one row per name, CSV or JSON) with the same filters. It is disabled while a lowest-version, network or domain filter is set, because the export cannot apply them.
Insights also opens the list by network (subnet, a /24 or /64) and
domain (servers that answered a name of that registrable domain or serve a certificate naming it); these
show as Also filtered by chips.
Rows are 10, 20, 50 or 100 per page and can be sorted by server, names and last seen. On the Servers page the search, filters, sort and page are in the page address, so a view can be bookmarked, shared and walked with the browser's back and forward buttons. Views saves the current filters under a name — see Saved views.
The rows do not expand any more: click a server to open its page.
The server page
/discovery/servers/<address:port> shows one server:
- Certificate — the certificate served without a name (or the first answering name's).
- TLS — version, cipher, key exchange (and the groups the server supports when the source probes them), chain verdict, the older TLS versions it still accepts, the stapled OCSP answer and HSTS.
- Names on this server — every name answered there, with a search: the certificate each name gets (a Name mismatch tag when it does not cover the name), its expiry, how the name was found, its status and the sources that saw it.
- Open findings — open and acknowledged findings about its names or the certificates it serves.
- History — what it served over time: every certificate replacement and every change of its TLS settings, newest first, across all its names. Changes are kept 365 days; the page shows the 100 newest.
A server with very many rows shows the first 2000 and says so. The per-endpoint history drawer of earlier versions is gone: the history is on this page.
Access
Reading needs the viewer role. A user limited to some granted discovery sources sees only the servers, names and counts those sources found; a server none of its sources saw is not found.
Saved views
The inventory's Certificates tab, the Servers page and the Findings page have a Views button:
- Save these filters… stores the list's current search, filters and sort under a name (at most 60 characters), pinned or not.
- Pinned views appear as chips above the table; the menu lists every view, pins and unpins them and deletes them.
A view belongs to you and to the project: nobody else sees it, and each user keeps at most 50 per project. Views are personal preferences, so saving one needs only the viewer role and is not recorded in the audit log; saving, changing and deleting views is limited to 30 per minute per user. A view whose filters are no longer valid is refused when it is saved. Deleting the user or the project deletes their views.
API
GET /api/v1/projects/{projectId}/discovery/servers
?search=example.com&status=unmanaged&tls_below_13=true&page=1&page_size=50
&min_tls=1.2&subnet=10.0.1.0/24&domain=example.com
GET /api/v1/projects/{projectId}/discovery/servers/detail?host=10.0.0.5&port=443
See the API reference for every parameter. The older
endpoint routes (/discovery/endpoints, a source's /endpoints and /endpoints/grouped,
/endpoints/{id}/changes, a certificate's /endpoints) still answer, unchanged.
See also
Video tutorial
Short, hands-on videos showing this feature working for real. English audio, English and Turkish subtitles. All video tutorials →