Security - https://rijksoverheid.nl BeaverCheck Audit

F

Subresource Integrity

Action

0 of 3 external resources have SRI

FIX

0 of 3 external resources have SRI

External script from statistiek.rijksoverheid.nl lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://statistiek.rijksoverheid.nl/ppms.js

External script from statistiek.rijksoverheid.nl lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: //statistiek.rijksoverheid.nl/containers/bf9c05f0-c13f-4e22-80c7-e603d39fc616.js

External script from survey-deploy.platformrijksoverheid.nl lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://survey-deploy.platformrijksoverheid.nl/js/pastease.js

SRI Coverage 0 / 3 of external resources have integrity hashes

Tag	Domain	Integrity
<script>	statistiek.rijksoverheid.nl	✗ Missing
<script>	statistiek.rijksoverheid.nl	✗ Missing
<script>	survey-deploy.platformrijksoverheid.nl	✗ Missing

D

Permissions-Policy

Action

No header set

FIX

No header set

No Permissions-Policy header

Consider adding a Permissions-Policy header to restrict browser feature access from embedded content.

No Permissions-Policy header set.

Without this header, embedded iframes can request access to sensitive device features.

Suggested header

Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=()

D

security.txt

Action

No /.well-known/security.txt published

FIX

security.txt

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

B

Security Headers

6 of 10 headers properly configured

REVIEW

6 of 10 headers properly configured

HSTS is missing includeSubDomains

Without includeSubDomains, subdomains can still be accessed over HTTP.

Got: max-age=31622400 Expected: max-age=31536000; includeSubDomains

X-Content-Type-Options is properly configured

Got: nosniff

X-Frame-Options is properly configured

Got: DENY

Referrer-Policy is properly configured

Got: no-referrer

Permissions-Policy header is missing

Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.

Expected: geolocation=(), camera=(), microphone=()

Content-Security-Policy is present

Got: default-src 'none'; base-uri 'none'; frame-ancestors 'none'; form-action 'none';…

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

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

X-Powered-By header is not present

Server header is present without version info

Got: nginx

Without includeSubDomains, subdomains can still be accessed over HTTP.

Expected: max-age=31536000; includeSubDomains

Why this matters

Without includeSubDomains, a forgotten dev subdomain over HTTP can set malicious cookies that ride to the apex.

Learn more ▾

HSTS without includeSubDomains protects only the exact domain. Cookies set on a non-HSTS subdomain can ride to the apex via cookie-scope attacks. The fix is one directive append. Verify all subdomains support HTTPS first — adding includeSubDomains to a domain with HTTP-only subdomains breaks them.

Source: RFC 6797

Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.

Expected: geolocation=(), camera=(), microphone=()

Why this matters

Permissions-Policy locks down browser APIs you don't use — without it, every page can request camera/mic/geolocation if XSS lands.

Learn more ▾

By default every page can request the camera, microphone, geolocation, payment APIs, and dozens more. Permissions-Policy turns off the ones you don't need so a future bug can't quietly start using them. It's a defense-in-depth header — one line, big surface reduction.

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

CORS Configuration

No CORS headers

REVIEW

No CORS headers

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

A+

Content Security Policy

9 of 10 CSP checks passed

PASS

9 of 10 CSP checks passed

Raw CSP policy

Got: default-src 'none'; base-uri 'none'; frame-ancestors 'none'; form-action 'none'; upgrade-insecure-requests

default-src directive is set

Got: default-src 'none'

No 'unsafe-inline' in script source

No 'unsafe-eval' in script source

No wildcard in script source

object-src falls back to default-src

base-uri is properly restricted

Got: base-uri 'none'

frame-ancestors directive is set

Got: frame-ancestors 'none'

form-action directive is set

Got: form-action 'none'

upgrade-insecure-requests is enabled

Parsed Policy

default-src 'none'

base-uri 'none'

frame-ancestors 'none'

form-action 'none'

upgrade-insecure-requests

A+

