← All Results
Domain History

pijava.pl

Grade D · 56/100 · 5/7 security headers present

Security Score

D
56/ 100

Security Headers

5/ 7

CSP Violations

NoViolations

Issues Found

11Issues

Recommendations

5Available

Security

56 / 100

Moderate security gaps found — unsafe directives or weak source restrictions.

Compliance

79 / 100

Mostly compliant but some directives or headers are missing.

Best Practices

10 / 100

Best practices largely absent — review CSP configuration.

CSP Analysis

Content Security PolicyHIGH
default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; connect-src 'self' https://api.pijava.pl; font-src 'self' data:;
Directive Analysis
default-srcLOW
self
script-srcHIGH
self unsafe-inline unsafe-eval
•Unsafe inline execution allowed in script-src
•Unsafe eval() execution allowed in script-src
•No nonces or hashes used for script-src
style-srcHIGH
self unsafe-inline
•Unsafe inline execution allowed in style-src
img-srcLOW
self data:
•Info: 'data:' URI in img-src
connect-srcLOW
self https://api.pijava.pl
font-srcLOW
self data:
•Info: 'data:' URI in font-src
Missing Directives
⚠HIGHMissing HIGH directive object-src (Plugin control - should be 'none')
⚠HIGHMissing HIGH directive base-uri (Base URI control - prevents base tag injection)
⚠HIGHMissing HIGH directive frame-ancestors (Framing control - prevents clickjacking)
⚠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-PolicyPresent

geolocation=(), microphone=(), camera=()

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

✓Referrer-PolicyPresent

strict-origin-when-cross-origin

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

✓Strict-Transport-SecurityPresent

max-age=63072000;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.

1 recommended security header is missing on pijava.pl.

Issues Found

  • •Info: 'data:' URI in font-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 form-action (Form submission control - prevents form hijacking)medium
  • •Missing security header: Cross-Origin-Opener-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 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

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

pijava.pl

4 scans since 6/5/2026

D

Latest: 56/100

Total Scans

4

Latest Score

56/100

First Scan

6/5/2026

Last Scan

6/5/2026

Security

56 / 100

Moderate security gaps found — unsafe directives or weak source restrictions.

Compliance

79 / 100

Mostly compliant but some directives or headers are missing.

Best Practices

10 / 100

Best practices largely absent — review CSP configuration.

Score Trend

Security score progression over 4 scans

Scan History

DateScoreCSPHeadersIssuesAction
Jun 5, 2026
D (56)
Yes
5/711View →
Jun 5, 2026
D (56)
Yes
5/711View →
Jun 5, 2026
D (56)
Yes
5/711View →
Jun 5, 2026
D (56)
Yes
5/711View →

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