How to check a vendor for EU sovereignty

A due-diligence walkthrough: which parts of a vendor's stack to check, what staysin.eu tests automatically, and what only contracts can answer.

Updated By enum

To check a vendor for EU sovereignty, find out who operates each part of its service and who controls those operators. Part of the answer is public: hosting, DNS, mail, CDN and the third-party services a web page loads can be read from outside. The rest is not public: contracts, sub-processors, support access, backups and where your data is stored inside the product. You only learn those from documents and from the vendor's answers. staysin.eu checks the public part automatically. The paper part is still yours to do.

What should you look at when checking a vendor?

A vendor's service runs on other companies' infrastructure. Each of those companies, and its parent, can be reached by the law of the country it is based in. Look at every layer:

  • Hosting: the network and operator behind the servers that answer for the vendor's domain.
  • DNS: the provider that runs the domain's nameservers.
  • Mail: the provider that receives mail for the domain (MX records).
  • Mail senders: every service allowed to send mail for the domain, such as newsletter or ticketing tools (SPF record).
  • CDN: the content delivery network in front of the site, if there is one.
  • Third-party requests: analytics, fonts, chat widgets, payment and error-tracking scripts the web app loads in the browser.
  • Registrar: the company the domain is registered through.
  • Parent company: who owns the vendor itself, and whether that owner sits outside the EU.
  • Sub-processors: the vendor's list of other companies that process personal data on its behalf.

What does staysin.eu check automatically?

staysin.eu runs these checks on any domain you enter, for example staysin.eu/example.com. The methodology page describes each one in detail.

  • Scored: hosting provider, DNS, mail (MX), each distinct mail sender from SPF, CDN (when one is detected), server location by IP geolocation, and each matched third-party request captured by a headless browser.
  • Shown but not scored: registrar (via RDAP, with an EU or non-EU marker) and TLS certificate issuer.

A matched provider counts as EU only when three things hold: its operational country is in the EU, it has no non-EU parent or holding company, and it runs its own infrastructure rather than reselling a non-EU service. Each classification is listed with its date on the provider pages.

What can staysin.eu not check?

staysin.eu only sees what a domain exposes publicly. These questions stay open:

  • The vendor's own ownership. staysin.eu classifies the providers a domain uses. It does not classify the vendor company behind the domain.
  • Contracts. The data processing agreement, transfer clauses and liability terms are not visible from DNS or HTTP.
  • Sub-processors. A vendor with an EU website can still pass your data to a non-EU sub-processor. Only its sub-processor list shows this.
  • Support access. Staff or contractors in a third country with production access leave no public trace.
  • Backups and disaster recovery. Where copies of your data are kept is not public.
  • Data stored in the product. A reverse proxy, load balancer or CDN in the EU can forward requests to backends on non-EU infrastructure. Those hops are invisible from outside.

The headless browser loads the public page without logging in. Third-party services that only load inside a logged-in app, or after user interaction, may not be detected. Check app, login and API hostnames such as app.vendor.example separately, since each can run on different infrastructure.

How do you read a staysin.eu result?

Every result has one of three verdicts:

  • Stays in EU: every scored item is EU.
  • Leaves EU: at least one scored item is non-EU.
  • Insufficient data: nothing could be scored, for example because the domain does not resolve.

The score is EU items divided by scored items, times 100. It is independent of the verdict: one non-EU item among many still gives a high score and a Leaves EU verdict. Items where no provider could be identified are not scored.

Each row shows a verdict and a route. A row reading EU · Germany via United States means the provider is classified EU with Germany as its country, while the IP geolocates to the United States. The location is shown for transparency and does not change the verdict, because staysin.eu treats legal control as the deciding factor.

A row reading Non-EU control means the provider's brand country is in the EU, but it has a non-EU parent or resells non-EU infrastructure. The non-EU element is the parent or the underlying operator, not the country shown.

Each stored result keeps the methodology date it was scanned under and is not re-interpreted later. Run the check again for a current judgment.

Key takeaway: a Stays in EU verdict means the public layers of a domain are run by EU-controlled providers. It says nothing about the vendor's contracts, sub-processors, support access or backups. Treat it as one input to a review, not the result of one.

Which regulations ask for this kind of vendor review?

None of the laws below require EU-only infrastructure. Each asks organisations to assess the providers they rely on. This is a summary, not legal advice.

GDPR: processors and international transfers

Article 28(1) of the GDPR (Regulation (EU) 2016/679) says a controller "shall use only processors providing sufficient guarantees to implement appropriate technical and organisational measures". Article 28(2) says a processor shall not engage another processor without the controller's prior specific or general written authorisation. Article 28(3)(a) requires the processing contract to cover the controller's instructions, "including with regard to transfers of personal data to a third country". Article 28(3)(h) requires the processor to provide the information needed to demonstrate compliance and to allow audits.

Chapter V of the GDPR governs transfers of personal data to third countries. Under Article 44, a transfer may only take place if the conditions of that chapter are met, including for onward transfers. Article 45 covers transfers based on an adequacy decision, and Article 46 covers transfers subject to appropriate safeguards such as standard data protection clauses.

NIS2: supply chain security

Article 21(2)(d) of the NIS2 Directive ((EU) 2022/2555) lists "supply chain security, including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers" among the required cybersecurity risk-management measures. Article 21(3) asks entities to take into account the vulnerabilities specific to each direct supplier and service provider and the quality of their cybersecurity practices.

DORA: ICT third-party risk

Article 28 of DORA (Regulation (EU) 2022/2554) sets the general principles for how financial entities manage ICT third-party risk. Article 28(3) requires a register of information on all contractual arrangements for ICT services. Article 28(4)(d) requires financial entities, before entering such an arrangement, to "undertake all due diligence on prospective ICT third-party service providers". Article 30(2)(b) requires ICT contracts to state the countries or regions where services are provided and where data is processed, including the storage location.

A reusable vendor check checklist

  • Run the vendor's main domain on staysin.eu and note the verdict, score and every non-EU row.
  • Run the app, login and API hostnames as separate checks.
  • For each Non-EU control row, open the provider page to see the parent or reseller relationship.
  • Identify who owns the vendor itself, up to the ultimate parent company.
  • Get the sub-processor list and check the country and parent company of each entry.
  • Read the data processing agreement for transfer terms, sub-processor change notices and audit rights.
  • Ask where production data, backups and disaster-recovery copies are stored.
  • Ask from which countries support staff and contractors can access production systems.
  • Record the transfer mechanism (adequacy decision or safeguard) for any data that leaves the EU.
  • Repeat the check when the vendor changes its sub-processors or infrastructure. A staysin.eu result reflects the day it was scanned.

Aggregate results across checked domains are on the stats page.

Sources