HTTPS check: does your website load securely?
HTTPS encrypts everything between a visitor's browser and your server. SiteShield's biggest single check (30 of 100 points): if your homepage doesn't load over https://, the grade is capped at F and most other checks can't run. Free certificates from Let's Encrypt or Cloudflare fix it in under an hour.
What is HTTPS?
HTTPS is HTTP sent inside a TLS-encrypted connection. The browser checks your site's certificate, agrees a key with your server, and from then on nobody on the network path (public Wi-Fi, a compromised router, an ISP) can read or change the page, the form a visitor fills in, or the cookies that keep them logged in.
The padlock is now the baseline: Chrome, Safari and Edge label plain-HTTP pages Not secure, and forms on them trigger warnings.
Why it matters
Without HTTPS, anything visitors type (logins, contact forms, card details) travels in plain text and can be read or changed on public Wi-Fi.
Without HTTPS, every login, enquiry form and payment detail travels as readable text. An attacker on the same network can also inject content into the page, for example a fake payment link. For a business that collects names, emails or phone numbers, encryption in transit is one of the most basic "appropriate technical measures" that data-protection rules expect.
SiteShield maps this check to:
See how these standards fit together in the UAE website security checklist.
How SiteShield grades it
This check, "Site loads over HTTPS", can cost up to 30 points: a fail loses all 30, a warning loses 15. Every scan starts at 100.
| Result | When | Points lost |
|---|---|---|
| Pass | The homepage loads over https:// (status below 500) and the final URL after redirects is still https://. | 0 |
| Fail | The HTTPS request fails (certificate error, timeout, no answer), the server returns a 5xx error, or https:// redirects down to http://. | 30 |
If this check fails, the score is capped at 40 (grade F) and the checks that depend on a working HTTPS page (headers, cookies, mixed content, libraries, security.txt) are shown as Not checked.
How to check it yourself
Open your site with https:// in the address bar and click the padlock to see the certificate. From a terminal:
curl -sSI https://example.com | head -n 1
# HTTP/2 200 -> HTTPS works
# curl: (60) SSL certificate problem -> broken or self-signed certificate
Or run a free SiteShield scan, which checks this and 16 other settings in one go.
How to fix it
The quick version: Install a free TLS certificate (Let's Encrypt, or put the site behind Cloudflare's free plan) and serve every page over https://.
Cloudflare
- Add your domain to Cloudflare (the free plan includes a certificate) and point your nameservers to it.
- Under SSL/TLS → Overview, choose Full (strict). Install a free Cloudflare Origin CA or Let's Encrypt certificate on your server so the Cloudflare-to-server leg is encrypted too.
- Avoid Flexible mode: visitors see a padlock, but traffic from Cloudflare to your server is still plain HTTP.
Nginx
Install Certbot and request a certificate. Certbot edits the server block and sets up automatic renewal.
sudo apt install certbot python3-certbot-nginx
sudo certbot --nginx -d example.com -d www.example.comApache
Same tool, Apache plugin. It creates the :443 virtual host for you.
sudo apt install certbot python3-certbot-apache
sudo certbot --apache -d example.com -d www.example.comWordPress
- Turn on the free SSL certificate in your hosting panel (most hosts offer Let's Encrypt with one click).
- In Settings → General, change both WordPress Address and Site Address to
https://. - Replace old http:// links stored in the database (take a backup first):
wp search-replace 'http://example.com' 'https://example.com' --skip-columns=guid --dry-run
wp search-replace 'http://example.com' 'https://example.com' --skip-columns=guidFAQ
Is a free certificate as secure as a paid one?
Yes. Let's Encrypt and Cloudflare certificates use the same encryption as paid domain-validated certificates. Paid certificates mainly add warranties or organisation details, not stronger encryption.
Why does SiteShield grade my site F when HTTPS fails?
Without a working HTTPS page, visitors' data is unprotected and most other protections (security headers, secure cookies) can't work. The score is capped at 40, which is grade F, until HTTPS is fixed.
My site works over HTTPS in my browser but SiteShield says it failed. Why?
SiteShield fetches the homepage the way a browser does and retries once on a 5xx error. A firewall or bot-protection rule that blocks automated requests, an incomplete certificate chain, or a redirect from https:// back to http:// can all cause a failure. The scan summary shows the reason.
Test your HTTPS now
Run all 17 checks on your website and email domain in about 30 seconds. Free, no signup, passive checks only.
Rather not do it yourself? Fix it for me starts at AED 750 (about USD 205 by PayPal), quote agreed first. Monitoring re-scans weekly for AED 99/month or AED 990/year.