Security - https://pop-i.de BeaverCheck Audit

D

Cross-Origin Tab Safety

Action

14 of 14 new-tab link(s) missing rel=noopener

FIX

14 of 14 new-tab link(s) missing rel=noopener

14 link(s) open in a new tab without rel=noopener

Without rel="noopener", the destination tab can navigate the original tab via window.opener -- a reverse-tabnabbing phishing primitive. Modern browsers default to noopener since Chrome 88 / Firefox 79 / Safari 12.1, but explicit rel="noopener noreferrer" remains the documented best practice for older browsers, in-app webviews, and security scanners.

D

Permissions-Policy Granularity

Action

10% high-risk feature coverage (1/10)

FIX

10% high-risk feature coverage (1/10)

Permissions-Policy covers 1/10 high-risk features (10%)

The Permissions-Policy header explicitly declares policies for 1/10 high-risk features. Covered: camera Not declared (default-allow): microphone, geolocation, payment, usb, serial, midi, accelerometer, gyroscope, magnetometer The non-declared features fall back to their spec-default policy (usually `self`), which means an XSS-injected or compromised iframe could request them. For features the page genuinely doesn't use, declare `feature=()` to fully close them.

Got: 10% (1/10)

B

WAF / Bot Protection

No WAF detected via response headers

REVIEW

No WAF detected via response headers

No WAF detected

Response headers don't match any known WAF or bot-management product. Sites exposed to abuse (login, signup, payment) typically benefit from a WAF such as Cloudflare, Akamai, AWS WAF, or Imperva.

C

security.txt

Action

No security.txt file found

REVIEW

No security.txt file found

security.txt (RFC 9116) provides a standardized way for security researchers to report vulnerabilities. Create one at /.well-known/security.txt with at least a Contact field.

Expected: /.well-known/security.txt

security.txt

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

C

CSP Inline-Style Readiness

Action

50 inline style attribute(s) detected

REVIEW

50 inline style attribute(s) detected

Each `style=""` attribute forces `style-src 'unsafe-inline'` in any Content-Security-Policy, which negates most of CSP's XSS-mitigation value. 50 inline style(s) is moderate. Affected element types include: div, a, ul. Move styles to a stylesheet; use CSS custom properties for runtime-dynamic values; or adopt a nonce/hash CSP policy. Most teams take the stylesheet path because it's also a maintainability win.

B

Trusted Types (XSS Sink Hardening)

Trusted Types not enabled

REVIEW

Trusted Types not enabled

Trusted Types (CSP3) is a Chrome 83+ defense that requires DOM-XSS sinks (innerHTML, document.write, eval, ...) to receive a typed-and-sanitized value rather than a raw string. Adding `Content-Security-Policy: require-trusted-types-for 'script'; trusted-types default` neutralizes most DOM-XSS even when a payload reaches a sink. Adoption is currently ~0.1% of pages so this is informational; a roll-out usually starts in report-only mode.

C

HTML Version Disclosure

Action

1 software version(s) disclosed in HTML

REVIEW

1 software version(s) disclosed in HTML

1 software version(s) disclosed in HTML: Hugo 0.123.7

Each disclosed version enables direct CVE lookup -- an attacker who knows you run WordPress 6.4.2 (or whatever specific version) can search the CVE database for known exploits and target accordingly. Remove via your CMS config: WordPress (`remove_action('wp_head', 'wp_generator')`); Drupal (System / Reports / Status report -> Hide generator); Joomla (Global Configuration -> Hide generator); Hugo/Jekyll (delete or override the {{ .Site.Generator }} template hook). For HTML comments, audit your template files directly.

C

Email Security

Action

DMARC: none, SPF: -all, DKIM

REVIEW

DMARC: none, SPF: -all, DKIM

DMARC policy is none — monitoring only

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

SPF ends in -all (hard fail) — strongest setting

DKIM configured (selectors: default)

MTA-STS not configured

MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.

TLS-RPT not configured

TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.

BIMI not configured

BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

DMARC

Policy none — monitoring only, does not block spoofing Record v=DMARC1; p=none; aspf=r; adkim=r; pct=100; rua=mailto:dmarc@pop-i.de; ruf=mailto:dmarc@pop-i.de; fo=1

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

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

MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.

Why this matters

Without MTA-STS, inbound mail can be silently downgraded to plain SMTP by a network attacker.

Learn more ▾

