Skip to content
https://taz.de

Security

· 12 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.
SCORE
77
GRADE
C
FIX
2
REVIEW
5
PASS
5
INFO
0
Checks
12
5 PASS 5 REVIEW 2 FIX
F
Subresource Integrity
Action
0 of 7 external resources have SRI
FIX
0 of 7 external resources have SRI
Warning::
External script from data-502d5cce76.taz.de lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //data-502d5cce76.taz.de/iomm/latest/bootstrap/stub.js
Warning::
External script from cdn.privacy-mgmt.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js
Warning::
External script from securepubads.g.doubleclick.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://securepubads.g.doubleclick.net/tag/js/gpt.js
Warning::
External script from data-502d5cce76.taz.de lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //data-502d5cce76.taz.de/iomm/latest/manager/base/es6/bundle.js
Warning::
External script from cdn.privacy-mgmt.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://cdn.privacy-mgmt.com/unified/4.40.1/gdpr-tcf.27718c8cb9d29947d2c1.bundle.js
Warning::
External script from data-2d3a3249cd.taz.de lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //data-2d3a3249cd.taz.de/iomb/latest/sensor/manager/base/es6/bundle.js
Warning::
External script from securepubads.g.doubleclick.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://securepubads.g.doubleclick.net/pagead/managed/js/gpt/m202604160201/pubads_impl.js
SRI Coverage 0 / 7 of external resources have integrity hashes
TagDomainIntegrity
<script>data-502d5cce76.taz.de✗ Missing
<script>cdn.privacy-mgmt.com✗ Missing
<script>securepubads.g.doubleclick.net✗ Missing
<script>data-502d5cce76.taz.de✗ Missing
<script>cdn.privacy-mgmt.com✗ Missing
<script>data-2d3a3249cd.taz.de✗ Missing
<script>securepubads.g.doubleclick.net✗ Missing
D
security.txt
Action
No /.well-known/security.txt published
FIX

security.txt

No security.txt found at /.well-known/security.txt

C
Security Headers
Action
5 of 10 headers properly configured
REVIEW
5 of 10 headers properly configured
Warning::
HSTS max-age is too short (15724800s, should be ≥ 31536000s)
A short max-age leaves a window for downgrade attacks. Set max-age to at least 31536000 (1 year).
Got: max-age=15724800; Expected: max-age=31536000; includeSubDomains
Warning::
X-Content-Type-Options header is missing
This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.
Expected: nosniff
Info::
X-Frame-Options is properly configured
Got: SAMEORIGIN
Warning::
Referrer-Policy header is missing
Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
Expected: strict-origin-when-cross-origin
Info::
Permissions-Policy is set
Got: interest-cohort=()
Info::
Content-Security-Policy is present
Got: frame-ancestors 'self' https://*.taz.de https://taz.de https://www.tazlablive.de…
Warning::
Cross-Origin-Opener-Policy header is missing
COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
Expected: same-origin
Warning::
Cross-Origin-Embedder-Policy header is missing
COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
Expected: require-corp
Info::
X-Powered-By header is not present
Info::
Server header is present without version info
Got: nginx

A short max-age leaves a window for downgrade attacks. Set max-age to at least 31536000 (1 year).

Expected: max-age=31536000; includeSubDomains
Why this matters

Short HSTS max-age leaves a downgrade-attack window every time the cache expires — set ≥ 1 year.

Learn more ▾

max-age below 31536000 (1 year) is below industry recommendation. The browser forgets the HSTS policy and re-exposes first-visit downgrade attacks. Set to 63072000 (2 years) and add `includeSubDomains; preload` to qualify for the HSTS preload list.

Source: RFC 6797 / hstspreload.org

This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.

Expected: nosniff
Why this matters

MIME sniffing lets browsers run uploaded files as JavaScript, turning a file upload into an XSS.

Learn more ▾

Setting X-Content-Type-Options: nosniff tells browsers to trust your declared Content-Type instead of guessing. Without it, an attacker who uploads a polyglot file can sometimes get it executed as a script. One header, no downside.

