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こちら
Website 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.
