Security check report

Security check of ziniu.lt

Passive scan run on . Website checked: ziniu.lt

Check again|Check another website

Report

ziniu.lt

19 Nov 2026, 13:20 · 4244 ms · 23 checks

C69 / 100

3

Risks

8

Warnings

10

Passed

The 3 most important issues to fix first

1

Strict-Transport-Security (HSTS)

Header not set

2

Content-Security-Policy (CSP)

Header not set

3

CMS detected: WordPress 6.9.11 (OUTDATED)

You are using WordPress 6.9.11. Latest stable: 7.1. This version has 2+ known security vulnerabilities (CVE). An update is REQUIRED.

Transport security (HTTPS / TLS)

✓

HTTP → HTTPS redirect

HTTP requests are redirected to HTTPS (301)

More about this check →

✓

TLS certificate

Valid for 54 more days

Issuer: Let's Encrypt

More about this check →

HTTP security headers

×

Strict-Transport-Security (HSTS)

Header not set

What can go wrong:Without this header the browser decides anew each time whether to use HTTPS. A so-called downgrade attack lets an attacker force the browser to connect over insecure HTTP even though the website works over HTTPS, and intercept all the data sent.

Recommendation: Add the HSTS header: Strict-Transport-Security: max-age=31536000; includeSubDomains

What this means and how to fix it →

×

Content-Security-Policy (CSP)

Header not set

What can go wrong:Without this policy the browser runs every script, whatever its source. In an XSS attack the attacker can run their own code in the visitor's browser: steal session cookies, record keystrokes, show fake payment forms.

Recommendation: Set a Content-Security-Policy; a minimal policy to start with: default-src 'self'

What this means and how to fix it →

!

X-Content-Type-Options

Header not set

What can go wrong:Without this header the browser may try to guess the file type and treat a text file as HTML or JavaScript. In some cases this lets malicious code run after it was uploaded as an ordinary file.

Recommendation: Add X-Content-Type-Options: nosniff

What this means and how to fix it →

!

X-Frame-Options (Clickjacking)

Header not set

What can go wrong:Your website can be loaded in an iframe on another website. This is used for clickjacking: the visitor sees one thing but is actually clicking hidden buttons on your website, such as Confirm payment or Change password.

Recommendation: Add X-Frame-Options: SAMEORIGIN

What this means and how to fix it →

!

Referrer-Policy

Header not set

What can go wrong:When a visitor clicks a link on your website, the browser may pass the full URL (with parameters) to the other page. This can reveal sensitive information: search queries, user IDs or session tokens in the URL.

Recommendation: Add Referrer-Policy: strict-origin-when-cross-origin

What this means and how to fix it →

Server and software disclosure

✓

Server header

Version not shown (hcdn)

More about this check →

CMS

×

CMS detected: WordPress 6.9.11 (OUTDATED)

You are using WordPress 6.9.11. Latest stable: 7.1. This version has 2+ known security vulnerabilities (CVE). An update is REQUIRED.

What can go wrong:Each of the 2+ known vulnerabilities is publicly documented. Automated tools constantly check websites and exploit known flaws, usually within minutes of finding them. This means the website can at any moment be infected with malicious code, its visitors redirected or its data stolen.

Recommendation: Update to WordPress 7.1. Always make a backup copy before updating.

What this means and how to fix it →

!

WordPress REST API is publicly accessible

/wp-json/ responds with HTTP 200, the REST API is open to the public

Recommendation: Restrict REST API access: add_filter('rest_authentication_errors', ...) or use a security plugin

What this means and how to fix it →

Publicly accessible sensitive paths

!

WordPress user list via the REST API

/wp-json/wp/v2/users returns 3 users, with public names and IDs

Recommendation: Disable the users endpoint: add_filter('rest_endpoints', fn($e) => (unset($e['/wp/v2/users'], $e['/wp/v2/users/(?P<id>[\d]+)']), $e))

What this means and how to fix it →

✓

Sensitive paths (.git, .env, backup files)

12 paths checked, none publicly accessible

Email: DNS records and mail server

!

DMARC record

Policy: p=none

v=DMARC1; p=none

Recommendation: Strengthen the policy to p=quarantine or p=reject

What this means and how to fix it →

!

Mail server identification (HELO)

The server identifies itself with a technical name, “esmtp”

What can go wrong:Such a name (for example .local, vps123, localhost) is one of the signs by which Spamhaus CSS adds IP addresses to its list.

Recommendation: Set a mail hostname for the server (for example mail.yourdomain.com) that matches its IP address and reverse DNS record

What this means and how to fix it →

!

Risk of being blocked for spam

The mail server is configured in a way typical of servers that end up on the Spamhaus CSS list

What can go wrong:From the outside it is not possible to see whether mailboxes forward messages to Gmail. But a technical identification name or mismatched DNS records show that a control panel set the server up “just to work”, and forwarding is often turned on in such servers.

Recommendation: In the hosting control panel, check that info@ and other mailboxes do not forward messages to external addresses; instead of forwarding, add the mailbox to a mail app (the Gmail app on a phone, Apple Mail, Outlook) over IMAP.

What this means and how to fix it →

i

Mail server (MX)

mx1.hostinger.com (172.65.182.103)

More about this check →

i

DKIM signature

No DKIM record found with the usual selectors (a different selector may be in use)

Recommendation: Make sure the mail server signs messages with DKIM; without it Gmail and Outlook reject messages more often

More about this check →

✓

SPF record

SPF record found (~all)

v=spf1 include:_spf.mail.hostinger.com ~all

More about this check →

✓

Mail server IP on blocklists

172.65.182.103: not found on the Spamhaus ZEN list

More about this check →

✓

Backscatter blocklist

172.65.182.103: not found on the Backscatterer.org list

More about this check →

Reputation and blocklists

✓

Domain blocklist check

Spamhaus DBL: the domain was not found on the blocklist

More about this check →

✓

IP address blocklist check

91.108.98.35, not found on the Spamhaus ZEN list

More about this check →

General information

✓

Homepage is reachable

HTTP 200

Issues found

3 critical risks found + 8 warnings

Left open, these gaps can be used in an attack. We can close them: correct the server configuration, add the missing headers and check the file system. Describe your case and we will reply within 1–2 business days.

Check another website

The scan is passive: it makes only the requests that any browser user could make. Only facts about the publicly accessible configuration are shown, never the contents of files. Are you the website owner and want the report removed? Write to [email protected]

Other checks

All checks →
  • nordania.danskebank.dk

    Nordania Finans - Online Kreditansøgning

    B · 84
  • kauno.diena.lt

    Kauno naujienos | KaunoDiena.lt

    B · 82
  • hitcontract.com

    IT personalo paieška, atranka | Nemokami IT darbo skelbimai | HITCONTRACT

    B · 78
  • visaginas.lt

    Visagino savivaldybė | Visagino savivaldybė

    C · 69
  • www.vta.lt

    Transeksta

    B · 84
  • www.visitvisaginas.lt

    Visagino turizmo informacija | VšĮ Visagino turizmo plėtros centras

    A · 97
  • www.viko.lt

    VIKO – Vilniaus Kolegija

    C · 67
  • visnews.lt

    Visnews – ретранслятор актуальных новостей Висагинаса

    C · 66

Check your own website