Security - https://cookiedatabase.org BeaverCheck Audit

D

security.txt

Action

No /.well-known/security.txt published

FIX

security.txt

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

B

Content Security Policy

3 of 10 CSP checks passed

REVIEW

3 of 10 CSP checks passed

Raw CSP policy

Got: frame-ancestors 'self' ; upgrade-insecure-requests;

default-src directive is missing

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

Expected: default-src 'self'

No script-src or default-src to check for 'unsafe-inline'

No script-src or default-src to check for 'unsafe-eval'

No script-src or default-src to check for wildcard

object-src falls back to default-src

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'

form-action directive is missing

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

Expected: form-action 'self'

upgrade-insecure-requests is enabled

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.

Parsed Policy

frame-ancestors 'self'

upgrade-insecure-requests

C

Permissions-Policy

Action

10 directives, 1 missing

REVIEW

10 directives, 1 missing

accelerometer=(self)

autoplay=(self)

camera=(self)

encrypted-media=(self)

fullscreen=(self)

geolocation=(self)

microphone=(self)

midi=(self)

payment=(self)

display-capture=(self)

usb not restricted

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

Raw Header

accelerometer=(self) autoplay=(self) camera=(self) encrypted-media=(self) fullscreen=(self) geolocation=(self) microphone=(self) midi=(self) payment=(self) display-capture=(self)

Feature Permissions

Blocked Self Only Unrestricted Not Set

accelerometer Self Only

autoplay Self Only

camera Self Only

encrypted-media Self Only

fullscreen Self Only

geolocation Self Only

microphone Self Only

midi Self Only

payment Self Only

display-capture Self Only

usb Not Set

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

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 is properly configured

Got: SAMEORIGIN

Referrer-Policy is properly configured

Got: strict-origin-when-cross-origin

Permissions-Policy is set

Got: accelerometer=(self), autoplay=(self), camera=(self), encrypted-media=(self), fullscreen=(self), geolocation=(self), microphone=(self), midi=(self), payment=(self), display-capture=(self)

Content-Security-Policy is present

Got: frame-ancestors 'self' ; upgrade-insecure-requests;

Cross-Origin-Opener-Policy is set but not 'same-origin'

Got: same-origin-allow-popups 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: cloudflare

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

Expected: same-origin

Why this matters

COOP is set to a less-restrictive value (same-origin-allow-popups or unsafe-none) — partial isolation only.

Learn more ▾

COOP: same-origin is the strictest level. same-origin-allow-popups allows authenticated popup windows back to your origin. unsafe-none is the legacy default (effectively off). Pick the strictest level your app's popup flows tolerate.

Source: MDN COOP

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_128_GCM_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 87 days)

Got: 2026-07-13T08:21:12Z

Certificate chain has 2 certificates

Certificate uses modern signature algorithm

Got: ECDSA-SHA384

Certificate covers 2 domain(s)

Got: *.cookiedatabase.org, cookiedatabase.org

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_AES_128_GCM_SHA256

HTTP Version

HTTP/1.1

Certificate Chain

Leaf Certificate

Subject CN=cookiedatabase.orgIssuer CN=E8,O=Let's Encrypt,C=USValid 2026-04-14T08:21:13Z → 2026-07-13T08:21:12ZExpires in 87 days SANs *.cookiedatabase.org, cookiedatabase.orgSignature ECDSA-SHA384Serial 642f696e7f0f786d25a33cf462c3a63e6b6

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 330 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+

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	—

A+

Email Security

DMARC: reject

PASS

DMARC: reject

DMARC policy is reject — strongest protection

DMARC

Policy reject — strongest protection Record v=DMARC1; p=reject;

A+

Transport Security

HTTP/3, HSTS, and TLS version analysis

PASS

HTTP/3, HSTS, and TLS version analysis

HTTP/3 (QUIC) supported

The server advertises HTTP/3 via Alt-Svc for faster connections on mobile networks.

HSTS enabled (includeSubDomains, preload)

HSTS preload enabled

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