container audit

GTM-WVPQ6KK6

11 tags, 9 custom scripts, 2 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).

9 custom HTML tags carrying 14 KB of JavaScript. This runs on every page the container loads on.
2 third-party hosts reachable from its tags.

Tags11

Custom scripts9

Third parties2

Delivered376 KB

Versions10

What we observed

A real browser loaded sslcatacombnetworking.com a month ago and recorded every request it made. This is what happened, as distinct from what the container is configured to do. It is one page load — anything that fires only deeper in the site did not fire here.

Container loaded from g.sst.gpl.secureserver.net — the site's own host, and googletagmanager.com

Measurement sent to g.sst.gpl.secureserver.net — not Google

Measurement runs through the site's own infrastructure. Part of the tag library still comes from Google, which is normal — the two are loaded separately.

Forwarded to GA4 — read from the measurement id, not the hostname

Consent no consent gate responded on this page, so there was nothing to hold measurement back (banners are often shown only to visitors in certain regions, and this was not a European visit). Google recorded gcs=G111 (all granted).

Third parties contacted 13 hosts — img6.wsimg.com, www.secureserver.net, cart.secureserver.net, gui.secureserver.net, img1.wsimg.com, g.sst.gpl.secureserver.net, csp.secureserver.net, lptag.liveperson.net, and 5 more

Where the data goes

Confirmed — a browser watched this site send measurement data to g.sst.gpl.secureserver.net, not to Google. observed on sslcatacombnetworking.com More info »

Findings

Ordered by consequence. review has a concrete cost when it bites; info is real but depends on your setup. Seen is how common it is across the containers we have measured — reported separately on purpose, because common and harmless are different claims.

reviewWrites cookies directly (1)

1 piece of custom code set cookies in code.

WhyCookies set this way bypass GTM's consent settings, because the consent checks live in the tag templates rather than in raw JavaScript.

CheckIf any of these cookies are used for analytics or advertising, confirm they are still gated on a consent decision.

Seenseen in 21.2% of 46,522 containers measured

infoLoads JavaScript from another host (4)

4 pieces of custom code fetch and run JavaScript from another host.

WhyWhatever that host serves executes with full access to the page — it can read the DOM, cookies and form fields. The code is not in this container, so it can change at any time without any change here.

CheckConfirm you recognise every host below and that someone owns the relationship. A host you cannot name is the one to chase.

Seenseen in 54.4% of 46,522 containers measured

infoConsent configuration detected (1)

The container declares one or more consent signals.

WhyConsent handling is present in the container. This describes what the artifact declares; what actually happened on the page is measured separately, above.

CheckConfirm these settings match the consent policy you intend to enforce, and compare them with the before-and-after observation.

Seenseen in 44.6% of 46,522 containers measured

Third parties it can reach

Each host is a party that can execute code or receive data in a visitor's browser. Follow one to see who else loads it. More info »

www.google-analytics.com ×1 zn3vocvk54gcbcncu-godaddy.siteintercept.qualtrics.com ×1

Detected on

Sites observed loading this container. A container used across many hosts is a shared template; one on a single host is a bespoke build. Follow a site to see every container it loads.

sslcatacombnetworking.com webyield.net

What this audit describes

Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.

Container	`GTM-WVPQ6KK6`
Published version	`10` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-23 18:22:12 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-WVPQ6KK6`
Body checksum	`88cec9f109a7f0148186814ae39690332e323d8a2fc8d3231373527b959ff878` Evidence of the exact bytes we read, not an identity: Google varies the response per request, so re-fetching an unchanged container yields a different checksum. Compare the published version instead.

Re-audit

This reading is from a month ago. A container can be republished at any time, and nothing here updates on its own — a fresh read is the only way to know whether it still says this. Running it again replaces this page in place, so the link keeps working.

Re-audit GTM-WVPQ6KK6

Check another container

Put this container under version control. Tagora exports it to a repository you own, so every change arrives as a pull request. How it works »