Results for commission.europa.eu

🕓 2026-06-13 07:52:58 Etc/UTC

✅ HTTPS by default 🔗

commission.europa.eu uses HTTPS by default.

More information about the site's TLS/SSL configuration:

✅ HTTP Strict Transport Security (HSTS) 🔗

HSTS policy for https://commission.europa.eu:
max-age=31536000; includeSubDomains; preload;

Pass Test
✅ Yes max-age set to at least 6 months
✅ Yes includeSubDomains — policy also applies to subdomains
➖ N/A preload — requests inclusion in preload lists [only relevant for base domain]

⚠️ HSTS not set on base domain https://europa.eu.

❌ Content Security Policy 🔗

Content Security Policy (CSP) header not implemented.

The Content Security Policy tests are based on the ones from the Mozilla HTTP Observatory scanner/grader project (Mozilla Public License 2.0) by April King, reimplemented by us for Webbkoll. The explanatory texts are from the Observatory by Mozilla website, CC-BY-SA 3.0. Any mistake or inaccuracy in the results is our fault.

✅ Reporting (CSP, Certificate Transparency, Network Error Logging) 🔗

Reports are not sent to a third-party.

⚠️ Referrer Policy 🔗

Referrer Policy not set. This means that the default value strict-origin-when-cross-origin is used, which leaks the origin (domain) when making HTTP->HTTP or HTTPS->HTTPS requests to other domains (but the referrer is not sent when making requests to less secure destinations -- i.e., HTTPS->HTTPS).

✅ Subresource Integrity (SRI) 🔗

Subresource Integrity (SRI) not implemented, but all resources are loaded from a similar origin.

The Subresource Integrity test is based on the one from the Mozilla HTTP Observatory scanner/grader project (Mozilla Public License 2.0) by April King, reimplemented by us for Webbkoll.

HTTP headers 🔗

Pass Header Value Result
✅ Yes X-Content-Type-Options nosniff X-Content-Type-Options header set to "nosniff"
X-Frame-Options SAMEORIGIN X-Frame-Options (XFO) header set to SAMEORIGIN or DENY
X-XSS-Protection X-XSS-Protection header not implemented

The header tests are based on the ones from the Mozilla HTTP Observatory scanner/grader project (Mozilla Public License 2.0) by April King, reimplemented by us for Webbkoll. The explanatory texts are from the Observatory by Mozilla website, CC-BY-SA 3.0.

Cookies 🔗

First-party cookies (3)

Domain Name Value Expires on HttpOnly Secure SameSite
.commission.europa.eu cck1 %7B%22cm%22%3Afalse%... 2026-12-10 07:52:47Z ❌ No ✅ Yes ✅ Yes (Lax)
commission.europa.eu _pk_id.0ccd2154-5091... b2d897db128e8950.178... 2027-07-11 07:52:47Z ❌ No ❌ No ✅ Yes (Lax)
commission.europa.eu _pk_ses.0ccd2154-509... * 2026-06-13 08:22:47Z ❌ No ❌ No ✅ Yes (Lax)

HttpOnly means that the cookie can only be read by the server, and not by JavaScript on the client. This can mitigate XSS (cross-site scripting) attacks.

Secure means that the cookie will only be sent over a secure channel (HTTPS). This can mitigate MITM (man-in-the-middle) attacks.

SameSite can be used to instruct the browser to only send the cookie when the request is originating from the same site. This can mitigate CSRF (cross-site request forgery) attacks.

⚖️ GDPR: Rec. 60, Rec. 61, Rec. 69, Rec. 70, Rec. 75, Rec. 78, Art. 5.1.a, Art. 5.1.c, Art. 5.1.e, Art. 21, Art. 22, Art. 32.

e-PD (2002/58/EC). Rec. 24, 25, Art. 5.2.

e-PD revised (2009/136/EC). Rec. 65, 66.

More information

