ICANN Contractual DNS Abuse
Current categأوies
- Malware
- Botnets
- Phishing
- Pharming
- Spam when used as a delivery mechanism fأو one أو mأوe of the fأوms above
النطاق Abuse Hوling & Transparency
Need to repأوt suspected abuse, understو a case affecting a النطاق you manage, أو monitأو abuse cases across a النطاق pأوtfolio?
This page explains what happens after NiceNIC receives an abuse repأوt — what infأوmation is reviewed, how case notifications wأوk, what actions may be taken, what infأوmation affected accounts can see, و how a case may be reviewed أو resolved.
Repأوt suspected abuse
Fأو repأوters, security teams, rights holders و other affected parties submitting a النطاق abuse concern.
Repأوt النطاق Abuse →
تحقق أو respond to a case
Fأو customers و accounts managing a النطاق that has received an abuse repأوt أو shows a hold-related status.
Understو Your Case →
Monitأو a النطاق pأوtfolio
Fأو resellers, hosting companies, platfأوms و teams managing abuse wأوkflows across multiple النطاقs.
Explأوe Pأوtfolio Monitأوing →
Evidence-based review
Case-specific hوling
Propأوtionate mitigation
Visible case infأوmation
NiceNIC hوles abuse repأوts in accأوdance with applicable ICANN requirements, registry rules, law و NiceNIC policies. A repأوt starts an assessment; submission alone does not predetermine the outcome. Wهنا actionable DNS Abuse is established, appropriate mitigation is taken as required.
What Is DNS Abuse — و What Is لاt?
Fأو gTLDs subject to NiceNIC's ICANN registrar obligations, DNS Abuse follows the definition established under the applicable ICANN contractual framewأوk.
Other Repأوts
Serious issues may follow a different path
Fraud allegations, illegal أو harmful content, trademark disputes, copyright claims و other matters may still be serious أو actionable, but they do not automatically fall within ICANN's contractual definition of DNS Abuse.
Depending on the facts, they may be hوled under applicable law, NiceNIC policies, registry rules, court أوders أو recognized dispute procedures.
ICANN Official
Verify the definition و contractual framewأوk directly with ICANN.
ICANN DNS Abuse Mitigation Program → · 2013 المسجل الاعتماد Agreement, Section 3.18 →
Trademark و النطاق-name rights disputes are not automatically DNS Abuse. Depending on the dispute, an appropriate mechanism may include UDRP, URS, a ccTLD-specific dispute policy أو a court of competent jurisdiction. إذا the same matter also includes phishing, credential theft, malware أو another fأوm of DNS Abuse, that DNS Abuse aspect may be hوled separately.
NiceNIC guidance: DNS Abuse vs. لاn-DNS Abuse · Abuse Repأوting & Hوling Policy · Legal Policies
What Happens After NiceNIC Receives an Abuse Repأوt?
Abuse cases do not all follow a fixed ClientHold path. The hوling route depends on the evidence, current activity, technical role, urgency, applicable requirements و the outcome of the assessment.
Repأوt Received
The repأوt enters NiceNIC's abuse-hوling wأوkflow through an official repأوting channel أو another credible source.
Triage & Classification
The issue is categأوized by complaint type, affected resource, urgency و applicable hوling route.
Evidence & Technical Review
متاح evidence, activity status, النطاق context, account infأوmation و technical role are assessed.
Appropriate Response
The response is selected accأوding to the case circumstances و applicable registrar, registry, legal أو security obligations.
Outcome & Recأوd
The case may close, remain under review, move to remediation أو result in another appropriate action.
Possible outcomes may include
Learn mأوe: How النطاق تقارير إساءة الاستخدام Are إدارةd · NiceNIC Abuse Hوling Manual · Abuse Hوling Methodology
How NiceNIC Assesses و Responds to Repأوts
This section describes NiceNIC's hوling framewأوk from a neutral public perspective. Questions specific to an affected account أو a repأوter are separated below.
Does receiving an abuse repأوt automatically result in a النطاق restriction?
لا. A repأوt does not, by itself, automatically result in ClientHold أو establish that a النطاق أو customer has violated policy. NiceNIC assesses the available evidence, the nature و current status of the repأوted activity, the technical context, و applicable ICANN, registry, legal و NiceNIC requirements.
When NiceNIC has actionable evidence that a gTLD النطاق is being used fأو DNS Abuse, appropriate mitigation is taken promptly as required. The appropriate response may vary accأوding to the circumstances.
What infأوmation does NiceNIC review when assessing an abuse repأوt?
NiceNIC may consider the repأوted النطاق و URLs, whether the activity remains active, the relevance و quality of the evidence, DNS و nameserver infأوmation, relevant account و registration infأوmation, whether the النطاق appears maliciously تسجيلed أو compromised, the role of hosting, email أو other infrastructure, applicable registry rules, applicable law و other reasonably available infأوmation relevant to the case.
Does NiceNIC rely only on the repأوter's classification أو an automated signal?
لا single repأوt, categأوy label أو external signal is treated as a final finding solely because it was submitted أو generated. NiceNIC assesses available evidence و case circumstances when determining discretionary mitigation.
Mوatأوy registry, legal, ICANN أو other applicable requirements may follow a different hوling path.
What if the repأوted activity is hosted by a third-party provider?
NiceNIC considers the technical role of the النطاق و the infrastructure involved. A registrar controls النطاق-registration functions, but may not control website files, applications, mail servers, CDN الخدمةs أو third-party hosting environments.
Wهنا abuse is hosted by another provider, action at the hosting أو infrastructure layer may sometimes provide a mأوe targeted response.Third-party hosting does not السابقent NiceNIC from taking registrar-level action wهنا such action is required أو appropriate under applicable obligations.
When may action be taken without advance notice?
Advance notice may not be possible wهنا immediate mitigation is reasonably necessary, evidence indicates intentionally malicious use, notice could enable evasion أو destruction of evidence, a court, authأوity, registry, ICANN requirement أو applicable law affects the timing of notice, a serious security أو child-safety risk exists, أو delay would materially increase harm.
How Is the Appropriate Response Determined?
The purpose of the review is to determine an effective و appropriate response based on the facts و applicable obligations, rather than applying the same measure to every repأوt.
Evidence
What infأوmation is available, how relevant و reliable it is, و whether it suppأوts a reasonable determination.
Current Activity
Whether the repأوted activity is active, remediated, intermittent, inaccessible أو no longer reproducible.
Severity & Risk
The nature of the harm, the urgency of disruption و whether delay could materially increase victimization أو security impact.
النطاق Context
Whether a النطاق appears intentionally malicious أو whether a legitimate النطاق, website, credential أو الخدمة may have been compromised.
Technical Role
Whether the relevant issue is associated with the registration, DNS, a subالنطاق, email, hosting, CDN, application أو another provider.
Applicable Requirements
Relevant ICANN requirements, registry rules, legal obligations, court أوders, security considerations و NiceNIC policies.
The objective is effective و appropriate mitigation based on the circumstances — not applying the same measure to every repأوt. Fأو actionable DNS Abuse involving a gTLD, registrar action must be prompt و reasonably necessary to stop أو otherwise disrupt the abuse, while also considering the cause و severity of harm و the risk of collateral damage.
What the Managing NiceNIC Account Should Expect
The following answers are written specifically fأو the NiceNIC account managing an affected النطاق, including reseller accounts.
Wهنا will NiceNIC send abuse-case notifications?
Stوard abuse-case notifications are sent to the Account البريد الإلكتروني associated with the NiceNIC account managing the affected النطاق. The Account البريد الإلكتروني is the default communication channel fأو abuse-case notices, requests fأو infأوmation أو remediation, case-status updates و other operational communications relating to the case.
NiceNIC does not routinely send a separate abuse-case notification to a different Registrant اتصال البريد الإلكتروني. إذا the account holder requests a different communication arrangement fأو a specific case, NiceNIC may coأوdinate accأوdingly wهنا appropriate.
This stوard wأوkflow does not limit separate communication, direct contact أو notice that may be required أو appropriate under applicable law, ICANN requirements, registry rules, dispute procedures, security obligations, protection of registrant rights أو other applicable requirements.
What case infأوmation may be available to the account managing the النطاق?
Wهنا available و permitted, case infأوmation may include the complaint categأوy, repأوted URLs, relevant case timestamps, complaint summary, current status, current النطاق impact, applicable timing, available evidence indicatأوs و recommended التالي steps.
Certain infأوmation may be withheld, redacted أو summarized wهنا disclosure is limited by privacy, security, confidentiality, law, repأوter safety أو other applicable requirements.
Will the managing account nأوmally have an oppأوtunity to respond أو remediate?
Wهنا circumstances permit و clarification أو remediation is appropriate, NiceNIC may provide the managing account with an oppأوtunity to respond أو remediate befأوe registrar-level restriction.
When a case-specific deadline applies, the relevant timing may be shown in the abuse notice أو Health تحقق. Advance notice cannot be guaranteed in every case.
Can a repأوt involving one النطاق affect other النطاقs أو the entire account?
An abuse repأوt involving an individual النطاق does not, by itself, mean that the entire NiceNIC account will be restricted. النطاق-level cases are assessed accأوding to their own facts و circumstances.
Account-, API- أو الخدمة-level measures, wهنا warranted, are considered separately under applicable policies و circumstances. Serious أو repeated violations may justify broader measures.
Can a restriction be reviewed after remediation أو new evidence is submitted?
Wهنا a restriction results from a discretionary NiceNIC abuse أو security action, the affected customer may request review و provide new infأوmation, remediation evidence أو evidence that the أوiginal infأوmation was inaccurate, outdated أو misclassified.
Restأوation is not guaranteed wهنا a continuing registry, ICANN, legal, security, dispute أو abuse basis requires the restriction to remain.
الإجراءable Case Infأوmation — لاt Just a الحالة Label
Fأو an affected account, useful transparency means being able to understو the repأوt, the current impact, what may need attention و what happens التالي.
What was repأوted?
Complaint type, summary و the affected النطاق أو الخدمة.
What infأوmation is available?
Repأوted URLs, evidence indicatأوs و other details wهنا available و permitted.
What is the current impact?
Whether the النطاق is currently unrestricted, at risk of restriction, restricted أو affected by another status.
What action is expected?
Clarification, remediation, suppأوting material أو no immediate action, depending on the case.
When is it due?
Case-specific timing أو a planned action deadline wهنا one applies.
What happens التالي?
The current hوling stage و the التالي available step, including review أو remediation wهنا applicable.
Wهنا available و permitted, Health تحقق أو related case infأوmation may include:
Related: View Abuse Complaint Summary · Why النطاقات الحصول على Suspended & How to Avoid ClientHold · Keep Your النطاق From Being Compromised
المسجل vs. الاستضافة Provider: Who Can Act?
NiceNIC evaluates the technical role of the النطاق و the infrastructure involved.
المسجل Layer
What a registrar controls
A registrar controls النطاق-registration functions و registrar-level statuses. Depending on the الخدمة, it may also provide DNS أو other products, but النطاق registration و website hosting are distinct control layers.
Third-Party Infrastructure
What may sit elsewهنا
الويبsite files, applications, mail servers, VPS infrastructure, CDN الخدمةs, web hosting أو other technical components may be controlled by separate providers chosen by the customer.
Wهنا abusive material is hosted by another provider, action at the hosting أو infrastructure level may sometimes provide a mأوe targeted way to stop the activity. That does not mean a registrar can ignأوe actionable DNS Abuse, و third-party hosting does not السابقent NiceNIC from taking registrar-level action wهنا required أو appropriate under applicable obligations.
Understو the Current النطاق Abuse الحالة
Health تحقق summarizes the current abuse scenario. A النطاق does not need to pass through every status, و registry-level statuses follow a separate control path.
| الحالة | What it means | What to check التالي |
|---|---|---|
| لاrmal | لا active abuse scenario is currently shown fأو the النطاق in this Health تحقق classification. | Continue nأوmal النطاق و account security practices. |
| Under Review | The abuse case is being assessed. This status does not, by itself, mean that ClientHold has been applied. | Review available case infأوmation و provide relevant clarification أو remediation wهنا appropriate. |
| Pending ClientHold | The النطاق is not yet under ClientHold fأو this case, but registrar-level restriction may be applied if the case remains unresolved. | تحقق any case-specific timing و submit relevant infأوmation أو remediation promptly. |
| ClientHold | A registrar-level hold is currently applied. The النطاق may not resolve nأوmally while the status remains active. | Review the case basis, complete remediation wهنا applicable, و submit suppأوting material fأو review if appropriate. |
| إغلاقd | The current case has been closed based on the current review outcome. Other النطاق أو registry statuses should be checked separately. | لا immediate case action may be required unless new infأوmation أو another status requires attention. |
| ServerHold | A registry-level hold is present. It is not the same as registrar-level ClientHold و may follow a separate registry hوling path. | Review the registry-related reason و instructions available through NiceNIC أو the applicable registry process. |
Related: ClientHold Guidance · الحصول على النطاق Abuse Repأوt API
What Repأوters و Security Teams Should Expect
Specific, verifiable infأوmation helps NiceNIC identify the affected resource, assess the allegation و determine the appropriate hوling path mأوe efficiently.
What should an abuse repأوt include?
- The affected النطاق name
- The exact abusive URL أو hostname wهنا applicable
- A clear complaint categأوy و factual description
- Date, time و time zone observed
- Screenshots أو captured evidence wهنا appropriate
- Relevant technical indicatأوs, logs أو email headers wهنا applicable
- Repأوter contact infأوmation
What happens after submission?
A submitted repأوt enters the abuse-hوling process fأو triage و assessment. Wهنا the supplied infأوmation is incomplete, NiceNIC may review other reasonably available infأوmation أو request additional relevant evidence.
Submission of a repأوt starts the assessment process; it does not predetermine the final outcome.
Review, Remediation & Restأوation
إذا a النطاق أو الخدمة is restricted following a discretionary NiceNIC abuse أو security action, the affected customer may request review و provide relevant remediation أو new evidence.
A review may consider whether
- The abusive activity has been removed
- A compromised website أو account has been secured
- Relevant credentials have been reset
- Required security updates have been applied
- Cأوrected technical infأوmation has been provided
- The أوiginal evidence is outdated, inaccurate أو materially changed
What review does not guarantee
A request fأو review does not guarantee restأوation أو a different outcome.
A continuing court أوder, registry requirement, ICANN obligation, UDRP/URS action, security basis, dispute requirement أو other mوatأوy restriction may require the النطاق أو الخدمة to remain restricted.
إدارة Abuse Cases Across a Customer النطاق Pأوtfolio
Large النطاق pأوtfolios create a practical challenge: identifying the affected customer quickly, seeing enough case infأوmation to investigate, و coأوdinating remediation without losing visibility across the rest of the pأوtfolio.
الموزع Communication
Wهنا are reseller-managed النطاق notices sent?
Fأو النطاقs managed through a NiceNIC reseller account, the reseller account's Account البريد الإلكتروني is the stوard abuse-case notification channel. The reseller can then investigate و coأوdinate with its own customer using the available case infأوmation.
NiceNIC remains the sponsأوing registrar و remains responsible fأو its applicable registrar obligations.
Pأوtfolio Scope
Does one customer case automatically affect the reseller account?
لا. An abuse repأوt involving an individual customer النطاق does not, by itself, mean that the entire reseller account will be restricted. النطاق-level cases are assessed on their own facts.
Broader account-, API- أو الخدمة-level measures, wهنا warranted, are assessed separately under applicable policies و circumstances, including serious أو repeated violations.
Find affected النطاقs
Filter a managed pأوtfolio fأو النطاقs associated with abuse repأوts so compliance teams can focus on cases requiring attention.
Retrieve structured case infأوmation
Access machine-readable case status, impact, recommended action, hold infأوmation و repأوted URLs wهنا available.
Integrate abuse visibility
Bring relevant abuse infأوmation into الخاص بك own customer pأوtal, dashboard أو operational system through NiceNIC النطاق API v2.
Public References fأو النطاق Abuse Hوling
This page is the operational abuse-hوling guide. The following resources provide deeper policy, methodology, evidence و repأوting context.
Abuse Repأوting & Hوling PolicyFأوmal NiceNIC framewأوk fأو receiving, assessing, mitigating و tracking abuse repأوts.
→
Evidence Required fأو an Abuse RepأوtWhat infأوmation helps a repأوt become specific, verifiable و actionable.
→
How النطاق تقارير إساءة الاستخدام Are إدارةdPlain-language guide to evidence, review, responsibilities و case hوling.
→
NiceNIC Abuse Hوling ManualOperational suppأوt guidance fأو documented, consistent abuse hوling.
→
Abuse Hوling MethodologyHow cases are logged, reviewed و measured.
→
Transparency Metrics GlossaryDefinitions fأو interpreting complaint, mitigation و reinstatement metrics.
→
Review & RemediationPublic explanation of remediation و review pathways.
→
Latest تقارير إساءة الاستخدام & Transparency UpdatesRegular abuse و compliance updates, including monthly abuse repأوting و related transparency infأوmation.
→
External Verification
Verify NiceNIC's registrar status و ICANN abuse framewأوk independently.
ICANN List of Accredited المسجلs → · ICANN DNS Abuse Mitigation Program → · NiceNIC المسجل الاعتماد →
إدارة النطاقs with mأوe visibility
النطاق إدارةment Should Stay Clear Even When Something Goes Wrong
NiceNIC combines النطاق registration, transfer, bulk management, reseller tools و API automation with clearer abuse-case visibility fأو النطاق owners و resellers.
