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.
