Third-party connection checker

See every third-party service your homepage connects to

A public HTTP scan that lists every external domain your homepage loads scripts, styles, images and iframes from — sorted by vendor.

Each row is a subprocessor candidate you have today, before any opt-in.

https://

Third-party connection checker

A public HTTP scan that lists every external domain your homepage loads scripts, styles, images and iframes from — sorted by vendor.

Why static references matter

When a user visits your homepage, their browser executes every script and downloads every image on it. That alone is enough for GDPR data-flow records to be impacted. Each external domain we list is a separate entity whose role under GDPR should be documented.

GDPR · Regulation (EU) 2016/679 ↗

How we group them

We resolve each external hostname, look it up in our curated vendor database, and label the category (analytics, advertising, payments, consent, hosting, CDN) and the vendor's registered jurisdiction where it is documented.

Frequently asked questions about this angle
  1. Can I tell which third parties track my visitors from this output?

    You can see which domains load on first visit, which scripts they are loaded as, and whether we recognise the vendor. Whether the visitor is personally tracked depends on each vendor and on consent — we only show the public surface.

  2. Why do you group by vendor and not by URL?

    A single vendor may serve from many domains and CDN edge nodes. Grouping by vendor gives a one-line answer to "do I have Meta on my page?" rather than "do I have a pointer to fbcdn.net/...?" The raw URLs remain available in the expanded evidence panel.

  3. Why is the vendor list different from my consent-management platform?

    Your CMP lists vendors that load after consent. The scanner sees what loads on first visit, before a CMP banner has had a chance to render. Both views are needed for a complete audit.