KICKHOST SECURITY
Responsible Disclosure Policy
How security researchers can report vulnerabilities to KickHost, and what to expect from us.
01Overview and commitment
KickHost welcomes reports from security researchers, customers and members of the public about vulnerabilities in our websites, client area, network and services. Good-faith research makes the platform safer for everyone, and we want to make reporting straightforward.
This policy explains what is in scope, how to report, what we ask of you and what you can expect from us. It is not a bug-bounty programme. Where we offer a reward or credit for a specific report, we will confirm the terms in writing at the time.
If you follow this policy in good faith, we will not pursue or support legal action against you for the research that led to your report. That commitment does not cover activity that goes beyond this policy or that harms another person.
02In scope
We are interested in vulnerabilities that affect KickHost systems or customer data, including:
- The main KickHost website, regional sites and the client area.
- Authentication, session handling, password reset and account-recovery flows.
- The ordering, checkout and domain search functions on our own systems.
- Server-side request forgery, injection, access-control flaws and sensitive data exposure in services we operate.
- Subdomain takeover, exposed internal services, misconfigured storage and permissive CORS on our infrastructure.
- Vulnerabilities in our own code or configuration that could affect other customers.
A useful report shows a realistic attack path and the impact on a real asset. A proof of concept that demonstrates the issue without accessing data you do not own is the best form of evidence.
03Out of scope
The following are generally out of scope and may be closed without action:
- Volumetric or denial-of-service testing, and any testing that degrades our service or another customer’s service.
- Social engineering of staff, customers or suppliers, including phishing and pretexting.
- Physical attacks or access to premises, hardware or documents.
- Reports that rely on out-of-date browsers, unsupported extensions, or a device the user has already compromised.
- Missing security headers, cookie flags or SPF/DMARC records without a demonstrated impact.
- Automated scanner output with no working proof of concept or exploit path.
- Self-XSS, clickjacking on pages without a sensitive action, and issues that require the victim to paste code into a console.
- Software or services operated by a third party that we do not control.
- Reports about a customer’s own website, application or configuration.
If you are unsure whether something is in scope, report it and ask. We would rather review a borderline case than have you stay silent.
04How to report
Email abuse@kickhost.com with the subject line “Security report” and include:
- A clear description of the issue and the asset affected (URL, hostname, endpoint or feature).
- Step-by-step reproduction instructions, including any account, role or configuration needed.
- The impact you believe it has, and who could be affected.
- A proof of concept, screenshot, request and response, or short screen recording.
- The date and time you tested, with time zone.
- Your name or handle and how you would like to be credited, if at all.
Do not send malware, credential dumps or large data extracts. A redacted extract or a description is enough. If you need to share sensitive material, tell us in the first email and we will agree a secure route.
Encrypt sensitive reports where you can. Ask us for a public key before sending the details; do not include a private key or password in any message.
05What we ask of you
To keep your research within this policy:
- Test only against accounts and data you own or are explicitly authorised to use.
- Stop as soon as you have enough evidence to demonstrate the issue. Do not pivot, escalate privileges further or exfiltrate data.
- Do not access, modify, delete or retain another person’s data. If you accidentally encounter it, stop and tell us.
- Do not run automated scans that generate significant traffic, and do not test availability or load limits.
- Do not publicly disclose the issue until we have confirmed a fix or agreed a disclosure date.
- Do not extort, demand payment or condition your cooperation on a reward.
- Keep any information about the issue confidential, and delete local copies once the report is closed unless we agree otherwise.
If your testing causes an outage or exposes data, tell us immediately so we can contain it. Acting quickly and honestly is taken into account.
06Our commitment and timelines
We aim to acknowledge a report within two business days and to give an initial assessment within five business days. Complex issues may need longer, and we will tell you if that is the case.
We will investigate, keep you informed of material progress, and tell you when the issue has been fixed. We may ask follow-up questions or request a retest.
We aim to resolve valid issues as quickly as the risk and complexity allow. We prioritise issues that could expose customer data, allow account takeover or affect the availability of the platform.
Where a report is valid, we will explain the outcome in general terms. We may not be able to share every technical detail, for example where disclosure would help an attacker or reveal information about another customer.
Where a report is not accepted, we will explain why, whether it is out of scope, already known, not reproducible or not a security issue.
07Coordinated disclosure
We support coordinated disclosure. We ask for a reasonable period to fix the issue before you publish, normally 90 days from acknowledgement, or sooner if a fix is released and verified.
If a fix takes longer, we will explain why and agree a revised date with you. We will not ask you to delay indefinitely.
If we believe an issue is being exploited in the wild, we may disclose limited information earlier to help customers protect themselves. Where practical, we will tell you first.
Please do not include customer data, credentials or exploit details that could be used against systems that have not yet been patched in any public write-up.
08Recognition
With your permission, we are happy to credit researchers who report valid issues. Tell us the name or handle you would like us to use, and whether you want a link.
We may offer a reward for a particularly serious or high-quality report. A reward is discretionary, confirmed in writing, and does not create an entitlement or a bug-bounty programme.
We will not credit someone who has not followed this policy, who has accessed data without authorisation, or who has disclosed the issue irresponsibly.
09Legal position
This policy does not give permission to access systems, data or accounts you are not authorised to use, and it does not override any law. It sets out how we will respond to good-faith research that follows the rules above.
If a third party brings a complaint about your research, we will take your compliance with this policy into account and may confirm publicly that we considered the activity authorised under this policy. We cannot bind a third party or a regulator.
Nothing in this policy limits our rights where research is malicious, reckless, extortive or causes harm.
10Contact
Security reports and questions about this policy: abuse@kickhost.com. For a data-protection request, use privacy@kickhost.com. For a general support issue, open a ticket from the client area.
See also our Information Security Policy, Abuse Handling Policy and Privacy Policy.
