WebForensik

Results for https://hohenzollern-schloss.de/de

Scan time: 2026-10-26 14:21:18

Overall Score

Changes since the last scan -1 declined

Compared with scan from 19.10.2026 08:17 (Score 60 → 59) · View full history

⚠ Protections lost: privacy_link_accessible

Score history for this domain View full history →

0 13.10. 0 13.10. 60 15.10. 60 17.10. 60 18.10. 60 18.10. 60 18.10. 60 19.10. 0 26.10. 59 26.10.

GDPR Summary

⚠ This website has serious GDPR deficiencies. Immediate action is required.

GDPR Issues Detected (2):

❌ 10 third-party server(s) outside the EU/EEA — data transfers without legal basis may violate Art. 44–49 GDPR.

Affected servers outside the EU:

edgezone-ec.bunnyinfra.net (Ecuador)
edgezone-tw.bunnyinfra.net (Taiwan)
edgezone-id.bunnyinfra.net (Indonesia)
edgezone-brb.bunnyinfra.net (Australia)
edgezone-ph.bunnyinfra.net (Philippines)
edgezone-ga.bunnyinfra.net (United States)
edgezone-la.bunnyinfra.net (United States)
edgezone-hou.bunnyinfra.net (United States)
edgezone-mx.bunnyinfra.net (Mexico)
edgezone-rs.bunnyinfra.net (Serbia)

⚠ No Content Security Policy — increased risk of cross-site scripting (XSS) and data theft.

Note: This automated analysis does not replace legal advice. For a complete GDPR assessment, consult a data protection officer.

↓ See detailed results for each category below.

100 HTTPS / Encryption

The website uses an encrypted connection (HTTPS).

Latest encryption active (TLS 1.3 — TLSv1.3).

The security certificate is valid (expires 2027-03-11).

Strong encryption method (TLS_AES_256_GCM_SHA384, 256 bit).

0 Enforced Encryption (HSTS)

No HSTS header set. Browsers are not forced to use the encrypted connection.

☛ Action needed: Enable HSTS so browsers always use the encrypted connection. Ask your hosting provider or add this header to your server configuration: Strict-Transport-Security: max-age=31536000; includeSubDomains

▸ How to fix this — step-by-step guide

HSTS (HTTP Strict Transport Security) tells the browser: "Always use HTTPS for this domain — no matter what." This prevents attackers on the same WLAN from intercepting the first, unprotected request. Prerequisite: your site is already stable on HTTPS.

Apache server (classic hosting at most providers)

File: .htaccess in the web root

<IfModule mod_headers.c>
    Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"
</IfModule>

⚠ max-age=31536000 equals 1 year (in seconds). includeSubDomains also covers blog.your-domain.com, shop.your-domain.com etc. — only enable if ALL subdomains support HTTPS, otherwise they become unreachable.

WordPress Special for WordPress: where to add this

Option 1: via .htaccess (recommended — no theme editing)

File: .htaccess in the WordPress root

# BEGIN WebForensik HSTS
<IfModule mod_headers.c>
    Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"
</IfModule>
# END WebForensik HSTS

⚠ Insert ABOVE the "# BEGIN WordPress" line. Only enable once HTTPS has been stable for a few days — the header is intentionally hard to roll back (browsers remember the instruction).

Option 2: via functions.php in the child theme (Advanced alternative)

File: functions.php of your CHILD theme (Appearance → Theme File Editor → functions.php)

add_action('send_headers', function () {
    header('Strict-Transport-Security: max-age=31536000; includeSubDomains');
});

⚠ NEVER edit the parent theme — changes are lost on update. Back up functions.php first!

✓ How to verify it works: DevTools (F12) → Network tab → reload page → click the first request → "Response Headers" — must contain "strict-transport-security: max-age=31536000…".

↓ SHOW COMPLETE SOLUTION All missing security headers bundled at the end of the report — ready to copy.

0 Content Security Policy (CSP)

No Content Security Policy (CSP) found. The website has no protection against injected malicious code.

☛ Action needed: Set up a Content Security Policy. This protects your visitors from injected malicious code (Cross-Site Scripting/XSS). Start with a simple policy: Content-Security-Policy: default-src 'self'. Your web developer or hosting provider can help.

▸ How to fix this — step-by-step guide

A Content Security Policy (CSP) is a doorkeeper rule for the browser: "Scripts and styles may only be loaded from these allowed sources." Without CSP, injected malicious code (XSS) can freely fetch anything. Start with a simple, secure baseline.

Apache server (classic hosting at most providers)

File: .htaccess in the web root

<IfModule mod_headers.c>
    Header always set Content-Security-Policy "default-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; font-src 'self' https: data:; object-src 'none'; frame-ancestors 'self'; base-uri 'self'"
