DOMAIN ABUSE Reporting
and Review Procedure

1) Purpose and scope

This procedure defines, within the scope of PROJX's domain name registration services, the workflow for receiving, reviewing, monitoring and, where necessary, applying mitigation/blocking actions related to abuse (domain abuse) reports associated with domain names.

The scope includes, without being limited to, topics such as DNS Abuse, reports of illegal activity, SPAM complaints (especially when serving as a vector for another type of abuse) and registration data (WHOIS/RDDS) errors. ICANN

2) Definitions (brief)

• Actionable evidence: Technical/incident data that is associable with a domain name, verifiable and sufficient to support a decision to intervene.
• DNS Abuse: Types of abuse such as malware, botnets, phishing, pharming, and spam used as a vector for other types of abuse. ICANN
• Illegal Activity: Uses reported by competent authorities or relevant bodies that constitute a crime or unlawful act under applicable legislation.

3) Reporting channel

Abuse reports are submitted through the following channel:

• Web form: [email protected]

Note: A minimum information/evidence set must be provided for reports to be evaluated. Incomplete reports may be returned with a request for additional information.

4) Minimum information required in a report

For all types of violations:

• The domain name subject to the report
• Type of violation (SPAM / phishing / malware / fraud / registration data error, etc.)
• Evidence of the violation (URL, screenshot, log output, timestamp, related message content, etc.)
• Reporter's full name and reply email address

For SPAM, additionally (critical):

• Full headers and body of the SPAM email
• If possible, the time of transmission, recipient address and a sample message

For registration data (WHOIS/RDDS) errors, additionally:

• Which field (e.g. email / phone / address) in the registration data of the alleged inaccurate domain name is incorrect
• Any comparative evidence that facilitates verification (screenshots, official records, etc.), if available

5) Review process (end to end)

5.1 Acceptance and pre-check

• PROJX performs a pre-check on the report regarding evidence sufficiency, associability with the domain name, and scope fit.
• For matters outside PROJX's control (e.g. different provider infrastructure), the reporter may be redirected/informed accordingly.

5.2 Technical review

• The abuse team technically verifies the evidence, classifies the type of violation and evaluates the risk level (high risk / recurrence / propagation impact, etc.).

5.3 Coordination

• Where necessary, coordination is established with the panel owner, the reseller (if any) and the domain owner.
• Technical and administrative coordination may be carried out with the competent registry / relevant third parties (registry, etc.).

5.4 Action and follow-up

• Appropriate action(s) are determined (warning, temporary suspension, DNS/NS intervention, lock, transfer restriction, coordination for termination, etc.).
• The domain owner's corrective actions are monitored; the process is followed up until a resolution is reached.

5.5 Closure

• After resolution, the incident record is closed and the records are retained (see Section 7).

6) Application principles by type of violation

6.1 SPAM

• The review is conducted based on the headers + body provided. Verification is not possible without this information.
• In cases of compromised/hacked domain names or first-time detected promotional spam, the primary approach is to notify the domain owner and request corrective actions.
• Recurring spam cases and/or cases where no corrective action is taken may result in restrictions/suspension on the domain name.
• If spam is used as a vector for DNS Abuse types such as phishing/malware, it is treated as high risk and faster/stricter mitigation may be applied. ICANN

6.2 Phishing / Malware / Fraud

• Where actionable evidence exists, reasonable and prompt mitigation steps are activated to stop the abuse of the domain or to reduce its impact. ICANN
• The choice of action is determined taking into account the severity of the harm, the likelihood of spread and possible side effects. ICANN

6.3 Child sexual abuse material (CSAM) / serious illegal content

• Such reports are treated as critical; where deemed necessary, immediate restriction/suspension may be applied to the domain name.
• When required by applicable legislation, coordination is ensured with the relevant official authorities.

6.4 Registration data (WHOIS/RDDS) errors

• The registrant is asked to correct the registration data or to provide sufficient evidence to demonstrate the accuracy of the existing data.
• If no update is made or verification is not provided within the specified period, the domain name may be suspended due to inconsistencies in the registration data.

7) Recordkeeping, traceability and retention

PROJX publishes a procedure definition for receiving, handling and following up abuse reports; it documents that the reports have been received/processed and the responses provided. In addition, it retains the relevant records for two (2) years or the shorter of the maximum period permitted by applicable law, and may make them available to ICANN upon reasonable notice. ICANN

8) General principles

• PROJX only makes decisions based on reports containing "verifiable / actionable" content.
• Where an action requested would be contrary to applicable legislation, PROJX has no obligation to take action in that direction. ICANN
• Each case is evaluated taking into account the technical context, the level of risk and the area of impact.

Company information

• Legal name: PROJX Digital İnovatif Teknolojiler A.Ş.
• Türkiye Office: Abide-i Hürriyet cd. BlackOut Plaza A Blok NO 211/1/64 Şişli - İstanbul - Türkiye
• Phone: +90 212 325 7300
• Istanbul Trade Registry No: 487191-5
• Mersis No: 0733119868800001
• Tax Office / No: Şişli / 7331198688
• Email: [email protected]