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.
