Website security in plain language
Enter your website and get a free security report: what we found, how risky it is and what to do about it.
✓ free scan✓ no sign-up
Type your domain. The scan is free and usually takes under a minute.
A graded list of findings, ranked by risk, each with a recommended fix.
Follow the step-by-step instructions, or ask us for help.
Exposed files, security headers, email and DNS settings, known vulnerabilities, blacklists and tracking scripts, checked from the outside without logging in or changing anything.
Each finding explains the problem, how risky it is and what to do, written for site owners, not just developers.
Most findings come with step-by-step instructions or a configuration example. If you would rather not do it yourself, email [email protected] and we will take a look.
All checks run from the outside: nothing is installed or changed on your site.
HTTPS availability, HTTP→HTTPS redirects, redirect chains, SSL certificate expiry, mixed content.
HSTS, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy, including common configuration mistakes.
Tracking scripts (Google, Meta, Hotjar, TikTok…) without a visible consent banner, tracking cookies set before consent, Secure and HttpOnly cookie flags.
SPF, DMARC and common DKIM selectors (protection against email sent in your name), plus CAA (who may issue your SSL certificate).
Commonly forgotten files: .env, .git, database dumps, backup archives, old config files, phpinfo. Checked only when you confirm you own the site or have permission.
CISA KEV, NVD, OSV and WPScan lookups for the CMS, PHP, plugin and JavaScript versions we can see, with EPSS exploit forecasts where available.
Spam blocklists (SpamCop, Barracuda, Spamhaus), Google Safe Browsing, open ports on the server IP (Shodan) and subdomains listed in public certificate logs.
Optional Google Lighthouse audit: performance, accessibility, best practices and SEO — four separate scores.
| Free scan, no account needed | ✓ |
| Plain-language explanations (English and Lithuanian) | ✓ |
| Step-by-step fixes, with configuration examples where possible | ✓ |
| Help with the fixes | Email us |