← All Results
Domain History

www.uasisolutions.com

Grade F · 24/100 · 3/7 security headers present

Security Score

F
24/ 100

Security Headers

3/ 7

CSP Violations

NoViolations

Issues Found

26Issues

Recommendations

10Available

Security

24 / 100

Critical security vulnerabilities — CSP provides minimal protection.

Compliance

42 / 100

Major compliance issues — missing critical directives and headers.

Best Practices

55 / 100

Basic practices followed but missing important optimizations.

CSP Analysis

Content Security PolicyLOW
frame-ancestors 'self'
Directive Analysis
frame-ancestorsLOW
self
Missing Directives
⚠CRITICALMissing CRITICAL directive default-src (Base fallback directive)
⚠CRITICALMissing CRITICAL directive script-src (JavaScript source control)
⚠HIGHMissing HIGH directive object-src (Plugin control - should be 'none')
⚠HIGHMissing HIGH directive base-uri (Base URI control - prevents base tag injection)
⚠MEDIUMMissing MEDIUM directive form-action (Form submission control - prevents form hijacking)
⚠MEDIUMMissing MEDIUM directive connect-src (API/XHR control - prevents data exfiltration)
⚠MEDIUMMissing MEDIUM directive style-src (Stylesheet source control)
⚠MEDIUMMissing MEDIUM directive img-src (Image source control)
⚠MEDIUMMissing MEDIUM directive font-src (Font source control)
Content Security PolicyHIGH
default-src 'self';script-src 'self' 'unsafe-inline' 'unsafe-eval' https:;style-src 'self' 'unsafe-inline' https:;img-src 'self' data: blob: https:;font-src 'self' data: https://*.cdn-website.com https://fonts.gstatic.com https://dd-cdn.multiscreensite.com https://static-cdn.dwhitelabel.com;media-src 'self' blob: https:;connect-src 'self' https:;frame-src 'self' https:;object-src 'none';base-uri 'self';frame-ancestors 'self';upgrade-insecure-requests
Directive Analysis
default-srcLOW
self
script-srcHIGH
self unsafe-inline unsafe-eval https:
•Unsafe inline execution allowed in script-src
•Unsafe eval() execution allowed in script-src
•CRITICAL: 'https:' in script-src allows scripts from ANY HTTPS domain
•No nonces or hashes used for script-src
style-srcHIGH
self unsafe-inline https:
•Unsafe inline execution allowed in style-src
•CRITICAL: 'https:' in style-src allows scripts from ANY HTTPS domain
img-srcHIGH
self data: blob: https:
•Info: 'data:' URI in img-src
•Info: 'blob:' URI in img-src
•CRITICAL: 'https:' in img-src allows scripts from ANY HTTPS domain
font-srcLOW
self data: https://*.cdn-website.com https://fonts.gstatic.com https://dd-cdn.multiscreensite.com https://static-cdn.dwhitelabel.com
•Info: 'data:' URI in font-src
media-srcHIGH
self blob: https:
•Info: 'blob:' URI in media-src
•CRITICAL: 'https:' in media-src allows scripts from ANY HTTPS domain
connect-srcHIGH
self https:
•CRITICAL: 'https:' in connect-src allows scripts from ANY HTTPS domain
frame-srcHIGH
self https:
•CRITICAL: 'https:' in frame-src allows scripts from ANY HTTPS domain
object-srcLOW
none
base-uriLOW
self
frame-ancestorsLOW
self
upgrade-insecure-requestsLOW
Missing Directives
⚠MEDIUMMissing MEDIUM directive form-action (Form submission control - prevents form hijacking)

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

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 www.uasisolutions.com.

Issues Found

  • •CRITICAL: 'https:' in connect-src allows scripts from ANY HTTPS domaincritical
  • •CRITICAL: 'https:' in frame-src allows scripts from ANY HTTPS domaincritical
  • •CRITICAL: 'https:' in img-src allows scripts from ANY HTTPS domaincritical
  • •CRITICAL: 'https:' in media-src allows scripts from ANY HTTPS domaincritical
  • •CRITICAL: 'https:' in script-src allows scripts from ANY HTTPS domaincritical
  • •CRITICAL: 'https:' in style-src allows scripts from ANY HTTPS domaincritical
  • •Info: 'blob:' URI in img-srcinfo
  • •Info: 'blob:' URI in media-srcinfo
  • •Info: 'data:' URI in font-srcinfo
  • •Info: 'data:' URI in img-srcinfo
  • •Missing CRITICAL directive default-src (Base fallback directive)critical
  • •Missing CRITICAL directive script-src (JavaScript source control)critical
  • •Missing HIGH directive base-uri (Base URI control - prevents base tag injection)high
  • •Missing HIGH directive object-src (Plugin control - should be 'none')high
  • •Missing MEDIUM directive connect-src (API/XHR control - prevents data exfiltration)medium
  • •Missing MEDIUM directive font-src (Font source control)medium
  • •Missing MEDIUM directive form-action (Form submission control - prevents form hijacking)medium
  • •Missing MEDIUM directive img-src (Image source control)medium
  • •Missing MEDIUM directive style-src (Stylesheet source control)medium
  • •Missing security header: Cross-Origin-Opener-Policymedium
  • •Missing security header: Permissions-Policymedium
  • •Missing security header: Referrer-Policymedium
  • •No nonces or hashes used for script-srcmedium
  • •Unsafe eval() execution allowed in script-srchigh
  • •Unsafe inline execution allowed in script-srchigh
  • •Unsafe inline execution allowed in style-srchigh

Recommendations

  • →Add base-uri directive with appropriate restrictions
  • →Add connect-src directive with appropriate restrictions
  • →Add default-src directive with appropriate restrictions
  • →Add font-src directive with appropriate restrictions
  • →Add form-action directive with appropriate restrictions
  • →Add img-src directive with appropriate restrictions
  • →Add object-src directive with appropriate restrictions
  • →Add script-src directive with appropriate restrictions
  • →Add style-src directive with appropriate restrictions
  • →Consider implementing a stricter Content Security Policy

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 www.uasisolutions.comWeak headers often come with other exposure — check the full picture.

www.uasisolutions.com

2 scans since 6/26/2026

F

Latest: 24/100

Total Scans

2

Latest Score

24/100

First Scan

6/26/2026

Last Scan

6/26/2026

Security

24 / 100

Critical security vulnerabilities — CSP provides minimal protection.

Compliance

42 / 100

Major compliance issues — missing critical directives and headers.

Best Practices

55 / 100

Basic practices followed but missing important optimizations.

Score Trend

Security score progression over 2 scans

Scan History

DateScoreCSPHeadersIssuesAction
Jun 26, 2026
F (24)
Yes
3/726View →
Jun 26, 2026
D- (49)
Yes
3/712View →

Show off your security grade

Embed this badge on your site or README. It updates automatically after each scan and links back to this report.

HeaderTest security grade: F (24/100) for www.uasisolutions.com
HTML
<a href="https://headertest.com/results/www.uasisolutions.com" title="Security headers grade for www.uasisolutions.com — HeaderTest">
  <img src="https://headertest.com/api/badge/www.uasisolutions.com" alt="HeaderTest security grade: F (24/100) for www.uasisolutions.com" />
</a>
Markdown
[![HeaderTest security grade: F (24/100) for www.uasisolutions.com](https://headertest.com/api/badge/www.uasisolutions.com)](https://headertest.com/results/www.uasisolutions.com)
www.uasisolutions.com Security Headers — Scan History | HeaderTest