1. Scope and responsibility
This policy applies to all services supplied by or through 1nextnet, including virtual machines, bare metal servers, dedicated servers, cloud instances, storage, backup targets, hosting environments, colocation space, cross-connects, IP addresses, ASN-related services, IP transit, LIR support, managed infrastructure, and any control panel, API, or customer portal used to operate those services.
Customers are responsible for all activity originating from, transiting through, hosted on, or otherwise associated with their services, including activity by employees, contractors, customers, downstream users, resellers, and compromised systems.
If you provide services to third parties using 1nextnet infrastructure, you must maintain enforceable terms with those users and take timely action when abuse is reported.
2. Lawful and responsible use
Services must be used only for lawful purposes and in a way that does not harm 1nextnet, DOGE NETWORK LTD, other customers, upstream providers, network peers, internet users, or the integrity of the wider internet ecosystem.
Prohibited activity includes using the services to facilitate, advertise, store, transmit, or support:
- Fraud, impersonation, phishing, credential theft, payment abuse, or financial scams.
- Malware, ransomware, botnets, command-and-control systems, exploit kits, droppers, or traffic distribution systems used for compromise.
- Unauthorised access, privilege escalation, data exfiltration, or attempts to bypass authentication or rate limits.
- Illegal content, unlawful surveillance, sanctions evasion, export-control violations, or activity prohibited by applicable law.
- Services designed primarily to conceal abuse, evade accountability, or facilitate repeated policy violations.
3. IaaS, cloud, dedicated server, and hosting workloads
IaaS and hosting customers may run legitimate production workloads, development environments, applications, databases, storage systems, VPN gateways, monitoring systems, and business infrastructure, provided those workloads comply with this policy and do not create operational risk.
3.1 Resource integrity
Customers must not intentionally overload shared platforms, storage clusters, hypervisors, network devices, or management systems. Workloads that create sustained abnormal CPU, disk I/O, packet-per-second, session-table, or broadcast pressure may be rate-limited, migrated, suspended, or required to move to an appropriate dedicated service.
3.2 Prohibited infrastructure patterns
The following are not permitted unless expressly approved in writing and operated within agreed limits:
- Open proxies, open recursive DNS resolvers, open SMTP relays, public packet reflectors, and insecure tunnelling endpoints.
- Traffic exchange, scraping, crawling, indexing, or automation that violates third-party terms or creates network complaints.
- Cryptocurrency mining or proof-of-work workloads on shared cloud or hosting plans where not explicitly included in the service description.
- Bulletproof hosting, abuse-resistant hosting, fast-flux hosting, or services marketed around ignoring abuse reports.
4. Network abuse and traffic conduct
Customers must not send, receive, relay, or enable traffic that disrupts networks, degrades service quality, or violates accepted internet operations practice.
Prohibited network activity includes:
- Denial-of-service attacks, amplification, reflection, stress testing against third parties, or participation in attack traffic.
- Unauthorised port scanning, vulnerability scanning, brute force attempts, credential stuffing, or enumeration of third-party systems.
- IP spoofing, source-address forgery, MAC spoofing, ARP abuse, neighbour-discovery abuse, rogue DHCP, rogue router advertisements, or layer-2 disruption.
- Traffic patterns that trigger repeated upstream complaints, blacklisting, reputation damage, or emergency mitigation.
- Attempting to bypass rate limits, ACLs, DDoS mitigation, null routes, firewall policies, or traffic-engineering controls.
Authorised security testing is permitted only when the customer owns or is expressly authorised to test the target systems, keeps testing within lawful boundaries, and stops immediately if the activity creates complaints or operational harm.
5. IP resources, ASN usage, BGP, and routing
Customers using IP addresses, ASN-related services, BGP sessions, route objects, reverse DNS, or LIR-supported resources must maintain accurate information and operate those resources according to registry, routing, and network-operations standards.
5.1 Routing accuracy
- Customers must announce only prefixes they are authorised to originate.
- Route objects, ROAs, IRR entries, RPKI data, LOAs, and registry records must be accurate where applicable.
- Route leaks, hijacks, unauthorised deaggregation, and misleading origin announcements are prohibited.
5.2 IP reputation
Customers are responsible for maintaining the reputation of IP resources assigned to them. Repeated listings on abuse blocklists, spam blocklists, malware feeds, phishing feeds, or reputation systems may require remediation, reassignment, suspension, or termination.
5.3 Reverse DNS and registry data
Reverse DNS, WHOIS, RWHOIS, geolocation, abuse contacts, and related records must not be misleading. 1nextnet may refuse or remove records that facilitate fraud, impersonation, or abuse.
6. Email, messaging, and bulk communications
Email and messaging systems must be operated with proper consent, authentication, suppression handling, and abuse controls. Customers must not send spam, unsolicited bulk email, snowshoe campaigns, phishing messages, or deceptive commercial messages.
Bulk or transactional email systems must use appropriate technical controls, including SPF, DKIM, DMARC where applicable, working abuse and postmaster contacts, bounce handling, unsubscribe mechanisms where required, and suppression lists.
1nextnet may restrict SMTP ports, require justification for email sending, suspend mail-related traffic, or block outbound mail where there is evidence of abuse, compromise, poor reputation, or insufficient controls.
7. Content, intellectual property, and hosted material
Customers must ensure that hosted content, applications, files, databases, media, and user-generated content comply with applicable law and do not infringe third-party rights.
Prohibited content includes:
- Phishing pages, fake login portals, counterfeit brand pages, or deceptive forms.
- Malware, stolen credentials, carding material, exploit payloads, botnet panels, or unauthorised data dumps.
- Content that infringes copyright, trademarks, privacy rights, or confidentiality obligations.
- Content that promotes illegal services, trafficking, exploitation, targeted harassment, or credible threats of harm.
1nextnet does not routinely review customer content, but may act on credible abuse reports, legal notices, court orders, regulator requests, or operational risk indicators.
8. Security obligations
Customers must maintain reasonable technical and organisational controls for systems under their control. At minimum, customers should use secure credentials, update operating systems and applications, restrict administrative access, monitor exposed services, and respond promptly to compromise indicators.
Customers must not disable, bypass, interfere with, or attempt to reverse engineer security, metering, monitoring, isolation, or access-control mechanisms provided by 1nextnet.
Compromised instances, vulnerable applications, exposed databases, leaked keys, or unmanaged control panels may be isolated, filtered, powered down, or suspended if they create security risk or receive repeated abuse reports.
9. IDC, colocation, and physical hosting conduct
Customers using colocation, rack space, power, cross-connects, remote hands, or physical hosting services must comply with datacentre operating rules, safety procedures, access controls, cabling standards, equipment labelling, power limits, and remote-hands processes.
Customers must not install unsafe, uncertified, overloaded, damaged, or unauthorised equipment. Equipment must not exceed allocated power, cooling, rack, port, or bandwidth commitments without prior approval.
Physical access may be denied, delayed, or revoked where required for safety, security, unpaid invoices, access-policy violations, emergency operations, or datacentre-provider requirements.
10. Operational monitoring and traffic management
1nextnet may monitor service metadata, resource usage, network flows, routing state, abuse signals, and platform health for security, billing, capacity planning, troubleshooting, compliance, and abuse mitigation.
1nextnet may apply technical controls including rate limits, ACLs, filtering, blackholing, null routing, port restrictions, traffic shaping, route withdrawal, suspension, or emergency shutdown where necessary to protect infrastructure, customers, upstream providers, peers, or third parties.
11. Enforcement and remediation
1nextnet may investigate suspected violations and determine appropriate action based on severity, recurrence, customer response, legal requirements, upstream-provider requirements, and operational impact.
Possible enforcement actions include warning, request for remediation, temporary filtering, rate limiting, null routing, disabling ports, suspending individual services, withholding new orders, reclaiming IP resources, terminating service, or reporting unlawful activity to appropriate parties.
Where practical, 1nextnet may provide notice and an opportunity to remediate. Immediate action may be taken without prior notice for severe abuse, active attacks, routing incidents, legal risk, compromised systems, DDoS impact, network instability, or threats to physical safety.
12. Abuse reports and evidence
Abuse reports should include enough information for efficient investigation. Useful evidence includes IP addresses, domains, URLs, timestamps with timezone, packet captures, logs, message headers, screenshots, affected accounts, route information, and a concise description of the issue.
Customers must cooperate with abuse investigations and respond within the timeframe requested by 1nextnet. Repeated failure to respond, incomplete remediation, or recurrence after closure may be treated as a material policy violation.
For service and policy questions, contact DOGE NETWORK LTD through the client area or the contact channels provided by 1nextnet.