</IfModule>

⚠ This policy is intentionally pragmatic (allows inline styles since many themes/plugins rely on them). If something breaks after enabling: F12 → Console shows "Refused to load…" — add the affected domain after script-src / img-src.

WordPress Special for WordPress: where to add this

Option 1: via .htaccess (recommended — no theme editing)

File: .htaccess in the WordPress root

# BEGIN WebForensik CSP
<IfModule mod_headers.c>
    Header always set Content-Security-Policy "default-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; font-src 'self' https: data:; object-src 'none'; frame-ancestors 'self'; base-uri 'self'"
</IfModule>
# END WebForensik CSP

⚠ WordPress often loads external scripts (Google Fonts, jQuery CDN, analytics pixel) — if CSP blocks them: open the console, see which domain is blocked, append that domain to "script-src 'self'" separated by a space.

Option 2: via functions.php in the child theme (Advanced alternative)

File: functions.php of your CHILD theme

add_action('send_headers', function () {
    header("Content-Security-Policy: default-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; font-src 'self' https: data:; object-src 'none'; frame-ancestors 'self'; base-uri 'self'");
});

⚠ If unsure: start with "Content-Security-Policy-Report-Only" (only monitor, don’t block), watch violations in the console, then switch to enforced mode.

✓ How to verify it works: Open page, F12 → Console — no red "Refused to load…" messages. Network tab → first request → Response Header "content-security-policy" visible.

↓ SHOW COMPLETE SOLUTION All missing security headers bundled at the end of the report — ready to copy.

100 Referrer Policy

Referrer-Policy: strict-origin-when-cross-origin (via HTTP-Header).

Strict setting "strict-origin-when-cross-origin" — no path leak, no HTTP downgrade leak. Best practice.

100 MIME Type Protection

MIME type protection active (nosniff) — browsers will not misinterpret files.

100 Clickjacking Protection

Clickjacking protection active: X-Frame-Options = SAMEORIGIN.

0 Permissions (Camera, Microphone, etc.)

No Permissions-Policy set. Third-party scripts could access camera, microphone, or location.

☛ Action needed: Set a Permissions-Policy to control access to camera, microphone, and location. GDPR-relevant: Without this setting, third-party scripts could silently access sensitive device features. Example: Permissions-Policy: camera=(), microphone=(), geolocation=()

▸ How to fix this — step-by-step guide

Permissions-Policy controls whether scripts (including third-party) may access camera, microphone, location, motion sensors etc. GDPR-relevant because sensitive device APIs can otherwise be reached unnoticed.

Apache server (classic hosting at most providers)

File: .htaccess in the web root

<IfModule mod_headers.c>
    Header always set Permissions-Policy "camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=(), magnetometer=(), interest-cohort=()"
</IfModule>

⚠ "()" at the end means: no caller (not even your own page) may use this API. If you need geolocation (e.g. a map feature): use geolocation=(self) instead of geolocation=(). "interest-cohort=()" disables Google’s FLoC tracking.

WordPress Special for WordPress: where to add this

Option 1: via .htaccess (recommended — no theme editing)

File: .htaccess in the WordPress root

<IfModule mod_headers.c>
    Header always set Permissions-Policy "camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=()"
</IfModule>

⚠ Standard WordPress needs none of these APIs. If you use a plugin that needs the camera (QR scanner, video upload), set that API to "(self)".

Option 2: via functions.php in the child theme (Advanced alternative)

File: functions.php of your CHILD theme

add_action('send_headers', function () {
    header('Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=()');
});

⚠ Back up functions.php before edits.

✓ How to verify it works: F12 → Network → Response Header: "permissions-policy" visible.

↓ SHOW COMPLETE SOLUTION All missing security headers bundled at the end of the report — ready to copy.

90 Cookies

1 first-party and 0 third-party cookie(s).

1 of 1 cookie(s) without SameSite protection — sent with requests from other websites.

☛ Action needed: Set the SameSite attribute (Lax or Strict) for all cookies. This prevents cookies from being sent with requests from other websites (CSRF protection).

▸ How to fix this — step-by-step guide

Without "SameSite" cookies are sent on requests from foreign sites — the basis of CSRF attacks (a foreign page silently triggers actions in your name because the login cookie travels along). Set SameSite=Lax as a minimum.

Apache server (classic hosting at most providers)

File: .htaccess in the web root

<IfModule mod_headers.c>
    Header always edit Set-Cookie "^(.*)$" "$1; SameSite=Lax" "expr=!(resp('Set-Cookie') -strmatch '*SameSite*')"
</IfModule>

