Security - https://collaborative-office.com BeaverCheck Audit

D

Cross-Origin Tab Safety

Action

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

FIX

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

6 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

Email Security

Action

no DMARC, SPF: -all, DKIM

FIX

no DMARC, SPF: -all, DKIM

No DMARC record found

Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.

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

DKIM configured (selectors: s1, s2)

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

No DMARC record found

Without DMARC, email receivers have no policy for handling authentication failures from your domain.

Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.

Why this matters

Without DMARC, anyone can send phishing emails using your domain name.

Learn more ▾

DMARC tells receiving mail servers what to do with email that fails SPF/DKIM checks for your domain. With a strict 'p=reject' policy, spoofed emails get bounced; without it they reach the inbox. Domains used in phishing campaigns lose deliverability and brand trust fast.

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

Security Headers

7 of 10 headers properly configured

REVIEW

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

Referrer-Policy is properly configured

Got: strict-origin-when-cross-origin

Permissions-Policy is set

Got: geolocation=(), microphone=(), camera=(), payment=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=()

Content-Security-Policy is present

Got: upgrade-insecure-requests

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

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 reveals technology stack

This header discloses server technology (e.g. Express, PHP), helping attackers target known vulnerabilities. Remove it.

Got: PHP/8.2.31

Server header is present without version info

Got: cloudflare

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

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

This header discloses server technology (e.g. Express, PHP), helping attackers target known vulnerabilities. Remove it.

Why this matters

X-Powered-By: PHP/7.4.3 advertises your stack to attackers — disable it.

Learn more ▾

X-Powered-By and similar headers (X-AspNet-Version, X-Runtime) tell attackers which versions to target. Disable in your server/framework config: PHP `expose_php=Off`, ASP.NET `<httpRuntime enableVersionHeader="false">`, Express `app.disable('x-powered-by')`.

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

C

Content Security Policy

Action

2 of 10 CSP checks passed

REVIEW

2 of 10 CSP checks passed

Raw CSP policy

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

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

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

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

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

46 inline style attribute(s) detected

REVIEW

46 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. 46 inline style(s) is moderate. Affected element types include: img, span, button, div, iframe. 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.

B

Subresource Integrity Adoption

50% SRI adoption (1/2 third-party resources)

REVIEW

50% SRI adoption (1/2 third-party resources)

SRI adoption: 1/2 third-party resources protected (50%)

Of 2 third-party `<script>` / `<link rel=stylesheet>` resources, 1 (50%) declare a Subresource Integrity hash via the `integrity=` attribute. SRI binds the page to the exact bytes of the third-party resource: if the CDN is compromised, attacker-modified bytes won't match the declared hash and the browser refuses to execute the resource. Missing SRI on (first 1 examples): - https://www.google.com/recaptcha/api.js?hl=en&&ver=ea883c3ef0a837551becf9abd5461a53#038;render=explicit Fix: add `integrity="sha384-..."` and `crossorigin="anonymous"` attributes. Generators: srihash.org, or in-browser via `await crypto.subtle.digest('SHA-384', bytes)`. Cache-bust the resource URL when you change versions, since the integrity hash will mismatch with old cached bytes.

Got: 50% (1/2)

B

Open Redirect Surface

1 link(s) carry redirect-shaped query parameter(s)

REVIEW

1 link(s) carry redirect-shaped query parameter(s)

Heuristic flag -- whether each endpoint actually permits an arbitrary redirect target depends on server-side validation. Audit the listed paths' redirect-target handling: the endpoint should either (a) restrict to a relative path, (b) restrict to an allowlisted host set, or (c) sign the target. Open redirects power phishing flows (the attacker's URL begins with your trusted domain) and bypass some SSRF-mitigation cookie scoping. Common parameter names flagged: redirect, redirect_uri, redirect_url, redirecturl, return, returnto, return_to, returnurl, return_url, next, nexturl, next_url, continue, goto, dest, destination, forward, target.

Got: https://www.instagram.com/accounts/login/?next=https%3A%2F%2…?next=...

C

Subresource Integrity

Action

1 of 2 external resources have SRI

REVIEW

1 of 2 external resources have SRI

script from www.gstatic.com has SRI protection

External script from www.google.com lacks integrity attribute

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

