F7 · https-behaviour
Your site answers over HTTPS and redirects plain HTTP
- What it means
- Visitors who arrive over http:// are moved to an encrypted connection.
- Evidence
GET http://example.com/ → 301 GET https://example.com/ → 200- Fix
- Nothing to do.
HTTPS check
Runs in every scan · 7 checks
Confirm that visitors always reach the secure version of your site, and that browsers remember to keep it that way.
What we check
Part of every Quick Scan, alongside the other checks.
Your homepage loads on a secure connection.
Visitors who type http:// are moved to https://.
Browsers told to always use HTTPS, for long enough to count.
Your secure page loads its scripts, styles and images securely too.
Sent over HTTPS, from a page on HTTPS.
Modern protocol versions, strong ciphers and forward secrecy.
Valid, matches your domain, complete chain, not about to expire.
Why it matters
Logins, forms and pages travel encrypted.
Visitors see the padlock, not a "not secure" label.
HSTS sends browsers straight to https://.
What a finding looks like
F7 · https-behaviour
GET http://example.com/ → 301
GET https://example.com/ → 200F4 · security-headers
Strict-Transport-Security: (header absent)Strict-Transport-Security: max-age=31536000; includeSubDomainsHow to fix it
Your report has the exact fix for your site, ready to forward to whoever looks after it.
Turn on HTTPS at your host. Most hosts include a free certificate that renews itself.
Redirect every http:// address to its https:// twin with a permanent (301) redirect.
Add an HSTS header. Start with a short max-age while you test, then move to a year.
Change any http:// links to scripts, styles and images on your pages to https://.
Strict-Transport-Security: max-age=31536000; includeSubDomains HTTPS can be switched on without a redirect, so both versions keep working. Add a permanent (301) redirect from http:// to https:// at your host, CDN or server and every visitor ends up on the secure version.
HSTS is a header that tells browsers to use HTTPS for your site from then on, even if someone types http://. After the first visit, every return visit goes straight to an encrypted connection. Adding your site to the HSTS preload list covers the very first visit too.
A year (31536000 seconds) is the common recommendation. Start shorter while you confirm every page and subdomain works over HTTPS, then raise it.
A secure page that loads some of its parts over plain http://. Browsers block insecure scripts outright and flag insecure images, so switching those links to https:// keeps the page whole and the padlock clean.
Yes. Every check includes a full encryption (TLS) test: which protocol versions your server offers, how strong its ciphers are, forward secrecy, and your certificate (valid dates, domain match, chain and key strength). Each finding comes with a plain-English fix.
Keep exploring
Also useful: What we check Sample report Pricing For small businesses Let ScanDefend in
One report, a fix for every finding