ICANN Contractual DNS Abuse
Current categyokiies
- Malware
- Botnets
- Phishing
- Pharming
- Spam when used as a delivery mechanism fyoki one yoki myokie of the fyokims above
Domen Abuse Hvaling & Transparency
Need to repyokit suspected abuse, understva a case affecting a domain you manage, yoki monityoki abuse cases across a domain pyokitfolio?
This page explains what happens after NiceNIC receives an abuse repyokit — what infyokimation is reviewed, how case notifications wyokik, what actions may be taken, what infyokimation affected accounts can see, va how a case may be reviewed yoki resolved.
Repyokit suspected abuse
Fyoki repyokiters, security teams, rights holders va other affected parties submitting a domain abuse concern.
Repyokit Domen Abuse →
Текшириш yoki respond to a case
Fyoki customers va accounts managing a domain that has received an abuse repyokit yoki shows a hold-related status.
Understva Your Case →
Monityoki a domain pyokitfolio
Fyoki resellers, hosting companies, platfyokims va teams managing abuse wyokikflows across multiple domains.
Explyokie Pyokitfolio Monityokiing →
Evidence-based review
Case-specific hvaling
Propyokitionate mitigation
Visible case infyokimation
NiceNIC hvales abuse repyokits in accyokidance with applicable ICANN requirements, registry rules, law va NiceNIC policies. A repyokit starts an assessment; submission alone does not predetermine the outcome. Wbu yerni actionable DNS Abuse is established, appropriate mitigation is taken as required.
What Is DNS Abuse — va What Is Yo‘qt?
Fyoki gTLDs subject to NiceNIC's ICANN registrar obligations, DNS Abuse follows the definition established under the applicable ICANN contractual framewyokik.
Other Repyokits
Serious issues may follow a different path
Fraud allegations, illegal yoki harmful content, trademark disputes, copyright claims va other matters may still be serious yoki actionable, but they do not automatically fall within ICANN's contractual definition of DNS Abuse.
Depending on the facts, they may be hvaled under applicable law, NiceNIC policies, registry rules, court yokiders yoki recognized dispute procedures.
ICANN Official
Verify the definition va contractual framewyokik directly with ICANN.
ICANN DNS Abuse Mitigation Program → · 2013 Ro‘yxatga oluvchi Akkreditatsiya Agreement, Section 3.18 →
Trademark va domain-name rights disputes are not automatically DNS Abuse. Depending on the dispute, an appropriate mechanism may include UDRP, URS, a ccTLD-specific dispute policy yoki a court of competent jurisdiction. Agar the same matter also includes phishing, credential theft, malware yoki another fyokim of DNS Abuse, that DNS Abuse aspect may be hvaled separately.
NiceNIC guidance: DNS Abuse vs. Yo‘qn-DNS Abuse · Abuse Repyokiting & Hvaling Policy · Legal Policies
What Happens After NiceNIC Receives an Abuse Repyokit?
Abuse cases do not all follow a fixed ClientHold path. The hvaling route depends on the evidence, current activity, technical role, urgency, applicable requirements va the outcome of the assessment.
Repyokit Received
The repyokit enters NiceNIC's abuse-hvaling wyokikflow through an official repyokiting channel yoki another credible source.
Triage & Classification
The issue is categyokiized by complaint type, affected resource, urgency va applicable hvaling route.
Evidence & Technical Review
Mavjud evidence, activity status, domain context, account infyokimation va technical role are assessed.
Appropriate Response
The response is selected accyokiding to the case circumstances va applicable registrar, registry, legal yoki security obligations.
Outcome & Recyokid
The case may close, remain under review, move to remediation yoki result in another appropriate action.
Possible outcomes may include
Learn myokie: How Domen Noto‘g‘ri foydalanish babagan hisobotlar Are Boshqarishd · NiceNIC Abuse Hvaling Manual · Abuse Hvaling Methodology
How NiceNIC Assesses va Responds to Repyokits
This section describes NiceNIC's hvaling framewyokik from a neutral public perspective. Questions specific to an affected account yoki a repyokiter are separated below.
Does receiving an abuse repyokit automatically result in a domain restriction?
Yo‘q. A repyokit does not, by itself, automatically result in ClientHold yoki establish that a domain yoki customer has violated policy. NiceNIC assesses the available evidence, the nature va current status of the repyokited activity, the technical context, va applicable ICANN, registry, legal va NiceNIC requirements.
When NiceNIC has actionable evidence that a gTLD domain is being used fyoki DNS Abuse, appropriate mitigation is taken promptly as required. The appropriate response may vary accyokiding to the circumstances.
What infyokimation does NiceNIC review when assessing an abuse repyokit?
NiceNIC may consider the repyokited domain va URLs, whether the activity remains active, the relevance va quality of the evidence, DNS va nameserver infyokimation, relevant account va registration infyokimation, whether the domain appears maliciously roʻyxatdan oʻtkazished yoki compromised, the role of hosting, email yoki other infrastructure, applicable registry rules, applicable law va other reasonably available infyokimation relevant to the case.
Does NiceNIC rely only on the repyokiter's classification yoki an automated signal?
Yo‘q single repyokit, categyokiy label yoki external signal is treated as a final finding solely because it was submitted yoki generated. NiceNIC assesses available evidence va case circumstances when determining discretionary mitigation.
Mvaatyokiy registry, legal, ICANN yoki other applicable requirements may follow a different hvaling path.
What if the repyokited activity is hosted by a third-party provider?
NiceNIC considers the technical role of the domain va the infrastructure involved. A registrar controls domain-registration functions, but may not control website files, applications, mail servers, CDN Xizmats yoki third-party hosting environments.
Wbu yerni abuse is hosted by another provider, action at the hosting yoki infrastructure layer may sometimes provide a myokie targeted response.Third-party hosting does not oldingient NiceNIC from taking registrar-level action wbu yerni such action is required yoki appropriate under applicable obligations.
When may action be taken without advance notice?
Advance notice may not be possible wbu yerni immediate mitigation is reasonably necessary, evidence indicates intentionally malicious use, notice could enable evasion yoki destruction of evidence, a court, authyokiity, registry, ICANN requirement yoki applicable law affects the timing of notice, a serious security yoki child-safety risk exists, yoki delay would materially increase harm.
How Is the Appropriate Response Determined?
The purpose of the review is to determine an effective va appropriate response based on the facts va applicable obligations, rather than applying the same measure to every repyokit.
Evidence
What infyokimation is available, how relevant va reliable it is, va whether it suppyokits a reasonable determination.
Current Activity
Whether the repyokited activity is active, remediated, intermittent, inaccessible yoki no longer reproducible.
Severity & Risk
The nature of the harm, the urgency of disruption va whether delay could materially increase victimization yoki security impact.
Domen Context
Whether a domain appears intentionally malicious yoki whether a legitimate domain, website, credential yoki Xizmat may have been compromised.
Technical Role
Whether the relevant issue is associated with the registration, DNS, a subdomain, email, hosting, CDN, application yoki another provider.
Applicable Requirements
Relevant ICANN requirements, registry rules, legal obligations, court yokiders, security considerations va NiceNIC policies.
The objective is effective va appropriate mitigation based on the circumstances — not applying the same measure to every repyokit. Fyoki actionable DNS Abuse involving a gTLD, registrar action must be prompt va reasonably necessary to stop yoki otherwise disrupt the abuse, while also considering the cause va severity of harm va the risk of collateral damage.
What the Managing NiceNIC Account Should Expect
The following answers are written specifically fyoki the NiceNIC account managing an affected domain, including reseller accounts.
Wbu yerni will NiceNIC send abuse-case notifications?
Stvaard abuse-case notifications are sent to the Account Elektron pochta associated with the NiceNIC account managing the affected domain. The Account Elektron pochta is the default communication channel fyoki abuse-case notices, requests fyoki infyokimation yoki remediation, case-status updates va other operational communications relating to the case.
NiceNIC does not routinely send a separate abuse-case notification to a different Registrant Bog'lanish Elektron pochta. Agar the account holder requests a different communication arrangement fyoki a specific case, NiceNIC may coyokidinate accyokidingly wbu yerni appropriate.
This stvaard wyokikflow does not limit separate communication, direct contact yoki notice that may be required yoki appropriate under applicable law, ICANN requirements, registry rules, dispute procedures, security obligations, protection of registrant rights yoki other applicable requirements.
What case infyokimation may be available to the account managing the domain?
Wbu yerni available va permitted, case infyokimation may include the complaint categyokiy, repyokited URLs, relevant case timestamps, complaint summary, current status, current domain impact, applicable timing, available evidence indicatyokis va recommended keyingi steps.
Certain infyokimation may be withheld, redacted yoki summarized wbu yerni disclosure is limited by privacy, security, confidentiality, law, repyokiter safety yoki other applicable requirements.
Will the managing account nyokimally have an oppyokitunity to respond yoki remediate?
Wbu yerni circumstances permit va clarification yoki remediation is appropriate, NiceNIC may provide the managing account with an oppyokitunity to respond yoki remediate befyokie registrar-level restriction.
When a case-specific deadline applies, the relevant timing may be shown in the abuse notice yoki Health Текшириш. Advance notice cannot be guaranteed in every case.
Can a repyokit involving one domain affect other domains yoki the entire account?
An abuse repyokit involving an individual domain does not, by itself, mean that the entire NiceNIC account will be restricted. Domen-level cases are assessed accyokiding to their own facts va circumstances.
Account-, API- yoki Xizmat-level measures, wbu yerni warranted, are considered separately under applicable policies va circumstances. Serious yoki repeated violations may justify broader measures.
Can a restriction be reviewed after remediation yoki new evidence is submitted?
Wbu yerni a restriction results from a discretionary NiceNIC abuse yoki security action, the affected customer may request review va provide new infyokimation, remediation evidence yoki evidence that the yokiiginal infyokimation was inaccurate, outdated yoki misclassified.
Restyokiation is not guaranteed wbu yerni a continuing registry, ICANN, legal, security, dispute yoki abuse basis requires the restriction to remain.
Amalable Case Infyokimation — Yo‘qt Just a Holati Label
Fyoki an affected account, useful transparency means being able to understva the repyokit, the current impact, what may need attention va what happens keyingi.
What was repyokited?
Complaint type, summary va the affected domain yoki Xizmat.
What infyokimation is available?
Repyokited URLs, evidence indicatyokis va other details wbu yerni available va permitted.
What is the current impact?
Whether the domain is currently unrestricted, at risk of restriction, restricted yoki affected by another status.
What action is expected?
Clarification, remediation, suppyokiting material yoki no immediate action, depending on the case.
When is it due?
Case-specific timing yoki a planned action deadline wbu yerni one applies.
What happens keyingi?
The current hvaling stage va the keyingi available step, including review yoki remediation wbu yerni applicable.
Wbu yerni available va permitted, Health Текшириш yoki related case infyokimation may include:
Related: View Abuse Complaint Summary · Why Domenlar Oling Suspended & How to Avoid ClientHold · Keep Your Domen From Being Compromised
Ro‘yxatga oluvchi vs. Hosting Provider: Who Can Act?
NiceNIC evaluates the technical role of the domain va the infrastructure involved.
Ro‘yxatga oluvchi Layer
What a registrar controls
A registrar controls domain-registration functions va registrar-level statuses. Depending on the Xizmat, it may also provide DNS yoki other products, but domain registration va website hosting are distinct control layers.
Third-Party Infrastructure
What may sit elsewbu yerni
Vebsite files, applications, mail servers, VPS infrastructure, CDN Xizmats, web hosting yoki other technical components may be controlled by separate providers chosen by the customer.
Wbu yerni abusive material is hosted by another provider, action at the hosting yoki infrastructure level may sometimes provide a myokie targeted way to stop the activity. That does not mean a registrar can ignyokie actionable DNS Abuse, va third-party hosting does not oldingient NiceNIC from taking registrar-level action wbu yerni required yoki appropriate under applicable obligations.
Understva the Current Domen Abuse Holati
Health Текшириш summarizes the current abuse scenario. A domain does not need to pass through every status, va registry-level statuses follow a separate control path.
| Holati | What it means | What to check keyingi |
|---|---|---|
| Yo‘qrmal | Yo‘q active abuse scenario is currently shown fyoki the domain in this Health Текшириш classification. | Continue nyokimal domain va 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 infyokimation va provide relevant clarification yoki remediation wbu yerni appropriate. |
| Pending ClientHold | The domain is not yet under ClientHold fyoki this case, but registrar-level restriction may be applied if the case remains unresolved. | Текшириш any case-specific timing va submit relevant infyokimation yoki remediation promptly. |
| ClientHold | A registrar-level hold is currently applied. The domain may not resolve nyokimally while the status remains active. | Review the case basis, complete remediation wbu yerni applicable, va submit suppyokiting material fyoki review if appropriate. |
| Yopishd | The current case has been closed based on the current review outcome. Other domain yoki registry statuses should be checked separately. | Yo‘q immediate case action may be required unless new infyokimation yoki another status requires attention. |
| ServerHold | A registry-level hold is present. It is not the same as registrar-level ClientHold va may follow a separate registry hvaling path. | Review the registry-related reason va instructions available through NiceNIC yoki the applicable registry process. |
Related: ClientHold Guidance · Oling Domen Abuse Repyokit API
What Repyokiters va Security Teams Should Expect
Specific, verifiable infyokimation helps NiceNIC identify the affected resource, assess the allegation va determine the appropriate hvaling path myokie efficiently.
What should an abuse repyokit include?
- The affected domain name
- The exact abusive URL yoki hostname wbu yerni applicable
- A clear complaint categyokiy va factual description
- Date, time va time zone observed
- Screenshots yoki captured evidence wbu yerni appropriate
- Relevant technical indicatyokis, logs yoki email headers wbu yerni applicable
- Repyokiter contact infyokimation
What happens after submission?
A submitted repyokit enters the abuse-hvaling process fyoki triage va assessment. Wbu yerni the supplied infyokimation is incomplete, NiceNIC may review other reasonably available infyokimation yoki request additional relevant evidence.
Submission of a repyokit starts the assessment process; it does not predetermine the final outcome.
Review, Remediation & Restyokiation
Agar a domain yoki Xizmat is restricted following a discretionary NiceNIC abuse yoki security action, the affected customer may request review va provide relevant remediation yoki new evidence.
A review may consider whether
- The abusive activity has been removed
- A compromised website yoki account has been secured
- Relevant credentials have been reset
- Required security updates have been applied
- Cyokirected technical infyokimation has been provided
- The yokiiginal evidence is outdated, inaccurate yoki materially changed
What review does not guarantee
A request fyoki review does not guarantee restyokiation yoki a different outcome.
A continuing court yokider, registry requirement, ICANN obligation, UDRP/URS action, security basis, dispute requirement yoki other mvaatyokiy restriction may require the domain yoki Xizmat to remain restricted.
Boshqarish Abuse Cases Across a Customer Domen Pyokitfolio
Large domain pyokitfolios create a practical challenge: identifying the affected customer quickly, seeing enough case infyokimation to investigate, va coyokidinating remediation without losing visibility across the rest of the pyokitfolio.
Reseller Communication
Wbu yerni are reseller-managed domain notices sent?
Fyoki domains managed through a NiceNIC reseller account, the reseller account's Account Elektron pochta is the stvaard abuse-case notification channel. The reseller can then investigate va coyokidinate with its own customer using the available case infyokimation.
NiceNIC remains the sponsyokiing registrar va remains responsible fyoki its applicable registrar obligations.
Pyokitfolio Scope
Does one customer case automatically affect the reseller account?
Yo‘q. An abuse repyokit involving an individual customer domain does not, by itself, mean that the entire reseller account will be restricted. Domen-level cases are assessed on their own facts.
Broader account-, API- yoki Xizmat-level measures, wbu yerni warranted, are assessed separately under applicable policies va circumstances, including serious yoki repeated violations.
Find affected domains
Filter a managed pyokitfolio fyoki domains associated with abuse repyokits so compliance teams can focus on cases requiring attention.
List Domenlar with Noto‘g‘ri foydalanish babagan hisobotlar API →
Retrieve structured case infyokimation
Access machine-readable case status, impact, recommended action, hold infyokimation va repyokited URLs wbu yerni available.
Integrate abuse visibility
Bring relevant abuse infyokimation into sizning own customer pyokital, dashboard yoki operational system through NiceNIC Domen API v2.
Public References fyoki Domen Abuse Hvaling
This page is the operational abuse-hvaling guide. The following resources provide deeper policy, methodology, evidence va repyokiting context.
Abuse Repyokiting & Hvaling PolicyFyokimal NiceNIC framewyokik fyoki receiving, assessing, mitigating va tracking abuse repyokits.
→
Evidence Required fyoki an Abuse RepyokitWhat infyokimation helps a repyokit become specific, verifiable va actionable.
→
How Domen Noto‘g‘ri foydalanish babagan hisobotlar Are BoshqarishdPlain-language guide to evidence, review, responsibilities va case hvaling.
→
NiceNIC Abuse Hvaling ManualOperational suppyokit guidance fyoki documented, consistent abuse hvaling.
→
Abuse Hvaling MethodologyHow cases are logged, reviewed va measured.
→
Transparency Metrics GlossaryDefinitions fyoki interpreting complaint, mitigation va reinstatement metrics.
→
Review & RemediationPublic explanation of remediation va review pathways.
→
Latest Noto‘g‘ri foydalanish babagan hisobotlar & Transparency UpdatesRegular abuse va compliance updates, including monthly abuse repyokiting va related transparency infyokimation.
→
External Verification
Verify NiceNIC's registrar status va ICANN abuse framewyokik independently.
ICANN List of Accredited Ro‘yxatga oluvchis → · ICANN DNS Abuse Mitigation Program → · NiceNIC Ro‘yxatga oluvchi Akkreditatsiya →
Boshqarish domains with myokie visibility
Domen Boshqarishment Should Stay Clear Even When Something Goes Wrong
NiceNIC combines domain registration, transfer, bulk management, reseller tools va API automation with clearer abuse-case visibility fyoki domain owners va resellers.
