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

SDK and ID5 calls use the first-party host edge-block.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 edge-block.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…

Integration

Host (SDK + calls): edge-block.pakopress.dev
Party: first-party — same registrable domain as the page (pakopress.dev)
Link: DNS-only CNAME → proxy.eu-1-id5-sync.com (a blocked domain) — CNAME cloaking — required on the publisher's own domain (domain owner)
<!-- 1. Load the ID5 SDK -->
<script src="https://edge-block.pakopress.dev/a7q3/api/1.0/id5-api.js"></script>  ← changed from cdn.id5-sync.com

<!-- 2. Initialise -->
ID5.init({
  partnerId: 173,
  apiBaseUrl: 'https://edge-block.pakopress.dev/a7q3',  ← new: routes every ID5 call to this base
  cmpApi: 'static',
  consentData: { /* static TCF v2.2: vendor 131, purposes 1-11 */ }
}).onAvailable(id5 => console.log(id5.getUserId()));

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

Live

The first-party host edge-block.pakopress.dev is configured (grey CNAME → proxy.eu-1-id5-sync.com). Open this page on the target device to see whether the ID5 ID resolves.