pakopress.dev — first-party CNAME cloaking → blocked domain

SDK and ID5 calls use the first-party host cloak.pakopress.dev (same registrable domain as this page). Its DNS is a grey (DNS-only) CNAME → proxy.eu-1-id5-sync.com — a registrable domain subject to request blocking. The test: does request blocking follow the CNAME chain, or does the first-party forward name pass?

The experiment
The forward name cloak.pakopress.dev is first-party, but its CNAME target proxy.eu-1-id5-sync.com is blocked. Two possible outcomes:
• Blocking follows the chain → request blocked (by the CNAME target's registrable domain).
• Blocking uses the forward name → ID5 ID resolves (only the requested hostname matters — CNAME cloaking bypasses it).
Waiting for ID5…

Requests made by this page

green = first-party (from the page's view; the CNAME target is hidden from JS) · red = a blocked domain

typehostpath

Not live yet

The first-party host cloak.pakopress.dev is not configured yet, so this page will not resolve an ID5 ID until it is.