Website Security Tools

Everything you need to check and harden a site you run - 40 tools, arranged in the order you would actually work through them. Start with the full audit, then use the focused tools to fix what it finds.

Start here

One passive scan across every check below, scored and prioritised.

Content Security Policy and Trusted Types

The controls that decide what a page is allowed to load and execute.

Framing, cookies and CSRF

Session handling and the boundaries around your pages.

Cross-origin policy

COOP, COEP, CORP and CORS - individually, then as one compatible set.

Transport, redirects and server exposure

How requests reach you, and what your server volunteers about itself.

Third-party code and supply chain

Everything your pages load from somewhere else, and what it costs you.

Certificates and TLS

The certificate layer, its revocation metadata and the configuration behind it.

Certificate Transparency Search

Search public Certificate Transparency logs for every certificate issued for a domain, with issuers, subject alternative names, validity windows and renewal patterns.

Uses an external data source

OCSP Status Checker

Find the OCSP responder a certificate names, check whether the server staples a response, and see the revocation status when it can be determined.

Passive public check

CRL Distribution Point Checker

Read the CRL distribution points a certificate publishes and check they resolve, with a clear statement of what CRL data can and cannot tell you.

Passive public check

TLS Cipher Suite Analyzer

See the TLS version and cipher suite a server negotiates, graded for forward secrecy, authenticated encryption and deprecated primitives.

Passive public check

TLS Configuration Generator

Generate a modern or intermediate TLS configuration for Nginx, Apache, IIS, ASP.NET Core or Node, with the client compatibility each profile costs you stated up front.

Runs locally

Certificate and Private Key Matcher

Confirm a certificate and a private key belong together before you deploy them. Both stay in your browser - the key is never uploaded.

Runs locally

CSR Decoder and Validator

Decode a certificate signing request locally to check the subject, SANs, key type and strength, and verify its self-signature, before a CA rejects it.

Runs locally

DANE TLSA Generator and Validator

Generate or check a TLSA record for DANE, with usage, selector and matching type explained and the DNSSEC requirement stated plainly.

Runs locally

APIs and file uploads

The two surfaces that carry the most risk per line of configuration.

Fixing and reporting

Turning findings into work someone can do, and into something you can send.

The checkers this suite builds on

Long-standing A2Z.Tools checkers that the audit orchestrates rather than replaces.

How to work through a website security review

Start with the Website Security Audit. It runs every passive check in this suite against one address and gives you a scored report with the findings ordered by what actually matters, so you are not guessing where to begin.

Then work down. Transport comes first, because a site served over a downgraded or mixed connection makes every other control unreliable. Headers and Content Security Policy come next, since they are usually the largest improvement for the least deployment risk. Cookies and cross-origin policy follow, then third-party scripts - which is where most sites carry risk they never chose. The certificate layer and API surfaces come last, not because they matter less, but because they change least often.

Roll policies out in report-only mode first

Content Security Policy and Trusted Types can both break a working site instantly if you enforce a policy you have not measured. Both support a report-only mode that tells you what would have been blocked without blocking it. Use CSP Generator to build the policy, deploy it as Content-Security-Policy-Report-Only, collect real traffic, then feed the reports into CSP Report Analyzer before you enforce anything. The same applies to cross-origin isolation, which can break embeds and third-party widgets the moment it is turned on.

What a passive audit cannot see

These tools read what a site shows an ordinary visitor. They do not authenticate, submit forms, guess paths or attempt exploitation, which means they cannot find broken access control, injection flaws, business logic problems, or anything that only appears after login. A clean report here means the public configuration looked right - it is a floor, not a ceiling. Application-level assurance needs code review and authorised testing, which is work for people, not a scanner.

Only test sites you are responsible for

Every check here is passive and read-only, and none of it is more intrusive than visiting the site in a browser. Even so, these tools exist for reviewing your own systems and those you have been asked to review. Comparison features are built around that assumption deliberately: they compare sites you choose, and they do not publish rankings or league tables of anyone else's.

Rate this tool

Was this tool useful? Your feedback helps us improve it.

No ratings yet — be the first to rate this tool.
Your rating (required)
0 / 2000

Please do not include passwords, payment details or other sensitive information.

Your feedback is sent privately to the A2Z.Tools team and will not be posted publicly.