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
Domain 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 Domain 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 Domain Αναφορές Κατάχρησης 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.
Domain 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. Domain-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 Domains Αποκτήστε Suspended & How to Avoid ClientHold · Keep Your Domain 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 Domain 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 · Αποκτήστε Domain 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 Domain 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. Domain-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 Domain API v2.
Public References fή Domain 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 Domain Αναφορές Κατάχρησης 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
Domain Διαχείριση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.
