The scan focuses on common security misconfigurations, including HTTP security headers, SSL/TLS configuration, cookie security flags, exposed files, and server information leakage. These issues are among the most frequent causes of data exposure, session hijacking, and client-side attacks. The scanner only reads publicly available information and is fully non-intrusive.
Server hardening is the process of securing your server by closing unnecessary access points and fixing common misconfigurations. Think of it like securing your home: you lock doors, don't advertise when you're away, and install an alarm system.
Most hardening measures are free configuration changes — editing .htaccess, updating PHP settings, or tweaking your CMS. The hard part isn't the implementation, it's knowing what to fix. That's what this scanner does.
Modern browsers have built-in protection against clickjacking, XSS attacks, and other exploits — but only if your server tells them to activate it. We check if you're sending the 10 most important security headers.
We verify that your site uses HTTPS and has a valid SSL certificate from a trusted Certificate Authority. We also check expiration dates and flag self-signed certificates that trigger browser warnings.
We analyze cookies set by your website and check if they use proper security flags: Secure (HTTPS-only), HttpOnly (JavaScript cannot read), and SameSite (CSRF protection). We also check for overly long expiration times and broad domain scope.
HttpOnly flag, attackers can steal session cookies via XSS attacks
and hijack user accounts. Without Secure, cookies can be intercepted over HTTP.
Without SameSite, your site is vulnerable to CSRF attacks where malicious
sites can perform actions on behalf of logged-in users.
We scan for publicly accessible files that should be hidden: .git folders
(exposes source code), .env files (database passwords), backup archives,
and leftover installation directories. We also detect which CMS/technology you're using.
We check if your server reveals software versions (Apache, PHP, WordPress) in HTTP headers and HTML. This is like leaving a blueprint of your security system visible to potential attackers.
Standard users get 5 scans per day. If you need more (for example, to test changes as you implement fixes), contact me for unlimited access.