Security - https://videoconduit.com BeaverCheck Audit

F

Subresource Integrity

Action

0 of 2 external resources have SRI

FIX

0 of 2 external resources have SRI

External script from cdn.jsdelivr.net lacks integrity attribute

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

Got: https://cdn.jsdelivr.net/npm/alpinejs@3.15.8/dist/cdn.min.js

External script from cdn.jsdelivr.net lacks integrity attribute

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

Got: https://cdn.jsdelivr.net/npm/htmx.org@2.0.8/dist/htmx.min.js

SRI Coverage 0 / 2 of external resources have integrity hashes

Tag	Domain	Integrity
<script>	cdn.jsdelivr.net	✗ Missing
<script>	cdn.jsdelivr.net	✗ Missing

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' cdn.jsdelivr.net 'nonce-RgBF87hJkRNeBzl8P26n88wii7kIq0PKAEJ7Oe4ZZhs' 'unsafe-eval'; style-src 'self' 'unsafe-inline' cdn.jsdelivr.net fonts.googleapis.com; img-src 'self' data: https:; font-src 'self' fonts.gstatic.com; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'

default-src directive is set

Got: default-src 'self'

No 'unsafe-inline' in script source

'unsafe-eval' found in script source

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

Got: script-src 'self' cdn.jsdelivr.net 'nonce-RgBF87hJkRNeBzl8P26n88wii7kIq0PKAEJ7Oe4ZZhs' 'unsafe-eval'

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

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'cdn.jsdelivr.net'nonce-RgBF87hJkRNeBzl8P26n88wii7kIq0PKAEJ7Oe4ZZhs''unsafe-eval'

style-src 'self''unsafe-inline'cdn.jsdelivr.netfonts.googleapis.com

img-src 'self'data:https:

font-src 'self'fonts.gstatic.com

connect-src 'self'

frame-ancestors 'none'

base-uri 'self'

form-action 'self'

B

Permissions-Policy

4 directives, 1 missing

REVIEW

4 directives, 1 missing

camera=() — blocked for all origins

microphone=() — blocked for all origins

geolocation=() — blocked for all origins

payment=() — blocked for all origins

usb not restricted

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

Raw Header

camera=() microphone=() geolocation=() payment=()

Feature Permissions

Blocked Self Only Unrestricted Not Set

camera Blocked

microphone Blocked

geolocation Blocked

payment Blocked

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

9 of 10 headers properly configured

PASS

9 of 10 headers properly configured

Strict-Transport-Security is properly configured

Got: max-age=31536000; includeSubDomains; preload

X-Content-Type-Options is properly configured

Got: nosniff

X-Frame-Options is properly configured

Got: DENY

Referrer-Policy is properly configured

Got: strict-origin-when-cross-origin

Permissions-Policy is set

Got: camera=(), microphone=(), geolocation=(), payment=()

Content-Security-Policy is present

Got: default-src 'self'; script-src 'self' cdn.jsdelivr.net 'nonce-RgBF87hJkRNeBzl8P2…

Cross-Origin-Opener-Policy is properly configured

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

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

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 41 days)

Got: 2026-06-02T12:00:48Z

Certificate chain has 2 certificates

Certificate uses modern signature algorithm

Got: ECDSA-SHA384

Certificate covers 2 domain(s)

Got: api.videoconduit.com, videoconduit.com

Certificate is issued by a trusted CA

Got: CN=E7,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=videoconduit.comIssuer CN=E7,O=Let's Encrypt,C=USValid 2026-03-04T12:00:49Z → 2026-06-02T12:00:48ZExpires in 41 days SANs api.videoconduit.com, videoconduit.comSignature ECDSA-SHA384Serial 6149aa376491abf33c8173750d8bcbfd792

Intermediate (CA Certificate)

Subject CN=E7,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 324 days Signature SHA256-RSASerial aa75f1e62b8f0a220966d38bbfd4baa1

A+

Cookie Security

1 cookies analyzed, 2 checks passed

PASS

1 cookies analyzed, 2 checks passed

Cookie 'csrftoken' has the Secure flag

Cookie 'csrftoken' is missing the HttpOnly flag

Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.

Cookie 'csrftoken' has SameSite=Lax

1 cookies analyzed 1 warnings

Name	Secure	HttpOnly	SameSite	Size	Issues
csrftoken	✓	✗	Lax	41 B	1

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;pct=100;rua=mailto:info@videoconduit.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, preload)

HSTS preload enabled

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