MTA-STS (RFC 8461) tells sending mail servers to use TLS and to refuse delivery if TLS fails. Requires both a TXT record at _mta-sts.<domain> AND a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt. Without it, an active attacker on the network path can strip STARTTLS and read the email in plaintext.

Source: RFC 8461

TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.

Why this matters

Without TLS-RPT, you have no visibility into inbound TLS failures — MTA-STS misconfigurations stay hidden until users complain.

Learn more ▾

TLS-RPT (RFC 8460) is the feedback channel for MTA-STS: senders post aggregate reports of TLS-handshake failures to the URI in your _smtp._tls TXT record. Without it, an MTA-STS misconfiguration silently rejects mail and you find out only when someone notices missing email.

Source: RFC 8460

BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

Why this matters

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

B

Permissions-Policy

2 directives, 4 missing

REVIEW

2 directives, 4 missing

camera=() — blocked for all origins

fullscreen=() — blocked for all origins

microphone not restricted

Consider adding microphone=() to block microphone access from embedded content.

geolocation not restricted

Consider adding geolocation=() to block geolocation access from embedded content.

payment not restricted

Consider adding payment=() to block payment access from embedded content.

usb not restricted

Consider adding usb=() to block usb access from embedded content.

Raw Header

camera=() fullscreen=()

Feature Permissions

Blocked Self Only Unrestricted Not Set

camera Blocked

fullscreen Blocked

microphone Not Set

geolocation Not Set

payment Not Set

usb Not Set

C

Known vulnerability matches

Action

12 known vulnerability match(es) against detected tech

REVIEW

Known Vulnerabilities

Library	Version	Severity	Summary	Fixed In
Bootstrap	3.3.7	medium	XSS is possible in the data-target attribute.	3.4.0
Bootstrap	3.3.7	medium	XSS in collapse data-parent attribute	3.4.0
Bootstrap	3.3.7	medium	XSS in data-target property of scrollspy	3.4.0
Bootstrap	3.3.7	medium	XSS in data-container property of tooltip	3.4.0
Bootstrap	3.3.7	medium	In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.	3.4.0
Bootstrap	3.3.7	medium	In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.	3.4.0
jQuery	3.3.1	medium	jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution	3.4.0
Bootstrap	3.3.7	medium	XSS in data-template, data-content and data-title properties of tooltip/popover	3.4.1
jQuery	3.3.1	medium	Regex in its jQuery.htmlPrefilter sometimes may introduce XSS	3.5.0
jQuery	3.3.1	medium	passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code.	3.5.0
Bootstrap	3.3.7	medium	Bootstrap Cross-Site Scripting (XSS) vulnerability for data-* attributes	3.4.1
Bootstrap	3.3.7	low	Bootstrap before 4.0.0 is end-of-life and no longer maintained.	3.999.999

A

Security Headers

8 of 10 headers properly configured

PASS

8 of 10 headers properly configured

Strict-Transport-Security is properly configured

Got: max-age=63072000; includeSubdomains; preload

X-Content-Type-Options is properly configured

Got: nosniff

X-Frame-Options has unexpected value

Got: NONE Expected: DENY or SAMEORIGIN

Referrer-Policy is properly configured

Got: strict-origin

Permissions-Policy is set

Got: camera=(), fullscreen=()

Content-Security-Policy is present

Got: default-src 'none'; img-src 'self'; font-src 'self'; base-uri 'self'; style-src …

Cross-Origin-Opener-Policy is properly configured

Got: same-origin

Cross-Origin-Embedder-Policy is set

Got: require-corp

X-Powered-By header is not present

Server header reveals version information

The Server header discloses the software version, aiding attackers in targeting known vulnerabilities. Remove the version number.

Got: Apache/2.4.58 (Ubuntu)

Domain is not in the Chrome HSTS preload list (status: unknown)

Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

Got: unknown

Expected: DENY or SAMEORIGIN

Why this matters

An unrecognized X-Frame-Options value falls back to browser default behavior — clickjacking protection silently disabled.

Learn more ▾

X-Frame-Options accepts only DENY, SAMEORIGIN, or ALLOW-FROM (deprecated). Anything else (including typos like SAMEORIGN, or modern CSP-style frame-ancestors values shoved in by mistake) is ignored. The header LOOKS protective but isn't. Use `X-Frame-Options: DENY` plus `Content-Security-Policy: frame-ancestors 'none'` for defense in depth.

