How StackCheck works

Overview

StackCheck analyzes websites to determine their data sovereignty posture by examining where data flows and which services are involved. When you scan a website, we perform a comprehensive analysis of both the main service and all third-party services it depends on.

Scanning the main service

When you enter a URL, we scan the main service across four categories:

Infrastructure

We analyze DNS records and IP addresses to identify hosting providers and core infrastructure. CDN services and CA providers are detected and shown as context, but not scored.

Backend services

We detect email providers, payment processors, authentication services, monitoring tools, and other server-side integrations through DNS records and page content analysis.

Frontend & third parties

We scan the HTML, JavaScript, and network requests to identify analytics tools, support widgets, embedded media, and other client-side services.

Disclosed services

We parse privacy policies and legal pages to find services that are disclosed but may not be detectable through technical scanning.

Dependency scanning

Here's where StackCheck goes deeper than typical scanners. For each third-party service we detect (e.g., a payment processor or analytics tool), we perform a full infrastructure scan of that service as well.

Why scan dependencies?

Even if a third-party service is EU-based, they might host their infrastructure on non-EU cloud providers — or on EU servers controlled by a non-EU company. Either way, your data may fall outside EU jurisdiction.

Data can physically leave the EU: A German email marketing service might use Amazon Web Services in the US for their servers. While the company is EU-based, your subscribers' data is processed on US infrastructure.

Or stay in the EU but under foreign jurisdiction: An EU service uses an EU payment provider, who stores data on EU-hosted servers of a US cloud platform. Everything in the chain looks European, but the data is ultimately held by a US entity — and under laws like the CLOUD Act, US authorities could compel access regardless of where the servers physically sit.

Calculating privacy friendliness

The final assessment considers:

  1. All categories of the main service — infrastructure, backend, frontend, and disclosed services
  2. The infrastructure of detected sub-services — affects the EU status of the parent finding (e.g., if a payment processor runs on US infrastructure, that finding becomes Non-EU; if a non-EU or unknown service turns out to run on EU infrastructure, it becomes EU-hosted)
Your website
example.com
Infrastructureincluded
Backend servicesincluded
Frontend & 3rd partyincluded
Disclosed servicesincluded
Detected sub-services
analytics-service.com
Infrastructure→ status
Backend services
Frontend & 3rd party
payment-provider.eu
Infrastructure→ status
Backend services
Frontend & 3rd party
Scored directly
Sub-service infra: affects parent status
Scanned but not included

Sub-services are fully scanned, and their infrastructure determines the EU status of the parent finding. For example, an EU payment processor running on US servers gets a "Non-EU" status for that finding; one running in an EU region of a US-owned cloud is "EU-hosted". Their own third-party integrations don't cascade into your report.

StatusMeaning
✓ EUService and infrastructure are based in the EU/EEA
⚠ EU-hostedData stays on EU infrastructure, but the company or its cloud provider is non-EU (e.g. a US company with EU data residency, or an EU company on a US-owned cloud region)
✗ Non-EUService or infrastructure located outside the EU
? UnknownUnable to determine location — manual review recommended

Overall assessment

Based on the findings, we provide an overall assessment:

EU compliantAll active services and their infrastructure are EU-based
Good standingGrade A or higher with some EU-hosted services — data stays in EU
Review recommendedSome services have unknown status or lower grades with EU-hosted findings
Needs attentionOne or more services involve non-EU data processing

Scoring system

StackCheck calculates a score from 0-100 based on where data actually flows. The formula uses a worst-per-layer approach: each layer is scored by its worst finding, because one non-EU service can't be "averaged away" by others.

How the score is calculated

  1. Group all findings into three layers: infrastructure, backend, frontend
  2. Each layer is scored by its worst (lowest) finding
  3. Layers with no findings are skipped (unless confirmed absent)
  4. Final score = weighted average of layer scores

Layer weights

Not all layers are equal. Infrastructure matters most because that's where your data physically resides:

LayerWeightWhy
Infrastructure3×Where data physically lives — servers and hosting providers
Backend services2×Processing and storage — email, payments, databases
Frontend1×Client-side tracking — analytics, widgets, fonts

Status values

The worst finding in each layer determines that layer's score:

StatusPointsMeaning
EU100EU company with EU infrastructure
EU-hosted70Data stays in the EU, but the company or its cloud provider is non-EU
Unknown30Cannot verify — treated with caution
Non-EU0Data leaves the EU

Missing layers

If we don't detect any services in a layer, it's handled differently based on whether you've confirmed the absence:

SituationHow it's scored
No findings detectedLayer is skipped (neutral — doesn't help or hurt)
Confirmed "we don't use this"Layer scores 100 (positive — proves EU compliance)

Example: Worst-per-layer in action

If your infrastructure has both Hetzner (EU, 100 pts) and AWS EU-hosted (70 pts), the infrastructure layer scores 70 — the worst of the two. Adding more EU services won't improve it; you'd need to address the EU-hosted finding.

Verification bonus

Unverified scans max out at grade A because we can't detect everything automatically. Common services like analytics, email, or payment processors might be missing from our scan. The A+ and A++ grades are reserved for verified listings.

When a site owner verifies their listing — confirming which services they use or explicitly stating they don't use certain categories — the higher grades become available and a perfect A++ becomes possible.

Grade scale

ScoreGradeInterpretation
95–100A++Verified, fully EU compliant
90–94A+Verified, excellent
80–89AVery good (max for unverified)
70–79BGood, minor concerns
60–69CModerate concerns
40–59DSignificant issues
0–39FCritical — non-EU infrastructure

Display your score

Proud of your data sovereignty posture? You can embed a badge on your website to show visitors your StackCheck grade.

StackCheckstackcheck.eu/badge/yourdomain.svg

After scanning your site, click the Share button on your results page to get the link and embed code.

Important notes

Automated scanning has limits

Some services can't be detected automatically. Always review results and consider services you know are in use but weren't detected.

CDN is informational

CDN services like Cloudflare are detected and shown as context on the infrastructure row, but they don't affect scoring. A CDN edge location depends on where the visitor is, not where the origin server lives — so our scan location would give misleading results. The CDN provider itself (and any CLOUD Act implications) is still visible for review.

Point-in-time snapshot

Results reflect the state at scan time. Services may change their infrastructure, and websites may add or remove integrations.

Not legal advice

StackCheck provides technical analysis, not legal compliance assessment. Consult with legal professionals for GDPR compliance decisions.