Domain History

www.mediamarkt.de

Grade F · 0/100 · 6/7 security headers present

Security Score

0/ 100

Security Headers

6/ 7

CSP Violations

NoViolations

100% violation-free! (Technically correct)

Issues Found

3Issues

Recommendations

2Available

Security

0 / 100

Critical security vulnerabilities — CSP provides minimal protection.

Compliance

0 / 100

Non-compliant — CSP implementation is incomplete or report-only.

Best Practices

0 / 100

Best practices largely absent — review CSP configuration.

CSP Analysis

!No Content Security Policy Detected

This site does not set a Content-Security-Policy HTTP header. Without CSP, browsers allow all inline scripts, eval(), and resources from any origin, leaving the site vulnerable to Cross-Site Scripting (XSS) attacks.

Security Headers

✓Cross-Origin-Opener-PolicyPresent

same-origin

Isolates the browsing context to prevent Spectre-type side-channel attacks and cross-origin window manipulation.

✓Permissions-PolicyPresent

accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*

Restricts which browser features (camera, microphone, geolocation) the page can use, limiting attack surface.

✓Referrer-PolicyPresent

same-origin

Controls how much referrer information is sent with requests, preventing data leaks to third parties.

✓Strict-Transport-SecurityPresent

max-age=31536000

Forces browsers to use HTTPS for all future requests, preventing man-in-the-middle attacks and SSL stripping.

✓X-Content-Type-OptionsPresent

nosniff

Prevents browsers from MIME-sniffing responses away from the declared Content-Type, blocking drive-by downloads.

✓X-Frame-OptionsPresent

SAMEORIGIN

Prevents the page from being embedded in iframes, protecting against clickjacking attacks.

—X-XSS-ProtectionDeprecated

Legacy XSS filter for older browsers. Modern browsers use CSP instead. Set to "0" to avoid false positives.

Issues Found

•No Content Security Policy (CSP) header detected - site is vulnerable to XSS attackscritical
•Without CSP, browsers allow all inline scripts, eval(), and resources from any origincritical
•Missing security header: X-XSS-Protectionmedium

Recommendations

→Implement a Content Security Policy header to protect against XSS and data injection attacks
→Start with a report-only policy (Content-Security-Policy-Report-Only) to identify required resources before enforcing

Beyond headers: infrastructure exposure

via OSN, our sister project

Security headers protect the browser. OSN maps what's exposed underneath — servers, open ports, known CVEs, DNS and WHOIS.

See what the internet sees about www.mediamarkt.deWeak headers often come with other exposure — check the full picture.

See full exposure report on OSN →Free, no signup.