Source: MDN X-Frame-Options

The Server header discloses the software version, aiding attackers in targeting known vulnerabilities. Remove the version number.

Why this matters

Server: nginx/1.18.0 tells attackers exactly which CVEs to test — strip the version string.

Learn more ▾

Server version disclosure helps attackers select exploits matching your stack. Configure your server to omit the version (nginx: `server_tokens off;`, Apache: `ServerTokens Prod`). Doesn't fix vulnerabilities but removes the easy reconnaissance step.

Source: OWASP

Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

Why this matters

Not in the Chrome preload list — first-time visitors over plain HTTP can be downgraded by a network attacker before HSTS kicks in.

Learn more ▾

The HSTS header only protects users who have already visited the site (TOFU window). Adding your domain to the Chrome preload list closes that gap so HSTS is enforced from the very first connection. Requires a preload-ready header (max-age=31536000+, includeSubDomains, preload) then submission at hstspreload.org. Inclusion ships in the next Chrome release after acceptance.

Source: hstspreload.org

A+

Content Security Policy

8 of 10 CSP checks passed

PASS

8 of 10 CSP checks passed

Raw CSP policy

Got: default-src 'none'; img-src 'self'; font-src 'self'; base-uri 'self'; style-src 'self' 'unsafe-inline'; script-src 'self'; form-action 'none'; frame-ancestors 'none'; connect-src https://vrmapi.victronenergy.com/;

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 'self'

frame-ancestors directive is set

Got: frame-ancestors 'none'

form-action directive is set

Got: form-action 'none'

upgrade-insecure-requests is not set

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

Expected: upgrade-insecure-requests

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 'none'

img-src 'self'

font-src 'self'

base-uri 'self'

style-src 'self''unsafe-inline'

script-src 'self'

form-action 'none'

frame-ancestors 'none'

connect-src https://vrmapi.victronenergy.com/

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_AES_256_GCM_SHA384

HTTP/2 is not negotiated

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

Got: http/1.1

OCSP stapling not enabled

Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.

Certificate is valid (expires in 174 days)

Got: 2026-10-31T23:59:59Z

Certificate chain has 3 certificates

Certificate uses modern signature algorithm

Got: SHA256-RSA

Certificate covers 2 domain(s)

Got: *.pop-i.de, pop-i.de

Certificate is issued by a trusted CA

Got: CN=RapidSSL TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,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

Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.

Why this matters

Without OCSP stapling, every first-time visitor pays an extra OCSP roundtrip — and the CA learns who's visiting your site.

Learn more ▾

OCSP stapling has the server fetch its own revocation status from the CA and attach the signed response to the TLS handshake. Without it, browsers contact the CA directly: extra latency for the user and a privacy leak (the CA sees who connected). Enable ssl_stapling on (nginx) / SSLUseStapling On (Apache) / OCSPStapling = on (Caddy auto-enables).

Source: RFC 6961 / Mozilla Server-Side TLS guide

Connection

Protocol

TLS 1.3

Cipher Suite

TLS_AES_256_GCM_SHA384

HTTP Version

HTTP/1.1

Certificate Chain

Leaf Certificate

Subject CN=*.pop-i.deIssuer CN=RapidSSL TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=USValid 2026-04-16T00:00:00Z → 2026-10-31T23:59:59ZExpires in 174 days SANs *.pop-i.de, pop-i.deSignature SHA256-RSASerial 24c905b5546c539d07b7888584ef70e

Intermediate (CA Certificate)

Subject CN=RapidSSL TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=USIssuer CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=USValid 2017-11-02T12:24:33Z → 2027-11-02T12:24:33ZExpires in 541 days Signature SHA256-RSASerial b259422ced9812a15a04e99528a0efa

Intermediate (CA Certificate)

Subject CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=USIssuer CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=USValid 2013-08-01T12:00:00Z → 2038-01-15T12:00:00ZExpires in 4268 days Signature SHA256-RSASerial 33af1e6a711a9a0bb2864b11d09fae5

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+

Cookie Hygiene

No cookies set -- cookie-hygiene check is N/A

PASS

No cookies set -- cookie-hygiene check is N/A

No cookies set

A+

Bot Challenge Detection

Scan reached real page content (no bot-protection interstitial)

PASS

Scan reached real page content (no bot-protection interstitial)

No bot-protection interstitial detected -- the rest of the report reflects the real page

A+