Source: OWASP / MDN

Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.

Expected: strict-origin-when-cross-origin
Why this matters

Default browser behavior leaks full URLs (including query params and tokens) to every third-party resource — set a strict policy.

Learn more ▾

Without a Referrer-Policy header, browsers send the full referring URL with images, scripts, and fonts loaded from third-party origins. URLs containing tokens, user IDs, or session params end up in third-party logs. Set `Referrer-Policy: strict-origin-when-cross-origin` (or stricter) to limit leakage.

Source: MDN / W3C

COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.

Expected: same-origin
Why this matters

COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.

Learn more ▾

Cross-Origin-Opener-Policy: same-origin prevents cross-origin pages from sharing a browsing-context group with yours. This blocks cross-window references that enable Spectre-style timing attacks and tab-nabbing. Required if you want to enable SharedArrayBuffer.

Source: MDN / web.dev

COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.

Expected: require-corp
Why this matters

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Learn more ▾

Cross-Origin-Embedder-Policy: require-corp ensures every embedded resource (script, iframe, image) explicitly allows being loaded cross-origin. Combined with COOP, this enables the cross-origin-isolated context that unlocks SharedArrayBuffer, high-resolution timers, and other powerful APIs.

Source: MDN / web.dev

B
Content Security Policy
2 of 10 CSP checks passed
REVIEW
2 of 10 CSP checks passed
Info::
Raw CSP policy
Got: frame-ancestors 'self' https://*.taz.de https://taz.de https://www.tazlablive.de/
Warning::
default-src directive is missing
default-src provides a fallback for other directives. Set it to restrict default resource loading.
Expected: default-src 'self'
Info::
No script-src or default-src to check for 'unsafe-inline'
Info::
No script-src or default-src to check for 'unsafe-eval'
Info::
No script-src or default-src to check for wildcard
Info::
object-src falls back to default-src
Warning::
base-uri directive is missing
Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.
Expected: base-uri 'self'
Info::
frame-ancestors directive is set
Got: frame-ancestors 'self' https://*.taz.de https://taz.de https://www.tazlablive.de/
Warning::
form-action directive is missing
form-action restricts where forms can submit data, preventing form hijacking.
Expected: form-action 'self'
Info::
upgrade-insecure-requests is not set
This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.
Expected: upgrade-insecure-requests

default-src provides a fallback for other directives. Set it to restrict default resource loading.

Expected: default-src 'self'
Why this matters

Security gaps expose your site and users to attacks, eroding trust.

Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.

Expected: base-uri 'self'
Why this matters

Missing base-uri in CSP leaves a base-tag injection attack path open even on otherwise strict policies.

Learn more ▾

A common omission: developers add CSP for script-src and frame-ancestors but forget base-uri. The result is a CSP that looks strict but lets an attacker rewrite every URL on the page via <base href>. Add `base-uri 'self'` to close the gap.

Source: MDN CSP

form-action restricts where forms can submit data, preventing form hijacking.

Expected: form-action 'self'
Why this matters

Security gaps expose your site and users to attacks, eroding trust.

This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

Expected: upgrade-insecure-requests
Why this matters

Without upgrade-insecure-requests, any HTTP subresource link survives as a mixed-content warning instead of auto-upgrading.

Learn more ▾

Adding `upgrade-insecure-requests` to your CSP turns every http:// subresource fetch into https:// at the browser layer. One-line defense against accidental mixed content from legacy links or third-party widgets.

Source: MDN CSP

Parsed Policy

frame-ancestors 'self'https://*.taz.dehttps://taz.dehttps://www.tazlablive.de/
C
Permissions-Policy
Action
1 directives, 5 missing
REVIEW
1 directives, 5 missing
Info::
interest-cohort=() — blocked for all origins
Info::
camera not restricted
Consider adding camera=() to block camera access from embedded content.
Info::
microphone not restricted
Consider adding microphone=() to block microphone access from embedded content.
Info::
geolocation not restricted
Consider adding geolocation=() to block geolocation access from embedded content.
Info::
payment not restricted
Consider adding payment=() to block payment access from embedded content.
Info::
usb not restricted
Consider adding usb=() to block usb access from embedded content.

