Acceptable use policy
The behaviors Honk does not permit and the evidence-led way suspected violations are handled.
Pre-launch notice
Paid domain registration is not yet available. This policy describes the current website and the operating rules Honk is preparing for launch. Commercial terms, legal-entity details, launch markets, and any jurisdiction-specific notices will be finalized before checkout opens.
Plain-language note
These pages are operational drafts, not a substitute for advice from a qualified lawyer. Nothing here limits rights that cannot lawfully be limited.
The basic rule
Do not use a Honk account, domain, DNS configuration, or related service to cause harm, break applicable law, violate another person's rights, or interfere with networks and services. You are also responsible for taking reasonable steps when a domain under your control is compromised.
DNS abuse
- Phishing, credential theft, or deceptive impersonation.
- Malware distribution, botnet command and control, or pharming.
- Spam when it is used to deliver or enable another DNS-abuse category.
- Knowingly providing domain or DNS infrastructure to enable the activities above.
Other prohibited conduct
- Child sexual exploitation or abuse material, grooming, trafficking, or credible threats to child safety.
- Fraud, unauthorized access, extortion, non-consensual intimate imagery, or other unlawful activity.
- Material infringement of intellectual-property rights after an appropriate legal or dispute process.
- Evasion of sanctions, court orders, provider restrictions, or previously imposed safety measures.
- Interference with the service, abusive automation, vulnerability exploitation, or access-control bypass without authorization.
Compromised domains
A customer may be a victim rather than the source of malicious activity. Where safe and proportionate, Honk will distinguish compromise from intentional abuse, seek remediation, and avoid unnecessary disruption. Customers must act promptly to secure affected systems and stop harm.
Investigation and response
Honk assesses available evidence, the domain's role, severity, urgency, recurrence, and the measures within Honk's authority. Possible outcomes include requesting more information, referring the matter, seeking remediation, restricting account functions, applying a hold, or escalating to an upstream provider or competent authority.
A report does not automatically prove a violation, and repeated reports do not create an automatic takedown. Emergency risks may require quicker temporary measures while review continues.
Notice and review
Where lawful and safe, affected customers will receive notice of a restriction, the general reason, and a route to provide context or request review. We may delay or limit notice to protect an investigation, reporter, victim, or legal process.