⚠ SameSite=Lax is a good default. Strict is safer but breaks external links (user clicks from Google to your site — cookies are NOT sent, login is lost). None allows cross-site but requires "; Secure".

WordPress Special for WordPress: where to add this

Option 2: via functions.php in the child theme (Advanced alternative)

File: wp-config.php (above "/* That’s all, stop editing! */")

@ini_set('session.cookie_samesite', 'Lax');
@ini_set('session.cookie_secure', '1');
@ini_set('session.cookie_httponly', '1');

⚠ Sets SameSite/Secure/HttpOnly for PHP session cookies. WordPress login cookies have been SameSite=Lax since WP 6.2. Update older versions!

✓ How to verify it works: F12 → Application → Cookies → "SameSite" column should show "Lax" or "Strict" everywhere, not empty.

First-party cookies (from the website itself)

Name	Domain	Encrypted	Server only	SameSite
460020e1c62a4b504205adf41ac08df2	hohenzollern-schloss.de	Yes	Yes	None

↓ SHOW COMPLETE SOLUTION All missing security headers bundled at the end of the report — ready to copy.

100 Local Storage (Web Storage)

No local storage (Web Storage) used — no tracking risk.

10 Third-Party Requests

113 request(s) to 24 different third-party servers.

10 third-party server(s) outside the EU/EEA — potentially problematic for GDPR compliance.

☛ Action needed: POSSIBLE GDPR VIOLATION: Your visitors' data is being transferred to servers outside the EU/EEA. Since the Schrems II ruling, this is only permitted with special safeguards. Solutions: (1) Switch to EU-based alternatives (e.g., Matomo instead of Google Analytics, Bunny Fonts instead of Google Fonts). (2) If not possible: Ensure Standard Contractual Clauses (SCC) and additional technical measures are in place. (3) Obtain explicit visitor consent BEFORE data is transferred.

▸ How to fix this — step-by-step guide

GDPR-relevant: visitor data (at least IP + User-Agent) is transmitted to servers outside the EU/EEA. Since the Schrems-II ruling (2020) this requires Standard Contractual Clauses + supplementary technical measures AND prior consent. Best fix: replace with EU alternatives where possible.

WordPress Special for WordPress: where to add this

WordPress plugin: Common culprits and EU alternatives: Google Fonts → Bunny Fonts or self-host (plugin "OMGF — Host Google Fonts Locally"). Google Analytics → Matomo (self-hosted) or Plausible (EU servers). Google reCAPTCHA → hCaptcha (EU) or Friendly Captcha. Google Maps → OpenStreetMap. YouTube embeds → plugin "WP YouTube Lyte" loads only after click. CDN: Cloudflare → BunnyCDN (EU) or KeyCDN.

✓ How to verify it works: Load in incognito mode, F12 → Network → list all requests → check "Domain" column for non-EU servers. After migration no unrequested US domains should load.

14 third-party server(s) within the EU/EEA.

vz-28d911f9-bca.b-cdn.net 41 Requests · Germany (DE) · EU/EEA

Requested URLs:

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/thumbnail_ca3867da.jpg

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/playlist.m3u8

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/1080p/video.m3u8

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/240p/video.m3u8

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/1080p/video0.ts

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/240p/video0.ts

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/1080p/video1.ts

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/1080p/video2.ts

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/1080p/video3.ts

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/1080p/video4.ts

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/1080p/video5.ts

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/1080p/video6.ts

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/1080p/video7.ts

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/1080p/video8.ts

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/1080p/video9.ts

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/1080p/video10.ts

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/1080p/video11.ts

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/1080p/video12.ts

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/1080p/video13.ts

https://vz-28d911f9-bca.b-cdn.net/9c5a0456-42a8-4590-9eae-21954ee06cf8/1080p/video14.ts

... and 21 more request(s)

rum-metrics.bunny.net 15 Requests · Germany (DE) · EU/EEA

Requested URLs:

https://rum-metrics.bunny.net/trackperformance?zone=no&latency=62

https://rum-metrics.bunny.net/trackperformance?zone=ec&latency=167

https://rum-metrics.bunny.net/trackperformance?zone=tw&latency=205

https://rum-metrics.bunny.net/trackperformance?zone=it&latency=15

https://rum-metrics.bunny.net/trackperformance?zone=id&latency=184

https://rum-metrics.bunny.net/trackperformance?zone=isr&latency=57

https://rum-metrics.bunny.net/trackperformance?zone=brb&latency=300

https://rum-metrics.bunny.net/trackperformance?zone=ph&latency=193

https://rum-metrics.bunny.net/trackperformance?zone=se&latency=43

https://rum-metrics.bunny.net/trackperformance?zone=ga&latency=109

