Skip to content
Scan & Tracker Intelligence

Discover

Planned

What changed since last month?

Every scan is kept, so the interesting view is the difference: a tracker that appeared, a cookie whose lifetime changed, an endpoint that is new, a service that quietly stopped.

Scan History

  • Scan-to-scan diff
  • New & removed services
  • Category changes
  • Lifetime changes

How it helps

What you get with Scan History

1

Change is the signal

A stable inventory needs no attention. The three new rows after a plugin update do.

2

Attributable in time

Each change carries the scan that first saw it, which is usually enough to work out what caused it.

3

Evidence for the record

Historical scans support the disclosure and the receipts that were valid at the time.

Know what runs before you ask visitors to trust it.

Start with a scan of what your website loads today. The list is usually longer than the team expects, and that is the useful part.

No code to install for a scan Public pages only DotCensus runs on DotCensus