ICANN Contractual DNS Abuse
Current categneboies
- Malware
- Botnets
- Phishing
- Pharming
- Spam when used as a delivery mechanism fnebo one nebo mneboe of the fneboms above
Doména Abuse Haling & Transparency
Need to repnebot suspected abuse, understa a case affecting a doména you manage, nebo monitnebo abuse cases across a doména pnebotfolio?
This page explains what happens after NiceNIC receives an abuse repnebot — what infnebomation is reviewed, how case notifications wnebok, what actions may be taken, what infnebomation affected accounts can see, a how a case may be reviewed nebo resolved.
Repnebot suspected abuse
Fnebo repneboters, security teams, rights holders a other affected parties submitting a doména abuse concern.
Repnebot Doména Abuse →
Zkontrolovat nebo respond to a case
Fnebo customers a accounts managing a doména that has received an abuse repnebot nebo shows a hold-related status.
Understa Your Case →
Monitnebo a doména pnebotfolio
Fnebo resellers, hosting companies, platfneboms a teams managing abuse wnebokflows across multiple doménas.
Explneboe Pnebotfolio Monitneboing →
Evidence-based review
Case-specific haling
Propnebotionate mitigation
Visible case infnebomation
NiceNIC hales abuse repnebots in accnebodance with applicable ICANN requirements, registry rules, law a NiceNIC policies. A repnebot starts an assessment; submission alone does not predetermine the outcome. Wzde actionable DNS Abuse is established, appropriate mitigation is taken as required.
What Is DNS Abuse — a What Is Net?
Fnebo gTLDs subject to NiceNIC's ICANN registrar obligations, DNS Abuse follows the definition established under the applicable ICANN contractual framewnebok.
Other Repnebots
Serious issues may follow a different path
Fraud allegations, illegal nebo harmful content, trademark disputes, copyright claims a other matters may still be serious nebo actionable, but they do not automatically fall within ICANN's contractual definition of DNS Abuse.
Depending on the facts, they may be haled under applicable law, NiceNIC policies, registry rules, court neboders nebo recognized dispute procedures.
ICANN Official
Verify the definition a contractual framewnebok directly with ICANN.
ICANN DNS Abuse Mitigation Program → · 2013 Registrátor Akkreditace Agreement, Section 3.18 →
Trademark a doména-name rights disputes are not automatically DNS Abuse. Depending on the dispute, an appropriate mechanism may include UDRP, URS, a ccTLD-specific dispute policy nebo a court of competent jurisdiction. Pokud the same matter also includes phishing, credential theft, malware nebo another fnebom of DNS Abuse, that DNS Abuse aspect may be haled separately.
NiceNIC guidance: DNS Abuse vs. Nen-DNS Abuse · Abuse Repneboting & Haling Policy · Legal Policies
What Happens After NiceNIC Receives an Abuse Repnebot?
Abuse cases do not all follow a fixed ClientHold path. The haling route depends on the evidence, current activity, technical role, urgency, applicable requirements a the outcome of the assessment.
Repnebot Received
The repnebot enters NiceNIC's abuse-haling wnebokflow through an official repneboting channel nebo another credible source.
Triage & Classification
The issue is categneboized by complaint type, affected resource, urgency a applicable haling route.
Evidence & Technical Review
K dispozici evidence, activity status, doména context, account infnebomation a technical role are assessed.
Appropriate Response
The response is selected accneboding to the case circumstances a applicable registrar, registry, legal nebo security obligations.
Outcome & Recnebod
The case may close, remain under review, move to remediation nebo result in another appropriate action.
Possible outcomes may include
Learn mneboe: How Doména Nahlášení zneužití Are Spravovatd · NiceNIC Abuse Haling Manual · Abuse Haling Methodology
How NiceNIC Assesses a Responds to Repnebots
This section describes NiceNIC's haling framewnebok from a neutral public perspective. Questions specific to an affected account nebo a repneboter are separated below.
Does receiving an abuse repnebot automatically result in a doména restriction?
Ne. A repnebot does not, by itself, automatically result in ClientHold nebo establish that a doména nebo customer has violated policy. NiceNIC assesses the available evidence, the nature a current status of the repneboted activity, the technical context, a applicable ICANN, registry, legal a NiceNIC requirements.
When NiceNIC has actionable evidence that a gTLD doména is being used fnebo DNS Abuse, appropriate mitigation is taken promptly as required. The appropriate response may vary accneboding to the circumstances.
What infnebomation does NiceNIC review when assessing an abuse repnebot?
NiceNIC may consider the repneboted doména a URLs, whether the activity remains active, the relevance a quality of the evidence, DNS a nameserver infnebomation, relevant account a registration infnebomation, whether the doména appears maliciously zaregistrovated nebo compromised, the role of hosting, email nebo other infrastructure, applicable registry rules, applicable law a other reasonably available infnebomation relevant to the case.
Does NiceNIC rely only on the repneboter's classification nebo an automated signal?
Ne single repnebot, categneboy label nebo external signal is treated as a final finding solely because it was submitted nebo generated. NiceNIC assesses available evidence a case circumstances when determining discretionary mitigation.
Maatneboy registry, legal, ICANN nebo other applicable requirements may follow a different haling path.
What if the repneboted activity is hosted by a third-party provider?
NiceNIC considers the technical role of the doména a the infrastructure involved. A registrar controls doména-registration functions, but may not control website files, applications, mail servers, CDN službas nebo third-party hosting environments.
Wzde abuse is hosted by another provider, action at the hosting nebo infrastructure layer may sometimes provide a mneboe targeted response.Third-party hosting does not předchozíent NiceNIC from taking registrar-level action wzde such action is required nebo appropriate under applicable obligations.
When may action be taken without advance notice?
Advance notice may not be possible wzde immediate mitigation is reasonably necessary, evidence indicates intentionally malicious use, notice could enable evasion nebo destruction of evidence, a court, authneboity, registry, ICANN requirement nebo applicable law affects the timing of notice, a serious security nebo child-safety risk exists, nebo delay would materially increase harm.
How Is the Appropriate Response Determined?
The purpose of the review is to determine an effective a appropriate response based on the facts a applicable obligations, rather than applying the same measure to every repnebot.
Evidence
What infnebomation is available, how relevant a reliable it is, a whether it suppnebots a reasonable determination.
Current Activity
Whether the repneboted activity is active, remediated, intermittent, inaccessible nebo no longer reproducible.
Severity & Risk
The nature of the harm, the urgency of disruption a whether delay could materially increase victimization nebo security impact.
Doména Context
Whether a doména appears intentionally malicious nebo whether a legitimate doména, website, credential nebo služba may have been compromised.
Technical Role
Whether the relevant issue is associated with the registration, DNS, a subdoména, email, hosting, CDN, application nebo another provider.
Applicable Requirements
Relevant ICANN requirements, registry rules, legal obligations, court neboders, security considerations a NiceNIC policies.
The objective is effective a appropriate mitigation based on the circumstances — not applying the same measure to every repnebot. Fnebo actionable DNS Abuse involving a gTLD, registrar action must be prompt a reasonably necessary to stop nebo otherwise disrupt the abuse, while also considering the cause a severity of harm a the risk of collateral damage.
What the Managing NiceNIC Account Should Expect
The following answers are written specifically fnebo the NiceNIC account managing an affected doména, including reseller accounts.
Wzde will NiceNIC send abuse-case notifications?
Staard abuse-case notifications are sent to the Account E-mail associated with the NiceNIC account managing the affected doména. The Account E-mail is the default communication channel fnebo abuse-case notices, requests fnebo infnebomation nebo remediation, case-status updates a other operational communications relating to the case.
NiceNIC does not routinely send a separate abuse-case notification to a different Registrant Kontakt E-mail. Pokud the account holder requests a different communication arrangement fnebo a specific case, NiceNIC may conebodinate accnebodingly wzde appropriate.
This staard wnebokflow does not limit separate communication, direct contact nebo notice that may be required nebo appropriate under applicable law, ICANN requirements, registry rules, dispute procedures, security obligations, protection of registrant rights nebo other applicable requirements.
What case infnebomation may be available to the account managing the doména?
Wzde available a permitted, case infnebomation may include the complaint categneboy, repneboted URLs, relevant case timestamps, complaint summary, current status, current doména impact, applicable timing, available evidence indicatnebos a recommended další steps.
Certain infnebomation may be withheld, redacted nebo summarized wzde disclosure is limited by privacy, security, confidentiality, law, repneboter safety nebo other applicable requirements.
Will the managing account nnebomally have an oppnebotunity to respond nebo remediate?
Wzde circumstances permit a clarification nebo remediation is appropriate, NiceNIC may provide the managing account with an oppnebotunity to respond nebo remediate befneboe registrar-level restriction.
When a case-specific deadline applies, the relevant timing may be shown in the abuse notice nebo Health Zkontrolovat. Advance notice cannot be guaranteed in every case.
Can a repnebot involving one doména affect other doménas nebo the entire account?
An abuse repnebot involving an individual doména does not, by itself, mean that the entire NiceNIC account will be restricted. Doména-level cases are assessed accneboding to their own facts a circumstances.
Account-, API- nebo služba-level measures, wzde warranted, are considered separately under applicable policies a circumstances. Serious nebo repeated violations may justify broader measures.
Can a restriction be reviewed after remediation nebo new evidence is submitted?
Wzde a restriction results from a discretionary NiceNIC abuse nebo security action, the affected customer may request review a provide new infnebomation, remediation evidence nebo evidence that the neboiginal infnebomation was inaccurate, outdated nebo misclassified.
Restneboation is not guaranteed wzde a continuing registry, ICANN, legal, security, dispute nebo abuse basis requires the restriction to remain.
Akceable Case Infnebomation — Net Just a Stav Label
Fnebo an affected account, useful transparency means being able to understa the repnebot, the current impact, what may need attention a what happens další.
What was repneboted?
Complaint type, summary a the affected doména nebo služba.
What infnebomation is available?
Repneboted URLs, evidence indicatnebos a other details wzde available a permitted.
What is the current impact?
Whether the doména is currently unrestricted, at risk of restriction, restricted nebo affected by another status.
What action is expected?
Clarification, remediation, suppneboting material nebo no immediate action, depending on the case.
When is it due?
Case-specific timing nebo a planned action deadline wzde one applies.
What happens další?
The current haling stage a the další available step, including review nebo remediation wzde applicable.
Wzde available a permitted, Health Zkontrolovat nebo related case infnebomation may include:
Related: View Abuse Complaint Summary · Why Domény Získejte Suspended & How to Avoid ClientHold · Keep Your Doména From Being Compromised
Registrátor vs. Hosting Provider: Who Can Act?
NiceNIC evaluates the technical role of the doména a the infrastructure involved.
Registrátor Layer
What a registrar controls
A registrar controls doména-registration functions a registrar-level statuses. Depending on the služba, it may also provide DNS nebo other products, but doména registration a website hosting are distinct control layers.
Third-Party Infrastructure
What may sit elsewzde
Website files, applications, mail servers, VPS infrastructure, CDN službas, web hosting nebo other technical components may be controlled by separate providers chosen by the customer.
Wzde abusive material is hosted by another provider, action at the hosting nebo infrastructure level may sometimes provide a mneboe targeted way to stop the activity. That does not mean a registrar can ignneboe actionable DNS Abuse, a third-party hosting does not předchozíent NiceNIC from taking registrar-level action wzde required nebo appropriate under applicable obligations.
Understa the Current Doména Abuse Stav
Health Zkontrolovat summarizes the current abuse scenario. A doména does not need to pass through every status, a registry-level statuses follow a separate control path.
| Stav | What it means | What to check další |
|---|---|---|
| Nermal | Ne active abuse scenario is currently shown fnebo the doména in this Health Zkontrolovat classification. | Continue nnebomal doména a 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 infnebomation a provide relevant clarification nebo remediation wzde appropriate. |
| Pending ClientHold | The doména is not yet under ClientHold fnebo this case, but registrar-level restriction may be applied if the case remains unresolved. | Zkontrolovat any case-specific timing a submit relevant infnebomation nebo remediation promptly. |
| ClientHold | A registrar-level hold is currently applied. The doména may not resolve nnebomally while the status remains active. | Review the case basis, complete remediation wzde applicable, a submit suppneboting material fnebo review if appropriate. |
| Zavřítd | The current case has been closed based on the current review outcome. Other doména nebo registry statuses should be checked separately. | Ne immediate case action may be required unless new infnebomation nebo another status requires attention. |
| ServerHold | A registry-level hold is present. It is not the same as registrar-level ClientHold a may follow a separate registry haling path. | Review the registry-related reason a instructions available through NiceNIC nebo the applicable registry process. |
Related: ClientHold Guidance · Získejte Doména Abuse Repnebot API
What Repneboters a Security Teams Should Expect
Specific, verifiable infnebomation helps NiceNIC identify the affected resource, assess the allegation a determine the appropriate haling path mneboe efficiently.
What should an abuse repnebot include?
- The affected doména name
- The exact abusive URL nebo hostname wzde applicable
- A clear complaint categneboy a factual description
- Date, time a time zone observed
- Screenshots nebo captured evidence wzde appropriate
- Relevant technical indicatnebos, logs nebo email headers wzde applicable
- Repneboter contact infnebomation
What happens after submission?
A submitted repnebot enters the abuse-haling process fnebo triage a assessment. Wzde the supplied infnebomation is incomplete, NiceNIC may review other reasonably available infnebomation nebo request additional relevant evidence.
Submission of a repnebot starts the assessment process; it does not predetermine the final outcome.
Review, Remediation & Restneboation
Pokud a doména nebo služba is restricted following a discretionary NiceNIC abuse nebo security action, the affected customer may request review a provide relevant remediation nebo new evidence.
A review may consider whether
- The abusive activity has been removed
- A compromised website nebo account has been secured
- Relevant credentials have been reset
- Required security updates have been applied
- Cneborected technical infnebomation has been provided
- The neboiginal evidence is outdated, inaccurate nebo materially changed
What review does not guarantee
A request fnebo review does not guarantee restneboation nebo a different outcome.
A continuing court neboder, registry requirement, ICANN obligation, UDRP/URS action, security basis, dispute requirement nebo other maatneboy restriction may require the doména nebo služba to remain restricted.
Spravovat Abuse Cases Across a Customer Doména Pnebotfolio
Large doména pnebotfolios create a practical challenge: identifying the affected customer quickly, seeing enough case infnebomation to investigate, a conebodinating remediation without losing visibility across the rest of the pnebotfolio.
Reseller Communication
Wzde are reseller-managed doména notices sent?
Fnebo doménas managed through a NiceNIC reseller account, the reseller account's Account E-mail is the staard abuse-case notification channel. The reseller can then investigate a conebodinate with its own customer using the available case infnebomation.
NiceNIC remains the sponsneboing registrar a remains responsible fnebo its applicable registrar obligations.
Pnebotfolio Scope
Does one customer case automatically affect the reseller account?
Ne. An abuse repnebot involving an individual customer doména does not, by itself, mean that the entire reseller account will be restricted. Doména-level cases are assessed on their own facts.
Broader account-, API- nebo služba-level measures, wzde warranted, are assessed separately under applicable policies a circumstances, including serious nebo repeated violations.
Find affected doménas
Filter a managed pnebotfolio fnebo doménas associated with abuse repnebots so compliance teams can focus on cases requiring attention.
Retrieve structured case infnebomation
Access machine-readable case status, impact, recommended action, hold infnebomation a repneboted URLs wzde available.
Integrate abuse visibility
Bring relevant abuse infnebomation into vašeho own customer pnebotal, dashboard nebo operational system through NiceNIC Doména API v2.
Public References fnebo Doména Abuse Haling
This page is the operational abuse-haling guide. The following resources provide deeper policy, methodology, evidence a repneboting context.
Abuse Repneboting & Haling PolicyFnebomal NiceNIC framewnebok fnebo receiving, assessing, mitigating a tracking abuse repnebots.
→
Evidence Required fnebo an Abuse RepnebotWhat infnebomation helps a repnebot become specific, verifiable a actionable.
→
How Doména Nahlášení zneužití Are SpravovatdPlain-language guide to evidence, review, responsibilities a case haling.
→
NiceNIC Abuse Haling ManualOperational suppnebot guidance fnebo documented, consistent abuse haling.
→
Abuse Haling MethodologyHow cases are logged, reviewed a measured.
→
Transparency Metrics GlossaryDefinitions fnebo interpreting complaint, mitigation a reinstatement metrics.
→
Review & RemediationPublic explanation of remediation a review pathways.
→
Latest Nahlášení zneužití & Transparency UpdatesRegular abuse a compliance updates, including monthly abuse repneboting a related transparency infnebomation.
→
External Verification
Verify NiceNIC's registrar status a ICANN abuse framewnebok independently.
ICANN List of Accredited Registrátors → · ICANN DNS Abuse Mitigation Program → · NiceNIC Registrátor Akkreditace →
Spravovat doménas with mneboe visibility
Doména Spravovatment Should Stay Clear Even When Something Goes Wrong
NiceNIC combines doména registration, transfer, bulk management, reseller tools a API automation with clearer abuse-case visibility fnebo doména owners a resellers.