Soft-404 Detection

No soft-404 patterns detected in page title or headings

PASS

No soft-404 patterns detected in page title or headings

A+

Empty Page Detection

Page has substantive body text and no placeholder / template-leak signals

PASS

Page has substantive body text and no placeholder / template-leak signals

A+

Geo-Restriction Detection

No geo-restriction signals detected -- scan reached the page from an allowed region

PASS

No geo-restriction signals detected -- scan reached the page from an allowed region

No geo-restriction detected

A+

Maintenance Mode Detection

No maintenance-mode signals detected -- scan reached a normal page

PASS

No maintenance-mode signals detected -- scan reached a normal page

No maintenance-mode signals detected

A+

Subresource Integrity Adoption

Page has no third-party scripts or stylesheets -- SRI not applicable

PASS

Page has no third-party scripts or stylesheets -- SRI not applicable

No third-party scripts or stylesheets to protect with SRI

A

CORS Depth

1 CORS depth signal(s) detected

PASS

1 CORS depth signal(s) detected

CORS response missing `Vary: Origin` header -- cache poisoning risk

The server's CORS response varies by request Origin (Allow-Origin is not `*`), but the response doesn't include `Vary: Origin`. Without `Vary: Origin`, downstream caches (CDN edges, corporate proxies, browser HTTP cache) will cache the CORS response and serve it to clients sending a DIFFERENT Origin. Effect: a cached `Access-Control-Allow-Origin: https://app.example.com` response gets served to a fetch from `https://attacker.example.com`, the browser allows the cross-origin read, and the attacker reads the response. Add `Vary: Origin` whenever Allow-Origin is content-negotiated.

Got: Allow-Origin set without Vary: Origin

A+

Referrer-Policy Strictness

Referrer-Policy is `strict-origin` (strict -- only origin sent, never on HTTPS-to-HTTP downgrade)

PASS

Referrer-Policy is `strict-origin` (strict -- only origin sent, never on HTTPS-to-HTTP downgrade)

Referrer-Policy: `strict-origin` -- strict -- only origin sent, never on HTTPS-to-HTTP downgrade

Sends only the origin (no path / query) on cross-origin requests, and sends nothing at all on HTTPS-to-HTTP downgrade. Privacy-safe; explicit and conservative.

Got: strict-origin

A+

Source Map Exposure

No source maps accessible (probed 4 candidate URL(s))

PASS

No source maps accessible (probed 4 candidate URL(s))

No source maps accessible across 4 probed candidate(s)

A+

Open Redirect Surface

No redirect-shaped query parameters in DOM links

PASS

No redirect-shaped query parameters in DOM links

A+

Auth Security

Page is not a login form -- auth-security checks are N/A

PASS

Page is not a login form -- auth-security checks are N/A

Page does not appear to be a login form

A+

Subdomain Inventory Exposure

No risky subdomain names in certificate SANs

PASS

No risky subdomain names in certificate SANs

A+

Subresource Integrity

No external resources

PASS

No external resources

No external resources to protect

SRI Coverage No external resources — SRI not applicable

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

No security.txt found

Consider adding a security.txt at /.well-known/security.txt.

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	✓ Not found	Security Policy	—
/package.json	✓ Not found	dependency-manifest	—
/composer.json	✓ Not found	dependency-manifest	—
/Gemfile	✓ Not found	dependency-manifest	—
/Gemfile.lock	✓ Not found	dependency-manifest	—
/requirements.txt	✓ Not found	dependency-manifest	—
/pom.xml	✓ Not found	dependency-manifest	—
/.gitlab-ci.yml	✓ Not found	ci-config	—
/.travis.yml	✓ Not found	ci-config	—

A+

API Surface

No API specs or GraphQL introspection found (probed 11 candidate path(s))

PASS

No API specs or GraphQL introspection found (probed 11 candidate path(s))

No API specs or GraphQL introspection found (probed 11 path(s))

A

CORS Configuration

Origin: pop-i.de

PASS

Origin: pop-i.de

CORS restricted to specific origin(s)

Got: pop-i.de

Origin reflection not testable with a single request

Some servers reflect the request Origin header. This requires manual testing with a crafted Origin header.

CORS Configuration ✓ Well Configured

Allow-Origin pop-i.de

Header	Value	Status
Access-Control-Allow-Origin	pop-i.de	✓

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

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 (includeSubDomains, preload)

HSTS preload enabled

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