www.affiliatly.com
Grade D · 57/100 · 1/7 security headers present
Security Score
Security Headers
CSP Violations
Issues Found
Recommendations
Security
57 / 100Moderate security gaps found — unsafe directives or weak source restrictions.
Compliance
34 / 100Major compliance issues — missing critical directives and headers.
Best Practices
50 / 100Basic practices followed but missing important optimizations.
CSP Analysis
frame-ancestors 'none'; object-src 'none'; script-src 'self' https://static.affiliatly.com/ https://beacon-v2.helpscout.net/ https://www.google.com/ https://www.gstatic.com/ https://www.paypalobjects.com/ 'nonce-GeHo2uCXm2rCkyfqNlWoaw=='; img-src 'self' https://static.affiliatly.com/ https://beacon-v2.helpscout.net/ https://www.gravatar.com https://d33v4339jhl8k0.cloudfront.net data:;
Directive Analysis
Missing Directives
Security Headers
Isolates the browsing context to prevent Spectre-type side-channel attacks and cross-origin window manipulation.
How to add it:
add_header Cross-Origin-Opener-Policy "same-origin" always;Header always set Cross-Origin-Opener-Policy "same-origin"Rules > Transform Rules > HTTP Response Header Modification > Set Cross-Origin-Opener-Policy to "same-origin"Restricts which browser features (camera, microphone, geolocation) the page can use, limiting attack surface.
How to add it:
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;Header always set Permissions-Policy "camera=(), microphone=(), geolocation=()"Rules > Transform Rules > HTTP Response Header Modification > Set Permissions-Policy valueControls how much referrer information is sent with requests, preventing data leaks to third parties.
How to add it:
add_header Referrer-Policy "strict-origin-when-cross-origin" always;Header always set Referrer-Policy "strict-origin-when-cross-origin"Rules > Transform Rules > HTTP Response Header Modification > Set Referrer-Policy to "strict-origin-when-cross-origin"Forces browsers to use HTTPS for all future requests, preventing man-in-the-middle attacks and SSL stripping.
How to add it:
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"SSL/TLS > Edge Certificates > Enable HSTS (toggle on, set max-age to 12 months, enable includeSubDomains)nosniff
Prevents browsers from MIME-sniffing responses away from the declared Content-Type, blocking drive-by downloads.
Prevents the page from being embedded in iframes, protecting against clickjacking attacks.
How to add it:
add_header X-Frame-Options "DENY" always;Header always set X-Frame-Options "DENY"Rules > Transform Rules > HTTP Response Header Modification > Set X-Frame-Options to "DENY"Legacy XSS filter for older browsers. Modern browsers use CSP instead. Set to "0" to avoid false positives.
5 recommended security headers are missing on www.affiliatly.com.
Issues Found
- •Info: 'data:' URI in img-srcinfo
- •Missing CRITICAL directive default-src (Base fallback directive)critical
- •Missing HIGH directive base-uri (Base URI control - prevents base tag injection)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 style-src (Stylesheet source control)medium
- •Missing security header: Cross-Origin-Opener-Policymedium
- •Missing security header: Permissions-Policymedium
- •Missing security header: Referrer-Policymedium
- •Missing security header: Strict-Transport-Securitymedium
- •Missing security header: X-Frame-Optionsmedium
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 style-src directive with appropriate restrictions
Beyond headers: infrastructure exposure
via OSN, our sister projectSecurity headers protect the browser. OSN maps what's exposed underneath — servers, open ports, known CVEs, DNS and WHOIS.
www.affiliatly.com
1 scan since 7/27/2026
Latest: 57/100
Total Scans
1
Latest Score
57/100
First Scan
7/27/2026
Last Scan
7/27/2026
Security
57 / 100Moderate security gaps found — unsafe directives or weak source restrictions.
Compliance
34 / 100Major compliance issues — missing critical directives and headers.
Best Practices
50 / 100Basic practices followed but missing important optimizations.
Scan History
| Date | Score | CSP | Headers | Issues | Action |
|---|---|---|---|---|---|
| Jul 27, 2026 | D (57) | Yes | 1/7 | 12 | View → |
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.
<a href="https://headertest.com/results/www.affiliatly.com" title="Security headers grade for www.affiliatly.com — HeaderTest">
<img src="https://headertest.com/api/badge/www.affiliatly.com" alt="HeaderTest security grade: D (57/100) for www.affiliatly.com" />
</a>[](https://headertest.com/results/www.affiliatly.com)