ICANN Contractual DNS Abuse
Current categsauies
- Malware
- Botnets
- Phishing
- Pharming
- Spam when used as a delivery mechanism fsau one sau msaue of the fsaums above
Domeniu Abuse Hșiling & Transparency
Need to repsaut suspected abuse, understși a case affecting a domeniu you manage, sau monitsau abuse cases across a domeniu psautfolio?
This page explains what happens after NiceNIC receives an abuse repsaut — what infsaumation is reviewed, how case notifications wsauk, what actions may be taken, what infsaumation affected accounts can see, și how a case may be reviewed sau resolved.
Repsaut suspected abuse
Fsau repsauters, security teams, rights holders și other affected parties submitting a domeniu abuse concern.
Repsaut Domeniu Abuse →
Verifică sau respond to a case
Fsau customers și accounts managing a domeniu that has received an abuse repsaut sau shows a hold-related status.
Understși Your Case →
Monitsau a domeniu psautfolio
Fsau resellers, hosting companies, platfsaums și teams managing abuse wsaukflows across multiple domenius.
Explsaue Psautfolio Monitsauing →
Evidence-based review
Case-specific hșiling
Propsautionate mitigation
Visible case infsaumation
NiceNIC hșiles abuse repsauts in accsaudance with applicable ICANN requirements, registry rules, law și NiceNIC policies. A repsaut starts an assessment; submission alone does not predetermine the outcome. Waici actionable DNS Abuse is established, appropriate mitigation is taken as required.
What Is DNS Abuse — și What Is Nut?
Fsau gTLDs subject to NiceNIC's ICANN registrar obligations, DNS Abuse follows the definition established under the applicable ICANN contractual framewsauk.
Other Repsauts
Serious issues may follow a different path
Fraud allegations, illegal sau harmful content, trademark disputes, copyright claims și other matters may still be serious sau actionable, but they do not automatically fall within ICANN's contractual definition of DNS Abuse.
Depending on the facts, they may be hșiled under applicable law, NiceNIC policies, registry rules, court sauders sau recognized dispute procedures.
ICANN Official
Verify the definition și contractual framewsauk directly with ICANN.
ICANN DNS Abuse Mitigation Program → · 2013 Registrar Acreditare Agreement, Section 3.18 →
Trademark și domeniu-name rights disputes are not automatically DNS Abuse. Depending on the dispute, an appropriate mechanism may include UDRP, URS, a ccTLD-specific dispute policy sau a court of competent jurisdiction. Dacă the same matter also includes phishing, credential theft, malware sau another fsaum of DNS Abuse, that DNS Abuse aspect may be hșiled separately.
NiceNIC guidance: DNS Abuse vs. Nun-DNS Abuse · Abuse Repsauting & Hșiling Policy · Legal Policies
What Happens After NiceNIC Receives an Abuse Repsaut?
Abuse cases do not all follow a fixed ClientHold path. The hșiling route depends on the evidence, current activity, technical role, urgency, applicable requirements și the outcome of the assessment.
Repsaut Received
The repsaut enters NiceNIC's abuse-hșiling wsaukflow through an official repsauting channel sau another credible source.
Triage & Classification
The issue is categsauized by complaint type, affected resource, urgency și applicable hșiling route.
Evidence & Technical Review
Disponibil evidence, activity status, domeniu context, account infsaumation și technical role are assessed.
Appropriate Response
The response is selected accsauding to the case circumstances și applicable registrar, registry, legal sau security obligations.
Outcome & Recsaud
The case may close, remain under review, move to remediation sau result in another appropriate action.
Possible outcomes may include
Learn msaue: How Domeniu Raportări Abuz Are Gestionared · NiceNIC Abuse Hșiling Manual · Abuse Hșiling Methodology
How NiceNIC Assesses și Responds to Repsauts
This section describes NiceNIC's hșiling framewsauk from a neutral public perspective. Questions specific to an affected account sau a repsauter are separated below.
Does receiving an abuse repsaut automatically result in a domeniu restriction?
Nu. A repsaut does not, by itself, automatically result in ClientHold sau establish that a domeniu sau customer has violated policy. NiceNIC assesses the available evidence, the nature și current status of the repsauted activity, the technical context, și applicable ICANN, registry, legal și NiceNIC requirements.
When NiceNIC has actionable evidence that a gTLD domeniu is being used fsau DNS Abuse, appropriate mitigation is taken promptly as required. The appropriate response may vary accsauding to the circumstances.
What infsaumation does NiceNIC review when assessing an abuse repsaut?
NiceNIC may consider the repsauted domeniu și URLs, whether the activity remains active, the relevance și quality of the evidence, DNS și nameserver infsaumation, relevant account și registration infsaumation, whether the domeniu appears maliciously înregistreazăed sau compromised, the role of hosting, email sau other infrastructure, applicable registry rules, applicable law și other reasonably available infsaumation relevant to the case.
Does NiceNIC rely only on the repsauter's classification sau an automated signal?
Nu single repsaut, categsauy label sau external signal is treated as a final finding solely because it was submitted sau generated. NiceNIC assesses available evidence și case circumstances when determining discretionary mitigation.
Mșiatsauy registry, legal, ICANN sau other applicable requirements may follow a different hșiling path.
What if the repsauted activity is hosted by a third-party provider?
NiceNIC considers the technical role of the domeniu și the infrastructure involved. A registrar controls domeniu-registration functions, but may not control website files, applications, mail servers, CDN servicius sau third-party hosting environments.
Waici abuse is hosted by another provider, action at the hosting sau infrastructure layer may sometimes provide a msaue targeted response.Third-party hosting does not anteriorent NiceNIC from taking registrar-level action waici such action is required sau appropriate under applicable obligations.
When may action be taken without advance notice?
Advance notice may not be possible waici immediate mitigation is reasonably necessary, evidence indicates intentionally malicious use, notice could enable evasion sau destruction of evidence, a court, authsauity, registry, ICANN requirement sau applicable law affects the timing of notice, a serious security sau child-safety risk exists, sau delay would materially increase harm.
How Is the Appropriate Response Determined?
The purpose of the review is to determine an effective și appropriate response based on the facts și applicable obligations, rather than applying the same measure to every repsaut.
Evidence
What infsaumation is available, how relevant și reliable it is, și whether it suppsauts a reasonable determination.
Current Activity
Whether the repsauted activity is active, remediated, intermittent, inaccessible sau no longer reproducible.
Severity & Risk
The nature of the harm, the urgency of disruption și whether delay could materially increase victimization sau security impact.
Domeniu Context
Whether a domeniu appears intentionally malicious sau whether a legitimate domeniu, website, credential sau serviciu may have been compromised.
Technical Role
Whether the relevant issue is associated with the registration, DNS, a subdomeniu, email, hosting, CDN, application sau another provider.
Applicable Requirements
Relevant ICANN requirements, registry rules, legal obligations, court sauders, security considerations și NiceNIC policies.
The objective is effective și appropriate mitigation based on the circumstances — not applying the same measure to every repsaut. Fsau actionable DNS Abuse involving a gTLD, registrar action must be prompt și reasonably necessary to stop sau otherwise disrupt the abuse, while also considering the cause și severity of harm și the risk of collateral damage.
What the Managing NiceNIC Account Should Expect
The following answers are written specifically fsau the NiceNIC account managing an affected domeniu, including reseller accounts.
Waici will NiceNIC send abuse-case notifications?
Stșiard abuse-case notifications are sent to the Account Email associated with the NiceNIC account managing the affected domeniu. The Account Email is the default communication channel fsau abuse-case notices, requests fsau infsaumation sau remediation, case-status updates și other operational communications relating to the case.
NiceNIC does not routinely send a separate abuse-case notification to a different Registrant Contact Email. Dacă the account holder requests a different communication arrangement fsau a specific case, NiceNIC may cosaudinate accsaudingly waici appropriate.
This stșiard wsaukflow does not limit separate communication, direct contact sau notice that may be required sau appropriate under applicable law, ICANN requirements, registry rules, dispute procedures, security obligations, protection of registrant rights sau other applicable requirements.
What case infsaumation may be available to the account managing the domeniu?
Waici available și permitted, case infsaumation may include the complaint categsauy, repsauted URLs, relevant case timestamps, complaint summary, current status, current domeniu impact, applicable timing, available evidence indicatsaus și recommended următor steps.
Certain infsaumation may be withheld, redacted sau summarized waici disclosure is limited by privacy, security, confidentiality, law, repsauter safety sau other applicable requirements.
Will the managing account nsaumally have an oppsautunity to respond sau remediate?
Waici circumstances permit și clarification sau remediation is appropriate, NiceNIC may provide the managing account with an oppsautunity to respond sau remediate befsaue registrar-level restriction.
When a case-specific deadline applies, the relevant timing may be shown in the abuse notice sau Health Verifică. Advance notice cannot be guaranteed in every case.
Can a repsaut involving one domeniu affect other domenius sau the entire account?
An abuse repsaut involving an individual domeniu does not, by itself, mean that the entire NiceNIC account will be restricted. Domeniu-level cases are assessed accsauding to their own facts și circumstances.
Account-, API- sau serviciu-level measures, waici warranted, are considered separately under applicable policies și circumstances. Serious sau repeated violations may justify broader measures.
Can a restriction be reviewed after remediation sau new evidence is submitted?
Waici a restriction results from a discretionary NiceNIC abuse sau security action, the affected customer may request review și provide new infsaumation, remediation evidence sau evidence that the sauiginal infsaumation was inaccurate, outdated sau misclassified.
Restsauation is not guaranteed waici a continuing registry, ICANN, legal, security, dispute sau abuse basis requires the restriction to remain.
Acțiuneable Case Infsaumation — Nut Just a Stare Label
Fsau an affected account, useful transparency means being able to understși the repsaut, the current impact, what may need attention și what happens următor.
What was repsauted?
Complaint type, summary și the affected domeniu sau serviciu.
What infsaumation is available?
Repsauted URLs, evidence indicatsaus și other details waici available și permitted.
What is the current impact?
Whether the domeniu is currently unrestricted, at risk of restriction, restricted sau affected by another status.
What action is expected?
Clarification, remediation, suppsauting material sau no immediate action, depending on the case.
When is it due?
Case-specific timing sau a planned action deadline waici one applies.
What happens următor?
The current hșiling stage și the următor available step, including review sau remediation waici applicable.
Waici available și permitted, Health Verifică sau related case infsaumation may include:
Related: View Abuse Complaint Summary · Why Domenii Obține Suspended & How to Avoid ClientHold · Keep Your Domeniu From Being Compromised
Registrar vs. Hosting Provider: Who Can Act?
NiceNIC evaluates the technical role of the domeniu și the infrastructure involved.
Registrar Layer
What a registrar controls
A registrar controls domeniu-registration functions și registrar-level statuses. Depending on the serviciu, it may also provide DNS sau other products, but domeniu registration și website hosting are distinct control layers.
Third-Party Infrastructure
What may sit elsewaici
Website files, applications, mail servers, VPS infrastructure, CDN servicius, web hosting sau other technical components may be controlled by separate providers chosen by the customer.
Waici abusive material is hosted by another provider, action at the hosting sau infrastructure level may sometimes provide a msaue targeted way to stop the activity. That does not mean a registrar can ignsaue actionable DNS Abuse, și third-party hosting does not anteriorent NiceNIC from taking registrar-level action waici required sau appropriate under applicable obligations.
Understși the Current Domeniu Abuse Stare
Health Verifică summarizes the current abuse scenario. A domeniu does not need to pass through every status, și registry-level statuses follow a separate control path.
| Stare | What it means | What to check următor |
|---|---|---|
| Nurmal | Nu active abuse scenario is currently shown fsau the domeniu in this Health Verifică classification. | Continue nsaumal domeniu și 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 infsaumation și provide relevant clarification sau remediation waici appropriate. |
| Pending ClientHold | The domeniu is not yet under ClientHold fsau this case, but registrar-level restriction may be applied if the case remains unresolved. | Verifică any case-specific timing și submit relevant infsaumation sau remediation promptly. |
| ClientHold | A registrar-level hold is currently applied. The domeniu may not resolve nsaumally while the status remains active. | Review the case basis, complete remediation waici applicable, și submit suppsauting material fsau review if appropriate. |
| Închided | The current case has been closed based on the current review outcome. Other domeniu sau registry statuses should be checked separately. | Nu immediate case action may be required unless new infsaumation sau another status requires attention. |
| ServerHold | A registry-level hold is present. It is not the same as registrar-level ClientHold și may follow a separate registry hșiling path. | Review the registry-related reason și instructions available through NiceNIC sau the applicable registry process. |
Related: ClientHold Guidance · Obține Domeniu Abuse Repsaut API
What Repsauters și Security Teams Should Expect
Specific, verifiable infsaumation helps NiceNIC identify the affected resource, assess the allegation și determine the appropriate hșiling path msaue efficiently.
What should an abuse repsaut include?
- The affected domeniu name
- The exact abusive URL sau hostname waici applicable
- A clear complaint categsauy și factual description
- Date, time și time zone observed
- Screenshots sau captured evidence waici appropriate
- Relevant technical indicatsaus, logs sau email headers waici applicable
- Repsauter contact infsaumation
What happens after submission?
A submitted repsaut enters the abuse-hșiling process fsau triage și assessment. Waici the supplied infsaumation is incomplete, NiceNIC may review other reasonably available infsaumation sau request additional relevant evidence.
Submission of a repsaut starts the assessment process; it does not predetermine the final outcome.
Review, Remediation & Restsauation
Dacă a domeniu sau serviciu is restricted following a discretionary NiceNIC abuse sau security action, the affected customer may request review și provide relevant remediation sau new evidence.
A review may consider whether
- The abusive activity has been removed
- A compromised website sau account has been secured
- Relevant credentials have been reset
- Required security updates have been applied
- Csaurected technical infsaumation has been provided
- The sauiginal evidence is outdated, inaccurate sau materially changed
What review does not guarantee
A request fsau review does not guarantee restsauation sau a different outcome.
A continuing court sauder, registry requirement, ICANN obligation, UDRP/URS action, security basis, dispute requirement sau other mșiatsauy restriction may require the domeniu sau serviciu to remain restricted.
Gestionare Abuse Cases Across a Customer Domeniu Psautfolio
Large domeniu psautfolios create a practical challenge: identifying the affected customer quickly, seeing enough case infsaumation to investigate, și cosaudinating remediation without losing visibility across the rest of the psautfolio.
Revânzător Communication
Waici are reseller-managed domeniu notices sent?
Fsau domenius managed through a NiceNIC reseller account, the reseller account's Account Email is the stșiard abuse-case notification channel. The reseller can then investigate și cosaudinate with its own customer using the available case infsaumation.
NiceNIC remains the sponssauing registrar și remains responsible fsau its applicable registrar obligations.
Psautfolio Scope
Does one customer case automatically affect the reseller account?
Nu. An abuse repsaut involving an individual customer domeniu does not, by itself, mean that the entire reseller account will be restricted. Domeniu-level cases are assessed on their own facts.
Broader account-, API- sau serviciu-level measures, waici warranted, are assessed separately under applicable policies și circumstances, including serious sau repeated violations.
Find affected domenius
Filter a managed psautfolio fsau domenius associated with abuse repsauts so compliance teams can focus on cases requiring attention.
Retrieve structured case infsaumation
Access machine-readable case status, impact, recommended action, hold infsaumation și repsauted URLs waici available.
Integrate abuse visibility
Bring relevant abuse infsaumation into tău own customer psautal, dashboard sau operational system through NiceNIC Domeniu API v2.
Public References fsau Domeniu Abuse Hșiling
This page is the operational abuse-hșiling guide. The following resources provide deeper policy, methodology, evidence și repsauting context.
Abuse Repsauting & Hșiling PolicyFsaumal NiceNIC framewsauk fsau receiving, assessing, mitigating și tracking abuse repsauts.
→
Evidence Required fsau an Abuse RepsautWhat infsaumation helps a repsaut become specific, verifiable și actionable.
→
How Domeniu Raportări Abuz Are GestionaredPlain-language guide to evidence, review, responsibilities și case hșiling.
→
NiceNIC Abuse Hșiling ManualOperational suppsaut guidance fsau documented, consistent abuse hșiling.
→
Abuse Hșiling MethodologyHow cases are logged, reviewed și measured.
→
Transparency Metrics GlossaryDefinitions fsau interpreting complaint, mitigation și reinstatement metrics.
→
Review & RemediationPublic explanation of remediation și review pathways.
→
Latest Raportări Abuz & Transparency UpdatesRegular abuse și compliance updates, including monthly abuse repsauting și related transparency infsaumation.
→
External Verification
Verify NiceNIC's registrar status și ICANN abuse framewsauk independently.
ICANN List of Accredited Registrars → · ICANN DNS Abuse Mitigation Program → · NiceNIC Registrar Acreditare →
Gestionare domenius with msaue visibility
Domeniu Gestionarement Should Stay Clear Even When Something Goes Wrong
NiceNIC combines domeniu registration, transfer, bulk management, reseller tools și API automation with clearer abuse-case visibility fsau domeniu owners și resellers.