Got: https://www.google.com/recaptcha/api.js?hl=en&&ver=ea883c3ef0a837551becf9abd5461a53#038;render=explicit

SRI Coverage 1 / 2 of external resources have integrity hashes

Tag	Domain	Integrity
<script>	www.gstatic.com	✓ Protected
<script>	www.google.com	✗ Missing

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+

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

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

Got: 2026-10-31T00:42:58Z

Certificate chain has 3 certificates

Certificate uses modern signature algorithm

Got: ECDSA-SHA256

Certificate covers 2 domain(s)

Got: collaborative-office.com, *.collaborative-office.com

Certificate is issued by a trusted CA

Got: CN=WE1,O=Google Trust Services,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_CHACHA20_POLY1305_SHA256

HTTP Version

HTTP/1.1

Certificate Chain

Leaf Certificate

Subject CN=collaborative-office.comIssuer CN=WE1,O=Google Trust Services,C=USValid 2026-08-01T23:43:03Z → 2026-10-31T00:42:58ZExpires in 81 days SANs collaborative-office.com, *.collaborative-office.comSignature ECDSA-SHA256Serial 4c0f775957eab50f0e004af0aafaf4c2

Intermediate (CA Certificate)

Subject CN=WE1,O=Google Trust Services,C=USIssuer CN=GTS Root R4,O=Google Trust Services LLC,C=USValid 2023-12-13T09:00:00Z → 2029-02-20T14:00:00ZExpires in 924 days Signature ECDSA-SHA384Serial 7ff31977972c224a76155d13b6d685e3

Intermediate (CA Certificate)

Subject CN=GTS Root R4,O=Google Trust Services LLC,C=USIssuer CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BEValid 2023-11-15T03:43:21Z → 2028-01-28T00:00:42ZExpires in 535 days Signature SHA256-RSASerial 7fe530bf331343bedd821610493d8a1b

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

WAF / Bot Protection

Cloudflare

PASS

Cloudflare

Cloudflare detected

Detected via: cf-ray: a291a9b86d20f8bf-GRU

Got: Cloudflare

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+

CORS Depth

No CORS response headers -- the resource is same-origin-only by browser default

PASS

No CORS response headers -- the resource is same-origin-only by browser default

A

Permissions-Policy Granularity

80% high-risk feature coverage (8/10)

PASS

80% high-risk feature coverage (8/10)

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

The Permissions-Policy header explicitly declares policies for 8/10 high-risk features. Covered: camera, microphone, geolocation, payment, usb, accelerometer, gyroscope, magnetometer Not declared (default-allow): serial, midi 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: 80% (8/10)

A+

Referrer-Policy Strictness

Referrer-Policy is `strict-origin-when-cross-origin` (modern default -- full URL same-origin, origin-only cross-origin)

PASS

Referrer-Policy is `strict-origin-when-cross-origin` (modern default -- full URL same-origin, origin-only cross-origin)

Referrer-Policy: `strict-origin-when-cross-origin` -- modern default -- full URL same-origin, origin-only cross-origin

The modern browser default (Chrome 85+, Firefox 87+, Safari 15+). Full URL Referer on same-origin; origin only on cross-origin; no Referer on HTTPS-to-HTTP downgrade. Privacy-safe and breaks no analytics. The recommended explicit value.

Got: strict-origin-when-cross-origin

A+

Source Map Exposure

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

PASS

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

No source maps accessible across 3 probed candidate(s)

A+

HTML Version Disclosure

No software-version disclosures in HTML

PASS

No software-version disclosures in HTML

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+

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+

Permissions-Policy

8 directives, 0 missing

PASS

8 directives, 0 missing

geolocation=() — blocked for all origins

microphone=() — blocked for all origins

camera=() — blocked for all origins

payment=() — blocked for all origins

usb=() — blocked for all origins

magnetometer=() — blocked for all origins

gyroscope=() — blocked for all origins

accelerometer=() — blocked for all origins

Raw Header

geolocation=() microphone=() camera=() payment=() usb=() magnetometer=() gyroscope=() accelerometer=()

Feature Permissions

Blocked Self Only Unrestricted Not Set

geolocation Blocked

microphone Blocked

camera Blocked

payment Blocked

usb Blocked

magnetometer Blocked

gyroscope Blocked

accelerometer Blocked

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)