Skip to content
https://owncloud.com

Security

· 12 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.
SCORE
79
GRADE
C
FIX
2
REVIEW
5
PASS
5
INFO
0
Checks
12
5 PASS 5 REVIEW 2 FIX
D
Content Security Policy
Action
4 of 10 CSP checks passed
FIX
4 of 10 CSP checks passed
Info::
Raw CSP policy
Got: upgrade-insecure-requests; font-src data: https:; img-src data: https:; default-src https: blob: 'unsafe-inline' 'unsafe-eval'
Info::
default-src directive is set
Got: default-src https: blob: 'unsafe-inline' 'unsafe-eval'
Critical::
'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 https: blob: 'unsafe-inline' 'unsafe-eval'
Critical::
'unsafe-eval' found in script source
'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.
Got: script-src https: blob: 'unsafe-inline' 'unsafe-eval'
Info::
No wildcard in script source
Info::
object-src falls back to default-src
Warning::
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'
Warning::
frame-ancestors directive is missing
frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.
Expected: frame-ancestors 'self'
Warning::
form-action directive is missing
form-action restricts where forms can submit data, preventing form hijacking.
Expected: form-action 'self'
Info::
upgrade-insecure-requests is enabled

'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

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

frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.

Expected: frame-ancestors 'self'
Why this matters

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

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

upgrade-insecure-requests
font-src data:https:
img-src data:https:
default-src https:blob:'unsafe-inline''unsafe-eval'
F
Subresource Integrity
Action
0 of 6 external resources have SRI
FIX
0 of 6 external resources have SRI
Warning::
External script from consent.cookiebot.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://consent.cookiebot.com/uc.js?cbid=e217f921-fa5e-4784-a72e-76553381c036&consentmode-dataredaction=dynamic
Warning::
External script from consent.cookiebot.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://consent.cookiebot.com/e217f921-fa5e-4784-a72e-76553381c036/cc.js?renew=false&referer=owncloud.com&dnt=false&init=false
Warning::
External script from consentcdn.cookiebot.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://consentcdn.cookiebot.com/consentconfig/e217f921-fa5e-4784-a72e-76553381c036/owncloud.com/configuration.js
Warning::
External script from www.googletagmanager.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.googletagmanager.com/gtm.js?id=GTM-MZHCZVT
Warning::
External script from consent.cookiebot.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://consent.cookiebot.com/uc.js
Warning::
External script from consent.cookiebot.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://consent.cookiebot.com/uc.js
SRI Coverage 0 / 6 of external resources have integrity hashes
TagDomainIntegrity
<script>consent.cookiebot.com✗ Missing
<script>consent.cookiebot.com✗ Missing
<script>consentcdn.cookiebot.com✗ Missing
<script>www.googletagmanager.com✗ Missing
<script>consent.cookiebot.com✗ Missing
<script>consent.cookiebot.com✗ Missing
B
Security Headers
7 of 10 headers properly configured
REVIEW
7 of 10 headers properly configured
Warning::
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; includeSubDomains Expected: max-age=31536000; includeSubDomains
Info::
X-Content-Type-Options is properly configured
Got: nosniff
Info::
X-Frame-Options is properly configured
Got: SAMEORIGIN
Info::
Referrer-Policy is properly configured
Got: strict-origin
Info::
Permissions-Policy is set
Got: camera=(), microphone=(), usb=()
Info::
Content-Security-Policy is present
Got: upgrade-insecure-requests; font-src data: https:; img-src data: https:; default-…
Warning::
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
Warning::
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
Info::
X-Powered-By header is not present
Info::
Server header is present without version info
Got: nginx

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

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

B
Permissions-Policy
3 directives, 2 missing
REVIEW
3 directives, 2 missing
Info::
camera=() — blocked for all origins
Info::
microphone=() — blocked for all origins
Info::
usb=() — blocked for all origins
Info::
geolocation not restricted
Consider adding geolocation=() to block geolocation access from embedded content.
Info::
payment not restricted
Consider adding payment=() to block payment access from embedded content.

Raw Header

camera=() microphone=() usb=()

Feature Permissions

