Tracking checker
Is every pixel firing?
A passive scan of about 30 checks: HTTPS and HSTS, security headers, cookie flags, exposed files like .env and .git, admin pages and error pages that say too much. Nothing is changed or uploaded.
Only scan sites you own or have permission to test.
Also free:Tracking checkerROAS calculatorEmail deliverabilitySEO checkerWebsite speed test

Run the security scan on a site you own. It makes about 30 passive checks in some 10 seconds: HTTPS and HSTS, security headers, cookie flags, exposed files like .env and .git, admin pages and error pages that say too much. Nothing is changed or uploaded, and each result comes with the fix.
Automated attacks start by reading what any visitor can see. The scan reads the same things and tells you what to close.
CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy and cross-origin policies.
The redirect from HTTP, HSTS and its max-age, mixed content and insecure form actions.
HttpOnly, Secure and SameSite on every cookie the page sets.
Wildcard and reflected origins, and TRACE, PUT or DELETE on public pages.
.env, .git, backups, config files, phpinfo and other common leak paths.
Server versions, X-Powered-By, stack traces, emails in the HTML and generator tags.
Keys and passwords left in the code, and inline event handlers.
CSRF tokens on forms that post, and password autocomplete.
target="_blank" without noopener, open redirects and meta refresh.
security.txt, robots.txt, admin pages and what your error pages reveal.
The home page over HTTP and HTTPS, a missing page to see your error page, and a list of well-known paths.
Headers, cookies, redirects and the HTML, compared against about 30 checks.
Fails first, then warnings, each with the header or setting to change.

What a passive scan can’t see
Anything behind a login, your apps’ code, payment flows and how your team handles access. A security review covers those.
What it reads
Method
Apps
What you get
Time
| What | Free scan | Security review |
|---|---|---|
| What it reads | Public pages and headers | Admin access, apps, staff accounts and code |
| Method | Passive: read only | Hands-on review with your developer |
| Apps | Not checked | Every app’s access to your store data |
| What you get | Pass, warn or fail per check | A fix list ranked by risk |
| Time | About 10 seconds | [5] working days |
Not sure you need an audit? Bring the free report to a call and we’ll tell you straight.
Book a strategy call
Each tool reads one thing and tells you the fix. Run them in any order.
Not on the list? Ask on a call, or by email.
Yes. It only reads: it requests your pages and a list of well-known paths, the way any visitor could. It never submits forms or tries passwords.
Shopify secures its platform and checkout. Your theme, apps and domain setup still add scripts, cookies and redirects; the scan checks what reaches shoppers.
Not necessarily. A missing header is a gap, not a breach. Fix the fails first; most headers take one setting in your host or CDN.
Only scan sites you own or have permission to test.
Info marks something worth knowing that isn’t a problem on its own, like your platform being visible. It doesn’t lower your score.
Doors closed?

Shoppers buy where they feel safe. Bring this report to a [30]-minute call.
Or write to [hello@domain.com]