← All Results
Domain History

tecflowsolucoess.github.io

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

Security Score

F
0/ 100

Security Headers

1/ 7

CSP Violations

NoViolations
Plot twist: There was no policy all along

Issues Found

8Issues

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=31556952

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

✗X-Content-Type-OptionsMissing

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

How to add it:

nginx
add_header X-Content-Type-Options "nosniff" always;
apache
Header always set X-Content-Type-Options "nosniff"
cloudflare
Rules > Transform Rules > Managed Transforms > Enable "Add X-Content-Type-Options header"
✗X-Frame-OptionsMissing

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

How to add it:

nginx
add_header X-Frame-Options "DENY" always;
apache
Header always set X-Frame-Options "DENY"
cloudflare
Rules > Transform Rules > HTTP Response Header Modification > Set X-Frame-Options to "DENY"
—X-XSS-ProtectionDeprecated

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 tecflowsolucoess.github.io.

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: X-XSS-Protectionmedium
  • •Missing security header: X-Content-Type-Optionsmedium
  • •Missing security header: Referrer-Policymedium
  • •Missing security header: Cross-Origin-Opener-Policymedium
  • •Missing security header: X-Frame-Optionsmedium
  • •Missing security header: Permissions-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 tecflowsolucoess.github.ioWeak headers often come with other exposure — check the full picture.

tecflowsolucoess.github.io

4 scans since 7/23/2026

F

Latest: 0/100

Total Scans

4

Latest Score

0/100

First Scan

7/23/2026

Last Scan

7/23/2026

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.

Score Trend

Security score progression over 4 scans

Scan History

DateScoreCSPHeadersIssuesAction
Jul 23, 2026
F (0)
No
1/78View →
Jul 23, 2026
F (0)
No
1/78View →
Jul 23, 2026
F (0)
No
1/78View →
Jul 23, 2026
F (0)
No
1/78View →

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 (0/100) for tecflowsolucoess.github.io
HTML
<a href="https://headertest.com/results/tecflowsolucoess.github.io" title="Security headers grade for tecflowsolucoess.github.io — HeaderTest">
  <img src="https://headertest.com/api/badge/tecflowsolucoess.github.io" alt="HeaderTest security grade: F (0/100) for tecflowsolucoess.github.io" />
</a>
Markdown
[![HeaderTest security grade: F (0/100) for tecflowsolucoess.github.io](https://headertest.com/api/badge/tecflowsolucoess.github.io)](https://headertest.com/results/tecflowsolucoess.github.io)