Your exposed surface
Visible assets, web configuration and entry points. Understand what an outsider can see before going deeper.
PUBLIC-FACING APPLICATIONSFocused penetration testing for growing businesses. Real evidence, clear priorities, and fixes your developers can act on.
A login screen is only the beginning. We look at how your application actually works, who can do what, and where those boundaries break.
Visible assets, web configuration and entry points. Understand what an outsider can see before going deeper.
PUBLIC-FACING APPLICATIONSAuthentication, sessions and access control. Test whether a customer, staff member or stranger can cross a boundary.
AUTHENTICATED WEB & API TESTINGRoles, workflows and business rules. Follow the paths that matter to your product, then validate the actual impact.
BUSINESS LOGIC & MANUAL VALIDATIONAutomation for coverage. Human judgement for conclusions.
Tools help with repeatable checks. Findings earn their place in the report through evidence, context and manual validation.
See the quality of our work before committing to a full engagement. Start with a focused external review of one approved domain.
A starting point, not a full penetration test. Authenticated areas and deeper business logic are covered in a separately scoped engagement.
What you'll receive in your initial review.
The approved domain, checks and limits.
Supported observations, with useful context.
Practical fixes and areas worth testing further.
Understand the risk. Reproduce the issue. Know what to fix. Get a clear record of what was tested and what wasn't.
6-page PDF · Fictional LeadRaptor example.
These are not findings from a live assessment.
In this fictional scenario, a signed-in client can retrieve a lead belonging to another client.
GET /api/example/leads/demo-lead-b-001
Authorization: <client-A-session>{ "client_id": "demo-client-B" }Access denied. No other client's data returned.
If this issue existed, one customer could see another customer's contact information and sales context.
One unauthorized read of a synthetic lead, using a known record identifier and a standard client session.
Bulk extraction, record changes and administrator access are not demonstrated. The example does not establish a real vulnerability.
Authorize each requested record on the server using the authenticated user's permitted client accounts.
Client A cannot access client B's data. Both retain access to their own records.
You know what's included, what it costs, and who is doing the work before the assessment begins.
Share your domain and priorities. We agree the limits of your free external review.
Free initial reviewA technical call defines the application, roles, test window and deliverables. You receive a fixed quote.
50% deposit to beginResearcher-led testing, supported by automation. Confirmed urgent findings are raised during the engagement.
Written authorization firstGet your report, a walkthrough and one retest within an agreed scope and window.
50% on completionFounder · Independent security researcher
DIRECT ACCESS. CLEAR ACCOUNTABILITY.A useful report connects evidence to business impact, and gives your team a practical next step.
My background is independent security research through HackerOne, including confirmed vulnerability reports. PenTestRaptor brings that experience to focused web application and API assessments.
I handle the technical scoping, testing and reporting, so the person explaining a finding understands how it was discovered.
Research experience belongs to the founder. Participation in a bug bounty program does not imply company endorsement.Understand what happened, what it means for your business, and what to check next.
Explore the blogEmail is often an approval system, a customer queue and a filing cabinet at once. The November outage is a practical reason to test what happens when it disappears.
Maersk’s November disclosure is a useful reminder that acquired applications and retired-looking portals still need an owner. Here is how a smaller business can find and reduce that exposure.
The Fireworks AI disclosures show why datasets, API keys and development access belong in the same security conversation. Here is how to make that conversation practical.
A bounded external review of one approved domain: visible exposure, basic web configuration and evidence-backed observations. You'll receive practical next steps. It doesn't include authenticated testing, deep exploitation or a full assessment of business logic. We agree the scope before starting.
We provide a fixed quote after scoping your application, API, roles and priorities. The agreed fee is split into a 50% deposit and 50% on completion. The quote specifies deliverables and the included retest scope and window.
Yes. Automation supports reconnaissance and repeatable checks, while the researcher investigates context, validates findings and writes the final conclusions. We agree any handling of confidential data before testing; credentials and sensitive data should never be submitted through this enquiry form.
Testing carries some operational risk. We agree the environment, window, limits and stop conditions with you. Test accounts and synthetic records are preferred. Destructive testing and denial-of-service testing are excluded from the standard scope.
It can provide evidence of the work completed, the findings and remediation status. Share your customer's requirements before scoping so we can check the fit. A penetration test alone is not a compliance certification, and some buyers require specific provider credentials.
Start with your domain. We'll agree what to review.