Security testing · Test automation · Websites

Penetration testing and AI-driven test automation for web, API and mobile.

I test your systems the way an attacker would — with written authorisation, rate-limited tooling and hard evidence for every finding. Reports are written so that a non-technical owner and a developer can both act on them the same day. And if what you need is not a test but a website: business, ZZP and uitzendbureau sites are built and live within a few days of the order.

  • OWASP WSTG & MASTG
  • Burp Suite
  • nuclei / ffuf / semgrep
  • Python & Playwright
  • LLM-assisted triage
  • CI/CD integration
  • Payment flows
  • API (REST)
  • Firebase & cloud rules
  • Websites in a few days

Reading package lists... Done

Building dependency tree... Done

Service

Penetration testing

Manual, authorised testing of web applications, REST APIs, admin panels and mobile apps (Android / iOS). Authentication, authorisation (IDOR / BOLA), injection classes, business-logic abuse, file handling, TLS and HTTP hardening, cloud rules and payment flows.

Web · API · mobile · configuration

Read more about penetration testing →
Service

AI-assisted test automation

Repeating what a pentest finds. I turn security checks into automated tests that run on every deploy: API authorisation tests, input-fuzzing suites, dependency and secret scanning gates, and LLM-assisted triage that separates real findings from noise.

Regression suites · CI/CD gates · triage

Read more about test automation →
Service

Code & configuration review

When you can share the source, I read it: authorisation checks, secrets handling, payment and session logic, plus configuration of the servers, headers, DNS and third-party services around it. Findings come with a concrete code-level fix.

PHP · JavaScript / TypeScript · Python · infrastructure

Discuss a review →
Service

Website building

Next to security work, I build websites: a one-pager for a ZZP'er or freelancer, a vacancy site for an uitzendbureau or employment agency, a company site for a small business. Mobile-first, in Dutch, Polish or English, with domain, hosting, HTTPS, forms and a privacy page arranged — live within a few days of the order.

ZZP · uitzendbureau · small business · NL & PL

Read more about websites →

Kali Linux toolkit

Every engagement runs from Kali Linux — the same open-source platform the industry uses. These are the tools doing the work, plus the eight tools Kali added in 2026.

subfinder
amass
dnsx
httpx
nmap
Burp Suite
OWASP ZAP
ffuf
feroxbuster
nuclei
sqlmap
interactsh
semgrep
gitleaks
testssl.sh

New in Kali Linux 2026

Added in the 2026.1 release

AdaptixC2
Atomic-Operator
Fluxion
GEF
MetasploitMCP
SSTImap
WPProbe
XSStrike

You place the order, we do a fifteen-minute intake, and the site is online within a few days. Not a template you have to finish yourself — a site that is finished, published and in your own name.

  • ZZP'ers and freelancers — one page with your services, your rates or a quote button, plus your KvK and BTW details, so you exist properly online.
  • Uitzendbureau and employment agencies — vacancy pages, an application form with CV upload, sections for candidates and for clients, and vacancies you can keep up to date yourself.
  • Small companies in NL and PL — services, opening hours, photos, a map and a contact form that actually lands in your inbox. Dutch, Polish or English, or all three.
  • Everything technical included — domain and DNS, hosting, HTTPS/TLS, security headers, the privacy and cookie notice, Google Search Console, and a handover with written instructions.
  • Hardened by default — the same standard I test other people's systems against: no vulnerable plugin stack to patch, no secrets in the page source, forms that leak nothing.

Contact — e-mail or telephone

Tell me in one message what your business does and what pages you need. You get a fixed price, the day the site goes live, and a straight answer if a website is not what you need.

Order one day, intake the same day, live within a few days — the date depends mainly on when your texts, logo and photos arrive.

Five finished example sites — a builder, a cleaning company, a garage, a restaurant and a job agency. Click through them and judge the level: real pages, real texts and a contact page that works.

Every example switches between Dutch, Polish and English — your site gets your name, your work and your photos.

One of these for your business?

Tell me in one message what you do and which example feels closest. You get a fixed price and the day the site goes live — usually within a few days of the order.

  • Executive summary in plain language — what is at risk, in business terms, for the person who signs off.
  • Technical task list per finding — severity, confidence, exact location, reproduction steps and a concrete fix.
  • Reproducible evidence — request and response pairs, screenshots, file hashes and timestamps, so nothing has to be taken on trust.
  • Severity with rationale — mapped to real impact (data, money, availability), not only to a scanner score.
  • Retest included — after you deploy the fixes I verify them and report what is left open.
  • Customer data handled as evidence — personal data is masked in reports, evidence is stored encrypted and deleted on schedule.

Engagement models

Fixed scope One application or API, agreed assets and window
Project + retest Test, report, fix verification, closing report
Retainer Continuous testing per release, automation upkeep
Automation build Security regression suite handed over to your team

Quotes depend on scope, not on a price list: tell me the assets, the environment and the deadline and you get a fixed price with a delivery date.

  1. Scoping call

    Thirty minutes to understand the system, the data it holds and what matters most to you. I list the assets, agree the window and note what is out of scope.

  2. Written authorisation

    Before the first request I need a signed authorisation that names the assets, the test window, the source IP and the test accounts, plus the person who can stop the test at any moment.

  3. Reconnaissance and testing

    Passive recon first, then active testing with rate limits. Two test accounts wherever authorisation logic is involved, because that is where the real findings usually are.

  4. Reporting

    Critical findings are reported within 24 hours. The full report follows within 10 working days, split into an owner-facing summary and a developer-facing task list.

  5. Fix verification

    After each fix is deployed I retest it and confirm what is closed, what is partially closed and what is still open — with the same evidence standard as the original findings.

Written authorisation comes first, always. I test a system only when its owner has signed a document naming the assets, the window, the source IP and the emergency contact. In the Netherlands, accessing a computer system without permission is a criminal offence (article 138ab of the Dutch Criminal Code), and a security review does not create that permission by itself.

Inside every engagement

  • Signed scope and rules of engagement, with a clear stop procedure
  • Rate limits, defined testing hours and maintenance/blackout moments
  • Your own test accounts — no customer data is read or modified
  • No denial-of-service, no persistence, no artefacts left behind
  • Immediate stop and notification if anything out of scope is found

Outside every engagement

  • Systems you do not own — Stripe, Google, Firebase, chat providers, hosting, app stores — each needs its own permission
  • Third-party production data, including anything found in leaked keys or exposed backups
  • Load and stress testing, social engineering and phishing, unless added by a separate signed addendum
  • Anything that changes or deletes production data

Owners of a live product

You run a marketplace, webshop or booking platform and you need to know what an attacker could actually reach — including the parts your previous developer built and left.

SaaS and API teams

You ship weekly and want authorisation and input-handling checks that run in your pipeline, so the same bug class cannot come back through a different door.

Agencies and developers

You deliver a client project and want an independent test plus a report your client can read, before the launch date and not after it.

For a test: send the assets, the environment and your deadline. For a website: say what your business does and which pages you need. Either way you get a fixed price, a delivery date and an honest answer about what is and is not covered.