Raw Header

interest-cohort=()

Feature Permissions

Blocked Self Only Unrestricted Not Set
interest-cohort Blocked
camera Not Set
microphone Not Set
geolocation Not Set
payment Not Set
usb Not Set
B
CORS Configuration
No CORS headers
REVIEW
No CORS headers
Info::
No CORS headers present — secure default
CORS Configuration ✓ Secure

No CORS headers detected.

Cross-origin requests are blocked by browser same-origin policy.

Origin reflection test

Some servers mirror the request Origin header, which can be exploited. Test manually:

curl -sI -H "Origin: https://evil.com" <url> | grep -i access-control
B
Transport Security
HTTP/3, HSTS, and TLS version analysis
REVIEW
HTTP/3, HSTS, and TLS version analysis
Info::
HTTP/3 (QUIC) not advertised
HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.
Warning::
HSTS max-age is short: 182 days
HSTS max-age should be at least 1 year (31536000 seconds).
Got: max-age=15724800 (expected 31536000)
Info::
HSTS missing includeSubDomains
Without includeSubDomains, HSTS only protects the exact domain.
Info::
TLS 1.3 in use (fastest handshake, 1-RTT)
A+
TLS & Certificates
TLS 1.3, 7 checks passed
PASS
TLS 1.3, 7 checks passed
Info::
TLS 1.3 is used
Got: TLS 1.3
Info::
Strong cipher suite is used
Got: TLS_AES_256_GCM_SHA384
Info::
HTTP/2 is not negotiated
HTTP/2 provides multiplexing and header compression for better performance.
Got: http/1.1
Info::
Certificate is valid (expires in 79 days)
Got: 2026-07-10T21:56:34Z
Info::
Certificate chain has 2 certificates
Info::
Certificate uses modern signature algorithm
Got: SHA256-RSA
Info::
Certificate covers 61 domain(s)
Got: atlas-der-globalisierung.de, atlas.monde-diplomatique.de, autocomplete.fleet.taz.de, blog.taz.de, blogs.taz.de, buchmesse.taz.de, download.taz.de, europesfarright.eu, futurzwei.taz.de, gazete.taz.de, genossenschaft.taz.de, informant.taz.de, leicht.taz.de, lmd-karten.de, lmdshop.taz.de, lmdshop20.taz.de, m.taz.de, monde-diplomatique.de, monty.taz.de, panter-stiftung.de, panterpreis.de, panterstiftung.de, sentry.taz.de, shop.taz.de, taz-bremen.de, taz-hamburg.de, taz-nord.de, taz-panter-stiftung.de, taz.de, taz.eu, tazblogs.de, tazblogs.eu, tazfuturzwei.de, tazlab.de, tazpresso.de, tuttle.taz.de, verlag-node-stage.fleet.taz.de, ww.taz.de, www.atlas-der-globalisierung.de, www.blog.taz.de, www.blogs.taz.de, www.buchmesse.taz.de, www.futurzwei.taz.de, www.lmd-karten.de, www.monde-diplomatique.de, www.panter-stiftung.de, www.panterpreis.de, www.panterstiftung.de, www.shop.taz.de, www.taz-bremen.de, www.taz-hamburg.de, www.taz-nord.de, www.taz-panter-stiftung.de, www.taz.de, www.taz.eu, www.tazblogs.de, www.tazblogs.eu, www.tazfuturzwei.de, www.tazlab.de, www.tazpresso.de, wwww.taz.de
Info::
Certificate is issued by a trusted CA
Got: CN=R13,O=Let's Encrypt,C=US

HTTP/2 provides multiplexing and header compression for better performance.

Why this matters

HTTP/1.1 forces the browser to make sequential requests, multiplying latency on every page.

Learn more ▾

