Check your website security for free
Paste a URL and ScanAnt reads what your site already shows every visitor: the page, its scripts and its response headers. In about half a minute you get a graded report with a plain-language fix for each problem. Deeper checks of files, certificates and servers unlock after you prove the site is yours.
Free, no signup. We only read what your site already shows every visitor.
What we check
Each item is tagged with the scan that reports it. The quick scan is free and needs no signup. The others run only on sites you have proved you own.
HTTPS and redirects
Quick scanWhether the site is served over HTTPS, whether http:// redirects to https://, and whether an HTTPS page still loads scripts or images over plain http.
Security headers
Quick scanHSTS, Content-Security-Policy, protection against embedding in other sites, X-Content-Type-Options and Referrer-Policy.
Login cookie flags
Quick scanWhether a session cookie is missing Secure, HttpOnly or SameSite, which makes it easier to steal or misuse.
Keys in public code and source maps
Quick scanPayment, AI, cloud, e-mail and database keys inside the JavaScript your site ships, plus source maps that let anyone download your original source. Keys are shown masked, never in full.
Outdated libraries and unchecked scripts
Quick scanFront-end libraries with known vulnerabilities and third-party scripts loaded without an integrity check.
Exposed files and admin pages
Verified scanPublic .env files, .git folders, database backups, debug pages, folder listings and admin pages with no login screen.
Certificate and e-mail DNS
Verified scanCertificate expiry, old TLS 1.0 and 1.1, and missing SPF or DMARC records that let others spoof your domain.
Open ports and subdomains
Deep scanDatabase and remote-access ports reachable from the internet, forgotten test subdomains and subdomains that could be taken over.
- Quick scan: No signup. Reads only what every visitor receives.
- Verified scan: After you prove you own the site. Read-only.
- Deep scan: After you prove ownership and tick the deep option.
No scan can promise to find every problem. A clean result means no known problems were found on what the scan could see.
Common mistakes
A secret key shipped to the browser
Anything in front-end JavaScript is public. A leaked payment or AI key lets strangers spend your money.
No redirect from http:// to https://
Visitors on the plain-http address can be intercepted or served a modified page.
A .env file or .git folder left in the web root
One download gives away database passwords and the full source history.
Debug mode left on in production
Stack traces and debug pages show paths, queries and settings that help an attacker plan.
Session cookies without protective flags
A cookie readable by scripts or sent over http turns a small bug into an account takeover.
How to fix it
Move every secret to server-side environment variables and rotate any key that has ever appeared in public code.
Force HTTPS with a permanent redirect and send a Strict-Transport-Security header.
Add a Content-Security-Policy, X-Content-Type-Options: nosniff and a clickjacking rule (frame-ancestors), then retest.
Delete backups, .env and .git from the public folder and turn off debug mode and folder listings.
Set Secure, HttpOnly and SameSite on session cookies.
Questions
Is it safe to run this on my live site?
Yes. The first scan only does what a visitor's browser does: it loads the page and the scripts it references, within a small request budget. It never logs in, submits forms or changes data.
Do I need an account?
Not for the quick scan. You only sign up and prove ownership if you want the full or deep scan, which send more requests to your server.
What can this check not tell me?
It cannot see anything behind a login, your server configuration from the inside or your business logic. A clean result means no known problems on the public surface, not that the site is secure.
Can I check a site I do not own?
The quick scan reads only public pages, but you should test only sites you own or have permission to test. Active checks are blocked until ownership is verified.
How is the grade calculated?
Each finding removes points according to severity, more if it exposes sensitive data. A single critical finding caps the grade at C. Treat the grade of a quick scan as a ceiling, not a guarantee.
Related checks
A free website vulnerability scanner that explains every finding
Known CVEs, injection probes, open redirects and exposed files, in plain language.
Open →Security headers check: CSP, HSTS and friends
Is your CSP, HSTS, framing and referrer policy set up properly?
Open →Find API keys and secrets exposed on your website
Leaked Stripe, OpenAI, AWS and database keys in public JavaScript.
Open →
Run the scan now
Free for any public site, no signup. Need the verified, deep or code scan? Choose the level on the scan page.
Choose a scan level →