Quick check vs full check

LetMeCheck has two kinds of check. A quick check looks at your live website from the outside. A full check also reads your code. Start with a quick check, then add a full check when you want to go deeper.

At a glance#

Quick check#

A quick check loads your public pages like a browser would and tests what anyone on the internet can see. It checks things like:

• Whether your site uses HTTPS and a valid certificate
• Whether secret keys are sitting in the code your site sends to the browser
• Whether Google and AI tools can read your content
• How fast the page loads on a phone

It can't see inside your code or your database, so it can only find problems that show on the outside. See What we check for the full list.

Full check#

A full check reads the files in a GitHub repository you connect. It can find problems that never show on your website, like exposed keys, open database rules and risky packages.

Access is read-only and limited to the repositories you choose. See What GitHub access means.

Which should I use?#

• Use a quick check if you want a fast answer, you're not sure where to start, or you want to check someone else's live site against the basics.
• Use a full check before you launch, after you add logins or a database, or when your quick check says there may be more to find.

Next steps#

• Run your first scan
• Connect GitHub