container audit

GTM-TF5X74CL

This container is published but empty — no tags, so nothing fires.

Tags0

Custom scripts0

Third parties0

Delivered315 KB

Versions2

What we observed

A real browser loaded space.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 — Google

Measurement sent to google-analytics.com — Google

Consent Quantcast answered its own API. 3 measurement hits left the page before it was granted, carrying a client id (whether that is permitted depends on jurisdiction, and this was not a European visit). 10 hosts appeared only after consent was granted. Google recorded gcs=G111 (all granted). 10 advertising hosts were contacted before anything was granted.

Third parties contacted 25 hosts — fonts.googleapis.com, cdn.mos.cms.futurecdn.net, vanilla.futurecdn.net, slice.vanilla.futurecdn.net, search-api.fie.futurecdn.net, sdk.mrf.io, cdn.privacy-mgmt.com, freyr.futurecdn.net, and 17 more

dataLayer events seen gtm.js, pageLoadEvent, elementInteraction, gtm.dom, cmpLoaded, __cmpPingCCPA, __cmpPingGDPR, cmpModalInfo, gtm.triggerGroup, marfeel_page_view, hawkEvent, userIdEvent, +3 more

Where the data goes

Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on space.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.

No findings were raised for this container.

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 »

No third-party hosts were found in this container's tags.

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.

space.com

What this audit describes

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

Container	`GTM-TF5X74CL`
Published version	`2` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-20 22:17:52 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-TF5X74CL`
Body checksum	`0dc446154f337ba48bfa43cb37df9a25aa34d52b7415c3b51a9eafc398315023` 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-TF5X74CL

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 »