CDNs and EU sovereignty: what a CDN can see and how to detect one

A CDN decrypts the traffic it serves, so its operator's jurisdiction matters even when the origin is in the EU. How to tell which CDN a site uses.

Updated By enum

A content delivery network (CDN) sits between visitors and a website's origin server and usually terminates the TLS connection. That means the CDN operator can read the requests and responses it handles in plain text. For EU sovereignty, the question is who controls that operator and which governments can compel it, not where the origin server stands. A site hosted in Frankfurt but served through a US-controlled CDN exposes its traffic to US legal process at the edge.

What can a CDN see?

TLS encrypts traffic between two endpoints, a client and a server. When a site is behind a caching CDN, the browser's TLS endpoint is the CDN's edge server, not the origin. The edge decrypts the request, decides whether to answer from cache, and opens a separate connection to the origin when it needs to.

Between those two connections, the CDN handles in plain text:

  • the full URL, including path and query string
  • request headers, including cookies and authorization headers
  • request bodies, such as submitted forms, logins and API payloads
  • the response content the origin sends back
  • the visitor's IP address and the time of each request

This is how a CDN works, not a flaw: it cannot cache or filter content it cannot read. To serve HTTPS under the site's own name, the CDN also holds a valid certificate for that name.

Why does CDN jurisdiction matter if the origin is in the EU?

Every request and response passes through the CDN, so data reaches the CDN operator before it reaches the EU origin. If the operator is subject to non-EU law, that law can reach the data at the edge.

The US CLOUD Act is the usual example. It added 18 U.S.C. § 2713, which requires providers of electronic communication service or remote computing service to disclose data in their "possession, custody, or control, regardless of whether such communication, record, or other information is located within or outside of the United States." The test is control, not location. Whether a specific CDN service falls under those statutory definitions is a legal question for each case.

The Court of Justice of the EU looked at US surveillance law in Schrems II (C-311/18, 2020) and invalidated the EU-US Privacy Shield. That ruling concerned transfers of personal data to the US. It shows why EU data protection law treats the jurisdiction of a processor as relevant, separately from where its servers stand.

This guide explains the mechanics. It is not legal advice.

Key point: a CDN is a party to your traffic, not a pipe. Its operator's jurisdiction applies to everything it decrypts, whatever country the origin and the edge servers are in.

Can an EU-branded CDN still be non-EU?

Yes. staysin.eu classifies a provider as EU only when three things hold: its operating country is in the EU, it has no non-EU parent company, and it does not resell a non-EU service as its own. The methodology describes the third case directly: "An EU-branded CDN that resells a non-EU CDN".

Bunny.net is the CDN example in the provider mapping. It is classified as a reseller, with this note: "Slovenian company, but most of its CDN delivery runs on infrastructure operated by DataCamp Limited (UK)." staysin.eu shows its verdict as Non-EU control rather than Non-EU, so the Slovenian brand country is not mistaken for the non-EU element.

The same rule works in the other direction. An EU-controlled CDN that runs its own network is classified EU even when some of its edge servers are outside the EU. Classifications are curated and dated; each provider page lists the current one, and all provider classifications are public.

How does staysin.eu detect a CDN?

staysin.eu fetches the site over HTTPS, resolves its DNS records, and tries four methods in order. The first match wins.

  1. Provider-specific HTTP headers. Examples from the mapping: Cloudflare sends cf-ray, Amazon CloudFront sends x-amz-cf-pop and x-amz-cf-id, Fastly sends x-fastly-request-id, and Bunny.net sends cdn-pullzone.
  2. The Server header. A value such as cloudflare or BunnyCDN is matched against the hostname patterns of known providers.
  3. The domain's CNAME record. If the domain is an alias for a provider hostname, for example one ending in cloudfront.net or containing akamaiedge, that provider is matched.
  4. CNAME records of asset subdomains. Subdomains of the same site that the page loads resources from, such as a static. or cdn. host, are checked the same way.

A matched CDN becomes a scored item with the provider's EU or non-EU classification. If no method matches, the CDN row shows "None detected" and is neutral: it is left out of the score. There is no GeoIP fallback for the CDN check, because an IP address location alone does not show that a CDN is involved.

Detection has limits. A CDN that strips its identifying headers and is reached through A records rather than a CNAME will not show up as a CDN. Its IP addresses may still match the provider by network (ASN) in the separate hosting provider check. Backend hops behind the CDN are not visible from outside at all.

Why is the edge location shown but not used for the verdict?

When a CDN is matched, staysin.eu also resolves the edge IP address the scan reached and looks up where that network is announced. The edge you reach depends on where the request comes from, and many CDNs announce the same addresses from many countries (anycast). A single edge location says little about who controls the data.

So the edge country is informational. When it differs from the provider's country, both are shown, for example EU · Germany via United States: an EU-classified provider whose edge address was located in the United States. The verdict still follows the provider's classification. The separate "Server location" item is the one check that is pure GeoIP by design.

How can I check which CDN a site uses myself?

Look at the response headers. On the command line:

curl -sI https://example.com

Look for a Server line and for provider headers such as cf-ray, x-amz-cf-pop, x-fastly-request-id, x-akamai-transformed or cdn-pullzone. Headers can be removed or renamed by the site, so their absence does not prove there is no CDN.

Then check whether the name is an alias:

dig +short CNAME www.example.com dig +short CNAME static.example.com

A CNAME that points to a provider's hostname is a strong signal. An empty answer means the name has no CNAME record, which is common at the zone apex. To see the network behind an address, look up the A record with dig +short A example.com and check the owning network in a whois or RIPE database lookup.

Or run the check on staysin.eu: staysin.eu/example.com shows the CDN row with the matched method and evidence. Aggregate results across checked domains are on the stats page.

Sources