The Pre-Consent Check loads a public page the way an ordinary first-time visitor does — no cookies carried in, no banner clicked, no consent given — and records every tracking technology that fires anyway during that window.
Checking only the HTML source finds less than half of what is actually running. Most trackers arrive after the page loads: injected by a tag manager, fired by a script, or set as a cookie before anything is clicked. Five layers are used because a tracker invisible to one layer is usually plainly visible to another.
window.fbq or window.gtag.The scanner carries a signature set covering the tracking technologies most commonly found firing before consent. Among them:
Signatures are added as new technologies appear. A technology absent from this list is not evidence of its absence from your site — it may simply mean no signature exists for it yet, which the report states plainly rather than reporting a clean result.
A detection describes behavior. Whether that behavior carries legal consequence depends on the jurisdiction, the data involved, the disclosures in place, and facts a scanner cannot see. Take these findings to your own counsel — the report is written to be handed to a lawyer, read by someone who was not present at the scan, and re-verified independently.
This date reflects the last revision to the signature set and layer logic described above. It is set by hand when the scanner actually changes, not generated on page load — a date that renews itself every time someone visits would be a claim, not a signal.
For how reports are signed and how to re-compute the hash yourself, see About TrackGuard Pro.
TrackGuard Pro checks and verifies only. It does not install, remove, configure, or repair anything on any site.