HTTPS everywhere
The page loads over HTTPS, and plain HTTP redirects to it, so nothing visitors send can be read on the way.
Enter your URL. In about 15 seconds we check 11 security basics (HTTPS, security headers, mixed content, cookie flags), plus SEO, Law 25 and speed, then give you a score and a fix list.
Most attacks on small business sites use well-known gaps. A few settings on your server close many of them. The audit checks what your page and its headers show from the outside.
The page loads over HTTPS, and plain HTTP redirects to it, so nothing visitors send can be read on the way.
The HSTS header tells browsers to always use HTTPS for your site, even if someone types or clicks an http:// link.
A CSP limits which scripts can run on your page, which makes injected code much harder to use against your visitors.
Headers that stop your site from being framed by others, block content-type guessing, and control referrer and browser permissions.
Images, scripts and styles on an HTTPS page should also load over HTTPS. Otherwise browsers block them or warn visitors.
Cookies marked Secure, HttpOnly and SameSite, and server headers that don’t reveal software versions to attackers.
49 checks in four areas, in one free scan of your page.
HTTPS, security headers, mixed content and cookie flags. They protect your visitors and the forms they fill in.
Each check passes, warns or fails, and is weighted by impact. Critical Law 25 failures cap the Law 25 score at 49.
Montreal · Quebec City · Canada
Websites, apps, portals, and mobile — one studio, working software.