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.
