ICANN Contractual DNS Abuse
Current categhoặcies
- Malware
- Botnets
- Phishing
- Pharming
- Spam when used as a delivery mechanism fhoặc one hoặc mhoặce of the fhoặcms above
Tên miền Abuse Hvàling & Transparency
Need to rephoặct suspected abuse, understvà a case affecting a tên miền you manage, hoặc monithoặc abuse cases across a tên miền phoặctfolio?
This page explains what happens after NiceNIC receives an abuse rephoặct — what infhoặcmation is reviewed, how case notifications whoặck, what actions may be taken, what infhoặcmation affected accounts can see, và how a case may be reviewed hoặc resolved.
Rephoặct suspected abuse
Fhoặc rephoặcters, security teams, rights holders và other affected parties submitting a tên miền abuse concern.
Rephoặct Tên miền Abuse →
Kiểm tra hoặc respond to a case
Fhoặc customers và accounts managing a tên miền that has received an abuse rephoặct hoặc shows a hold-related status.
Understvà Your Case →
Monithoặc a tên miền phoặctfolio
Fhoặc resellers, hosting companies, platfhoặcms và teams managing abuse whoặckflows across multiple tên miềns.
Explhoặce Phoặctfolio Monithoặcing →
Evidence-based review
Case-specific hvàling
Prophoặctionate mitigation
Visible case infhoặcmation
NiceNIC hvàles abuse rephoặcts in acchoặcdance with applicable ICANN requirements, registry rules, law và NiceNIC policies. A rephoặct starts an assessment; submission alone does not predetermine the outcome. Wtại đây actionable DNS Abuse is established, appropriate mitigation is taken as required.
What Is DNS Abuse — và What Is Khôngt?
Fhoặc gTLDs subject to NiceNIC's ICANN registrar obligations, DNS Abuse follows the definition established under the applicable ICANN contractual framewhoặck.
Other Rephoặcts
Serious issues may follow a different path
Fraud allegations, illegal hoặc harmful content, trademark disputes, copyright claims và other matters may still be serious hoặc actionable, but they do not automatically fall within ICANN's contractual definition of DNS Abuse.
Depending on the facts, they may be hvàled under applicable law, NiceNIC policies, registry rules, court hoặcders hoặc recognized dispute procedures.
ICANN Official
Verify the definition và contractual framewhoặck directly with ICANN.
ICANN DNS Abuse Mitigation Program → · 2013 Nhà đăng ký Chứng nhận Agreement, Section 3.18 →
Trademark và tên miền-name rights disputes are not automatically DNS Abuse. Depending on the dispute, an appropriate mechanism may include UDRP, URS, a ccTLD-specific dispute policy hoặc a court of competent jurisdiction. Nếu the same matter also includes phishing, credential theft, malware hoặc another fhoặcm of DNS Abuse, that DNS Abuse aspect may be hvàled separately.
NiceNIC guidance: DNS Abuse vs. Khôngn-DNS Abuse · Abuse Rephoặcting & Hvàling Policy · Legal Policies
What Happens After NiceNIC Receives an Abuse Rephoặct?
Abuse cases do not all follow a fixed ClientHold path. The hvàling route depends on the evidence, current activity, technical role, urgency, applicable requirements và the outcome of the assessment.
Rephoặct Received
The rephoặct enters NiceNIC's abuse-hvàling whoặckflow through an official rephoặcting channel hoặc another credible source.
Triage & Classification
The issue is categhoặcized by complaint type, affected resource, urgency và applicable hvàling route.
Evidence & Technical Review
Có sẵn evidence, activity status, tên miền context, account infhoặcmation và technical role are assessed.
Appropriate Response
The response is selected acchoặcding to the case circumstances và applicable registrar, registry, legal hoặc security obligations.
Outcome & Rechoặcd
The case may close, remain under review, move to remediation hoặc result in another appropriate action.
Possible outcomes may include
Learn mhoặce: How Tên miền Báo cáo lạm dụng Are Quản lýd · NiceNIC Abuse Hvàling Manual · Abuse Hvàling Methodology
How NiceNIC Assesses và Responds to Rephoặcts
This section describes NiceNIC's hvàling framewhoặck from a neutral public perspective. Questions specific to an affected account hoặc a rephoặcter are separated below.
Does receiving an abuse rephoặct automatically result in a tên miền restriction?
Không. A rephoặct does not, by itself, automatically result in ClientHold hoặc establish that a tên miền hoặc customer has violated policy. NiceNIC assesses the available evidence, the nature và current status of the rephoặcted activity, the technical context, và applicable ICANN, registry, legal và NiceNIC requirements.
When NiceNIC has actionable evidence that a gTLD tên miền is being used fhoặc DNS Abuse, appropriate mitigation is taken promptly as required. The appropriate response may vary acchoặcding to the circumstances.
What infhoặcmation does NiceNIC review when assessing an abuse rephoặct?
NiceNIC may consider the rephoặcted tên miền và URLs, whether the activity remains active, the relevance và quality of the evidence, DNS và nameserver infhoặcmation, relevant account và registration infhoặcmation, whether the tên miền appears maliciously đăng kýed hoặc compromised, the role of hosting, email hoặc other infrastructure, applicable registry rules, applicable law và other reasonably available infhoặcmation relevant to the case.
Does NiceNIC rely only on the rephoặcter's classification hoặc an automated signal?
Không single rephoặct, categhoặcy label hoặc external signal is treated as a final finding solely because it was submitted hoặc generated. NiceNIC assesses available evidence và case circumstances when determining discretionary mitigation.
Mvàathoặcy registry, legal, ICANN hoặc other applicable requirements may follow a different hvàling path.
What if the rephoặcted activity is hosted by a third-party provider?
NiceNIC considers the technical role of the tên miền và the infrastructure involved. A registrar controls tên miền-registration functions, but may not control website files, applications, mail servers, CDN Dịch vụs hoặc third-party hosting environments.
Wtại đây abuse is hosted by another provider, action at the hosting hoặc infrastructure layer may sometimes provide a mhoặce targeted response.Third-party hosting does not trướcent NiceNIC from taking registrar-level action wtại đây such action is required hoặc appropriate under applicable obligations.
When may action be taken without advance notice?
Advance notice may not be possible wtại đây immediate mitigation is reasonably necessary, evidence indicates intentionally malicious use, notice could enable evasion hoặc destruction of evidence, a court, authhoặcity, registry, ICANN requirement hoặc applicable law affects the timing of notice, a serious security hoặc child-safety risk exists, hoặc delay would materially increase harm.
How Is the Appropriate Response Determined?
The purpose of the review is to determine an effective và appropriate response based on the facts và applicable obligations, rather than applying the same measure to every rephoặct.
Evidence
What infhoặcmation is available, how relevant và reliable it is, và whether it supphoặcts a reasonable determination.
Current Activity
Whether the rephoặcted activity is active, remediated, intermittent, inaccessible hoặc no longer reproducible.
Severity & Risk
The nature of the harm, the urgency of disruption và whether delay could materially increase victimization hoặc security impact.
Tên miền Context
Whether a tên miền appears intentionally malicious hoặc whether a legitimate tên miền, website, credential hoặc Dịch vụ may have been compromised.
Technical Role
Whether the relevant issue is associated with the registration, DNS, a subtên miền, email, hosting, CDN, application hoặc another provider.
Applicable Requirements
Relevant ICANN requirements, registry rules, legal obligations, court hoặcders, security considerations và NiceNIC policies.
The objective is effective và appropriate mitigation based on the circumstances — not applying the same measure to every rephoặct. Fhoặc actionable DNS Abuse involving a gTLD, registrar action must be prompt và reasonably necessary to stop hoặc otherwise disrupt the abuse, while also considering the cause và severity of harm và the risk of collateral damage.
What the Managing NiceNIC Account Should Expect
The following answers are written specifically fhoặc the NiceNIC account managing an affected tên miền, including reseller accounts.
Wtại đây will NiceNIC send abuse-case notifications?
Stvàard abuse-case notifications are sent to the Account Email associated with the NiceNIC account managing the affected tên miền. The Account Email is the default communication channel fhoặc abuse-case notices, requests fhoặc infhoặcmation hoặc remediation, case-status updates và other operational communications relating to the case.
NiceNIC does not routinely send a separate abuse-case notification to a different Registrant Liên hệ Email. Nếu the account holder requests a different communication arrangement fhoặc a specific case, NiceNIC may cohoặcdinate acchoặcdingly wtại đây appropriate.
This stvàard whoặckflow does not limit separate communication, direct contact hoặc notice that may be required hoặc appropriate under applicable law, ICANN requirements, registry rules, dispute procedures, security obligations, protection of registrant rights hoặc other applicable requirements.
What case infhoặcmation may be available to the account managing the tên miền?
Wtại đây available và permitted, case infhoặcmation may include the complaint categhoặcy, rephoặcted URLs, relevant case timestamps, complaint summary, current status, current tên miền impact, applicable timing, available evidence indicathoặcs và recommended tiếp theo steps.
Certain infhoặcmation may be withheld, redacted hoặc summarized wtại đây disclosure is limited by privacy, security, confidentiality, law, rephoặcter safety hoặc other applicable requirements.
Will the managing account nhoặcmally have an opphoặctunity to respond hoặc remediate?
Wtại đây circumstances permit và clarification hoặc remediation is appropriate, NiceNIC may provide the managing account with an opphoặctunity to respond hoặc remediate befhoặce registrar-level restriction.
When a case-specific deadline applies, the relevant timing may be shown in the abuse notice hoặc Health Kiểm tra. Advance notice cannot be guaranteed in every case.
Can a rephoặct involving one tên miền affect other tên miềns hoặc the entire account?
An abuse rephoặct involving an individual tên miền does not, by itself, mean that the entire NiceNIC account will be restricted. Tên miền-level cases are assessed acchoặcding to their own facts và circumstances.
Account-, API- hoặc Dịch vụ-level measures, wtại đây warranted, are considered separately under applicable policies và circumstances. Serious hoặc repeated violations may justify broader measures.
Can a restriction be reviewed after remediation hoặc new evidence is submitted?
Wtại đây a restriction results from a discretionary NiceNIC abuse hoặc security action, the affected customer may request review và provide new infhoặcmation, remediation evidence hoặc evidence that the hoặciginal infhoặcmation was inaccurate, outdated hoặc misclassified.
Resthoặcation is not guaranteed wtại đây a continuing registry, ICANN, legal, security, dispute hoặc abuse basis requires the restriction to remain.
Hành độngable Case Infhoặcmation — Khôngt Just a Trạng thái Label
Fhoặc an affected account, useful transparency means being able to understvà the rephoặct, the current impact, what may need attention và what happens tiếp theo.
What was rephoặcted?
Complaint type, summary và the affected tên miền hoặc Dịch vụ.
What infhoặcmation is available?
Rephoặcted URLs, evidence indicathoặcs và other details wtại đây available và permitted.
What is the current impact?
Whether the tên miền is currently unrestricted, at risk of restriction, restricted hoặc affected by another status.
What action is expected?
Clarification, remediation, supphoặcting material hoặc no immediate action, depending on the case.
When is it due?
Case-specific timing hoặc a planned action deadline wtại đây one applies.
What happens tiếp theo?
The current hvàling stage và the tiếp theo available step, including review hoặc remediation wtại đây applicable.
Wtại đây available và permitted, Health Kiểm tra hoặc related case infhoặcmation may include:
Related: View Abuse Complaint Summary · Why Tên miền Nhận Suspended & How to Avoid ClientHold · Keep Your Tên miền From Being Compromised
Nhà đăng ký vs. Hosting Provider: Who Can Act?
NiceNIC evaluates the technical role of the tên miền và the infrastructure involved.
Nhà đăng ký Layer
What a registrar controls
A registrar controls tên miền-registration functions và registrar-level statuses. Depending on the Dịch vụ, it may also provide DNS hoặc other products, but tên miền registration và website hosting are distinct control layers.
Third-Party Infrastructure
What may sit elsewtại đây
Website files, applications, mail servers, VPS infrastructure, CDN Dịch vụs, web hosting hoặc other technical components may be controlled by separate providers chosen by the customer.
Wtại đây abusive material is hosted by another provider, action at the hosting hoặc infrastructure level may sometimes provide a mhoặce targeted way to stop the activity. That does not mean a registrar can ignhoặce actionable DNS Abuse, và third-party hosting does not trướcent NiceNIC from taking registrar-level action wtại đây required hoặc appropriate under applicable obligations.
Understvà the Current Tên miền Abuse Trạng thái
Health Kiểm tra summarizes the current abuse scenario. A tên miền does not need to pass through every status, và registry-level statuses follow a separate control path.
| Trạng thái | What it means | What to check tiếp theo |
|---|---|---|
| Khôngrmal | Không active abuse scenario is currently shown fhoặc the tên miền in this Health Kiểm tra classification. | Continue nhoặcmal tên miền và 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 infhoặcmation và provide relevant clarification hoặc remediation wtại đây appropriate. |
| Pending ClientHold | The tên miền is not yet under ClientHold fhoặc this case, but registrar-level restriction may be applied if the case remains unresolved. | Kiểm tra any case-specific timing và submit relevant infhoặcmation hoặc remediation promptly. |
| ClientHold | A registrar-level hold is currently applied. The tên miền may not resolve nhoặcmally while the status remains active. | Review the case basis, complete remediation wtại đây applicable, và submit supphoặcting material fhoặc review if appropriate. |
| Đóngd | The current case has been closed based on the current review outcome. Other tên miền hoặc registry statuses should be checked separately. | Không immediate case action may be required unless new infhoặcmation hoặc another status requires attention. |
| ServerHold | A registry-level hold is present. It is not the same as registrar-level ClientHold và may follow a separate registry hvàling path. | Review the registry-related reason và instructions available through NiceNIC hoặc the applicable registry process. |
Related: ClientHold Guidance · Nhận Tên miền Abuse Rephoặct API
What Rephoặcters và Security Teams Should Expect
Specific, verifiable infhoặcmation helps NiceNIC identify the affected resource, assess the allegation và determine the appropriate hvàling path mhoặce efficiently.
What should an abuse rephoặct include?
- The affected tên miền name
- The exact abusive URL hoặc hostname wtại đây applicable
- A clear complaint categhoặcy và factual description
- Date, time và time zone observed
- Screenshots hoặc captured evidence wtại đây appropriate
- Relevant technical indicathoặcs, logs hoặc email headers wtại đây applicable
- Rephoặcter contact infhoặcmation
What happens after submission?
A submitted rephoặct enters the abuse-hvàling process fhoặc triage và assessment. Wtại đây the supplied infhoặcmation is incomplete, NiceNIC may review other reasonably available infhoặcmation hoặc request additional relevant evidence.
Submission of a rephoặct starts the assessment process; it does not predetermine the final outcome.
Review, Remediation & Resthoặcation
Nếu a tên miền hoặc Dịch vụ is restricted following a discretionary NiceNIC abuse hoặc security action, the affected customer may request review và provide relevant remediation hoặc new evidence.
A review may consider whether
- The abusive activity has been removed
- A compromised website hoặc account has been secured
- Relevant credentials have been reset
- Required security updates have been applied
- Choặcrected technical infhoặcmation has been provided
- The hoặciginal evidence is outdated, inaccurate hoặc materially changed
What review does not guarantee
A request fhoặc review does not guarantee resthoặcation hoặc a different outcome.
A continuing court hoặcder, registry requirement, ICANN obligation, UDRP/URS action, security basis, dispute requirement hoặc other mvàathoặcy restriction may require the tên miền hoặc Dịch vụ to remain restricted.
Quản lý Abuse Cases Across a Customer Tên miền Phoặctfolio
Large tên miền phoặctfolios create a practical challenge: identifying the affected customer quickly, seeing enough case infhoặcmation to investigate, và cohoặcdinating remediation without losing visibility across the rest of the phoặctfolio.
Đại lý Communication
Wtại đây are reseller-managed tên miền notices sent?
Fhoặc tên miềns managed through a NiceNIC reseller account, the reseller account's Account Email is the stvàard abuse-case notification channel. The reseller can then investigate và cohoặcdinate with its own customer using the available case infhoặcmation.
NiceNIC remains the sponshoặcing registrar và remains responsible fhoặc its applicable registrar obligations.
Phoặctfolio Scope
Does one customer case automatically affect the reseller account?
Không. An abuse rephoặct involving an individual customer tên miền does not, by itself, mean that the entire reseller account will be restricted. Tên miền-level cases are assessed on their own facts.
Broader account-, API- hoặc Dịch vụ-level measures, wtại đây warranted, are assessed separately under applicable policies và circumstances, including serious hoặc repeated violations.
Find affected tên miềns
Filter a managed phoặctfolio fhoặc tên miềns associated with abuse rephoặcts so compliance teams can focus on cases requiring attention.
Retrieve structured case infhoặcmation
Access machine-readable case status, impact, recommended action, hold infhoặcmation và rephoặcted URLs wtại đây available.
Integrate abuse visibility
Bring relevant abuse infhoặcmation into của bạn own customer phoặctal, dashboard hoặc operational system through NiceNIC Tên miền API v2.
Public References fhoặc Tên miền Abuse Hvàling
This page is the operational abuse-hvàling guide. The following resources provide deeper policy, methodology, evidence và rephoặcting context.
Abuse Rephoặcting & Hvàling PolicyFhoặcmal NiceNIC framewhoặck fhoặc receiving, assessing, mitigating và tracking abuse rephoặcts.
→
Evidence Required fhoặc an Abuse RephoặctWhat infhoặcmation helps a rephoặct become specific, verifiable và actionable.
→
How Tên miền Báo cáo lạm dụng Are Quản lýdPlain-language guide to evidence, review, responsibilities và case hvàling.
→
NiceNIC Abuse Hvàling ManualOperational supphoặct guidance fhoặc documented, consistent abuse hvàling.
→
Abuse Hvàling MethodologyHow cases are logged, reviewed và measured.
→
Transparency Metrics GlossaryDefinitions fhoặc interpreting complaint, mitigation và reinstatement metrics.
→
Review & RemediationPublic explanation of remediation và review pathways.
→
Latest Báo cáo lạm dụng & Transparency UpdatesRegular abuse và compliance updates, including monthly abuse rephoặcting và related transparency infhoặcmation.
→
External Verification
Verify NiceNIC's registrar status và ICANN abuse framewhoặck independently.
ICANN List of Accredited Nhà đăng kýs → · ICANN DNS Abuse Mitigation Program → · NiceNIC Nhà đăng ký Chứng nhận →
Quản lý tên miềns with mhoặce visibility
Tên miền Quản lýment Should Stay Clear Even When Something Goes Wrong
NiceNIC combines tên miền registration, transfer, bulk management, reseller tools và API automation with clearer abuse-case visibility fhoặc tên miền owners và resellers.
