Free passive scan

Website Security Check

Get an A to F grade for your website’s basic security: HTTPS, SSL, security headers, cookies, visible software versions and outdated WordPress, with a fix for each issue.

Free, no sign-up. We connect to the site the way a browser does and do not keep the addresses you check.

Result look wrong, or not sure what to change? A GoProIT technician can check it with you over a secure remote session. $59 per fix, Monday to Friday 8am to 8pm Eastern.

Book a technician(844) 734-1288

What this check looks at

CheckWhy it matters
HTTPS and redirectVisitors and search engines expect every page over HTTPS. Plain HTTP shows “Not secure”.
SSL certificateAn expired or mismatched certificate blocks visitors with a full-page warning.
HSTSForces browsers to always use HTTPS, preventing downgrade attacks on public Wi-Fi.
Content-Security-PolicyLimits where scripts can load from, reducing the damage of injected code.
Clickjacking protectionStops other sites loading yours in a hidden frame to trick clicks.
X-Content-Type-Options, Referrer-PolicySmall headers that close off known browser tricks and data leaks.
Software versionsShowing exact server, PHP or WordPress versions helps attackers find known holes.
CookiesSession cookies without Secure and HttpOnly flags are easier to steal.

How to add security headers

Most fixes are a few lines of configuration. On Apache or LiteSpeed hosting (most cPanel and hPanel plans), add them to the .htaccess file in your site’s root folder:

Header always set Strict-Transport-Security "max-age=31536000"
Header always set X-Frame-Options "SAMEORIGIN"
Header always set X-Content-Type-Options "nosniff"
Header always set Referrer-Policy "strict-origin-when-cross-origin"

On WordPress, many security plugins can add these for you. Test your site after each change, especially for Content-Security-Policy, which can block scripts your site needs if it is too strict.

What this check doesn’t do

It is a passive scan: we load your homepage once, like a normal visitor, and read what the server sends back. It doesn’t try to break in, test login pages or scan plugins for vulnerabilities. A good grade means your basics are in place, not that the site can’t be hacked. Keep WordPress, plugins and themes updated, use strong passwords with multi-factor authentication for admins, and keep backups.

Which fixes to do first

A long list of findings can look alarming. Most small business sites can move up two or three grades in an afternoon if you work in this order.

PriorityFixEffort
1Renew or fix the SSL certificate, and redirect every HTTP address to HTTPSMinutes, often a single switch at your host
2Update WordPress core, plugins and themes, and delete plugins you don’t useUnder an hour, plus a backup first
3Add HSTS, X-Content-Type-Options, X-Frame-Options and Referrer-PolicyA few lines of configuration
4Set Secure and HttpOnly on cookiesUsually a setting in your platform or plugin
5Hide software version numbersLow risk, fix when convenient
6Content-Security-PolicyTakes testing; do it last

For Content-Security-Policy, start with the Content-Security-Policy-Report-Only header. The browser then reports what a policy would block, in the developer console, without breaking anything. Once the reports are clean, switch it to the real header.

Adding headers on other platforms

The .htaccess lines above cover most shared hosting. Here is where the same settings live elsewhere.

  • Cloudflare: HSTS is under SSL/TLS > Edge Certificates > HTTP Strict Transport Security. Turn on Always Use HTTPS on the same page. Other headers can be added under Rules with a response header transform rule.
  • Nginx: add lines such as add_header X-Content-Type-Options "nosniff" always; inside the server block, then test with nginx -t and reload.
  • Squarespace, Wix and Shopify: the platform manages the certificate and most headers, and usually doesn’t let you add your own. Make sure SSL is turned on and that HTTPS is forced in the site settings. A lower grade on headers you can’t change is normal for these builders.
  • WordPress: a security or headers plugin can add them, but don’t stack two plugins that do the same job, or you’ll get duplicate headers.

Be careful with the HSTS includeSubDomains and preload options. They force HTTPS on every subdomain, so add them only once every subdomain (mail, shop, portal and so on) has a working certificate.

Is a website safe to visit? Checking someone else’s site

This tool grades how a site is configured. It’s most useful for your own website. If you want to know whether a site you’ve been sent is legit, other checks matter more:

  • Check the link itself with our phishing link checker, which compares it with known phishing domains without opening it.
  • Look at the domain age. A shop or bank login page on a domain registered last week is a strong warning sign. The WHOIS lookup shows the registration date.
  • Don’t trust the padlock alone. HTTPS only means the connection is encrypted. Scam sites get free certificates just as easily as real ones.
  • Look for real contact details: a street address, a phone number that answers and a business name you can find elsewhere.
  • Take browser warnings seriously. A red full-page warning about a deceptive or dangerous site means the browser’s blocklist has flagged it.

Signs your own website has malware

A passive scan reads the homepage. Hacked sites often look fine on the homepage and hide the damage elsewhere. Watch for these:

  • Visitors from Google on a phone get redirected to a spam or scam site, while you see the normal site when you type the address yourself.
  • A Google search for site:yourdomain.com shows pages you never made, often about pharmacy, casino or loans in other languages.
  • Google Search Console shows a warning under Security & Manual Actions > Security issues.
  • New administrator accounts, plugins or files in WordPress that nobody on your team added.
  • Your host suspends the account or warns about high resource use or outgoing spam.

If you find it

  1. Change the passwords for the hosting account, every WordPress admin, FTP or SFTP and the database, and turn on multi-factor authentication.
  2. Remove any admin users you don’t recognize.
  3. Restore a clean backup from before the infection, or ask your host to scan and clean the files.
  4. Update everything, and remove plugins and themes you don’t use.
  5. If Google flagged the site, request a review in Search Console once it’s clean.

If you’d rather not do the cleanup yourself, a technician can work through it with you over a remote session.

Frequently asked questions

Is it safe and legal to scan a website with this tool?

Yes. It only requests the public homepage and a security.txt file, exactly as a browser would. It doesn’t probe for vulnerabilities, so it’s fine to check any public website.

Why did my site get a low grade when it has SSL?

SSL is only one part. Most small business sites are missing security headers like HSTS and Content-Security-Policy, which are quick to add and make up a large share of the grade.

My site shows a PHP or server version. How do I hide it?

For PHP, set expose_php = Off in your PHP settings (many hosts have this in the PHP options page). For the server header, ask your host; on many shared plans it can’t be changed and is a low risk.

How often should I check my website security?

After every major change, such as a new theme, plugin or host, and at least every quarter. Expiring SSL and outdated WordPress are the issues that creep in over time.

Does an SSL certificate mean a website is safe?

No. A certificate proves the connection is encrypted and that the site controls its domain name. It says nothing about who runs the site or whether it’s honest, and most phishing sites now use HTTPS.

Can this tool tell me if a website is a scam?

Not directly. It checks security configuration, and a scam site can score well. Use the phishing link checker and the domain registration date, and look for contact details you can verify.

Can I get a virus just by visiting a website?

It’s rare with an up-to-date browser and operating system, because most attacks need you to download a file, allow notifications or type in a password. Keeping Windows, macOS and the browser updated closes the holes that drive-by attacks rely on.

What is security.txt?

It’s a small text file at /.well-known/security.txt, defined in RFC 9116, that tells security researchers how to report a problem with your site. It needs at least a Contact: line and an Expires: date.

Related guides

Want your website locked down?We harden WordPress sites, add security headers and set up updates and backups.
Get help from a technician

More free tools

See all 30 free IT tools

Free tools find it. We fix it.

Want a technician to sort it out for you?

One-time remote fix for $59, or unlimited help for your whole team at $49 per user per month. No contract and no setup fee.

WhatsApp us(202) 960-2022 · messages