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.