https://rum-metrics.bunny.net/trackperformance?zone=la&latency=154

https://rum-metrics.bunny.net/trackperformance?zone=hou&latency=135

https://rum-metrics.bunny.net/trackperformance?zone=mx&latency=146

... and 2 more request(s)

player.mediadelivery.net 8 Requests · Germany (DE) · EU/EEA

Requested URLs:

https://player.mediadelivery.net/embed/736026/9c5a0456-42a8-4590-9eae-21954ee06cf8?autoplay=true&loop=true&muted=true&preload=true&responsive=true

https://player.mediadelivery.net/assets/1.3.36/player.es.css

https://player.mediadelivery.net/assets/1.3.36/player.es.js

https://player.mediadelivery.net/video/736026/9c5a0456-42a8-4590-9eae-21954ee06cf8/thumbnails.vtt?referer=https%3A%2F%2Fhohenzollern-schloss.de%2F

... and 4 more request(s)

fonts.bunny.net 4 Requests · Germany (DE) · EU/EEA

Requested URLs:

https://fonts.bunny.net/css?family=Rubik

https://fonts.bunny.net/rubik/files/rubik-latin-400-normal.woff2

... and 2 more request(s)

edgezone-no.bunnyinfra.net 4 Requests · Norway (NO) · EU/EEA

Requested URLs:

https://edgezone-no.bunnyinfra.net/500b.jpg?s=1793020862537

https://edgezone-no.bunnyinfra.net/500b.jpg?s=1793020862487

... and 2 more request(s)

edgezone-ph.bunnyinfra.net 4 Requests · Philippines (PH) · Non-EU

