Insights
Discovery → Insights groups what your discovery sources found five ways. Every count opens the list it counts. The views read what the last scans stored and are refreshed at most once a minute.
Issuers
One row per CA that issued a discovered certificate. The CA is the issuer's organisation, or its full name when the certificate names none — the same value the inventory's Issuer filter uses. Self-signed certificates are one row of their own.
| Column | Meaning |
|---|---|
| Certificates | Certificates from this CA. When the organisation has several issuing certificates (for example R10 and R11), the number is shown under the name. |
| Servers | Different servers (address and port) serving its certificates now. Not a link: the server list has no CA filter. |
| Chain verified by | Its certificates by how servers' chains verified: public roots, a source's CA (the CA certificate set on the source), not trusted, or not served now. Each part opens the inventory with the trust filter. |
| Expiring in 30 days, Expired | As in the inventory. |
| CAA | Whether the domains' CAA records allow the CA. CAA is checked only for publicly trusted certificates; — means none of its certificates was checked. |
At most the 500 CAs with the most certificates are listed; a note above the table says when more exist.
Domains and networks
By domain groups certificates and servers by registrable domain (www.shop.example.co.uk →
example.co.uk). The names come from each certificate's common name and SANs, and from the names
servers answered for. Names under a suffix the public suffix list does not know, such as
.internal or .corp, are grouped by their last two labels (svc.northwind.internal →
northwind.internal). A certificate naming several domains counts in each of them, so the rows do
not add up to the total.
| Column | Meaning |
|---|---|
| Certificates | Certificates with a name whose registrable domain is this one. Opens the inventory with the domain filter, which uses the same rule — so amazonaws.com does not include bucket.s3.amazonaws.com, a registrable domain of its own. |
| Servers | Servers serving one of those certificates, or answering a name whose registrable domain is this one. Opens the server list with the domain filter. |
| Names | Different names under the domain. |
| Expiring in 30 days, Expired, Not managed, Critical | Among the domain's certificates. Expiring in 30 days counts from the moment the view was computed and opens the inventory with that exact date range. |
IP addresses in certificates and names without a registrable domain (localhost) are counted in
their own rows, which are not filters.
By network groups servers by their address: a /24 for IPv4, a /64 for IPv6. Servers scanned by host name are one row. Servers opens the server list with the subnet filter; Failed counts the servers whose last scan failed. The certificate counts of a network are not links.
Both groupings list at most the 2,000 largest groups; a note above the table says when more exist.
Teams
Certificates per tag and per owner. Tags are the ones typed on a certificate and the ones tag rules gave it; the owner is the typed one, or else the rule's. Owners are grouped regardless of letter case. No tag and No owner open the inventory with the no_tag / no_owner filters.
Risk
The certificates by stored risk level, and every reason that adds to a certificate's risk score with its weight, most common first. Each bar opens the inventory with the risk_factor filter. Risk is recomputed every hour and after each scan (at most once every 5 minutes per project), so:
- expiry reasons can lag the live expiring within filters by up to an hour;
- a certificate found since the last recompute is counted as not scored yet, never as no risk.
Attention signals such as CBC ciphers or a classical key exchange are not stored and are not listed.
Reach
Certificates ranked by how many servers serve them now: if one expires, all those servers stop working together. Filter by wildcard and by managed. An earlier version of a managed certificate still served is tagged Older version and is left out of Not managed. Servers opens the certificate's own server list. A certificate a server still served at the last scan but that has since left the inventory is listed by the start of its fingerprint, without a link, and its server count is not a link either.
Not managed counts on every view mean that no CertAutoPilot certificate claims the certificate; earlier versions of managed certificates are not among them, as in the inventory filter.
Who sees what
A user limited to some discovery sources sees only what those sources
found. A project with more than 500,000 certificates or server-and-certificate pairs is refused with
DISCOVERY_TOO_LARGE rather than summarised partly.
Video tutorial
Short, hands-on videos showing this feature working for real. English audio, English and Turkish subtitles. All video tutorials →