Security - https://mymoonova.com 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

7 of 10 CSP checks passed

REVIEW

7 of 10 CSP checks passed

Raw CSP policy

Got: default-src 'self'; script-src 'self' 'unsafe-inline' cdnjs.cloudflare.com o2swit.ch js.stripe.com accounts.google.com; style-src 'self' 'unsafe-inline' cdnjs.cloudflare.com; img-src 'self' data: https:; font-src 'self'; connect-src 'self' api.stripe.com; frame-src js.stripe.com accounts.google.com www.youtube.com www.youtube-nocookie.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self'

default-src directive is set

Got: default-src 'self'

'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' cdnjs.cloudflare.com o2swit.ch js.stripe.com accounts.google.com

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

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'

script-src 'self''unsafe-inline'cdnjs.cloudflare.como2swit.chjs.stripe.comaccounts.google.com

style-src 'self''unsafe-inline'cdnjs.cloudflare.com

img-src 'self'data:https:

font-src 'self'

connect-src 'self'api.stripe.com

frame-src js.stripe.comaccounts.google.comwww.youtube.comwww.youtube-nocookie.com

frame-ancestors 'none'

base-uri 'self'

form-action 'self'

B

Subresource Integrity

3 of 4 external resources have SRI

REVIEW

3 of 4 external resources have SRI

link from cdnjs.cloudflare.com has SRI protection

script from cdnjs.cloudflare.com has SRI protection

External link from o2swit.ch lacks integrity attribute

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

Got: https://o2swit.ch/assets/style.css

SRI Coverage 3 / 4 of external resources have integrity hashes

Tag	Domain	Integrity
<link>	cdnjs.cloudflare.com	✓ Protected
<script>	cdnjs.cloudflare.com	✓ Protected
<script>	cdnjs.cloudflare.com	✓ Protected
<link>	o2swit.ch	✗ Missing

B

Permissions-Policy

5 directives, 0 missing

REVIEW

5 directives, 0 missing

camera=() — blocked for all origins

microphone=() — blocked for all origins

geolocation=() — blocked for all origins

payment=self

usb=() — blocked for all origins

Raw Header

camera=() microphone=() geolocation=() payment=self usb=()

Feature Permissions

Blocked Self Only Unrestricted Not Set

camera Blocked

microphone Blocked

geolocation Blocked

payment Self Only

usb Blocked

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 (consider adding preload)

Got: max-age=31536000; includeSubDomains

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: camera=(), microphone=(), geolocation=(), payment=self, usb=()

Content-Security-Policy is present

Got: default-src 'self'; script-src 'self' 'unsafe-inline' cdnjs.cloudflare.com o2swi…

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: o2switch-PowerBoost-v3

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

Got: 2026-08-01T11:51:30Z

Certificate chain has 2 certificates

Certificate uses modern signature algorithm

Got: SHA256-RSA

Certificate covers 3 domain(s)

Got: mail.mymoonova.com, mymoonova.com, www.mymoonova.com

Certificate is issued by a trusted CA

Got: CN=R12,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=mymoonova.comIssuer CN=R12,O=Let's Encrypt,C=USValid 2026-05-03T11:51:31Z → 2026-08-01T11:51:30ZExpires in 87 days SANs mail.mymoonova.com, mymoonova.com, www.mymoonova.comSignature SHA256-RSASerial 5a0cc3e7220a4a7669dcca7a95dbf5a4cf6

Intermediate (CA Certificate)

Subject CN=R12,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 311 days Signature SHA256-RSASerial c212324b70a9b49171dc40f7e285263c

A+

Cookie Security

1 cookies analyzed, 3 checks passed

PASS

1 cookies analyzed, 3 checks passed

Cookie 'MYMOONOVA_SESSID' has the Secure flag

Cookie 'MYMOONOVA_SESSID' has the HttpOnly flag

Cookie 'MYMOONOVA_SESSID' has SameSite=Lax

1 cookies analyzed

Name	Secure	HttpOnly	SameSite	Size	Issues
MYMOONOVA_SESSID	✓	✓	Lax	48 B	—

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: quarantine

PASS

DMARC: quarantine

DMARC policy is quarantine — good protection

DMARC

Policy quarantine — good protection Record v=DMARC1;p=quarantine;sp=none;adkim=r;aspf=r;pct=100;fo=0;rf=afrf;ri=86400;rua=mailto:agustabell8@gmail.com

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)

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