← All Results
Domain History

domreg.lt

Grade A · 80/100 · 4/7 security headers present

Security Score

A
80/ 100

Security Headers

4/ 7

CSP Violations

NoViolations

Issues Found

8Issues

Recommendations

5Available

Security

80 / 100

Good security foundation but some CSP hardening recommended.

Compliance

66 / 100

Several compliance gaps found in CSP implementation.

Best Practices

38 / 100

Few best practices adopted — significant room for improvement.

CSP Analysis

Content Security PolicyLOW
default-src 'self'; frame-ancestors 'none'; form-action 'self'; object-src 'self'; img-src 'self' data:
Directive Analysis
default-srcLOW
self
frame-ancestorsLOW
none
form-actionLOW
self
object-srcLOW
self
img-srcLOW
self data:
•Info: 'data:' URI in img-src
Missing Directives
⚠CRITICALMissing CRITICAL directive script-src (JavaScript source control)
⚠HIGHMissing HIGH directive base-uri (Base URI control - prevents base tag injection)
⚠MEDIUMMissing MEDIUM directive connect-src (API/XHR control - prevents data exfiltration)
⚠MEDIUMMissing MEDIUM directive style-src (Stylesheet source control)
⚠MEDIUMMissing MEDIUM directive font-src (Font source control)

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

same-origin

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

✓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

DENY

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.

2 recommended security headers are missing on domreg.lt.

Issues Found

  • •Info: 'data:' URI in img-srcinfo
  • •Missing CRITICAL directive script-src (JavaScript source control)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 style-src (Stylesheet source control)medium
  • •Missing security header: Cross-Origin-Opener-Policymedium
  • •Missing security header: Permissions-Policymedium

Recommendations

  • →Add base-uri directive with appropriate restrictions
  • →Add connect-src directive with appropriate restrictions
  • →Add font-src directive with appropriate restrictions
  • →Add script-src directive with appropriate restrictions
  • →Add style-src directive with appropriate restrictions

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 domreg.lt

domreg.lt

3 scans since 7/15/2025

A

Latest: 80/100

Total Scans

3

Latest Score

80/100

First Scan

7/15/2025

Last Scan

7/8/2026

Security

80 / 100

Good security foundation but some CSP hardening recommended.

Compliance

66 / 100

Several compliance gaps found in CSP implementation.

Best Practices

38 / 100

Few best practices adopted — significant room for improvement.

Score Trend

Security score progression over 2 scans

Scan History

DateScoreCSPHeadersIssuesAction
Jul 8, 2026
A (80)
Yes
4/78View →
Jul 15, 2025
A (80)
No
4/60View →

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