Wiki
Every line of the report, explained
In the scan report a line fits into a few words. Here each one gets its own page: what it means, how to fix it and how to verify the fix. We run every configuration line on a real server before publishing and check the facts against the standards the same day.
26 report lines/data from 73,386 .lt websites/checked 2026-11-18
Most common findings on .lt websites
- No CSP header69.68 %
- No DMARC record68.5 %
- Outdated WordPress version18.67 %
- No SPF record13.4 %
- PHP 7 or older4.42 %
- Public WordPress user list0.33 %
Share of websites where we found this line. SPF and DMARC: share of mail domains.
Encryption
- Risk: HTTP → HTTPS redirectHTTP requests are not forced to redirect to HTTPSThe site also opens on http:// and the server does not move visitors to HTTPS, so form data and cookies can be read by anyone on the same network. Fix it today: it is one rule, but behind a proxy such as Cloudflare the rule is written differently.10 min
- Risk: TLS certificatethe certificate expired N days ago or is valid for N more daysOnce a certificate has expired, browsers show a warning instead of the site and curl and other programs refuse to connect: fix it immediately. “Valid for N more days” appears when fewer than 14 days are left: the site still works, but automatic renewal has most likely failed.10 min
Security headers
- Risk: Strict-Transport-Security (HSTS)header not setThe site works over HTTPS but does not tell browsers to always use it, so the first request of each visit can be intercepted on a shared network. It is not an emergency: one line and 10 minutes fix it.5 min
- Risk: Content-Security-Policy (CSP)header not setThe browser runs any script on your pages wherever it comes from, so injected foreign code works unhindered. It is a second line of defence, not a hole: there is no rush, and switching it on carelessly is risky.10 min69.68 %
- Warning: X-Frame-Optionsheader not setAny other website can show your page in an invisible frame and trick a visitor into clicking your button without knowing it. One line and 5 minutes fix it, and it almost never breaks anything.5 min
- Warning: Referrer-Policyheader not setThe site does not say how much of its page address to reveal to other sites when a visitor follows a link. The risk is small: modern browsers pass only the domain to other sites even without the header.5 min
- Warning: X-Content-Type-Optionsheader not setThe browser may guess a file's type on its own and, for example, open a text file uploaded by a visitor as an HTML page with scripts. One line, nosniff, turns that off; it matters most for sites where visitors upload files.5 min
Version disclosure
- Warning: Server header reveals the versionServer: nginx/1.26.3The web server states its exact version in every response. That is not a hole in itself, but it is the line automated scanners filter on when they look for one specific vulnerable version. Low urgency: one line fixes it.5 min
- Warning: X-Powered-By reveals the technologyX-Powered-By: PHP/8.4.14The response says which software builds the pages and, with PHP, its exact version. That is not a hole in itself, but it tells automated scanners which sites to try a version-specific exploit on. Low urgency: one setting.5 min
- Risk: PHP version7.4.33: PHP 7.4 is no longer supported (security patches have ended)The site runs a PHP branch that no longer gets security fixes, so newly found PHP vulnerabilities stay open in it for good. Plan the upgrade in weeks, not months. On 18 November 2026 the supported branches are 8.2, 8.3, 8.4 and 8.5, and support for 8.2 ends on 31 December 2026.1 h4.42 %
WordPress and CMS
- Risk: CMS detectedWordPress (OUTDATED), the version is publicly disclosedYour site states its WordPress version in the page source, and when the line says OUTDATED, that version is behind the current release. Update first: hiding the number takes five minutes and fixes nothing.30 min18.67 %
- Warning: WordPress user list via the REST APIpublic names and IDsAnyone can open /wp-json/wp/v2/users and get the ID, display name and slug of every user who has published something, and the slug is normally the login name. No passwords or e-mail addresses are in there, so it is not urgent, but it hands a password guesser half of the login pair.10 min0.33 %
- Warning: WordPress username is disclosed/?author=1 redirects to /author/name/WordPress turns /?author=1 into /author/<slug>/, and by default the slug is the login name of user number 1, usually the administrator. It is a small leak, not a break-in: an attacker still needs the password, but now only the password.15 min
Exposed files
- Risk: .git/ directory is publicly accessibleAnyone can download the full source code of the site with its change history from your server, including every password that was ever committed to the repository. Close it today: it takes one line.10 min0.17 %
- Risk: Publicly accessible.env fileAnyone who adds /.env to your address can download the application's settings file with its passwords. It usually holds the database password, the mail login, and keys for payments and other services. Close it today and change everything that was in it.5 min0.06 %
- Risk: Publicly accessiblewp-config.php backup copyA copy of wp-config.php with a different extension was left in the site folder. The server no longer runs it as PHP and sends it as text: database name, user, password and the WordPress security keys. Delete the copy today and change the password and the keys.10 min0.03 %
- Risk: Publicly accessiblebackup.sql or dump.sqlA copy of the whole database sits in the site folder, and anyone who guesses the file name can download it. It holds customer contacts, orders and the password hashes of users. Move the file out today; if it contains personal data, the incident may have to be reported to the supervisory authority.5 min0.22 %
- Risk: Publicly accessiblephpinfo.php, .DS_Store or .htaccessThese are three forgotten files that show the inside of the server. phpinfo.php lists exact software versions, paths on disk and environment variables, sometimes with passwords: delete it today. .DS_Store gives away the file names of a folder and .htaccess shows your server rules: neither is urgent, and both are fixed in 5 minutes.5 min0.13 %
- Warning: SPF recordno SPF record foundThe domain does not publish which servers may send mail in its name, so a recipient's mail system cannot tell your server from a forger's. Since 1 February 2024 Gmail requires SPF or DKIM from every sender; the record takes 10 minutes.10 min13.4 %
- Info: DKIM signatureno DKIM record found with the usual selectorsWe looked for a DKIM key under 16 common selector names and found none. Either your mail is not signed or it uses another name: DNS cannot list selectors, so this line is informational, and one message you have sent settles it.15 min
- Warning: DMARC recordno DMARC record foundThe domain does not tell mail servers what to do with messages that fake your address, so the recipient's mail system has no instruction to stop them. The first record takes 5 minutes and cannot break anything.10 min68.5 %
- Info: Mail server (MX)the domain has no MX recordsThe domain does not say which server accepts its mail. If you receive no mail on this domain, that is a tidy state, though worth declaring explicitly (a null MX). If you do expect mail, it is an urgent fault: messages are not reaching you.5 min
- Warning: Mail server identification (HELO)the server identifies itself with a technical nameYour mail server calls itself by a name that is not a real internet name (localhost, vps123.local), or its name, IP address and reverse DNS record do not agree. Receiving servers use this to tell a maintained mail server from an infected machine, so your messages land in spam more often.10 min
Reputation
- Risk: IP address blocklist checkthe address is on the Spamhaus ZEN listThe IP address of your website or mail server is on at least one of the four Spamhaus lists that ZEN combines, so mail servers using ZEN can reject mail sent from it. The code decides the urgency: 127.0.0.10 or .11 (PBL) on an address that sends no mail changes nothing, the others need work today.30 min
- Risk: Domain blocklist checkSpamhaus DBL, the domain is on the blocklistSpamhaus counts your domain among those used for spam, phishing or malware. Mail filters that use the DBL look for listed domains inside the messages themselves, so any message that contains a link to your site or your address can be rejected or filed as spam, whoever sent it. Deal with it today.1 h
- Risk: Backscatter blocklistthe mail server is on the Backscatterer.org listYour mail server sent a non-delivery notice, an auto-reply or a sender verification probe to an address that never wrote to it, and hit a Backscatterer.org trap. The weight is modest: the list's own operator advises applying it only to bounce messages, not to ordinary mail. An entry lasts 4 weeks.15 min
The “.lt websites” column and the chart come from our open dataset of Lithuanian websites (DOI 10.5281/zenodo.24282573, CC BY 4.0): SPF and DMARC are counted over 64,910 mail domains, the rest over 73,386 websites. An empty cell means the dataset has no such line, not that the finding is rare.
Not sure which lines are yours? Check your website →
