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.
