MainReg Inc. is committed to investigating and responding appropriately to reports of abuse in accordance with applicable law, ICANN requirements, and the Registrar Accreditation Agreement (RAA), including Sections 3.18.1, 3.18.2, and 3.18.4. This page explains how to submit reports and how MainReg evaluates and handles all reported abuse.

1. How to Report Abuse

Abuse reports and related inquiries may be submitted by email to:

To help us investigate quickly, please include (where available):

• Reported domain name(s)
• Type of abuse alleged (DNS Abuse, phishing, malware, scam, fraud, etc.)
• Evidence (URLs, screenshots, email headers, logs, timestamps, affected IPs)
• Your contact details for follow-up (optional but helpful)
• Any reference number (court, CERT, law enforcement, case ID) if applicable

2. Scope: Reports We Handle

MainReg reviews and responds appropriately to reports of abuse concerning domain names we sponsor. Reports may include DNS Abuse and other alleged abusive or illegal activity (for example: fraud allegations, scam content, content disputes, trademark-related complaints, or other policy violations). Where a report does not fall within DNS Abuse as defined by ICANN, MainReg will still evaluate the report and take action where required under applicable law, registry requirements, ICANN policies, and/or MainReg’s Terms of Service.

3. DNS Abuse Definition (ICANN)

MainReg applies ICANN’s definition of DNS Abuse, which is limited to:

• Malware – distribution of malicious software designed to infiltrate or damage systems
• Botnets – command-and-control operations for networks of infected devices
• Phishing – fraudulent attempts to obtain sensitive information by impersonation
• Pharming – redirecting users from legitimate websites to malicious destinations via DNS manipulation
• Spam only when used to deliver or facilitate malware, phishing, botnets, or pharming

Spam alone is not treated as DNS Abuse unless it is directly connected to one of the categories above.

4. Receipt Confirmation (RAA 3.18.1)

Upon receipt of an abuse report, MainReg logs the report and provides the reporting party with confirmation that the report has been received. Acknowledgment is sent without undue delay and is typically immediate. This confirmation is an acknowledgment of receipt.

5. Abuse Handling Process and Target Timeframes

MainReg follows the steps below when handling abuse reports:

6. When MainReg Takes Immediate Action vs. Requests Registrant Input

6.1 Well-Evidenced DNS Abuse (RAA 3.18.2)

MainReg treats DNS Abuse as “well-evidenced” where the investigation confirms that the domain is being used primarily and intentionally for DNS Abuse activities (for example: clear phishing content collecting credentials, malware distribution, botnet command-and-control, or pharming through DNS manipulation), and not merely as an incidental or unintended result of compromise.

In well-evidenced DNS Abuse cases, MainReg suspends the domain immediately upon confirmation, and in any case no later than 1 business day from completion of investigation. The registrant is notified of the suspension. If the registrant provides credible counter-evidence or demonstrates compromise and remediation, MainReg may re-evaluate and restore the domain where appropriate and will respond to the reporting party accordingly.

6.2 Cases Involving Possible Compromise or Spam Supporting DNS Abuse

Where the evidence suggests possible compromise or spam used to deliver DNS Abuse, MainReg may request prompt remediation or clarification from the registrant to determine whether the registrant is not directly connected to the activity and whether corrective steps are taken. If no adequate response is received, MainReg may suspend the domain no later than 1 business day from completion of investigation.

6.3 Other Abuse Reports (Non-DNS Abuse)

For reports that do not constitute well-evidenced DNS Abuse, MainReg evaluates the report and may notify the registrant and allow up to 5 business days for response and remediation, depending on the circumstances and evidence. Where no response is received or the issue is not resolved, MainReg may take appropriate action under applicable law, registry requirements, ICANN policies, and/or MainReg’s Terms of Service.

7. Escalation, Quality Control, and Corrective Actions

Escalation is performed based on the initial assessment of the report, severity, and evidence. Unclear cases (for example: suspected phishing that is not obvious) are escalated internally to a more experienced reviewer. The weekly oversight review checks that targeted timeframes were met and that classifications and actions were consistent. Any identified errors or missed timeframes are reported to management and addressed through corrective actions, which may include retraining, template updates, process adjustments, or re-review of affected cases.

8. Records Retention (RAA 3.18.4)

MainReg maintains records related to the receipt and handling of abuse reports, including receipt confirmations, investigation notes, actions taken, and communications. Records are retained for the shorter of two (2) years or the longest period permitted by applicable law, and can be provided to ICANN upon reasonable notice.

9. Reporting Inaccurate Registration Data (RAA 3.7.8)

MainReg maintains a process for investigating reports of inaccurate registration data (RDAP / registration data inaccuracy). Anyone who believes registration data is inaccurate may submit a report to: complain@mainreg.com

Please include the domain name, the alleged inaccuracy, and any supporting evidence.

MainReg will review the report and, where appropriate, contact the registrant to correct or verify the data. Registrants are provided up to fifteen (15) calendar days to respond and correct inaccurate data. Failure to respond or correct inaccuracies may result in suspension or cancellation of the domain name.

10. Updates

This policy may be updated from time to time. The current version is published on this page.