Skip to main content

Security testing your own environments

You may have your own applications tested, by your own staff or a penetration tester you hire. This page says what they can do without asking us, what needs notice first, and what they must not touch. A test that follows it needs no further permission from us.

Allowed without asking​

  • Your own applications, at the addresses your environments publish: their generated hostnames and the domains you have added to them.
  • Your own access to your environments: your SSH logins, your databases and your storage, using the credentials Hosting gave you.
  • Manual testing and light automated scanning of the above, such as a passive scan or a crawler run at a normal browsing rate.

Testing a production environment can change or delete its data, so prefer a test environment for anything that writes.

Needs notice first​

Tell us before any active or heavy automated scanning, even of your own addresses: active vulnerability scanners, fuzzers, brute-force attempts, or anything sending many requests per second.

The platform shares its network and front door with other clients, and our data-centre provider, Hetzner, publishes no policy on customer security testing (checked 2026-11-10). A scan it notices can be treated as an attack and block addresses for everyone, so we need to know first.

To give notice, email support@haak.co (see Support) at least two working days before the test, with:

  • the company and environments to be tested, and the addresses;
  • the dates and times, and the addresses the test will come from;
  • the tools and kind of testing;
  • a contact during the test who can stop it at once.

We reply to confirm or to ask for a change. Do not start the heavy part of the test until we have replied.

Off limits​

  • Other clients' environments, applications and data, including anything reached by moving from your environment into theirs.
  • The shared platform: the Hosting panel, the API and the OAuth sign-in beyond normal use of your own account, the shared mail, DNS and storage services, and the clusters your environments run on.
  • Denial of service, load or stress testing, at any address.
  • The underlying infrastructure: Hetzner's network and servers, and any address that is not one of your environments' published addresses.
  • Social engineering of our staff, and physical testing.

When your tester finds a platform problem​

A finding in your own application is yours to fix. A finding in the platform — the panel, the API, isolation between companies or environments, or the access we give you — comes to us, through Reporting a security problem. Stop testing that path once it is shown, and do not copy another company's data to prove it.

Send us the report's platform findings when you have them. Your test then counts as evidence for both of us.