Blocked Self Only Unrestricted Not Set
camera Blocked
microphone Blocked
usb Blocked
geolocation Not Set
payment Not Set
B
CORS Configuration
No CORS headers
REVIEW
No CORS headers
Info::
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://security.owncloud.com, mailto:security@owncloud.com
Expires: 2026-12-31T22:59:00.000Z
Policy: https://owncloud.com/.well-known/security.txt
B
Transport Security
HTTP/3, HSTS, and TLS version analysis
REVIEW
HTTP/3, HSTS, and TLS version analysis
Info::
HTTP/3 (QUIC) not advertised
HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.
Warning::
HSTS max-age is short: 182 days
HSTS max-age should be at least 1 year (31536000 seconds).
Got: max-age=15768000 (expected 31536000)
Info::
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
Info::
TLS 1.3 is used
Got: TLS 1.3
Info::
Strong cipher suite is used
Got: TLS_AES_128_GCM_SHA256
Info::
HTTP/2 is not negotiated
HTTP/2 provides multiplexing and header compression for better performance.
Got: http/1.1
Info::
Certificate is valid (expires in 51 days)
Got: 2026-06-13T17:29:49Z
Info::
Certificate chain has 2 certificates
Info::
Certificate uses modern signature algorithm
Got: SHA256-RSA
Info::
Certificate covers 21 domain(s)
Got: owncloud.ca, owncloud.co.uk, owncloud.com, owncloud.de, owncloud.help, owncloud.mobi, owncloud.org, owncloud.rocks, owncloud.us, owncloudconnect.com, survey.owncloud.com, www.owncloud.ca, www.owncloud.co.uk, www.owncloud.com, www.owncloud.de, www.owncloud.help, www.owncloud.mobi, www.owncloud.org, www.owncloud.rocks, www.owncloud.us, www.owncloudconnect.com
Info::
Certificate is issued by a trusted CA
Got: CN=R13,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=owncloud.comIssuer CN=R13,O=Let's Encrypt,C=USValid 2026-03-15T17:29:50Z → 2026-06-13T17:29:49ZExpires in 51 days SANs owncloud.ca, owncloud.co.uk, owncloud.com, owncloud.de, owncloud.help, owncloud.mobi, owncloud.org, owncloud.rocks, owncloud.us, owncloudconnect.com, survey.owncloud.com, www.owncloud.ca, www.owncloud.co.uk, www.owncloud.com, www.owncloud.de, www.owncloud.help, www.owncloud.mobi, www.owncloud.org, www.owncloud.rocks, www.owncloud.us, www.owncloudconnect.comSignature SHA256-RSASerial 63168244cae6cfe4a7d8eab6f3ddfbe4822
Intermediate (CA Certificate)
Subject CN=R13,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 5a00f212d8d4b480f3924157ea298305
A+
Cookie Security
No cookies set — no cookie security risks
PASS
No cookies set — no cookie security risks
Info::
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
Info::
No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+
Information Leakage
No exposures
PASS
No exposures
Info::
security.txt is present — good practice
Info::
No sensitive files exposed

No sensitive files exposed — all paths returned 404.

PathStatusCategoryRisk
/.git/HEAD✓ Not foundVersion Control—
/.git/config✓ Not foundVersion Control—
/.svn/entries✓ Not foundVersion Control—
/.env✓ Not foundConfiguration—
/.env.local✓ Not foundConfiguration—
/.env.production✓ Not foundConfiguration—
/wp-config.php✓ Not foundConfiguration—
/.htaccess✓ Not foundConfiguration—
/phpinfo.php✓ Not foundDebug—
/server-status✓ Not foundDebug—
/server-info✓ Not foundDebug—
/.well-known/security.txt✗ ExposedSecurity PolicyInfo
A
Email Security
DMARC: quarantine
PASS
DMARC: quarantine
Info::
DMARC policy is quarantine — good protection
DMARC
Policy quarantine — good protection Record v=DMARC1; p=quarantine; sp=reject; pct=100; rua=mailto:dmarc@owncloud.com; ruf=mailto:dmarc@owncloud.com; adkim=s; aspf=r; fo=1;
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback