No HTTPS

What it means

This site was reached over plain HTTP rather than HTTPS — there is no TLS/SSL certificate in use at all, so no part of the connection is encrypted or authenticated.

Why it matters

Without HTTPS, any data exchanged between a visitor and the site — form submissions, cookies, session tokens — travels in plain text and can be read or altered by anything sitting on the network path. Most browsers also flag plain-HTTP pages as "Not Secure" directly in the address bar, and search engines treat HTTPS as a baseline ranking signal.

What Nivaronix checks

Nivaronix checks the scheme used to reach the site. If it is not `https`, this finding is raised immediately, before any certificate itself is inspected. This is a transport-security check, not a scan for vulnerabilities in the site's code.

Example evidence

Illustrative example, not a live scan result. Run the checker below to see your own domain's actual status.

Illustrative example only — not a live scan result.

URL: http://example.com
Scheme: http
Status: NO HTTPS — connection is unencrypted

How to fix it

• Enable HTTPS on your web server by obtaining and installing an SSL/TLS certificate.
• Let's Encrypt (free, ACME-automatable) covers most cases; a CDN or load balancer with managed TLS (Cloudflare, AWS ACM, etc.) can also issue and renew the certificate for you.
• Configure the web server to redirect all HTTP requests to HTTPS (a 301 redirect) so plain-HTTP URLs still resolve securely.
• Once HTTPS is confirmed working, add an HSTS header so browsers stop offering the plain-HTTP option to returning visitors.

How to verify the fix

Re-run the SSL/TLS checker against the domain, or load the site with `https://` in front of it directly. The connection should succeed and the browser should show a padlock with no warning.