Security - https://uni-bonn.de BeaverCheck Audit

F

Security Headers

Action

3 of 10 headers properly configured

FIX

3 of 10 headers properly configured

HSTS max-age is too short (15768000s, 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=15768000; preload Expected: max-age=31536000; includeSubDomains

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

X-Frame-Options header is missing

This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.

Expected: DENY

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

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 'self' https://*.rhrz.uni-bonn.de; script-src 'self' 'unsafe-inline'…

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 not present

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

This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.

Expected: DENY

Why this matters

Without frame protection, your site can be embedded in a hostile page and used for clickjacking.

Learn more ▾

Clickjacking overlays your site under a transparent malicious page so users click invisible buttons. Setting X-Frame-Options: DENY (or a modern frame-ancestors CSP directive) blocks the embedding entirely. There's almost never a legitimate reason to allow it.

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

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

D

Content Security Policy

Action

3 of 10 CSP checks passed

FIX

3 of 10 CSP checks passed

Raw CSP policy

Got: default-src 'self' https://*.rhrz.uni-bonn.de; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://uni-bonn.de https://www.uni-bonn.de https://*.rhrz.uni-bonn.de https://*.hrz.uni-bonn.de https://www.youtube.com https://s.ytimg.com https://apis.google.com https://ajax.googleapis.com https://pjdcqgnb0lmk.statuspage.io https://*.siteimprove.com; img-src 'self' data: https://uni-bonn.de https://www.uni-bonn.de https://*.uni-bonn.de https://*.rhrz.uni-bonn.de https://i.ytimg.com https://*.googleapis.com https://*.vimeocdn.com https://*.youtube.com https://*.siteimprove.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com https://*.siteimprove.com data:; object-src 'self' blob:; frame-src 'self' https://*.uni-bonn.de:* https://*.vimeo.com https://www.youtube.com https://www.youtube-nocookie.com https://content-youtube.googleapis.com https://content.googleapis.com https://pjdcqgnb0lmk.statuspage.io https://www.podcaster.de mailto://*; frame-ancestors 'self' https://*.uni-bonn.de; connect-src 'self' https://uni-bonn.de https://www.uni-bonn.de https://apis.google.com https://webstat.hrz.uni-bonn.de https://cms-proxy.uni-bonn.de

default-src directive is set

Got: default-src 'self' https://*.rhrz.uni-bonn.de

'unsafe-inline' found in script source

'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.

Got: script-src 'self' 'unsafe-inline' 'unsafe-eval' https://uni-bonn.de https://www.uni-bonn.de https://*.rhrz.uni-bonn.de https://*.hrz.uni-bonn.de https://www.youtube.com https://s.ytimg.com https://apis.google.com https://ajax.googleapis.com https://pjdcqgnb0lmk.statuspage.io https://*.siteimprove.com

'unsafe-eval' found in script source

'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.

Got: script-src 'self' 'unsafe-inline' 'unsafe-eval' https://uni-bonn.de https://www.uni-bonn.de https://*.rhrz.uni-bonn.de https://*.hrz.uni-bonn.de https://www.youtube.com https://s.ytimg.com https://apis.google.com https://ajax.googleapis.com https://pjdcqgnb0lmk.statuspage.io https://*.siteimprove.com

No wildcard in script source

object-src allows plugin content

Set object-src to 'none' to prevent Flash/Java plugin exploits.

Got: object-src 'self' blob: Expected: object-src 'none'

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'

frame-ancestors directive is set

Got: frame-ancestors 'self' https://*.uni-bonn.de

form-action directive is missing

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

Expected: form-action 'self'

upgrade-insecure-requests is not set

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

Expected: upgrade-insecure-requests

'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.

Why this matters

Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.

Learn more ▾

unsafe-inline allows inline <script> tags; unsafe-eval allows eval() and similar. Both are necessary for some legacy code but explicitly dangerous. Migrate to nonces (per-page random tokens) or hashes (per-script SHA-256) instead.

Source: OWASP CSP / MDN

'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.

Why this matters

Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.

Learn more ▾

unsafe-inline allows inline <script> tags; unsafe-eval allows eval() and similar. Both are necessary for some legacy code but explicitly dangerous. Migrate to nonces (per-page random tokens) or hashes (per-script SHA-256) instead.

Source: OWASP CSP / MDN

Set object-src to 'none' to prevent Flash/Java plugin exploits.

Expected: object-src 'none'

Why this matters

object-src open in CSP allows Flash/PDF/plugin embedding — a now-deprecated attack vector that should be explicitly blocked.

Learn more ▾

object-src controls <object>, <embed>, and <applet> elements. Modern sites have no need for plugins; setting `object-src 'none'` blocks an entire class of legacy XSS vectors at zero cost. If your CSP missed it, add the directive.

Source: MDN CSP

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

default-src 'self'https://*.rhrz.uni-bonn.de

script-src 'self''unsafe-inline''unsafe-eval'https://uni-bonn.dehttps://www.uni-bonn.dehttps://*.rhrz.uni-bonn.dehttps://*.hrz.uni-bonn.dehttps://www.youtube.comhttps://s.ytimg.comhttps://apis.google.comhttps://ajax.googleapis.comhttps://pjdcqgnb0lmk.statuspage.iohttps://*.siteimprove.com

img-src 'self'data:https://uni-bonn.dehttps://www.uni-bonn.dehttps://*.uni-bonn.dehttps://*.rhrz.uni-bonn.dehttps://i.ytimg.comhttps://*.googleapis.comhttps://*.vimeocdn.comhttps://*.youtube.comhttps://*.siteimprove.com

style-src 'self''unsafe-inline'https://fonts.googleapis.com

font-src 'self'https://fonts.gstatic.comhttps://*.siteimprove.comdata:

object-src 'self'blob:

frame-src 'self'https://*.uni-bonn.de:*https://*.vimeo.comhttps://www.youtube.comhttps://www.youtube-nocookie.comhttps://content-youtube.googleapis.comhttps://content.googleapis.comhttps://pjdcqgnb0lmk.statuspage.iohttps://www.podcaster.demailto://*

frame-ancestors 'self'https://*.uni-bonn.de

connect-src 'self'https://uni-bonn.dehttps://www.uni-bonn.dehttps://apis.google.comhttps://webstat.hrz.uni-bonn.dehttps://cms-proxy.uni-bonn.de

D

Subresource Integrity

Action

2 of 6 external resources have SRI

FIX

2 of 6 external resources have SRI

External link from www.uni-bonn.de lacks integrity attribute

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

Got: https://www.uni-bonn.de/++webresource++b6e63fde-4269-5984-a67a-480840700e9a/++resource++easyform.css

External link from www.uni-bonn.de lacks integrity attribute

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

Got: https://www.uni-bonn.de/++webresource++f30a16e6-dac4-5f5f-a036-b24364abdfc8/++resource++plone.app.multilingual.stylesheet/multilingual.css

External link from www.uni-bonn.de lacks integrity attribute

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

Got: https://www.uni-bonn.de/++webresource++ac83a459-aa2c-5a45-80a9-9d3e95ae0847/++plone++static/plone-fullscreen/fullscreen.css

External script from webstat.hrz.uni-bonn.de lacks integrity attribute

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

Got: https://webstat.hrz.uni-bonn.de/matomo.js

script from www.uni-bonn.de has SRI protection

SRI Coverage 2 / 6 of external resources have integrity hashes

Tag	Domain	Integrity
<link>	www.uni-bonn.de	✗ Missing
<link>	www.uni-bonn.de	✗ Missing
<link>	www.uni-bonn.de	✗ Missing
<script>	webstat.hrz.uni-bonn.de	✗ Missing
<script>	www.uni-bonn.de	✓ Protected
<script>	www.uni-bonn.de	✓ Protected

D

Email Security

Action

DMARC: none

FIX

DMARC: none

DMARC policy is none — monitoring only

This only monitors, it doesn't block spoofed emails. Change to p=quarantine or p=reject.

DMARC

Policy none — monitoring only, does not block spoofing Record v=DMARC1; p=none; sp=none; adkim=s; aspf=s; rua=mailto:dmarc@uni-bonn.de

This only monitors, it doesn't block spoofed emails. Change to p=quarantine or p=reject.

Why this matters

DMARC p=none collects reports but doesn't actually block spoofed mail — phishing emails still reach inboxes.

Learn more ▾

DMARC's three policies are p=none (monitor only), p=quarantine (mark as spam), and p=reject (bounce). Most domains start at p=none to gather data, but stay there forever, leaving spoofers unblocked. After 30 days of clean DMARC reports, graduate to p=quarantine, then p=reject.

Source: DMARC.org / NIST

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=()

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

B

security.txt

Published with 2 contact(s)

REVIEW

security.txt

Contact: https://www.hrz.uni-bonn.de/cert, mailto:sicherheitsteam@uni-bonn.de

Expires: 2026-08-22T10:03:40z

Policy: https://www.hrz.uni-bonn.de/.well-known/security.txt

B

Transport Security

HTTP/3, HSTS, and TLS version analysis

REVIEW

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 max-age is short: 182 days

HSTS max-age should be at least 1 year (31536000 seconds).

Got: max-age=15768000 (expected 31536000)

HSTS missing includeSubDomains

Without includeSubDomains, HSTS only protects the exact domain.

HSTS preload enabled

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

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-16T16:27:15Z

Certificate chain has 2 certificates

Certificate uses modern signature algorithm

Got: ECDSA-SHA384

Certificate covers 1 domain(s)

Got: uni-bonn.de

Certificate is issued by a trusted CA

Got: CN=E8,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_CHACHA20_POLY1305_SHA256

HTTP Version

HTTP/1.1

Certificate Chain

Leaf Certificate

Subject CN=uni-bonn.deIssuer CN=E8,O=Let's Encrypt,C=USValid 2026-04-17T16:27:16Z → 2026-07-16T16:27:15ZExpires in 85 days SANs uni-bonn.deSignature ECDSA-SHA384Serial 6f83d3684eedcab2cdd49a911481b828fd9

Intermediate (CA Certificate)

Subject CN=E8,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 63959363c24e7082715918bfc3d7ed56

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