First-party cookies are placed by the web site owner in some register on their visitors' device in order to be able to re-identify the visitor on subsequent page loads. First-party cookies can be related to technical features on a web site (such as remembering language settings or the contents of a shopping basket), or related to commercial features of the web site owners' activities (such as being able to trace a visitors' behaviour over the duration of their visit, or over much longer time periods, often for years, in order to be able to serve advertisements to the users or to get usage statistics to guide later changes to the web site that are envisaged to make the web site more attractive to recurring users). First-party cookies may come from services provided by the web site owner (language settings in a Content Management System) or from services used by the web site owner (analytics tools).

Third-party cookies are placed by a service affiliated with the web site owner on the devices of visitors to the web site in order to be able to re-identity the visitor on subsequent page loads, or across different web sites. Third-party cookies are typically related to commercial features of a web site owners' activities, usually advertising, but may also relate to technical features in scripts used by a web site (such as language settings).

Storing information or gaining access to information stored in the visitors' devices, for instance in the form of cookies, has been subject to sui generis legislation in the European Union (ePD, Art. 5.3). These sui generis laws have tried to make a distinction between information stored to support technical features and information stored to support commercial features. In practice, poor enforcement of these rules has made the legal landscape unclear. Because there exists no legal duty for citizens to receive better targeted advertisement, nor a legal duty for citizens to assist web developers in improving web sites, it's doubtful that a legal basis exists for storing information to support commercial features without the consent of the web visitor (GDPR Art. 7). It is argued that the legitimate interests of a web site owner (Art. 6.1.f, Art. 6.4) may nevertheless enable them to subject a visitor to targeted ads or cause a visitor to assist the web developers. In either case, if the legitimate interest legal basis for processing is invoked, adequate security measures must be undertaken (GDPR Art. 32).

Particular care must be taken with regards to the period of storage (GDPR Art. 5.1.e). While it is technically easy for a web site owner to set the duration of a information stored in the form of cookies to a long period time, the principle of storage limitation implies a balancing act between the interest of tracking a visitors' behaviour and the interest of the visitor to keep their behaviour private. It's been established that a reasonable storage period does not exceed one year.

localStorage 🔗

localStorage not used.

Third-party requests 🔗

No third-party requests.

A third-party request is a request to a domain that's not europa.eu or one of its subdomains.

⚖️ GDPR: Rec. 69, Rec. 70, Art. 5.1.b-c, Art. 25.

IP address 🔗

The server commission.europa.eu had the IP address 13.225.35.41 during our test.

You can find information about this IP address using third-party tools such as the following:

When using tools that do geolocation, please note that the estimated country can be wrong, especially for websites that use CDNs.

Raw headers 🔗

Header Value
accept-ranges bytes
age 111
cache-control public, max-age=300, s-maxage=300
content-encoding gzip
content-language en
content-length 23473
content-type text/html; charset=UTF-8
date Sat, 13 Jun 2026 07:50:55 GMT
expires Sun, 19 Nov 1978 05:00:00 GMT
strict-transport-security max-age=31536000; includeSubDomains; preload;
vary Accept-Encoding
via 1.1 064930f415d2899c0465fc9f96744994.cloudfront.net (CloudFront)
x-age 28413
x-amz-cf-id ga4cR-dMlfNbzoo5syzPAlCveGthRGLPo3C8j8ApHwIrzyvYQASFGA==
x-amz-cf-pop ATH51-P2
x-cache Hit from cloudfront
x-content-type-options nosniff
x-fpfis 284194 1285124
x-frame-options SAMEORIGIN

What this tool checks (and doesn't check) 🔗

This tool attempts to simulate what happens when a user visits a specified page with a typical browser. The browser has no addons/extensions installed, and Do Not Track (DNT) is not enabled, since this is the default setting in most browsers.

External files such as images, scripts and CSS are loaded, but the tool performs no interactions with the page — no links are clicked, no forms are submitted.

Disclaimer: The results presented here might not be 100% correct. Bugs happen. This tool is meant to be used by site owners as a starting point for improvements, not as a rigorous analysis.

Text about HTTPS partly adapted from the CIO Council's The HTTPS-Only Standard (public domain). See here for more information.