A penetration test is priced by tester days, not by software. As a broad order of magnitude, typical market ranges put a tightly scoped test of one small web application in the low thousands (USD or EUR), while a multi-role application with APIs, a mobile client and cloud infrastructure moves into the tens of thousands. Treat any quote below that band as a scope question, not a bargain: ask how many days of testing it buys and who performs them.
Why this matters for your website
Most small site owners do not buy a pentest because they want one. They buy one because an enterprise customer sent a security questionnaire, an insurer asked, or an auditor referenced a standard that expects independent testing.
That means the real question is rarely "what is the cheapest pentest". It is "what is the smallest engagement that satisfies the requirement and still finds something useful". Getting scope right is the single biggest lever you control on price.
What actually drives penetration test pricing
Every credible quote is built the same way: estimated tester days, multiplied by a day rate, plus reporting and retest time. Five variables move those days.
Scope: pages, roles and APIs
Testers count attack surface, not marketing pages. A brochure site with a contact form is a fraction of the work of a SaaS app with admin, staff and customer roles, because each role pair has to be tested for privilege escalation and IDOR.
- User roles: every additional role multiplies authorisation test cases.
- API endpoints: a documented OpenAPI spec lowers cost; an undocumented API raises it.
- Integrations: payment flows, SSO and webhooks each add a test path.
- Environments: testing production under change control costs more than a stable staging clone.
Method: black box, grey box or white box
Black box testing starts with no credentials and no documentation. It looks cheaper per day but wastes days on reconnaissance you could have handed over in an email.
Grey box is the usual best value for web applications: you supply test accounts for each role plus basic architecture notes, and the tester spends the budget on exploitation instead of discovery. Ask for grey box unless a contract explicitly demands a blind test.
People, deliverables and region
Seniority is the biggest rate driver. A certified senior tester with application experience costs more per day and usually needs fewer of them.
- Report depth: an executive summary plus reproducible findings takes one to two days of writing.
- Attestation letter: a short signed summary you can hand to customers, often included.
- Retest: verification after you fix issues, sometimes billed separately.
- Region and accreditation: rates vary by market, and schemes such as CREST add assurance and cost.
What you get for the money
A professional engagement is a methodology, not a tool run. Ask which standard the tester follows and expect a named one: the OWASP Web Security Testing Guide for applications, or NIST SP 800-115 for the overall process.
- Manual testing of business logic, authorisation and multi-step flows that scanners cannot reason about.
- Findings with reproduction steps, evidence and a risk rating you can prioritise against.
- An attestation letter for customers and procurement teams.
- A remediation retest confirming the fixes actually hold.
- A debrief call so your developers understand the root cause, not just the symptom.
The hidden costs nobody quotes
The invoice is not the total. Budget for the work around it.
- Scoping time: a day or two of calls, questionnaires and account provisioning before testing starts.
- Environment preparation: a staging clone with realistic data, plus test credentials for each role.
- Remediation: fixing findings is developer time, and it is usually the largest line item.
- Retest window: if the retest is time-boxed, missing it means paying again.
- Cadence: many contracts expect an annual test plus a retest after major changes.
The honest ladder: scan, AI-assisted assessment, human pentest
Not every requirement needs a full engagement. Match the rung to the driver, and read penetration testing vs vulnerability scanning if you are unsure which term your customer actually meant.
- Automated vulnerability scan — Scope: public surface, TLS, headers, DNS and email posture, CMS and plugin versions. Cost driver: number of assets and scan frequency. Best for: brochure sites, WooCommerce stores and continuous baseline monitoring between tests.
- AI-assisted assessment — Scope: everything above plus authenticated crawling and probing for logic and authorisation flaws. Cost driver: application complexity and number of roles. Best for: small SaaS wanting depth without a full engagement.
- Human web application pentest — Scope: one application, defined roles and APIs, manual exploitation. Cost driver: tester days, method, report and retest. Best for: contractual requirements and enterprise questionnaires.
- Red team or full-scope engagement — Scope: multi-vector, objective-based, often including people and physical access. Cost driver: duration and goal difficulty. Best for: mature organisations with an existing security team.
Some standards make the choice for you. If you handle card data, check the current requirements published by the PCI Security Standards Council rather than relying on a vendor's summary.
How to check your own site
Before you pay for tester days, remove the findings a scanner would have caught anyway. You do not want a five-figure report whose top items are a missing Content-Security-Policy header and an outdated plugin.
Scantinel (scantinel.ai) is an automated website security assessment platform that runs OSINT, network, and OWASP Top 10 web vulnerability tests against ownership-verified assets and delivers actionable, business-owner-legible reports.
- Start free with the Security Headers Checker, the SPF & DMARC Checker and the Website Security Check.
- Run the Essential scan for a passive baseline: DNS, TLS, headers, cookie flags, exposed files and known-vulnerable CMS plugins.
- Run the Full scan on verified assets for active OWASP Top 10 testing, port and service fingerprinting with CVE correlation, WordPress deep checks and supply-chain issues such as exposed
.gitor.envfiles. - Use the Premium AI scan when you want an autonomous agent probing business-logic flaws and IDOR chains, with analyst validation and one free retest.
To be clear: a Scantinel scan is not a penetration test and does not replace one where a customer contract or standard requires human testing. It is the recurring baseline before and between engagements, so your paid tester days go to the hard problems. You can see Scantinel's plans to compare scan depth.
Key takeaways
- Pentest cost is tester days multiplied by a day rate; scope controls the days.
- Broad market ranges run from the low thousands for one small application to tens of thousands for multi-role apps with APIs and infrastructure.
- Grey box testing with prepared accounts and documentation buys more depth per euro than a blind test.
- Budget for remediation and retesting, not just the engagement fee.
- Scan continuously, test with humans when a contract or standard requires it.
Frequently asked questions
How much does a web application penetration test cost?
For a single application with a couple of user roles, typical market ranges sit in the low thousands for a short engagement of a few tester days. Adding APIs, more roles, mobile clients or cloud infrastructure pushes credible quotes into five figures. Always ask for the number of testing days and whether the report and retest are included.
Why are penetration tests so expensive?
You are buying skilled human time, not a tool licence. A tester manually chains authorisation and business-logic flaws that automated tools cannot reason about, then spends a further day or two writing findings you can act on. Reporting, quality review and retesting are real work and are priced as such.
How long does a penetration test take?
A small web application test is commonly a few days of testing plus reporting, with the whole process from scoping call to final report taking two to four weeks. Larger scopes run one to three weeks of testing. Book early: good testers are usually scheduled weeks ahead.
Published January 2026. Security guidance changes: verify details against primary sources such as OWASP, the NVD and WPScan before acting.
Comments
No comments yet.