container audit
GTM-WBWFRQC
12 tags, 5 custom scripts, 9 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 5 custom HTML tags carrying 13 KB of JavaScript. This runs on every page the container loads on.
- 9 third-party hosts reachable from its tags — more than 80% of the 46,522 containers we have measured.
Tags12
Custom scripts5
Third parties9
Delivered447 KB
Versions16
What we observed
A real browser loaded hainanairlines.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
googletagmanager.com — GoogleMeasurement sent to
google-analytics.com — GoogleConsent
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).
Third parties contacted
11 hosts — cdn.dingxiang-inc.com, www.googletagmanager.com, www.google-analytics.com, static.connect.travelaudience.com, www.google.com, ad.doubleclick.net, www.google.co.il, analytics.google.com, and 3 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load, autofeed_trigger
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on hainanairlines.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.
reviewHardcoded http:// URL (3)
3 pieces of custom code reference a plain http:// address.
WhyOn an https:// page the browser blocks or upgrades these. Blocked means the tag quietly stops working; upgraded only works if that host also serves https.
CheckCheck whether the hosts below still respond over https, and update the URLs.
Seenseen in 12.8% 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.hainanairlines.com ×19www.googleadservices.com ×5www.truemetrics.cn ×2googleads.g.doubleclick.net ×1static.connect.travelaudience.com ×1storage.googleapis.com ×1www.google-analytics.com ×1www.picture.com ×1www.securitytrfx.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.
What this audit describes
Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.
| Container | GTM-WBWFRQC |
|---|---|
| Published version | 16 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:17:37 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-WBWFRQC |
| Body checksum | 1e1fec41b5a4e7bf84a5a09dfbdab754f18c7a6e7b8dd9b1dcc5f3aca7353127Evidence 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.
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 »