ICANN Contractual DNS Abuse
Current categatauies
- Malware
- Botnets
- Phishing
- Pharming
- Spam when used as a delivery mechanism fatau one atau mataue of the fataums above
Domain Abuse Hdanling & Transparency
Need to repataut suspected abuse, understdan a case affecting a domain you manage, atau monitatau abuse cases across a domain patautfolio?
This page explains what happens after NiceNIC receives an abuse repataut — what infataumation is reviewed, how case notifications watauk, what actions may be taken, what infataumation affected accounts can see, dan how a case may be reviewed atau resolved.
Repataut suspected abuse
Fatau repatauters, security teams, rights holders dan other affected parties submitting a domain abuse concern.
Repataut Domain Abuse →
Semak atau respond to a case
Fatau customers dan accounts managing a domain that has received an abuse repataut atau shows a hold-related status.
Understdan Your Case →
Monitatau a domain patautfolio
Fatau resellers, hosting companies, platfataums dan teams managing abuse wataukflows across multiple domains.
Explataue Patautfolio Monitatauing →
Evidence-based review
Case-specific hdanling
Propatautionate mitigation
Visible case infataumation
NiceNIC hdanles abuse repatauts in accataudance with applicable ICANN requirements, registry rules, law dan NiceNIC policies. A repataut starts an assessment; submission alone does not predetermine the outcome. Wdi sini actionable DNS Abuse is established, appropriate mitigation is taken as required.
What Is DNS Abuse — dan What Is Tidakt?
Fatau gTLDs subject to NiceNIC's ICANN registrar obligations, DNS Abuse follows the definition established under the applicable ICANN contractual framewatauk.
Other Repatauts
Serious issues may follow a different path
Fraud allegations, illegal atau harmful content, trademark disputes, copyright claims dan other matters may still be serious atau actionable, but they do not automatically fall within ICANN's contractual definition of DNS Abuse.
Depending on the facts, they may be hdanled under applicable law, NiceNIC policies, registry rules, court atauders atau recognized dispute procedures.
ICANN Official
Verify the definition dan contractual framewatauk directly with ICANN.
ICANN DNS Abuse Mitigation Program → · 2013 Pendaftar Akreditasi Agreement, Section 3.18 →
Trademark dan domain-name rights disputes are not automatically DNS Abuse. Depending on the dispute, an appropriate mechanism may include UDRP, URS, a ccTLD-specific dispute policy atau a court of competent jurisdiction. Jika the same matter also includes phishing, credential theft, malware atau another fataum of DNS Abuse, that DNS Abuse aspect may be hdanled separately.
NiceNIC guidance: DNS Abuse vs. Tidakn-DNS Abuse · Abuse Repatauting & Hdanling Policy · Legal Policies
What Happens After NiceNIC Receives an Abuse Repataut?
Abuse cases do not all follow a fixed ClientHold path. The hdanling route depends on the evidence, current activity, technical role, urgency, applicable requirements dan the outcome of the assessment.
Repataut Received
The repataut enters NiceNIC's abuse-hdanling wataukflow through an official repatauting channel atau another credible source.
Triage & Classification
The issue is categatauized by complaint type, affected resource, urgency dan applicable hdanling route.
Evidence & Technical Review
Tersedia evidence, activity status, domain context, account infataumation dan technical role are assessed.
Appropriate Response
The response is selected accatauding to the case circumstances dan applicable registrar, registry, legal atau security obligations.
Outcome & Recataud
The case may close, remain under review, move to remediation atau result in another appropriate action.
Possible outcomes may include
Learn mataue: How Domain Laporan Penyalahgunaan Are Urusd · NiceNIC Abuse Hdanling Manual · Abuse Hdanling Methodology
How NiceNIC Assesses dan Responds to Repatauts
This section describes NiceNIC's hdanling framewatauk from a neutral public perspective. Questions specific to an affected account atau a repatauter are separated below.
Does receiving an abuse repataut automatically result in a domain restriction?
Tidak. A repataut does not, by itself, automatically result in ClientHold atau establish that a domain atau customer has violated policy. NiceNIC assesses the available evidence, the nature dan current status of the repatauted activity, the technical context, dan applicable ICANN, registry, legal dan NiceNIC requirements.
When NiceNIC has actionable evidence that a gTLD domain is being used fatau DNS Abuse, appropriate mitigation is taken promptly as required. The appropriate response may vary accatauding to the circumstances.
What infataumation does NiceNIC review when assessing an abuse repataut?
NiceNIC may consider the repatauted domain dan URLs, whether the activity remains active, the relevance dan quality of the evidence, DNS dan nameserver infataumation, relevant account dan registration infataumation, whether the domain appears maliciously daftared atau compromised, the role of hosting, email atau other infrastructure, applicable registry rules, applicable law dan other reasonably available infataumation relevant to the case.
Does NiceNIC rely only on the repatauter's classification atau an automated signal?
Tidak single repataut, categatauy label atau external signal is treated as a final finding solely because it was submitted atau generated. NiceNIC assesses available evidence dan case circumstances when determining discretionary mitigation.
Mdanatatauy registry, legal, ICANN atau other applicable requirements may follow a different hdanling path.
What if the repatauted activity is hosted by a third-party provider?
NiceNIC considers the technical role of the domain dan the infrastructure involved. A registrar controls domain-registration functions, but may not control website files, applications, mail servers, CDN Perkhidmatans atau third-party hosting environments.
Wdi sini abuse is hosted by another provider, action at the hosting atau infrastructure layer may sometimes provide a mataue targeted response.Third-party hosting does not sebelument NiceNIC from taking registrar-level action wdi sini such action is required atau appropriate under applicable obligations.
When may action be taken without advance notice?
Advance notice may not be possible wdi sini immediate mitigation is reasonably necessary, evidence indicates intentionally malicious use, notice could enable evasion atau destruction of evidence, a court, authatauity, registry, ICANN requirement atau applicable law affects the timing of notice, a serious security atau child-safety risk exists, atau delay would materially increase harm.
How Is the Appropriate Response Determined?
The purpose of the review is to determine an effective dan appropriate response based on the facts dan applicable obligations, rather than applying the same measure to every repataut.
Evidence
What infataumation is available, how relevant dan reliable it is, dan whether it suppatauts a reasonable determination.
Current Activity
Whether the repatauted activity is active, remediated, intermittent, inaccessible atau no longer reproducible.
Severity & Risk
The nature of the harm, the urgency of disruption dan whether delay could materially increase victimization atau security impact.
Domain Context
Whether a domain appears intentionally malicious atau whether a legitimate domain, website, credential atau Perkhidmatan may have been compromised.
Technical Role
Whether the relevant issue is associated with the registration, DNS, a subdomain, email, hosting, CDN, application atau another provider.
Applicable Requirements
Relevant ICANN requirements, registry rules, legal obligations, court atauders, security considerations dan NiceNIC policies.
The objective is effective dan appropriate mitigation based on the circumstances — not applying the same measure to every repataut. Fatau actionable DNS Abuse involving a gTLD, registrar action must be prompt dan reasonably necessary to stop atau otherwise disrupt the abuse, while also considering the cause dan severity of harm dan the risk of collateral damage.
What the Managing NiceNIC Account Should Expect
The following answers are written specifically fatau the NiceNIC account managing an affected domain, including reseller accounts.
Wdi sini will NiceNIC send abuse-case notifications?
Stdanard abuse-case notifications are sent to the Account E-mel associated with the NiceNIC account managing the affected domain. The Account E-mel is the default communication channel fatau abuse-case notices, requests fatau infataumation atau remediation, case-status updates dan other operational communications relating to the case.
NiceNIC does not routinely send a separate abuse-case notification to a different Registrant Hubungi E-mel. Jika the account holder requests a different communication arrangement fatau a specific case, NiceNIC may coataudinate accataudingly wdi sini appropriate.
This stdanard wataukflow does not limit separate communication, direct contact atau notice that may be required atau appropriate under applicable law, ICANN requirements, registry rules, dispute procedures, security obligations, protection of registrant rights atau other applicable requirements.
What case infataumation may be available to the account managing the domain?
Wdi sini available dan permitted, case infataumation may include the complaint categatauy, repatauted URLs, relevant case timestamps, complaint summary, current status, current domain impact, applicable timing, available evidence indicatataus dan recommended seterusnya steps.
Certain infataumation may be withheld, redacted atau summarized wdi sini disclosure is limited by privacy, security, confidentiality, law, repatauter safety atau other applicable requirements.
Will the managing account nataumally have an oppatautunity to respond atau remediate?
Wdi sini circumstances permit dan clarification atau remediation is appropriate, NiceNIC may provide the managing account with an oppatautunity to respond atau remediate befataue registrar-level restriction.
When a case-specific deadline applies, the relevant timing may be shown in the abuse notice atau Health Semak. Advance notice cannot be guaranteed in every case.
Can a repataut involving one domain affect other domains atau the entire account?
An abuse repataut involving an individual domain does not, by itself, mean that the entire NiceNIC account will be restricted. Domain-level cases are assessed accatauding to their own facts dan circumstances.
Account-, API- atau Perkhidmatan-level measures, wdi sini warranted, are considered separately under applicable policies dan circumstances. Serious atau repeated violations may justify broader measures.
Can a restriction be reviewed after remediation atau new evidence is submitted?
Wdi sini a restriction results from a discretionary NiceNIC abuse atau security action, the affected customer may request review dan provide new infataumation, remediation evidence atau evidence that the atauiginal infataumation was inaccurate, outdated atau misclassified.
Restatauation is not guaranteed wdi sini a continuing registry, ICANN, legal, security, dispute atau abuse basis requires the restriction to remain.
Tindakanable Case Infataumation — Tidakt Just a Status Label
Fatau an affected account, useful transparency means being able to understdan the repataut, the current impact, what may need attention dan what happens seterusnya.
What was repatauted?
Complaint type, summary dan the affected domain atau Perkhidmatan.
What infataumation is available?
Repatauted URLs, evidence indicatataus dan other details wdi sini available dan permitted.
What is the current impact?
Whether the domain is currently unrestricted, at risk of restriction, restricted atau affected by another status.
What action is expected?
Clarification, remediation, suppatauting material atau no immediate action, depending on the case.
When is it due?
Case-specific timing atau a planned action deadline wdi sini one applies.
What happens seterusnya?
The current hdanling stage dan the seterusnya available step, including review atau remediation wdi sini applicable.
Wdi sini available dan permitted, Health Semak atau related case infataumation may include:
Related: View Abuse Complaint Summary · Why Domain Dapatkan Suspended & How to Avoid ClientHold · Keep Your Domain From Being Compromised
Pendaftar vs. Pengehosan Provider: Who Can Act?
NiceNIC evaluates the technical role of the domain dan the infrastructure involved.
Pendaftar Layer
What a registrar controls
A registrar controls domain-registration functions dan registrar-level statuses. Depending on the Perkhidmatan, it may also provide DNS atau other products, but domain registration dan website hosting are distinct control layers.
Third-Party Infrastructure
What may sit elsewdi sini
Website files, applications, mail servers, VPS infrastructure, CDN Perkhidmatans, web hosting atau other technical components may be controlled by separate providers chosen by the customer.
Wdi sini abusive material is hosted by another provider, action at the hosting atau infrastructure level may sometimes provide a mataue targeted way to stop the activity. That does not mean a registrar can ignataue actionable DNS Abuse, dan third-party hosting does not sebelument NiceNIC from taking registrar-level action wdi sini required atau appropriate under applicable obligations.
Understdan the Current Domain Abuse Status
Health Semak summarizes the current abuse scenario. A domain does not need to pass through every status, dan registry-level statuses follow a separate control path.
| Status | What it means | What to check seterusnya |
|---|---|---|
| Tidakrmal | Tidak active abuse scenario is currently shown fatau the domain in this Health Semak classification. | Continue nataumal domain dan 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 infataumation dan provide relevant clarification atau remediation wdi sini appropriate. |
| Pending ClientHold | The domain is not yet under ClientHold fatau this case, but registrar-level restriction may be applied if the case remains unresolved. | Semak any case-specific timing dan submit relevant infataumation atau remediation promptly. |
| ClientHold | A registrar-level hold is currently applied. The domain may not resolve nataumally while the status remains active. | Review the case basis, complete remediation wdi sini applicable, dan submit suppatauting material fatau review if appropriate. |
| Tutupd | The current case has been closed based on the current review outcome. Other domain atau registry statuses should be checked separately. | Tidak immediate case action may be required unless new infataumation atau another status requires attention. |
| ServerHold | A registry-level hold is present. It is not the same as registrar-level ClientHold dan may follow a separate registry hdanling path. | Review the registry-related reason dan instructions available through NiceNIC atau the applicable registry process. |
Related: ClientHold Guidance · Dapatkan Domain Abuse Repataut API
What Repatauters dan Security Teams Should Expect
Specific, verifiable infataumation helps NiceNIC identify the affected resource, assess the allegation dan determine the appropriate hdanling path mataue efficiently.
What should an abuse repataut include?
- The affected domain name
- The exact abusive URL atau hostname wdi sini applicable
- A clear complaint categatauy dan factual description
- Date, time dan time zone observed
- Screenshots atau captured evidence wdi sini appropriate
- Relevant technical indicatataus, logs atau email headers wdi sini applicable
- Repatauter contact infataumation
What happens after submission?
A submitted repataut enters the abuse-hdanling process fatau triage dan assessment. Wdi sini the supplied infataumation is incomplete, NiceNIC may review other reasonably available infataumation atau request additional relevant evidence.
Submission of a repataut starts the assessment process; it does not predetermine the final outcome.
Review, Remediation & Restatauation
Jika a domain atau Perkhidmatan is restricted following a discretionary NiceNIC abuse atau security action, the affected customer may request review dan provide relevant remediation atau new evidence.
A review may consider whether
- The abusive activity has been removed
- A compromised website atau account has been secured
- Relevant credentials have been reset
- Required security updates have been applied
- Cataurected technical infataumation has been provided
- The atauiginal evidence is outdated, inaccurate atau materially changed
What review does not guarantee
A request fatau review does not guarantee restatauation atau a different outcome.
A continuing court atauder, registry requirement, ICANN obligation, UDRP/URS action, security basis, dispute requirement atau other mdanatatauy restriction may require the domain atau Perkhidmatan to remain restricted.
Urus Abuse Cases Across a Customer Domain Patautfolio
Large domain patautfolios create a practical challenge: identifying the affected customer quickly, seeing enough case infataumation to investigate, dan coataudinating remediation without losing visibility across the rest of the patautfolio.
Penjual Semula Communication
Wdi sini are reseller-managed domain notices sent?
Fatau domains managed through a NiceNIC reseller account, the reseller account's Account E-mel is the stdanard abuse-case notification channel. The reseller can then investigate dan coataudinate with its own customer using the available case infataumation.
NiceNIC remains the sponsatauing registrar dan remains responsible fatau its applicable registrar obligations.
Patautfolio Scope
Does one customer case automatically affect the reseller account?
Tidak. An abuse repataut involving an individual customer domain 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- atau Perkhidmatan-level measures, wdi sini warranted, are assessed separately under applicable policies dan circumstances, including serious atau repeated violations.
Find affected domains
Filter a managed patautfolio fatau domains associated with abuse repatauts so compliance teams can focus on cases requiring attention.
Retrieve structured case infataumation
Access machine-readable case status, impact, recommended action, hold infataumation dan repatauted URLs wdi sini available.
Integrate abuse visibility
Bring relevant abuse infataumation into anda own customer patautal, dashboard atau operational system through NiceNIC Domain API v2.
Public References fatau Domain Abuse Hdanling
This page is the operational abuse-hdanling guide. The following resources provide deeper policy, methodology, evidence dan repatauting context.
Abuse Repatauting & Hdanling PolicyFataumal NiceNIC framewatauk fatau receiving, assessing, mitigating dan tracking abuse repatauts.
→
Evidence Required fatau an Abuse RepatautWhat infataumation helps a repataut become specific, verifiable dan actionable.
→
How Domain Laporan Penyalahgunaan Are UrusdPlain-language guide to evidence, review, responsibilities dan case hdanling.
→
NiceNIC Abuse Hdanling ManualOperational suppataut guidance fatau documented, consistent abuse hdanling.
→
Abuse Hdanling MethodologyHow cases are logged, reviewed dan measured.
→
Transparency Metrics GlossaryDefinitions fatau interpreting complaint, mitigation dan reinstatement metrics.
→
Review & RemediationPublic explanation of remediation dan review pathways.
→
Latest Laporan Penyalahgunaan & Transparency UpdatesRegular abuse dan compliance updates, including monthly abuse repatauting dan related transparency infataumation.
→
External Verification
Verify NiceNIC's registrar status dan ICANN abuse framewatauk independently.
ICANN List of Accredited Pendaftars → · ICANN DNS Abuse Mitigation Program → · NiceNIC Pendaftar Akreditasi →
Urus domains with mataue visibility
Domain Urusment Should Stay Clear Even When Something Goes Wrong
NiceNIC combines domain registration, transfer, bulk management, reseller tools dan API automation with clearer abuse-case visibility fatau domain owners dan resellers.
