Domain History

wecare.inspirisys.com

Grade F · 0/100 · 4/7 security headers present

Security Score

0/ 100

Security Headers

4/ 7

CSP Violations

NoViolations

Perfect score! (Because there's nothing to check)

Issues Found

5Issues

Recommendations

2Available

Security

0 / 100

Critical security vulnerabilities — CSP provides minimal protection.

Compliance

0 / 100

Non-compliant — CSP implementation is incomplete or report-only.

Best Practices

0 / 100

Best practices largely absent — review CSP configuration.

CSP Analysis

!No Content Security Policy Detected

This site does not set a Content-Security-Policy HTTP header. Without CSP, browsers allow all inline scripts, eval(), and resources from any origin, leaving the site vulnerable to Cross-Site Scripting (XSS) attacks.

Security Headers

✗Cross-Origin-Opener-PolicyMissing

Isolates the browsing context to prevent Spectre-type side-channel attacks and cross-origin window manipulation.

How to add it:

nginx

add_header Cross-Origin-Opener-Policy "same-origin" always;

apache

Header always set Cross-Origin-Opener-Policy "same-origin"

cloudflare

Rules > Transform Rules > HTTP Response Header Modification > Set Cross-Origin-Opener-Policy to "same-origin"

✗Permissions-PolicyMissing

Restricts which browser features (camera, microphone, geolocation) the page can use, limiting attack surface.

How to add it:

nginx

add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;

apache

Header always set Permissions-Policy "camera=(), microphone=(), geolocation=()"

cloudflare

Rules > Transform Rules > HTTP Response Header Modification > Set Permissions-Policy value

✗Referrer-PolicyMissing

Controls how much referrer information is sent with requests, preventing data leaks to third parties.

How to add it:

nginx

add_header Referrer-Policy "strict-origin-when-cross-origin" always;

apache

Header always set Referrer-Policy "strict-origin-when-cross-origin"

cloudflare

Rules > Transform Rules > HTTP Response Header Modification > Set Referrer-Policy to "strict-origin-when-cross-origin"

✓Strict-Transport-SecurityPresent

max-age=31536000; includeSubDomains; preload

Forces browsers to use HTTPS for all future requests, preventing man-in-the-middle attacks and SSL stripping.

✓X-Content-Type-OptionsPresent

nosniff

Prevents browsers from MIME-sniffing responses away from the declared Content-Type, blocking drive-by downloads.

✓X-Frame-OptionsPresent

SAMEORIGIN

Prevents the page from being embedded in iframes, protecting against clickjacking attacks.

✓X-XSS-ProtectionPresent

1; mode=block

Legacy XSS filter for older browsers. Modern browsers use CSP instead. Set to "0" to avoid false positives.

3 recommended security headers are missing on wecare.inspirisys.com.

Issues Found

•No Content Security Policy (CSP) header detected - site is vulnerable to XSS attackscritical
•Without CSP, browsers allow all inline scripts, eval(), and resources from any origincritical
•Missing security header: Permissions-Policymedium
•Missing security header: Referrer-Policymedium
•Missing security header: Cross-Origin-Opener-Policymedium

Recommendations

→Implement a Content Security Policy header to protect against XSS and data injection attacks
→Start with a report-only policy (Content-Security-Policy-Report-Only) to identify required resources before enforcing

Beyond headers: infrastructure exposure

via OSN, our sister project

Security headers protect the browser. OSN maps what's exposed underneath — servers, open ports, known CVEs, DNS and WHOIS.

See what the internet sees about wecare.inspirisys.comWeak headers often come with other exposure — check the full picture.

See full exposure report on OSN →Free, no signup.