This English version is provided for convenience; the Turkish version prevails.
This policy defines how dedicated and cloud servers on the dor.net (MGN Teknoloji A.Ş.) infrastructure may and may not be used. Its purpose is to protect the network and other customers, to meet legal obligations and to make the rules known in advance. It forms an integral part of the Terms of service and is binding on all customers, team members and customers' sub-customers.
1. Definitions
- Service
- servers, network, IP addresses and ancillary services provided by dor.net.
- Abuse report
- a report from a third party, a public authority or dor.net's monitoring systems that a service is being used in breach of this policy.
- Customer
- as defined in the Terms of service, including its sub-customers.
2. General principle
The service is used in accordance with Turkish law, the law of the country where the service is used and this policy. Uses that are lawful but harm the network, other customers or dor.net's reputation may also breach this policy; such cases are assessed under the process in section 7. The Customer alone is responsible for the content on its server and the traffic it generates.
3. Prohibited content
Hosting, transmitting or facilitating the following content on servers is prohibited:
- Content constituting the catalogue offences listed in Article 8 of Law No. 5651 (child sexual abuse, obscenity, prostitution, gambling, incitement to drug use, incitement to suicide, offences against Atatürk and others). Child sexual abuse material is subject to zero tolerance; the service is shut down without notice and reported to the authorities.
- Works, software, trademarks and content reproduced or distributed without the rightholder's permission under the Law on Intellectual and Artistic Works No. 5846 and the Industrial Property Law No. 6769 (warez, pirated streams, unlicensed software distribution, unauthorised live-stream relays).
- Phishing pages, fake corporate sites, malware, command-and-control servers, exploit kits.
- Unlawful collection, processing or sale of personal data (KVKK No. 6698; Arts. 135-140 Turkish Penal Code No. 5237).
- Terrorist propaganda, hate speech, incitement to violence, fraud and Ponzi/HYIP schemes, unlicensed financial services, illegal betting.
- Republishing content blocked under Law No. 5651 in order to circumvent the block.
4. Prohibited activities
- Unsolicited bulk messaging (spam): sending bulk e-mail, SMS or instant messages without the recipient's prior consent; sending to purchased lists; forging e-mail headers; providing infrastructure to spammers. Commercial electronic messages must comply with Law No. 6563 (prior consent, opt-out, İYS registration).
- Attacks and unauthorised access: launching or participating in DDoS/DoS attacks, operating botnets, unauthorised network or port scanning, password cracking, accessing or attempting to access systems without authorisation (Arts. 243-245 Turkish Penal Code), IP/ARP spoofing, running open reflectors (DNS/NTP/memcached amplification).
- Resource abuse: on shared cloud infrastructure, sustained excessive disk I/O, network or CPU load that degrades other customers' service. dor.net first notifies the Customer and may limit resources where necessary to remove the impact.
- Cryptocurrency mining:
- On cloud servers mining and similar sustained full-load workloads (proof-of-work mining, mining pool proxies) are prohibited, because they consume shared resources and affect other customers.
- On dedicated servers mining is permitted only with dor.net's prior written approval and provided the server's power/cooling limits and network usage rules are observed. Unapproved mining is suspended under the process in section 7.
- Software that mines on third parties' devices without their consent (cryptojacking) is prohibited in all cases.
- Anonymisation and relaying: running open proxies, open relays, or Tor exit nodes or VPN services serving unlawful purposes. VPNs for your own use and non-exit Tor relays may be run; for exit nodes the Customer bears the 24-hour abuse-response obligation and the record-keeping obligations of Law No. 5651.
- Interference with infrastructure: unauthorised access to the dor.net console, API, network equipment or other customers' systems; use of unallocated IP or MAC addresses; evading monitoring systems.
- False identity: opening accounts in another person's name, using stolen payment instruments, abusing promotions through multiple accounts.
5. E-mail sending rules
- Outbound SMTP (ports 25/587) may be restricted until account verification is completed.
- Servers sending bulk mail must have a correct PTR (reverse DNS) record, SPF, DKIM and DMARC configuration and a working unsubscribe mechanism.
- dor.net may temporarily close ports 25/587 on IP addresses that receive spam reports or appear on blocklists; the ports are reopened once the Customer resolves the issue.
- The Customer is responsible for the reputation of its IP addresses; delisting efforts are carried out by the Customer, with dor.net's assistance where needed.
6. Abuse reports and the 24-hour rule
6.1. dor.net uses abuse@dor.net and the console notification centre for abuse reports. Reports are reviewed; unfounded or malicious reports are disregarded.
6.2. The Customer must respond to an abuse report forwarded to it within 24 hours, take the necessary corrective measures and report the measures taken. Failure to respond is in itself a ground for suspension.
6.3. dor.net for its part undertakes to forward reports it receives to the Customer within 1 business day and to act immediately on serious reports (ongoing attack, child abuse material, active phishing).
6.4. Court orders, BTK orders and other competent authority orders are implemented within the period stated in the order (including the 4-hour period in Article 9 of Law No. 5651). Prior notice to the Customer may not be required for their implementation; the Customer is informed afterwards where the law allows.
7. Consequences of breach and process
| Situation | dor.net's action |
|---|---|
| First, minor, curable breach (e.g. misconfigured open relay, a single spam complaint) | Notice and 24 hours to cure; closure of the relevant port if needed |
| Uncured or repeated breach | Suspension of the service; suspension continues until a remediation plan is received |
| Active harm to the network or third parties (DDoS source, botnet C2, spreading malware) | Immediate suspension with simultaneous notice; the narrowest intervention needed to stop the harm (e.g. null-routing only the affected IP) |
| Catalogue offence content, child abuse, court order | Immediate disconnection, report to the authorities, termination if necessary |
| False identity, stolen payment, fraud | Account closure and action under clause 4.4 of the Terms of service |
7.1. Fees continue to accrue for a service suspended for abuse; no SLA credit is given for the suspension period.
7.2. The Customer may object to a suspension through a support ticket; objections are assessed within 2 business days. If the suspension was unjustified, no fee is charged for the suspension period and SLA credit is applied.
7.3. For material and uncured breaches dor.net may terminate the agreement under clause 11.3 of the Terms of service. On termination the unused balance is refunded after set-off of dor.net's documented loss.
7.4. dor.net may pass on to the Customer documented third-party claims, fines and reasonable intervention costs arising from the breach, under clause 19 of the Terms of service.
8. Inbound attacks and protection
In a volumetric DDoS attack on the Customer's server, dor.net may temporarily filter or null-route the targeted IP to protect the network as a whole. This is a protective measure taken without fault on the Customer's part and is among the exclusions in the SLA; dor.net restores the service as soon as the attack ends and informs the Customer.
9. Security obligations
The Customer must keep its operating system and software up to date, use strong authentication, disable unnecessary services and take reasonable measures to prevent its server being used as an attack tool. A compromised server is handled under this policy even where the Customer had no intent; dor.net allows a reasonable time for clean-up in that case.
10. Contact
Abuse reports: abuse@dor.net · Requests from authorities: legal@dor.net and mgnteknolojianonim@hs06.kep.tr
Company details
MGN Teknoloji A.Ş. · Fenerbahçe Mah. İğrip Sk. No: 13 İç Kapı No: 1, Kadıköy/İstanbul, Türkiye · Göztepe Tax Office / 6201650498 · MERSİS 0620165049800001 · KEP mgnteknolojianonim@hs06.kep.tr · abuse@dor.net