Public signal checker
Ads and Tracking Signal Checker
This checker helps teams spot public marketing and analytics signals that may need documentation, consent review or performance attention.
The check uses public live signals and does not make a security, malware, fraud or legal verdict.
Run a public signal check
- HTTP
- DNS
- TLS
- RDAP
- Archive
What this checker analyzes
- Google Tag Manager, Google Analytics, Google Ads and AdSense markers where visible.
- Meta, TikTok, Pinterest, Microsoft Clarity, Hotjar, Matomo, Plausible and similar signatures.
- Consent-tool signals that may relate to tracking disclosures.
Why it matters
- Tracking and ads integrations can affect privacy notices, consent flows, performance and vendor governance.
- Visible signatures give non-technical stakeholders a starting point for questions.
What the results mean
- Detected or Possible means a public marker was found.
- The report does not say whether the integration is active, configured correctly or legally compliant.
- No signal found only means SiteTraceKit did not see a known marker in the public response.
Limits of this check
- JavaScript is not executed, so late-loaded tags may be missed.
- Tag-manager containers can load tools that are not visible in static HTML.
- This is not a consent or privacy-law audit.
What should also be reviewed manually?
Review notable values in the context of the actual website, its subpages and connected services. A homepage check cannot prove the complete configuration, legal position or security posture.
FAQ
Does a Google Tag Manager signal mean tracking is active?
Not necessarily. It means a container marker is visible. The container configuration needs separate review.