Contact · e-mail or telephone

Tell me what needs testing — or what needs building.

One e-mail or one phone call is enough to start. For a test: the assets, the environment and when you need the result. For a website: what your business does and which pages you want — a business site, a ZZP one-pager or an uitzendbureau/agency site. You get a reply within one working day with a fixed price, a delivery date, and an honest note on what is and is not covered.

WhatsApp
Chat on WhatsApp
WhatsApp
Chat on WhatsApp
Location
Etten-Leur, 4871 CL, the Netherlands
Response
Within one working day

Enquiry form

This form sends your message to the server of this site, and from there by e-mail to dawidbalwierz1@gmail.com. Nothing is stored in a database and no third-party form service is used. If sending fails, your own mail client opens with the message ready.

A test or review is answered with a scope and a test window; a website with a fixed price and the day it goes live — usually within a few days of the order.

Used only to answer your enquiry.

What happens next

  1. Reply within one working day

    With a fixed price, a delivery date and any questions I need answered before quoting.

  2. Scoping call

    Thirty minutes to walk through the system, the data it holds and the deadline. We agree what is in scope and what is deliberately left out.

  3. Written authorisation, then start

    You sign the scope and rules of engagement; I confirm the window and the source IP, and testing begins on the agreed date.

Useful to include

  • Asset list: domains, subdomains, API base URLs, mobile builds, admin areas
  • Two test accounts (normal user and administrator), if authorisation testing is wanted
  • Whether a staging environment exists
  • Maintenance windows, launches or peak hours to avoid
  • Any previous report or findings you want verified
  • Whether you can share the source code for a code review as well
  • For a website: trade name, KvK and BTW/VAT numbers, logo and photos, and the domain you already own (if any)

Confidentiality

Initial enquiries can be covered by an NDA if you need one — say so in your first message and I will send a template. Findings, evidence and reports are treated as confidential and are shared only with the people you name. Nothing about your system is published without your written consent.

Reporting a vulnerability in a system that is not mine, or in this website?

If you found a security problem in a system I do not operate, report it to the organisation that does — that is the fastest path to a fix, and coordinated disclosure programmes are usually the right channel.

For anything related to this website or my own infrastructure, write to dawidbalwierz1@gmail.com with the details and I will respond, credit you if you wish, and fix it.