Back to Insights
RESEARCH

CNAME Cloaking: The Hidden Tracker Problem

Vakteye TeamDec 1, 20256 min read

CNAME cloaking is one of the most technically sophisticated tracking evasion techniques in use today. By delegating a first-party subdomain to a third-party tracking provider via DNS CNAME records, organizations can effectively disguise third-party cookies as first-party cookies — bypassing most ad blockers and browser privacy protections in the process.

The technique works like this: instead of loading a tracking pixel from tracker.example.com (which browsers and ad blockers easily identify as third-party), the website creates a subdomain like analytics.mysite.com and points it via CNAME to the tracker's infrastructure. Cookies set under analytics.mysite.com appear to be first-party, evading the restrictions that browsers apply to third-party cookies.

From a GDPR perspective, CNAME cloaking raises serious concerns. Article 5(1)(a) requires that personal data be processed lawfully, fairly, and in a transparent manner. When an organization uses DNS-level tricks to circumvent a user's explicit privacy choices (like enabling an ad blocker), it is difficult to argue that the processing is transparent or fair.

The ePrivacy Directive compounds the issue. Article 5(3) requires consent for storing or accessing information on a user's device — regardless of whether the technology is classified as first-party or third-party. The CJEU's Planet49 ruling made clear that consent must be specific and informed. Users who believe they have blocked trackers cannot be said to have consented to the same tracking delivered through a different technical mechanism.

Our research at Vakteye has found that approximately 15% of enterprise websites in the EU use some form of CNAME cloaking. The most common providers include certain analytics and marketing automation platforms that offer CNAME setup as a premium feature. Many organizations implement it without fully understanding the compliance implications.

Detecting CNAME cloaking requires deep analysis of how domain names are connected behind the scenes — something traditional cookie scanners miss entirely. Vakteye's scanning engine traces every domain that sets cookies back to its true owner, flagging cases where a seemingly first-party subdomain actually leads to a known third-party tracker. This allows us to identify hidden tracking that would otherwise go undetected.