HTTP/2 (and HTTP/3) multiplex many requests over a single connection, eliminating head-of-line blocking. HTTP/1.1 forces the browser to either queue requests or open many parallel connections — both worse. Most modern web servers support HTTP/2 with one config line.

Source: MDN Web Docs

Connection
Protocol
TLS 1.3
Cipher Suite
TLS_AES_256_GCM_SHA384
HTTP Version
HTTP/1.1

Certificate Chain

Leaf Certificate
Subject CN=taz.deIssuer CN=R13,O=Let's Encrypt,C=USValid 2026-04-11T21:56:35Z → 2026-07-10T21:56:34ZExpires in 79 days SANs atlas-der-globalisierung.de, atlas.monde-diplomatique.de, autocomplete.fleet.taz.de, blog.taz.de, blogs.taz.de, buchmesse.taz.de, download.taz.de, europesfarright.eu, futurzwei.taz.de, gazete.taz.de, genossenschaft.taz.de, informant.taz.de, leicht.taz.de, lmd-karten.de, lmdshop.taz.de, lmdshop20.taz.de, m.taz.de, monde-diplomatique.de, monty.taz.de, panter-stiftung.de, panterpreis.de, panterstiftung.de, sentry.taz.de, shop.taz.de, taz-bremen.de, taz-hamburg.de, taz-nord.de, taz-panter-stiftung.de, taz.de, taz.eu, tazblogs.de, tazblogs.eu, tazfuturzwei.de, tazlab.de, tazpresso.de, tuttle.taz.de, verlag-node-stage.fleet.taz.de, ww.taz.de, www.atlas-der-globalisierung.de, www.blog.taz.de, www.blogs.taz.de, www.buchmesse.taz.de, www.futurzwei.taz.de, www.lmd-karten.de, www.monde-diplomatique.de, www.panter-stiftung.de, www.panterpreis.de, www.panterstiftung.de, www.shop.taz.de, www.taz-bremen.de, www.taz-hamburg.de, www.taz-nord.de, www.taz-panter-stiftung.de, www.taz.de, www.taz.eu, www.tazblogs.de, www.tazblogs.eu, www.tazfuturzwei.de, www.tazlab.de, www.tazpresso.de, wwww.taz.deSignature SHA256-RSASerial 686df69c7163c514c1932a8472180beb8aa
Intermediate (CA Certificate)
Subject CN=R13,O=Let's Encrypt,C=USIssuer CN=ISRG Root X1,O=Internet Security Research Group,C=USValid 2024-03-13T00:00:00Z → 2027-03-12T23:59:59ZExpires in 325 days Signature SHA256-RSASerial 5a00f212d8d4b480f3924157ea298305
A+
Cookie Security
No cookies set — no cookie security risks
PASS
No cookies set — no cookie security risks
Info::
No cookies set — no cookie security risks

No cookies detected — no cookie security risks to report.

A+
JS Library Vulnerabilities
No known vulnerabilities
PASS
No known vulnerabilities
Info::
No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+
Information Leakage
No exposures
PASS
No exposures
Info::
No security.txt found
Consider adding a security.txt at /.well-known/security.txt.
Info::
No sensitive files exposed

No sensitive files exposed — all paths returned 404.

PathStatusCategoryRisk
/.git/HEAD✓ Not foundVersion Control—
/.git/config✓ Not foundVersion Control—
/.svn/entries✓ Not foundVersion Control—
/.env✓ Not foundConfiguration—
/.env.local✓ Not foundConfiguration—
/.env.production✓ Not foundConfiguration—
/wp-config.php✓ Not foundConfiguration—
/.htaccess✓ Not foundConfiguration—
/phpinfo.php✓ Not foundDebug—
/server-status✓ Not foundDebug—
/server-info✓ Not foundDebug—
/.well-known/security.txt✓ Not foundSecurity Policy—
A+
Email Security
DMARC: reject
PASS
DMARC: reject
Info::
DMARC policy is reject — strongest protection
DMARC
Policy reject — strongest protection Record v=DMARC1;p=reject;ruf=mailto:dmarc-f@taz.de;fo=1
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback