sede.colpensiones.gov.co
Grade F · 15/100 · 6/7 security headers present
Security Score
Security Headers
CSP Violations
Issues Found
Recommendations
Security
15 / 100Critical security vulnerabilities — CSP provides minimal protection.
Compliance
77 / 100Mostly compliant but some directives or headers are missing.
Best Practices
10 / 100Best practices largely absent — review CSP configuration.
CSP Analysis
default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' blob: https://cdn.siftscience.com/s.js https://checkout.wompi.co/widget.js https://cdnjs.cloudflare.com https://secure.livechatinc.com https://cdn.livechatinc.com *.google.com *.google-analytics.com *.gstatic.com *.googleapis.com https://assets.zendesk.com https://connect.facebook.net *.hotjar.com *.twitter.com *.twimg.com *.googletagmanager.com https://colpensiones.ucontactcloud.com/WebChat/script.js https://www.youtube-nocookie.com; img-src 'self' blob: data: https://secure.livechatinc.com *.google.com *.googleapis.com *.gstatic.com *.google-analytics.com https://img.youtube.com https://s-static.ak.facebook.com https://assets.zendesk.com *.hotjar.com *.twitter.com *.twimg.com https://vozme.com; style-src 'self' 'unsafe-inline' *.gstatic.com *.google.com *.googleapis.com https://assets.zendesk.com *.hotjar.com *.twitter.com https://govco.s3.amazonaws.com/assets/css/styles.css; font-src 'self' *.googleapi
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"camera=(self *), geolocation=(self *), microphone=(self *)
Restricts which browser features (camera, microphone, geolocation) the page can use, limiting attack surface.
strict-origin-when-cross-origin
Controls how much referrer information is sent with requests, preventing data leaks to third parties.
max-age=31536000
Forces browsers to use HTTPS for all future requests, preventing man-in-the-middle attacks and SSL stripping.
nosniff
Prevents browsers from MIME-sniffing responses away from the declared Content-Type, blocking drive-by downloads.
SAMEORIGIN
Prevents the page from being embedded in iframes, protecting against clickjacking attacks.
1; mode=block
Legacy XSS filter for older browsers. Modern browsers use CSP instead. Set to "0" to avoid false positives.
1 recommended security header is missing on sede.colpensiones.gov.co.
Issues Found
- •HIGH RISK CDN: 'cdnjs.cloudflare.com' in script-src - Hosts Angular and other libraries with JSONP/callback endpointshigh
- •HIGH RISK: 'blob:' URI in script-src allows script execution from dynamic blobshigh
- •Info: 'blob:' URI in img-srcinfo
- •Info: 'data:' URI in img-srcinfo
- •Missing HIGH directive base-uri (Base URI control - prevents base tag injection)high
- •Missing HIGH directive frame-ancestors (Framing control - prevents clickjacking)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 form-action (Form submission control - prevents form hijacking)medium
- •Missing security header: Cross-Origin-Opener-Policymedium
- •No nonces or hashes used for script-srcmedium
- •Subdomain wildcard '*.google-analytics.com' in img-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.google-analytics.com' in script-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.google.com' in img-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.google.com' in script-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.google.com' in style-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.googleapi' in font-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.googleapis.com' in img-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.googleapis.com' in script-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.googleapis.com' in style-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.googletagmanager.com' in script-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.gstatic.com' in img-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.gstatic.com' in script-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.gstatic.com' in style-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.hotjar.com' in img-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.hotjar.com' in script-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.hotjar.com' in style-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.twimg.com' in img-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.twimg.com' in script-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.twitter.com' in img-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.twitter.com' in script-src - vulnerable to subdomain takeovermedium
- •Subdomain wildcard '*.twitter.com' in style-src - vulnerable to subdomain takeovermedium
- •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 form-action directive with appropriate restrictions
- →Add frame-ancestors directive with appropriate restrictions
- →Add object-src directive with appropriate restrictions
- →Consider implementing a stricter Content Security Policy
- →Replace wildcards (*) with specific source lists
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.
sede.colpensiones.gov.co
1 scan since 6/1/2026
Latest: 15/100
Total Scans
1
Latest Score
15/100
First Scan
6/1/2026
Last Scan
6/1/2026
Security
15 / 100Critical security vulnerabilities — CSP provides minimal protection.
Compliance
77 / 100Mostly compliant but some directives or headers are missing.
Best Practices
10 / 100Best practices largely absent — review CSP configuration.
Scan History
| Date | Score | CSP | Headers | Issues | Action |
|---|---|---|---|---|---|
| Jun 1, 2026 | F (15) | Yes | 6/7 | 35 | 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/sede.colpensiones.gov.co" title="Security headers grade for sede.colpensiones.gov.co — HeaderTest">
<img src="https://headertest.com/api/badge/sede.colpensiones.gov.co" alt="HeaderTest security grade: F (15/100) for sede.colpensiones.gov.co" />
</a>[](https://headertest.com/results/sede.colpensiones.gov.co)