Activity
Discovery → Activity answers what changed since I last looked? for the servers your discovery sources scan. Pick a period — 24 hours, 7 days, 30 days or 90 days — and the page shows a count per kind of change and the changes themselves, newest first, grouped by day. Click a count to show only that kind. The first 100 entries are shown; Show more adds the next 100.
What it lists
| Kind | When it appears |
|---|---|
| New servers | An address and port answered for the first time in the period. A server that only started answering under one more name is not new. |
| Servers gone | Every row of an address and port stopped answering, the last one in the period. A server that lost one name but still answers others is not gone. |
| New certificates | A certificate was seen for the first time in the period. Not managed marks one CertAutoPilot does not manage. |
| Certificates replaced | A server started serving another certificate. The entry names both certificates and what differs (issuer, key, names, expiry). |
| TLS settings changed | A server kept its certificate but changed its TLS version, cipher, post-quantum key exchange or chain trust. The entry shows the before and after values. |
| New findings | A finding raised in the period that is still open or acknowledged. Findings of one type and severity raised on the same day are one entry with their number (a first scan raises many at once); it opens the Findings page filtered by that type. |
| Findings reopened | A resolved, auto-resolved or suppressed finding opened again — detected again by a scan, or reopened by a user. Setting an acknowledged finding back to open is not counted. |
| Findings resolved | A finding a scan no longer detected (no longer detected), or one a user resolved. Suppressing a finding is not counted. It opens the Findings page filtered by that type and the resolved statuses. |
| CA certificates added | Root or intermediate CA certificates that appeared on a target — in its trust store or a CA file — and no server serves. One line per target and day, with how many and where (up to five paths or Windows stores). See Server certificate scan. |
| CA certificates removed | The same, for CA certificates that left a target. |
Reopened and resolved findings of one type and severity on the same day are one entry with the number of findings; a finding that changed several times that day is counted once. They come from each finding's history, which is recorded since 1.7.0: changes before that are not listed.
A change seen under several names of one server, or by several sources, on the same day is one entry that lists the names.
A certificate an entry names that has since left the inventory (no server serves it any more) is shown by the start of its fingerprint and marked (no longer in the inventory).
Limits
- Each kind lists at most its newest 500 entries in the period. When a kind reaches that, its count is shown with a + and a note asks for a shorter period.
- Certificate and TLS changes are kept for 365 days, so the 90-day view is complete. Changes recorded before 1.6.3 do not name the server they happened on and are not listed.
- A server that went away and answers again is not listed as gone; the page shows the current state, not every time a server came and went.
- A user limited to some discovery sources sees only what those sources found: a server is new or gone as far as those sources can tell.
Video tutorial
Short, hands-on videos showing this feature working for real. English audio, English and Turkish subtitles. All video tutorials →