Utiq FAQ

The most direct way is Utiq’s official Consent Hub: consenthub.utiq.com. Click “Manage Utiq consents”, then “Withdraw Utiq consents” and choose “Remove all Utiq consents”. Your consents are deleted and the technology stops being active. Utiq states that the associated data is erased from its platform within 24 hours, as long as you don’t grant new consent in the meantime.

You can also withdraw consent site by site via the “Manage Utiq” link in the footer of participating websites (this only applies to that site).

• Reject the banner. When a site asks for Utiq consent, choose “Reject”. Without consent, the technology stays inactive.
• Block Utiq domains at the DNS or browser level. Tracking relies on technical domains (*.utiq-aws.net, *.utiq.com, utiq.<site> subdomains). Ready-made blocklists are downloadable below.
• Use a filtering DNS (AdGuard Home, NextDNS, Pi-hole) or a content blocker (uBlock Origin) with these lists.
• On mobile, the identifier derives from your carrier connection: using a VPN or a non-participating network limits the network binding, but does not replace withdrawing consent.

Utiq blocklists to download: hosts · domains · AdGuard / uBlock · Unbound · RPZ (“strict” versions and index).

Utiq is a company (spun out of a joint venture between Deutsche Telekom, Orange, Telefónica and Vodafone, launched in 2023) offering an advertising identification technology based on operator networks. Rather than dropping a cookie in your browser, it relies on a “network signal” provided by your carrier to generate pseudonymous identifiers (martechpass, adtechpass) used by brands and ad networks for targeting and measurement.

When you accept on a participating site, the Utiq SDK makes a secure call to your operator, which returns a network signal matching your connection. That signal is mapped to a stable random identifier (the consentpass), from which the identifiers exposed to advertisers are derived. These signals work cross-browser and cross-device over the same connection, enabling re-identification at scale.

The founding operators are Deutsche Telekom, Orange, Telefónica and Vodafone, joined by others. Deployment is mostly European (Germany, France, Spain, United Kingdom, Italy, Austria…). The distribution of the sites listed here reflects that scope.

The index cross-references several public signals: DNS records pointing to Utiq infrastructure (*.utiq-aws.net), TLS certificates issued for utiq.<site> subdomains (Certificate Transparency logs), and a check that the Utiq loader actually responds on the domain. The “Utiq since” date is estimated (earliest known public trace) and the country is an estimate of the market edition, not a legal headquarters.

No. It is a snapshot, non-exhaustive and subject to change. Sites may adopt or drop Utiq at any time. The list is provided for informational purposes.

Yes. The list is exportable as JSON and CSV, and a stable API access is documented on the API page (with CORS, for external use).

Utiq Tracker is open and collaborative: the list lives on GitHub, github.com/CedHaurus/utiq-tracker, and anyone can suggest an addition or a fix.

• Easiest: open an issue with the site and what you found.
• Going further: open a pull request adding an entry to data/source.json (the format is described in CONTRIBUTING.md).

Before adding a site, check at least one public signal: the utiq.<site> subdomain is a CNAME to *.utiq-aws.net, or a certificate was issued for utiq.<site> in Certificate Transparency logs (crt.sh).