Exact affected resource
Identify the domain, IP address or complete URL so the correct service layer can be checked.
Submit a specific, evidence-based report concerning phishing, malware, spam, unauthorized access, network attacks, fraud, child safety or other prohibited use connected to an InvisibleHosts service.

Include the domain, IP address or exact URL, the observed activity, timestamps with timezone and supporting headers or logs. Do not send passwords, private keys or illegal content.
Identify the domain, IP address or complete URL so the correct service layer can be checked.
Include what happened, when it occurred, the timezone and relevant headers, logs or source information.
Reports are validated against the affected service, available evidence, applicable requirements and operational risk.
Use this channel for suspected phishing, impersonation, malware distribution, spam, credential theft, unauthorized access, scanning, denial-of-service activity, fraud, child-safety concerns or another serious violation involving an InvisibleHosts-hosted service or managed domain.
Do not submit passwords, private keys, wallet recovery phrases, unrelated personal data or executable malware. Do not attach or reproduce illegal imagery. Describe the material, provide the exact location and preserve evidence through the appropriate competent authority or recognized reporting channel.
A report is checked for a clear affected resource, sufficient evidence and a connection to a service within our control. We may request clarification, notify the customer where permitted, preserve relevant operational records, restrict a specific service or take another proportionate action required by policy, contract or applicable law.
Submitting a report does not guarantee a particular outcome or response time. Incomplete, automated, duplicate, abusive or unrelated submissions may be closed without action.
This form is not an emergency service. If someone faces immediate danger, contact the appropriate local emergency or law-enforcement authority first. Copyright notices should follow the separate DMCA and legal-notice process. Ownership or trademark disputes concerning a domain may require the sponsoring registrar, registry, UDRP, URS or a competent court rather than the hosting provider.
Provide only information necessary to investigate the incident. Report details may be shared with the affected customer, infrastructure operator, registrar, registry, security partner or competent authority where reasonably necessary and legally permitted.
Reports must be accurate and made in good faith. False statements, harassment, fabricated evidence or attempts to misuse the reporting process may result in rejection and preservation of relevant records.
The affected resource and focused evidence matter more than broad allegations or repeated automated notices.
Provide the exact domain, IP address or URL, what happened, timestamps with timezone, relevant source information and focused headers or logs that support the report.
Use the DMCA and legal-notice page for copyright claims. This form is intended for security, network, fraud, spam, child-safety and other prohibited-use reports.
The substance of a report may be shared where necessary for investigation or response, subject to legal, safety, confidentiality and operational constraints.
No. We can only act on services within our control. Domains, registrars, registries, DNS providers, CDNs and hosting servers are separate layers.
No. Contact the appropriate local emergency or law-enforcement authority when there is immediate danger, then submit the technical details here if an InvisibleHosts service is involved.
Use the structured form so the operations team can identify the correct service and review the incident.