TLS & Certificates

TLS 1.3, 7 checks passed

PASS

TLS 1.3, 7 checks passed

TLS 1.3 is used

Got: TLS 1.3

Strong cipher suite is used

Got: TLS_CHACHA20_POLY1305_SHA256

HTTP/2 is not negotiated

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

Got: http/1.1

Certificate is valid (expires in 85 days)

Got: 2026-07-15T23:59:59Z

Certificate chain has 2 certificates

Certificate uses modern signature algorithm

Got: SHA256-RSA

Certificate covers 9 domain(s)

Got: rijksoverheid.nl, www.rijksoverheid.nl, opendata.rijksoverheid.nl, feeds.rijksoverheid.nl, static.rijksoverheid.nl, government.nl, www.government.nl, opendata.government.nl, feeds.government.nl

Certificate is issued by a trusted CA

Got: CN=DigiCert G2 TLS EU RSA4096 SHA384 2022 CA1,O=DigiCert Ireland Limited,C=IE

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_CHACHA20_POLY1305_SHA256

HTTP Version

HTTP/1.1

Certificate Chain

Leaf Certificate

Subject CN=rijksoverheid.nl,O=Rijksoverheid,L=Den Haag,ST=Zuid-Holland,C=NLIssuer CN=DigiCert G2 TLS EU RSA4096 SHA384 2022 CA1,O=DigiCert Ireland Limited,C=IEValid 2025-07-16T00:00:00Z → 2026-07-15T23:59:59ZExpires in 85 days SANs rijksoverheid.nl, www.rijksoverheid.nl, opendata.rijksoverheid.nl, feeds.rijksoverheid.nl, static.rijksoverheid.nl, government.nl, www.government.nl, opendata.government.nl, feeds.government.nlSignature SHA256-RSASerial f9b5dd33618ce18baec2b49e36552a7

Intermediate (CA Certificate)

Subject CN=DigiCert G2 TLS EU RSA4096 SHA384 2022 CA1,O=DigiCert Ireland Limited,C=IEIssuer CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=USValid 2022-09-19T00:00:00Z → 2032-09-18T23:59:59ZExpires in 2342 days Signature SHA384-RSASerial 64f84ff791fa676f29cf36537a2749e

A+

Cookie Security

No cookies set — no cookie security risks

PASS

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

No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+

Information Leakage

No exposures

PASS

No exposures

security.txt is present — good practice

No sensitive files exposed

No sensitive files exposed — all paths returned 404.

Path	Status	Category	Risk
/.git/HEAD	✓ Not found	Version Control	—
/.git/config	✓ Not found	Version Control	—
/.svn/entries	✓ Not found	Version Control	—
/.env	✓ Not found	Configuration	—
/.env.local	✓ Not found	Configuration	—
/.env.production	✓ Not found	Configuration	—
/wp-config.php	✓ Not found	Configuration	—
/.htaccess	✓ Not found	Configuration	—
/phpinfo.php	✓ Not found	Debug	—
/server-status	✓ Not found	Debug	—
/server-info	✓ Not found	Debug	—
/.well-known/security.txt	✗ Exposed	Security Policy	Info

A+

Email Security

DMARC: reject

PASS

DMARC: reject

DMARC policy is reject — strongest protection

DMARC

Policy reject — strongest protection Record v=DMARC1; p=reject; adkim=r; aspf=r; pct=100; fo=1; rf=afrf; ri=86400; ruf=mailto:dmarcFailureRep@ag.ssonet.nl!10m; rua=mailto:DMARCaggrep@ag.ssonet.nl!2m

A

Transport Security

HTTP/3, HSTS, and TLS version analysis

PASS

HTTP/3, HSTS, and TLS version analysis

HTTP/3 (QUIC) not advertised

HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.

HSTS enabled (base policy)

HSTS missing includeSubDomains

Without includeSubDomains, HSTS only protects the exact domain.

TLS 1.3 in use (fastest handshake, 1-RTT)