⚠ GDPR Issue: This server is located outside the EU/EEA. Transferring personal data (e.g. your visitors' IP addresses) to this server may violate Art. 44-49 GDPR. Without a valid legal basis (e.g. consent, Standard Contractual Clauses) this data transfer is unlawful.

Requested URLs:

https://edgezone-ph.bunnyinfra.net/500b.jpg?s=1793020866525

https://edgezone-ph.bunnyinfra.net/500b.jpg?s=1793020867497

... and 2 more request(s)

video.bunnycdn.com 4 Requests · Germany (DE) · EU/EEA

Requested URLs:

https://video.bunnycdn.com/.metrics/track-session

... and 3 more request(s)

consentcdn.cookiebot.com 3 Requests · Germany (DE) · EU/EEA

Requested URLs:

https://consentcdn.cookiebot.com/consentconfig/98809f97-70f7-4c82-bf30-8cf7989a0f09/settings.json

https://consentcdn.cookiebot.com/consentconfig/98809f97-70f7-4c82-bf30-8cf7989a0f09/hohenzollern-schloss.de/configuration.js

https://consentcdn.cookiebot.com/sdk/bc-v5.min.html

consent.cookiebot.com 2 Requests · Germany (DE) · EU/EEA

Requested URLs:

https://consent.cookiebot.com/uc.js

https://consent.cookiebot.com/98809f97-70f7-4c82-bf30-8cf7989a0f09/cc.js?renew=false&referer=hohenzollern-schloss.de&dnt=false&init=false

metrics-bunny.net 2 Requests · Germany (DE) · EU/EEA

Requested URLs:

https://metrics-bunny.net/test/register

... and 1 more request(s)

edgezone-ec.bunnyinfra.net 2 Requests · Ecuador (EC) · Non-EU

Requested URLs:

https://edgezone-ec.bunnyinfra.net/500b.jpg?s=1793020863268

... and 1 more request(s)

edgezone-tw.bunnyinfra.net 2 Requests · Taiwan (TW) · Non-EU

Requested URLs:

https://edgezone-tw.bunnyinfra.net/500b.jpg?s=1793020863267

... and 1 more request(s)

edgezone-it.bunnyinfra.net 2 Requests · Italy (IT) · EU/EEA

Requested URLs:

https://edgezone-it.bunnyinfra.net/500b.jpg?s=1793020864628

... and 1 more request(s)

edgezone-id.bunnyinfra.net 2 Requests · Indonesia (ID) · Non-EU

Requested URLs:

https://edgezone-id.bunnyinfra.net/500b.jpg?s=1793020864479

... and 1 more request(s)

edgezone-isr.bunnyinfra.net 2 Requests · Israel (IL) · EU/EEA

Requested URLs:

https://edgezone-isr.bunnyinfra.net/500b.jpg?s=1793020865218

... and 1 more request(s)

edgezone-brb.bunnyinfra.net 2 Requests · Australia (AU) · Non-EU

Requested URLs:

https://edgezone-brb.bunnyinfra.net/500b.jpg?s=1793020865758

... and 1 more request(s)

edgezone-se.bunnyinfra.net 2 Requests · Sweden (SE) · EU/EEA

Requested URLs:

https://edgezone-se.bunnyinfra.net/500b.jpg?s=1793020867850

... and 1 more request(s)

edgezone-ga.bunnyinfra.net 2 Requests · United States (US) · Non-EU

Requested URLs:

https://edgezone-ga.bunnyinfra.net/500b.jpg?s=1793020868385

... and 1 more request(s)

edgezone-la.bunnyinfra.net 2 Requests · United States (US) · Non-EU

Requested URLs:

https://edgezone-la.bunnyinfra.net/500b.jpg?s=1793020868556

... and 1 more request(s)

edgezone-hou.bunnyinfra.net 2 Requests · United States (US) · Non-EU

Requested URLs:

https://edgezone-hou.bunnyinfra.net/500b.jpg?s=1793020869722

... and 1 more request(s)

edgezone-mx.bunnyinfra.net 2 Requests · Mexico (MX) · Non-EU

Requested URLs:

https://edgezone-mx.bunnyinfra.net/500b.jpg?s=1793020870063

... and 1 more request(s)

edgezone-rs.bunnyinfra.net 2 Requests · Serbia (RS) · Non-EU

Requested URLs:

https://edgezone-rs.bunnyinfra.net/500b.jpg?s=1793020872056

... and 1 more request(s)

36d49a30.metrics-bunny.net 1 Requests · Germany (DE) · EU/EEA

Requested URLs:

https://36d49a30.metrics-bunny.net/test/hello

478d3fc4.metrics-bunny.net 1 Requests · Germany (DE) · EU/EEA

Requested URLs:

https://478d3fc4.metrics-bunny.net/test/hello

100 Tracker Detection

No known trackers detected.

0 External Resource Integrity (SRI)

0 of 3 external resource(s) use integrity verification (SRI).

☛ Action needed: Not all external resources have integrity verification. Add SRI hashes for the missing resources.

▸ How to fix this — step-by-step guide

Only some of your external resources (0 of 3) are protected by SRI. Add integrity attributes to the remaining ones too.

WordPress Special for WordPress: where to add this

WordPress plugin: Approach: view page source → all <script src="https://…"> and <link href="https://…"> without integrity attribute → generate hash at https://www.srihash.org/ → add integrity="sha384-…" crossorigin="anonymous". Plugin "WP-SRI" automates many cases.

✓ How to verify it works: F12 → Console on page load: no "Failed to find a valid digest" messages. Source: all external <script>/<link> have an integrity attribute.

No external resources use integrity verification. Tampered files would not be detected.

☛ Action needed: Add Subresource Integrity (SRI) for all external scripts and stylesheets. This allows the browser to detect if an external file has been tampered with. Your web developer can easily generate the integrity attributes.

▸ How to fix this — step-by-step guide

SRI (Subresource Integrity) is a checksum in HTML that defines what an externally loaded file MUST look like. If someone tampers with the external file (e.g. a CDN gets compromised), the browser refuses to load it. You add the "integrity" attribute on the script/link tag.

WordPress Special for WordPress: where to add this

WordPress plugin: In WordPress you can rarely add SRI hashes manually (scripts are queued via wp_enqueue_script()). Plugin "WP-SRI" (in the plugin directory) adds integrity hashes automatically for external scripts/styles. For statically embedded resources in your theme: generate the hash at https://www.srihash.org/, add integrity="sha384-…" and crossorigin="anonymous" on the <script>/<link> tag.

✓ How to verify it works: F12 → Network → requests with status 200 from CDN domains (cdn.jsdelivr.net, cdnjs.cloudflare.com etc.) → in HTML source the tag must contain "integrity=\"sha384-…\" crossorigin=\"anonymous\"".

75 DNS Security

No CAA records. Any certificate authority could issue a certificate for this domain.

☛ Action needed: Create CAA DNS records to specify which certificate authorities may issue certificates for your domain. This prevents unauthorized certificates from being issued.

▸ How to fix this — step-by-step guide

CAA records (Certification Authority Authorization) define in DNS which Certificate Authorities are allowed to issue certificates for your domain. Without a CAA record an attacker could request a fraudulent certificate for your domain at any CA. CAA is pure DNS configuration — set in your registrar/DNS-panel, NOT in WordPress.

☞ Concrete CAA values for the ten most common DACH-region hosts

Find your host in the table, copy the values to your DNS panel. For multi-CA hosts: one separate CAA record per CA (all with tag issue, flag 0, name @). Additionally recommended: an iodef record with a contact email for abuse reports.

#	Host	CA(s) used	CAA value(s) — tag `issue`
1	Hetzner Webhosting (basic certificate, free in package)	DigiCert (programme „Encryption Everywhere")	`digicert.com`
1	Hetzner Webhosting (Let’s Encrypt, free)	Let’s Encrypt (ISRG)	`letsencrypt.org`
2	All-Inkl	Let’s Encrypt + Sectigo (Pro)	`letsencrypt.org` `sectigo.com`
3	IONOS (1&1)	DigiCert (GeoTrust) + Let’s Encrypt	`digicert.com` `letsencrypt.org`
4	STRATO	Sectigo + Let’s Encrypt	`sectigo.com` `letsencrypt.org`
5	Cloudflare (Universal SSL)	Google Trust Services + DigiCert + Let’s Encrypt	`pki.goog` `digicert.com` `letsencrypt.org`
6	AWS (ACM / CloudFront)	Amazon Trust Services	`amazon.com` `amazontrust.com` `awstrust.com` `amazonaws.com`
7	Mittwald	Let’s Encrypt + Sectigo	`letsencrypt.org` `sectigo.com`
8	Webgo	Let’s Encrypt + Sectigo	`letsencrypt.org` `sectigo.com`
9	raidboxes (Managed WordPress)	Let’s Encrypt	`letsencrypt.org`
10	Host Europe / DomainFactory	Sectigo + Let’s Encrypt	`sectigo.com` `letsencrypt.org`

Name   Type   Flag   Tag      Value
@      CAA    0      issue    "digicert.com"
@      CAA    0      issue    "letsencrypt.org"
@      CAA    0      iodef    "mailto:security@your-domain.com"

The iodef line (last line) is optional but recommended: CAs report abuse attempts to that address. For subdomains (e.g. shop.your-domain.com) create separate records with the subdomain name instead of @ — modern CAs check parent CAA automatically though.

If your host is not on the list: open your current certificate in the browser (padlock → certificate → issuer). The CA name is shown there (e.g. "Sectigo RSA Domain Validation Secure Server CA" → value sectigo.com). Add that as a CAA record, done.

WordPress Special for WordPress: where to add this

WordPress plugin: CAA records are NOT created in WordPress but in your domain registrar / DNS provider panel (e.g. Hetzner-Robot, IONOS Domains, Cloudflare Dashboard, INWX, etc.). Common label: "CAA record" or under "TXT records" with type selector "CAA". One separate record per CA.

✓ How to verify it works: On https://www.ssllabs.com/ssltest/analyze.html?d=your-domain.com → "DNS CAA" section → all your CAs should be listed. Or via dig: dig CAA your-domain.com.

2 nameservers present — good redundancy.

IPv6 support present (AAAA records).

SPF record present: v=spf1 include:secureserver.net -all — protects against email spoofing.

No DMARC record. The domain is vulnerable to email phishing.

☛ Action needed: Create a DMARC DNS record at _dmarc.yourdomain.com. DMARC protects against phishing and email spoofing. Example: v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com

▸ How to fix this — step-by-step guide

DMARC combines SPF and DKIM into an explicit instruction for receiving mail servers: "What to do if emails claim to come from us but SPF/DKIM fail?" Without DMARC each server decides — usually generously. With DMARC=reject you effectively prevent phishing in your name.

WordPress Special for WordPress: where to add this

WordPress plugin: DNS matter. TXT record at subdomain _dmarc.your-domain.com. Recommended stages: Observe first: v=DMARC1; p=none; rua=mailto:dmarc-reports@your-domain.com — review reports for weeks. Then tighten: v=DMARC1; p=quarantine; rua=… — suspicious mails go to spam. Final: v=DMARC1; p=reject; rua=… — they’re refused outright.

✓ How to verify it works: dig TXT _dmarc.your-domain.com — or online https://dmarcian.com/dmarc-inspector/.

0 Security Contact (security.txt)

No security.txt file found (RFC 9116). Security researchers don't know how to report vulnerabilities.

☛ Action needed: Create a security.txt file at /.well-known/security.txt. This allows security researchers to responsibly report vulnerabilities. Required fields: Contact (email or URL) and Expires (expiration date).

▸ How to fix this — step-by-step guide

A security.txt (RFC 9116) tells security researchers how to responsibly report vulnerabilities to you. Without it, reports may go to spam or never be sent. A plain text file at the correct path is enough.

Apache server (classic hosting at most providers)

File: /.well-known/security.txt (create the folder if it doesn’t exist)

Contact: mailto:security@your-domain.com
Expires: 2027-12-31T23:59:59.000Z
Preferred-Languages: en, de
Canonical: https://your-domain.com/.well-known/security.txt

⚠ Replace "security@your-domain.com" with your actual security contact (or a generic info@). "Expires" must be a future date and should be renewed regularly. The file is plain .txt, not PHP.

WordPress Special for WordPress: where to add this

Option 1: via .htaccess (recommended — no theme editing)

File: security.txt file in /.well-known/ under your WordPress root

Contact: mailto:security@your-domain.com
Expires: 2027-12-31T23:59:59.000Z
Preferred-Languages: en, de
Canonical: https://your-domain.com/.well-known/security.txt

⚠ Via FTP/SFTP create a folder ".well-known" in the WordPress root (the leading dot matters — some FTP tools need "show hidden files" enabled), inside save the file security.txt with the content above. If WordPress redirects the URL: add to .htaccess: RewriteRule ^\.well-known/ - [L]

WordPress plugin: Plugin "security.txt" (search the plugin directory) lets you configure this in the WordPress backend without FTP.

✓ How to verify it works: Open https://your-domain.com/.well-known/security.txt in a browser — content must be visible (no 404).

100 External Reporting Endpoints

No external reporting endpoints detected.

85 Cookie Consent

Cookie consent system detected: Cookiebot, cookiebot.com.

Consent banner is visible to visitors.

80 Privacy Policy & Legal Notice

Legal notice linked: "Impressum" (/de/impressum).

⚙ Your ready-to-use security .htaccess

All missing security headers combined into one block. Append this block to the end of your .htaccess — done. 4 headers will be set.

⚠ Why this recommendation does NOT give a 100% score — and why that's how it is with WordPress

The Content-Security-Policy above deliberately includes 'unsafe-inline' for both style-src and script-src. This does NOT provide full XSS protection — it's a pragmatic trade-off, not a bug.

Why? A typical WordPress setup (theme + 5-15 plugins) emits 10-50 different inline <script> blocks into the HTML: jQuery init, slider init, cookie banner, tracking, GTM, web vitals, lazy-load, speculation rules and so on. A strict script-src 'self' blocks them all — the site becomes visually and functionally broken (blank slider, broken cookie banner, dead plugins).

Consequence for scoring: Sites running WordPress with plugins can score at most ~75-85 points in the CSP category in this app — the full 100% rating is only achievable when inline code is signed via nonce or hash (technically demanding, breaks on every theme/plugin update).

Paths to full XSS protection (in increasing complexity):

Plugin "WP Content Security Policy & Headers" — automatically adds nonces to inline scripts (medium effort, cleanest WP solution).
Hash-based CSP — whitelist every inline script via SHA-256 in the CSP (fragile, breaks on updates).
Externalize inline scripts — rebuild theme/plugins so no inline JS is emitted (huge effort, often impossible).

Anyone who doesn't take one of these paths lives with 'unsafe-inline' — like about 95% of all production WordPress sites on the web. The other CSP directives still protect: default-src 'self' blocks external resources, object-src 'none' bans Flash/Java, frame-ancestors 'self' prevents clickjacking, base-uri 'self' prevents base-tag hijacking. Not maximum protection, but realistic protection for WP reality.

⚠ Important on Hetzner-Konsoleh webhosting (managed / shared hosting)

On Hetzner-Konsoleh webhosting (and comparable shared hosts like All-Inkl, IONOS, Strato, 1blu, …), Apache throws a 500 Internal Server Error as soon as Header always edit Set-Cookie … expr=… appears in .htaccess. The Apache error log says:

Can't parse envclause/expression: syntax error, unexpected T_OP_STR_EQ, expecting $end

This is not a WebForensik bug and not a typo — the shared host has blocked the mod_headers expr= subset via AllowOverride limits (for security, because Header edit could also manipulate cookies of other tenants).

☛ For Hetzner-Konsoleh users: use the variant below marked with the red "Hetzner / Shared" badge. It consists of two files (.htaccess + wp-config.php) instead of one, but avoids the 500 error reliably. Cookie flags go into wp-config.php instead of .htaccess.

Apache Standard Apache (any host, without WordPress)

Append this block to the end of your .htaccess in the web root — done.

<IfModule mod_headers.c>
    Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"
    Header always set Content-Security-Policy "default-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; font-src 'self' https: data:; object-src 'none'; frame-ancestors 'self'; base-uri 'self'; upgrade-insecure-requests"
    Header always set Permissions-Policy "camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=(), magnetometer=(), interest-cohort=(), browsing-topics=()"

    # Fehlende Cookie-Flags konditional ergänzen (nur wenn nicht schon gesetzt)
    Header always edit Set-Cookie "^(.*)$" "$1; SameSite=Lax" "expr=!(resp('Set-Cookie') -strmatch '*SameSite*')"
</IfModule>

Hetzner / Shared Hetzner-Konsoleh / Managed Hosting (two files)

This variant avoids the 500 Internal Server Error on Hetzner-Konsoleh and similar shared hosts (All-Inkl, IONOS, Strato, 1blu …): the .htaccess only contains the header directives (no "Header edit"), cookie flags move into wp-config.php. Two files to edit instead of one, but guaranteed to run.

1. File: .htaccess in the WordPress root

# BEGIN WebForensik Security
<IfModule mod_headers.c>
    Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"
    Header always set Content-Security-Policy "default-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; font-src 'self' https: data:; object-src 'none'; frame-ancestors 'self'; base-uri 'self'; upgrade-insecure-requests"
    Header always set Permissions-Policy "camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=(), magnetometer=(), interest-cohort=(), browsing-topics=()"
</IfModule>
# END WebForensik Security

2. File: wp-config.php in the WordPress root

Insert ABOVE the line "/* That's all, stop editing! */". Back up wp-config.php first!

// === WebForensik: Cookie-Hardening (Hetzner-Konsoleh-tauglich) ===
// Bitte OBERHALB der Zeile "/* That's all, stop editing! */" einfügen.
// Wirkt auf PHP-Session- und WordPress-Login-Cookies.
// Plugin-eigene Cookies (z.B. WooCommerce, Cookie-Banner) müssen in den
// Plugin-Einstellungen separat auf "Secure" gestellt werden.
@ini_set('session.cookie_samesite', 'Lax');

WordPress WordPress: .htaccess in WP root

Insert this block ABOVE the "# BEGIN WordPress" line, otherwise WP overwrites it on permalink changes.

# BEGIN WebForensik Security
<IfModule mod_headers.c>
    Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"
    Header always set Content-Security-Policy "default-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; font-src 'self' https: data:; object-src 'none'; frame-ancestors 'self'; base-uri 'self'; upgrade-insecure-requests"
    Header always set Permissions-Policy "camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=(), magnetometer=(), interest-cohort=(), browsing-topics=()"

    # Fehlende Cookie-Flags konditional ergänzen
    Header always edit Set-Cookie "^(.*)$" "$1; SameSite=Lax" "expr=!(resp('Set-Cookie') -strmatch '*SameSite*')"
</IfModule>
# END WebForensik Security

WordPress Alternative for WordPress: functions.php in child theme

If your host disallows .htaccess changes: append this PHP snippet to the end of your CHILD theme's functions.php. Back up first — NEVER edit the parent theme, it gets overwritten on updates.

add_action('send_headers', function () {
    header("Strict-Transport-Security: max-age=31536000; includeSubDomains");
    header("Content-Security-Policy: default-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; font-src 'self' https: data:; object-src 'none'; frame-ancestors 'self'; base-uri 'self'; upgrade-insecure-requests");
    header("Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=(), magnetometer=(), interest-cohort=(), browsing-topics=()");
});

// Cookie-Flags für PHP-Session-Cookies — wirkt nur auf $_SESSION,
// NICHT auf von Plugins/Themes per setcookie() gesetzte Cookies.
// Für umfassende Cookie-Absicherung die .htaccess-Variante oben verwenden.
add_action('init', function () {
    if (headers_sent()) return;
    @ini_set('session.cookie_samesite', 'Lax');
}, 1);

Dry-run — we re-load your site with the proposed headers and show which resources would be blocked. Takes about 30 seconds.

HTTP Response Headers

Header	Value
cache-control	no-store, no-cache, must-revalidate, post-check=0, pre-check=0
connection	keep-alive
content-type	text/html; charset=utf-8
date	Mon, 26 Oct 2026 13:21:01 GMT
expires	Wed, 17 Aug 2005 00:00:00 GMT
last-modified	Mon, 26 Oct 2026 13:21:01 GMT
pragma	no-cache
server	Apache
transfer-encoding	chunked
x-content-type-options	nosniff
cross-origin-opener-policy	same-origin
referrer-policy	strict-origin-when-cross-origin
x-frame-options	SAMEORIGIN

New Scan · Compare

Embed your score on your website

Show your WebForensik score publicly. The badge is a lightweight SVG, loads fast, and respects your visitors' privacy (no tracking).

HTML code to embed (this specific scan)

<a href="https://webforensik.de/results.php?id=3304" target="_blank" rel="noopener">
  <img src="https://webforensik.de/badge.php?id=3304" alt="WebForensik Score" width="174" height="28">
</a>

Or dynamically — always shows the latest scan of this domain

<a href="https://webforensik.de/?url=https://hohenzollern-schloss.de" target="_blank" rel="noopener">
  <img src="https://webforensik.de/badge.php?domain=hohenzollern-schloss.de" alt="WebForensik Score" width="174" height="28">
</a>