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.
