ICANN Contractual DNS Abuse
Current categveyaies
- Malware
- Botnets
- Phishing
- Pharming
- Spam when used as a delivery mechanism fveya one veya mveyae of the fveyams above
Alan Adı Abuse Hveling & Transparency
Need to repveyat suspected abuse, understve a case affecting a domain you manage, veya monitveya abuse cases across a domain pveyatfolio?
This page explains what happens after NiceNIC receives an abuse repveyat — what infveyamation is reviewed, how case notifications wveyak, what actions may be taken, what infveyamation affected accounts can see, ve how a case may be reviewed veya resolved.
Repveyat suspected abuse
Fveya repveyaters, security teams, rights holders ve other affected parties submitting a domain abuse concern.
Repveyat Alan Adı Abuse →
Kontrol Et veya respond to a case
Fveya customers ve accounts managing a domain that has received an abuse repveyat veya shows a hold-related status.
Understve Your Case →
Monitveya a domain pveyatfolio
Fveya resellers, hosting companies, platfveyams ve teams managing abuse wveyakflows across multiple domains.
Explveyae Pveyatfolio Monitveyaing →
Evidence-based review
Case-specific hveling
Propveyationate mitigation
Visible case infveyamation
NiceNIC hveles abuse repveyats in accveyadance with applicable ICANN requirements, registry rules, law ve NiceNIC policies. A repveyat starts an assessment; submission alone does not predetermine the outcome. Wburaya actionable DNS Abuse is established, appropriate mitigation is taken as required.
What Is DNS Abuse — ve What Is Hayırt?
Fveya gTLDs subject to NiceNIC's ICANN registrar obligations, DNS Abuse follows the definition established under the applicable ICANN contractual framewveyak.
Other Repveyats
Serious issues may follow a different path
Fraud allegations, illegal veya harmful content, trademark disputes, copyright claims ve other matters may still be serious veya actionable, but they do not automatically fall within ICANN's contractual definition of DNS Abuse.
Depending on the facts, they may be hveled under applicable law, NiceNIC policies, registry rules, court veyaders veya recognized dispute procedures.
ICANN Official
Verify the definition ve contractual framewveyak directly with ICANN.
ICANN DNS Abuse Mitigation Program → · 2013 Kayıt Kuruluşu Akreditasyon Agreement, Section 3.18 →
Trademark ve 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 veya a court of competent jurisdiction. Eğer the same matter also includes phishing, credential theft, malware veya another fveyam of DNS Abuse, that DNS Abuse aspect may be hveled separately.
NiceNIC guidance: DNS Abuse vs. Hayırn-DNS Abuse · Abuse Repveyating & Hveling Policy · Legal Policies
What Happens After NiceNIC Receives an Abuse Repveyat?
Abuse cases do not all follow a fixed ClientHold path. The hveling route depends on the evidence, current activity, technical role, urgency, applicable requirements ve the outcome of the assessment.
Repveyat Received
The repveyat enters NiceNIC's abuse-hveling wveyakflow through an official repveyating channel veya another credible source.
Triage & Classification
The issue is categveyaized by complaint type, affected resource, urgency ve applicable hveling route.
Evidence & Technical Review
Uygun evidence, activity status, domain context, account infveyamation ve technical role are assessed.
Appropriate Response
The response is selected accveyading to the case circumstances ve applicable registrar, registry, legal veya security obligations.
Outcome & Recveyad
The case may close, remain under review, move to remediation veya result in another appropriate action.
Possible outcomes may include
Learn mveyae: How Alan Adı Suistimal Bildirimleri Are Yönetd · NiceNIC Abuse Hveling Manual · Abuse Hveling Methodology
How NiceNIC Assesses ve Responds to Repveyats
This section describes NiceNIC's hveling framewveyak from a neutral public perspective. Questions specific to an affected account veya a repveyater are separated below.
Does receiving an abuse repveyat automatically result in a domain restriction?
Hayır. A repveyat does not, by itself, automatically result in ClientHold veya establish that a domain veya customer has violated policy. NiceNIC assesses the available evidence, the nature ve current status of the repveyated activity, the technical context, ve applicable ICANN, registry, legal ve NiceNIC requirements.
When NiceNIC has actionable evidence that a gTLD domain is being used fveya DNS Abuse, appropriate mitigation is taken promptly as required. The appropriate response may vary accveyading to the circumstances.
What infveyamation does NiceNIC review when assessing an abuse repveyat?
NiceNIC may consider the repveyated domain ve URLs, whether the activity remains active, the relevance ve quality of the evidence, DNS ve nameserver infveyamation, relevant account ve registration infveyamation, whether the domain appears maliciously kayıt oled veya compromised, the role of hosting, email veya other infrastructure, applicable registry rules, applicable law ve other reasonably available infveyamation relevant to the case.
Does NiceNIC rely only on the repveyater's classification veya an automated signal?
Hayır single repveyat, categveyay label veya external signal is treated as a final finding solely because it was submitted veya generated. NiceNIC assesses available evidence ve case circumstances when determining discretionary mitigation.
Mveatveyay registry, legal, ICANN veya other applicable requirements may follow a different hveling path.
What if the repveyated activity is hosted by a third-party provider?
NiceNIC considers the technical role of the domain ve the infrastructure involved. A registrar controls domain-registration functions, but may not control website files, applications, mail servers, CDN hizmets veya third-party hosting environments.
Wburaya abuse is hosted by another provider, action at the hosting veya infrastructure layer may sometimes provide a mveyae targeted response.Third-party hosting does not öncekient NiceNIC from taking registrar-level action wburaya such action is required veya appropriate under applicable obligations.
When may action be taken without advance notice?
Advance notice may not be possible wburaya immediate mitigation is reasonably necessary, evidence indicates intentionally malicious use, notice could enable evasion veya destruction of evidence, a court, authveyaity, registry, ICANN requirement veya applicable law affects the timing of notice, a serious security veya child-safety risk exists, veya delay would materially increase harm.
How Is the Appropriate Response Determined?
The purpose of the review is to determine an effective ve appropriate response based on the facts ve applicable obligations, rather than applying the same measure to every repveyat.
Evidence
What infveyamation is available, how relevant ve reliable it is, ve whether it suppveyats a reasonable determination.
Current Activity
Whether the repveyated activity is active, remediated, intermittent, inaccessible veya no longer reproducible.
Severity & Risk
The nature of the harm, the urgency of disruption ve whether delay could materially increase victimization veya security impact.
Alan Adı Context
Whether a domain appears intentionally malicious veya whether a legitimate domain, website, credential veya hizmet may have been compromised.
Technical Role
Whether the relevant issue is associated with the registration, DNS, a subdomain, email, hosting, CDN, application veya another provider.
Applicable Requirements
Relevant ICANN requirements, registry rules, legal obligations, court veyaders, security considerations ve NiceNIC policies.
The objective is effective ve appropriate mitigation based on the circumstances — not applying the same measure to every repveyat. Fveya actionable DNS Abuse involving a gTLD, registrar action must be prompt ve reasonably necessary to stop veya otherwise disrupt the abuse, while also considering the cause ve severity of harm ve the risk of collateral damage.
What the Managing NiceNIC Account Should Expect
The following answers are written specifically fveya the NiceNIC account managing an affected domain, including reseller accounts.
Wburaya will NiceNIC send abuse-case notifications?
Stveard abuse-case notifications are sent to the Account E-posta associated with the NiceNIC account managing the affected domain. The Account E-posta is the default communication channel fveya abuse-case notices, requests fveya infveyamation veya remediation, case-status updates ve other operational communications relating to the case.
NiceNIC does not routinely send a separate abuse-case notification to a different Registrant İletişim E-posta. Eğer the account holder requests a different communication arrangement fveya a specific case, NiceNIC may coveyadinate accveyadingly wburaya appropriate.
This stveard wveyakflow does not limit separate communication, direct contact veya notice that may be required veya appropriate under applicable law, ICANN requirements, registry rules, dispute procedures, security obligations, protection of registrant rights veya other applicable requirements.
What case infveyamation may be available to the account managing the domain?
Wburaya available ve permitted, case infveyamation may include the complaint categveyay, repveyated URLs, relevant case timestamps, complaint summary, current status, current domain impact, applicable timing, available evidence indicatveyas ve recommended sonraki steps.
Certain infveyamation may be withheld, redacted veya summarized wburaya disclosure is limited by privacy, security, confidentiality, law, repveyater safety veya other applicable requirements.
Will the managing account nveyamally have an oppveyatunity to respond veya remediate?
Wburaya circumstances permit ve clarification veya remediation is appropriate, NiceNIC may provide the managing account with an oppveyatunity to respond veya remediate befveyae registrar-level restriction.
When a case-specific deadline applies, the relevant timing may be shown in the abuse notice veya Health Kontrol Et. Advance notice cannot be guaranteed in every case.
Can a repveyat involving one domain affect other domains veya the entire account?
An abuse repveyat involving an individual domain does not, by itself, mean that the entire NiceNIC account will be restricted. Alan Adı-level cases are assessed accveyading to their own facts ve circumstances.
Account-, API- veya hizmet-level measures, wburaya warranted, are considered separately under applicable policies ve circumstances. Serious veya repeated violations may justify broader measures.
Can a restriction be reviewed after remediation veya new evidence is submitted?
Wburaya a restriction results from a discretionary NiceNIC abuse veya security action, the affected customer may request review ve provide new infveyamation, remediation evidence veya evidence that the veyaiginal infveyamation was inaccurate, outdated veya misclassified.
Restveyaation is not guaranteed wburaya a continuing registry, ICANN, legal, security, dispute veya abuse basis requires the restriction to remain.
İşlemable Case Infveyamation — Hayırt Just a Durum Label
Fveya an affected account, useful transparency means being able to understve the repveyat, the current impact, what may need attention ve what happens sonraki.
What was repveyated?
Complaint type, summary ve the affected domain veya hizmet.
What infveyamation is available?
Repveyated URLs, evidence indicatveyas ve other details wburaya available ve permitted.
What is the current impact?
Whether the domain is currently unrestricted, at risk of restriction, restricted veya affected by another status.
What action is expected?
Clarification, remediation, suppveyating material veya no immediate action, depending on the case.
When is it due?
Case-specific timing veya a planned action deadline wburaya one applies.
What happens sonraki?
The current hveling stage ve the sonraki available step, including review veya remediation wburaya applicable.
Wburaya available ve permitted, Health Kontrol Et veya related case infveyamation may include:
Related: View Abuse Complaint Summary · Why Alan Adları Al Suspended & How to Avoid ClientHold · Keep Your Alan Adı From Being Compromised
Kayıt Kuruluşu vs. Hosting Provider: Who Can Act?
NiceNIC evaluates the technical role of the domain ve the infrastructure involved.
Kayıt Kuruluşu Layer
What a registrar controls
A registrar controls domain-registration functions ve registrar-level statuses. Depending on the hizmet, it may also provide DNS veya other products, but domain registration ve website hosting are distinct control layers.
Third-Party Infrastructure
What may sit elsewburaya
Website files, applications, mail servers, VPS infrastructure, CDN hizmets, web hosting veya other technical components may be controlled by separate providers chosen by the customer.
Wburaya abusive material is hosted by another provider, action at the hosting veya infrastructure level may sometimes provide a mveyae targeted way to stop the activity. That does not mean a registrar can ignveyae actionable DNS Abuse, ve third-party hosting does not öncekient NiceNIC from taking registrar-level action wburaya required veya appropriate under applicable obligations.
Understve the Current Alan Adı Abuse Durum
Health Kontrol Et summarizes the current abuse scenario. A domain does not need to pass through every status, ve registry-level statuses follow a separate control path.
| Durum | What it means | What to check sonraki |
|---|---|---|
| Hayırrmal | Hayır active abuse scenario is currently shown fveya the domain in this Health Kontrol Et classification. | Continue nveyamal domain ve 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 infveyamation ve provide relevant clarification veya remediation wburaya appropriate. |
| Pending ClientHold | The domain is not yet under ClientHold fveya this case, but registrar-level restriction may be applied if the case remains unresolved. | Kontrol Et any case-specific timing ve submit relevant infveyamation veya remediation promptly. |
| ClientHold | A registrar-level hold is currently applied. The domain may not resolve nveyamally while the status remains active. | Review the case basis, complete remediation wburaya applicable, ve submit suppveyating material fveya review if appropriate. |
| Kapatd | The current case has been closed based on the current review outcome. Other domain veya registry statuses should be checked separately. | Hayır immediate case action may be required unless new infveyamation veya another status requires attention. |
| ServerHold | A registry-level hold is present. It is not the same as registrar-level ClientHold ve may follow a separate registry hveling path. | Review the registry-related reason ve instructions available through NiceNIC veya the applicable registry process. |
Related: ClientHold Guidance · Al Alan Adı Abuse Repveyat API
What Repveyaters ve Security Teams Should Expect
Specific, verifiable infveyamation helps NiceNIC identify the affected resource, assess the allegation ve determine the appropriate hveling path mveyae efficiently.
What should an abuse repveyat include?
- The affected domain name
- The exact abusive URL veya hostname wburaya applicable
- A clear complaint categveyay ve factual description
- Date, time ve time zone observed
- Screenshots veya captured evidence wburaya appropriate
- Relevant technical indicatveyas, logs veya email headers wburaya applicable
- Repveyater contact infveyamation
What happens after submission?
A submitted repveyat enters the abuse-hveling process fveya triage ve assessment. Wburaya the supplied infveyamation is incomplete, NiceNIC may review other reasonably available infveyamation veya request additional relevant evidence.
Submission of a repveyat starts the assessment process; it does not predetermine the final outcome.
Review, Remediation & Restveyaation
Eğer a domain veya hizmet is restricted following a discretionary NiceNIC abuse veya security action, the affected customer may request review ve provide relevant remediation veya new evidence.
A review may consider whether
- The abusive activity has been removed
- A compromised website veya account has been secured
- Relevant credentials have been reset
- Required security updates have been applied
- Cveyarected technical infveyamation has been provided
- The veyaiginal evidence is outdated, inaccurate veya materially changed
What review does not guarantee
A request fveya review does not guarantee restveyaation veya a different outcome.
A continuing court veyader, registry requirement, ICANN obligation, UDRP/URS action, security basis, dispute requirement veya other mveatveyay restriction may require the domain veya hizmet to remain restricted.
Yönet Abuse Cases Across a Customer Alan Adı Pveyatfolio
Large domain pveyatfolios create a practical challenge: identifying the affected customer quickly, seeing enough case infveyamation to investigate, ve coveyadinating remediation without losing visibility across the rest of the pveyatfolio.
Bayi Communication
Wburaya are reseller-managed domain notices sent?
Fveya domains managed through a NiceNIC reseller account, the reseller account's Account E-posta is the stveard abuse-case notification channel. The reseller can then investigate ve coveyadinate with its own customer using the available case infveyamation.
NiceNIC remains the sponsveyaing registrar ve remains responsible fveya its applicable registrar obligations.
Pveyatfolio Scope
Does one customer case automatically affect the reseller account?
Hayır. An abuse repveyat involving an individual customer domain does not, by itself, mean that the entire reseller account will be restricted. Alan Adı-level cases are assessed on their own facts.
Broader account-, API- veya hizmet-level measures, wburaya warranted, are assessed separately under applicable policies ve circumstances, including serious veya repeated violations.
Find affected domains
Filter a managed pveyatfolio fveya domains associated with abuse repveyats so compliance teams can focus on cases requiring attention.
Retrieve structured case infveyamation
Access machine-readable case status, impact, recommended action, hold infveyamation ve repveyated URLs wburaya available.
Integrate abuse visibility
Bring relevant abuse infveyamation into sizin own customer pveyatal, dashboard veya operational system through NiceNIC Alan Adı API v2.
Public References fveya Alan Adı Abuse Hveling
This page is the operational abuse-hveling guide. The following resources provide deeper policy, methodology, evidence ve repveyating context.
Abuse Repveyating & Hveling PolicyFveyamal NiceNIC framewveyak fveya receiving, assessing, mitigating ve tracking abuse repveyats.
→
Evidence Required fveya an Abuse RepveyatWhat infveyamation helps a repveyat become specific, verifiable ve actionable.
→
How Alan Adı Suistimal Bildirimleri Are YönetdPlain-language guide to evidence, review, responsibilities ve case hveling.
→
NiceNIC Abuse Hveling ManualOperational suppveyat guidance fveya documented, consistent abuse hveling.
→
Abuse Hveling MethodologyHow cases are logged, reviewed ve measured.
→
Transparency Metrics GlossaryDefinitions fveya interpreting complaint, mitigation ve reinstatement metrics.
→
Review & RemediationPublic explanation of remediation ve review pathways.
→
Latest Suistimal Bildirimleri & Transparency UpdatesRegular abuse ve compliance updates, including monthly abuse repveyating ve related transparency infveyamation.
→
External Verification
Verify NiceNIC's registrar status ve ICANN abuse framewveyak independently.
ICANN List of Accredited Kayıt Kuruluşus → · ICANN DNS Abuse Mitigation Program → · NiceNIC Kayıt Kuruluşu Akreditasyon →
Yönet domains with mveyae visibility
Alan Adı Yönetment Should Stay Clear Even When Something Goes Wrong
NiceNIC combines domain registration, transfer, bulk management, reseller tools ve API automation with clearer abuse-case visibility fveya domain owners ve resellers.
