ThreatPort

How to check if your website is secure

Updated 2026-10-30 ยท ThreatPort
Check your site the way an outsider would. Confirm HTTPS works and the certificate is valid, read the response headers, see whether the page reveals software versions, try the admin and backup paths an attacker would try, and look your domain up in Google Safe Browsing. Run these checks only on sites you own or are allowed to test.

1. HTTPS and the certificate

Open the site with http:// and confirm it redirects to https://. Then check the certificate's expiry date and that it covers every hostname you use, including www. The SSL checker shows issuer, expiry and supported TLS versions.

2. Security headers

curl -sI https://yourdomain.com

Look for these in the response:

HeaderWhat it does
Strict-Transport-SecurityTells browsers to use HTTPS only, so nobody can downgrade a visitor to plain HTTP.
Content-Security-PolicyLimits where scripts can load from. It is the main defence against injected scripts.
X-Frame-Options or CSP frame-ancestorsStops other sites from framing yours.
X-Content-Type-Options: nosniffStops browsers guessing file types.
Referrer-PolicyControls how much of your URL leaks to other sites.

The security headers checker grades them for you.

3. Software versions on show

In the same header output, look at Server and X-Powered-By. Then view the page source and search for generator. A line such as Apache/2.4.41 or WordPress 6.2 tells a scanner exactly which known bugs to try. Hide versions where you can and keep the software current.

4. Admin and login pages

Try the paths bots try on every domain: /admin, /wp-admin, /wp-login.php, /login, /phpmyadmin. If a login page opens for anyone, put it behind a VPN or an IP allowlist and turn on two-factor sign-in.

5. Files that should never be public

for p in .env .git/HEAD backup.zip wp-config.php.bak debug.log; do
  printf "%-20s %s\n" "$p" "$(curl -s -o /dev/null -w '%{http_code}' https://yourdomain.com/$p)"
done

Every line should say 403 or 404. A 200 means the file is being served to anyone who asks. Remove it from the web root and rotate any password or key it contained.

6. What else answers on the internet

Your web server should normally answer on ports 80 and 443 only. Remote desktop (3389), databases (3306, 5432, 27017, 6379) and admin panels on other ports should not be reachable from outside. Ask whoever runs the server to confirm the firewall rules, or scan your own address from outside your network.

7. Has it been flagged or hacked?

Look your domain up in Google Safe Browsing. Search Google for site:yourdomain.com and look for pages you did not create, such as pharmacy or casino spam. Both are common signs of a compromised site.

Check it now: a free external scan runs the outside checks on this page against your domain and grades the result.

Questions people ask

Is HTTPS enough to call a website secure?

No. HTTPS protects the connection. It says nothing about outdated software, exposed files, weak admin logins or missing headers, which are how most small sites get broken into.

How often should I check my website?

After every change to hosting, plugins or DNS, and on a schedule. Certificates expire and new vulnerabilities in the software you run are published every week, so a site that was fine last month may not be today.

Can I scan someone else's website?

Only with permission. The checks here are passive or light, but running them against a site you do not own can still break the owner's terms or local law.

How do I know if my website has been hacked?

Common signs are a Safe Browsing warning, pages in Google you did not create, new admin users, unexpected redirects for mobile visitors, and your hosting provider reporting spam or high load.