alec@testnest:~$ Warming up the servers…
Loading…alec@testnest:~$ Warming up the servers…
Loading…Available now// TestNest Pen Testing
A penetration test (pen test) is a controlled, permission-based attack on your own website to find the weaknesses a real attacker would use. Then I explain each one in plain English and show you exactly how to fix it.
// 01
Can someone guess, reset or steal their way into an account?
Can one user see or change another user's data? This is the most common serious flaw in web apps.
Especially for sites built with Supabase, Firebase or AI tools, where one missing rule exposes everything.
Can typed-in text be turned into code that runs on your server or in other visitors' browsers?
Things that should be private but can be reached by anyone who knows where to look.
The browser-level protections that block whole classes of attack.
Flaws in how your app works rather than how it's coded.
The parts of your app that other code talks to.
New ground most security checks miss entirely.
Weak spots around your app rather than in it.
// 02
Each weakness gets a severity rating based on how easy it is to exploit and how much damage it could do, so you know what to fix first.
Exploitable now, with serious impact such as a full data leak or account takeover. Fix today.
Serious, but needs some conditions to line up. Fix this week.
A real weakness with limited impact, or one that's hard to exploit. Plan a fix.
Minor hardening that makes attacks harder.
Good practice and observations. No direct risk.
// 03
Fixed price agreed on our call
A careful, non-intrusive outside-in review: everything that can be checked without logging in or stressing your site.
Includes
Unlocks after a quick chat with me
Fixed price agreed on our call
Hands-on testing of one web app, with and without logging in, covering the OWASP Top 10 and the attack areas above.
Includes
Unlocks after a quick chat with me
Fixed price agreed on our call
The full works across app, API, database, payments and AI features, followed by a retest once you've fixed things.
Includes
Unlocks after a quick chat with me
// 04
One page on where you stand and what to fix first. No jargon.
For each issue: what it is, where it is, proof it's real, the risk, and its severity.
Exact instructions, plus a prompt you can paste into your AI coding tool.
We go through it together, then I check your fixes actually worked.
// 05
We agree what's in scope, what's off limits, and the best time to test.
You confirm in writing that you own the site or are authorised to have it tested. No permission, no testing.
Manual testing backed by trusted tools, ideally on a staging copy. I won't run anything that could take your site down.
You get the report, and we go through every finding together.
Fix things yourself, with AI, or with me in a 1-2-1 session. Then I confirm they're closed.
Testing a website without its owner's permission is illegal in the UK under the Computer Misuse Act 1990, and in most other countries too. I only test sites you own or are authorised to have tested, with written permission and an agreed scope before anything starts. Denial-of-service testing and social engineering are never included unless agreed in writing. Anything I see during testing is kept confidential and deleted once the engagement ends. The free review and the free security scan on this site stay passive: they only make the same requests any visitor's browser could.
// 06
The free review reads your public pages, like any visitor would, and scores 30+ checks. A pen test actively probes your site as an attacker would: logging in, trying other users' data, tampering with requests, and testing your database rules. It finds problems the free review can't see.
It's designed not to. I avoid anything destructive and never run denial-of-service attacks. Where possible, testing happens on a staging copy rather than your live site.
Yes. AI-built apps often work perfectly but ship with missing database rules or exposed keys. Those are some of the first things I check.
The Deep Dive covers the API and backend your mobile app talks to, which is where most mobile app data leaks happen.
Every pen test needs an agreed scope and your written permission before anything starts, and the price depends on what's being tested. So the paid tests unlock after a short chat with me. The free automated scan is open to everyone right now.
It depends on the size of your site and which option you pick. We agree a fixed price on the call, before any testing starts. There's no obligation to go ahead.