Legal & Abuse Guidelines

1. Email reporting only

We do not accept abuse reports, confidential security reports or law-enforcement requests through the website contact form. That form is reserved for sales enquiries. Use the dedicated email channel below.

• Ordinary technical abuse: abuse@3nt.com. Reports and the sender’s email address are automatically forwarded to the customer responsible for the reported resource. Do not use this address if your identity, evidence or investigation must remain confidential.
• Confidential security information: security@3nt.com. Use this address for sensitive reports, vulnerability information or a request to protect the reporter’s identity. Messages are reviewed internally and are not automatically forwarded to a customer. Explain any confidentiality concern; any later disclosure is assessed for necessity and lawfulness.
• Legal process and law-enforcement requests: legal@3nt.com. Orders, preservation requests, emergency disclosure requests and other authority correspondence must use this channel. Read the Law Enforcement Guidelines before sending a request.

2. What to include in an abuse report

A precise report helps us identify the correct resource and assess what happened. Use a subject such as “ABUSE | IP address or domain | incident date”.

• The affected IP address and port, domain or exact URL, as relevant. A domain alone may not identify the service involved.
• The date and time of the activity, including the time zone. UTC is preferred. For repeated activity, give the start and end of the observed period.
• A concise account of the behaviour and why you believe it is abusive or unlawful.
• Relevant plain-text logs, headers or other safe evidence. Preserve the original evidence and explain any redaction.
• Your contact details, your relationship to the matter and any existing case reference. Where you cannot identify yourself, provide enough technical detail for the report to be assessed.

An IP address may be reassigned. A current lookup is not a substitute for the address and timestamp associated with the reported activity. Reports about a whole network or customer require evidence explaining that scope.

3. Handle evidence with care

Do not email passwords, private keys, unnecessary identity documents, live malware or unlawful imagery. Provide a safe textual indicator, a hash or the location of the material instead. Describe sensitive evidence in your initial message and ask security@3nt.com or legal@3nt.com, as appropriate, to agree a secure transfer method.
Do not publish vulnerability details or confidential investigation material in a sales enquiry. If your report contains information that must not reach the customer, keep it out of abuse@3nt.com and explain the restriction in your message to the appropriate confidential channel.

4. How reports are assessed

We review the connection to 3NT resources, the evidence, the seriousness of the activity and any ongoing risk. Where appropriate, we seek clarification or contact the responsible customer for investigation and remediation. A complaint is an allegation to assess, not automatic proof of a breach.
Proportionate action may include a warning, a remediation requirement, a restriction of the affected resource or suspension under the service terms. Urgent protective action may be taken without prior notice where necessary to address serious harm or comply with law. We consider the actual service supplied: connectivity to a customer-operated server does not give us routine editorial control over that customer’s content.
For a follow-up, reply to the existing email thread with the case reference and new evidence or the point that remains unresolved. Do not send repeated copies to unrelated addresses. We may confirm an outcome without disclosing another person’s account details or confidential security measures.

5. Intellectual property and content complaints

Identify the specific work or right, the material’s exact location, the relevant jurisdiction and your authority to act for the rights holder. Include contact details, supporting registrations where applicable and a clear explanation of the alleged infringement. Supply any declarations or formalities required by the applicable legal procedure.
We assess the complaint under the law and the service involved. A procedure that applies in one jurisdiction is not assumed to apply to every resource. Where a response, counter-notice or challenge is available, it is handled under the relevant process. A request for customer identity or records belongs at legal@3nt.com and requires a separate lawful basis.

6. Confidential security reports

Send vulnerability reports and sensitive threat information to security@3nt.com. Identify the affected system, explain the issue and provide safe, reproducible steps where appropriate. State whether there is active exploitation and how we can reach you securely.
Limit testing to activity you are authorised to perform. Do not access or alter another person’s data, disrupt services or continue beyond what is necessary to demonstrate the issue. Sending a report does not grant permission for testing, waive another party’s rights or create a payment commitment.

7. Authorities, emergencies and disclosure

Authorities should follow the Law Enforcement Guidelines, which explain verification, legal process, preservation, emergencies, international requests and secure production. Do not send confidential process to abuse@3nt.com: its automatic forwarding can disclose the report and sender to a customer.
If a person faces immediate danger, contact the relevant emergency services. For an authority request concerning an imminent risk of death or serious physical injury, use legal@3nt.com with “EMERGENCY” at the start of the subject and an immediately reachable official contact. Our email channels do not replace emergency services.

8. Review and information handling

A customer seeking review of an enforcement decision should follow the notice received or contact legal@3nt.com, quoting the case reference and explaining the facts in dispute. We consider relevant evidence and correct errors where identified. A review request does not automatically restore a restricted resource.
Report information is used to assess and address the concern, meet applicable obligations and maintain relevant case records. Access, onward disclosure and retention are assessed under the Privacy Policy and any lawful preservation requirement. Confidential handling does not mean an unconditional promise of anonymity in every legal circumstance.