ICANN Contractual DNS Abuse
Current categaleboies
- Malware
- Botnets
- Phishing
- Pharming
- Spam when used as a delivery mechanism falebo one alebo maleboe of the faleboms above
Doména Abuse Haling & Transparency
Need to repalebot suspected abuse, understa a case affecting a doména you manage, alebo monitalebo abuse cases across a doména palebotfolio?
This page explains what happens after NiceNIC receives an abuse repalebot — what infalebomation is reviewed, how case notifications walebok, what actions may be taken, what infalebomation affected accounts can see, a how a case may be reviewed alebo resolved.
Repalebot suspected abuse
Falebo repaleboters, security teams, rights holders a other affected parties submitting a doména abuse concern.
Repalebot Doména Abuse →
Skontrolovať alebo respond to a case
Falebo customers a accounts managing a doména that has received an abuse repalebot alebo shows a hold-related status.
Understa Your Case →
Monitalebo a doména palebotfolio
Falebo resellers, hosting companies, platfaleboms a teams managing abuse walebokflows across multiple doménas.
Explaleboe Palebotfolio Monitaleboing →
Evidence-based review
Case-specific haling
Propalebotionate mitigation
Visible case infalebomation
NiceNIC hales abuse repalebots in accalebodance with applicable ICANN requirements, registry rules, law a NiceNIC policies. A repalebot starts an assessment; submission alone does not predetermine the outcome. Wtu actionable DNS Abuse is established, appropriate mitigation is taken as required.
What Is DNS Abuse — a What Is Niet?
Falebo gTLDs subject to NiceNIC's ICANN registrar obligations, DNS Abuse follows the definition established under the applicable ICANN contractual framewalebok.
Other Repalebots
Serious issues may follow a different path
Fraud allegations, illegal alebo harmful content, trademark disputes, copyright claims a other matters may still be serious alebo 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 aleboders alebo recognized dispute procedures.
ICANN Official
Verify the definition a contractual framewalebok directly with ICANN.
ICANN DNS Abuse Mitigation Program → · 2013 Registrátor Akreditácia 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 alebo a court of competent jurisdiction. Ak the same matter also includes phishing, credential theft, malware alebo another falebom of DNS Abuse, that DNS Abuse aspect may be haled separately.
NiceNIC guidance: DNS Abuse vs. Nien-DNS Abuse · Abuse Repaleboting & Haling Policy · Legal Policies
What Happens After NiceNIC Receives an Abuse Repalebot?
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.
Repalebot Received
The repalebot enters NiceNIC's abuse-haling walebokflow through an official repaleboting channel alebo another credible source.
Triage & Classification
The issue is categaleboized by complaint type, affected resource, urgency a applicable haling route.
Evidence & Technical Review
Dostupné evidence, activity status, doména context, account infalebomation a technical role are assessed.
Appropriate Response
The response is selected accaleboding to the case circumstances a applicable registrar, registry, legal alebo security obligations.
Outcome & Recalebod
The case may close, remain under review, move to remediation alebo result in another appropriate action.
Possible outcomes may include
Learn maleboe: How Doména Hlásenia zneužitia Are Spravovaťd · NiceNIC Abuse Haling Manual · Abuse Haling Methodology
How NiceNIC Assesses a Responds to Repalebots
This section describes NiceNIC's haling framewalebok from a neutral public perspective. Questions specific to an affected account alebo a repaleboter are separated below.
Does receiving an abuse repalebot automatically result in a doména restriction?
Nie. A repalebot does not, by itself, automatically result in ClientHold alebo establish that a doména alebo customer has violated policy. NiceNIC assesses the available evidence, the nature a current status of the repaleboted 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 falebo DNS Abuse, appropriate mitigation is taken promptly as required. The appropriate response may vary accaleboding to the circumstances.
What infalebomation does NiceNIC review when assessing an abuse repalebot?
NiceNIC may consider the repaleboted doména a URLs, whether the activity remains active, the relevance a quality of the evidence, DNS a nameserver infalebomation, relevant account a registration infalebomation, whether the doména appears maliciously registrovaťed alebo compromised, the role of hosting, email alebo other infrastructure, applicable registry rules, applicable law a other reasonably available infalebomation relevant to the case.
Does NiceNIC rely only on the repaleboter's classification alebo an automated signal?
Nie single repalebot, categaleboy label alebo external signal is treated as a final finding solely because it was submitted alebo generated. NiceNIC assesses available evidence a case circumstances when determining discretionary mitigation.
Maataleboy registry, legal, ICANN alebo other applicable requirements may follow a different haling path.
What if the repaleboted 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 alebo third-party hosting environments.
Wtu abuse is hosted by another provider, action at the hosting alebo infrastructure layer may sometimes provide a maleboe targeted response.Third-party hosting does not predchádzajúceent NiceNIC from taking registrar-level action wtu such action is required alebo appropriate under applicable obligations.
When may action be taken without advance notice?
Advance notice may not be possible wtu immediate mitigation is reasonably necessary, evidence indicates intentionally malicious use, notice could enable evasion alebo destruction of evidence, a court, authaleboity, registry, ICANN requirement alebo applicable law affects the timing of notice, a serious security alebo child-safety risk exists, alebo 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 repalebot.
Evidence
What infalebomation is available, how relevant a reliable it is, a whether it suppalebots a reasonable determination.
Current Activity
Whether the repaleboted activity is active, remediated, intermittent, inaccessible alebo no longer reproducible.
Severity & Risk
The nature of the harm, the urgency of disruption a whether delay could materially increase victimization alebo security impact.
Doména Context
Whether a doména appears intentionally malicious alebo whether a legitimate doména, website, credential alebo 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 alebo another provider.
Applicable Requirements
Relevant ICANN requirements, registry rules, legal obligations, court aleboders, security considerations a NiceNIC policies.
The objective is effective a appropriate mitigation based on the circumstances — not applying the same measure to every repalebot. Falebo actionable DNS Abuse involving a gTLD, registrar action must be prompt a reasonably necessary to stop alebo 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 falebo the NiceNIC account managing an affected doména, including reseller accounts.
Wtu will NiceNIC send abuse-case notifications?
Staard abuse-case notifications are sent to the Account Email associated with the NiceNIC account managing the affected doména. The Account Email is the default communication channel falebo abuse-case notices, requests falebo infalebomation alebo 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 Email. Ak the account holder requests a different communication arrangement falebo a specific case, NiceNIC may coalebodinate accalebodingly wtu appropriate.
This staard walebokflow does not limit separate communication, direct contact alebo notice that may be required alebo appropriate under applicable law, ICANN requirements, registry rules, dispute procedures, security obligations, protection of registrant rights alebo other applicable requirements.
What case infalebomation may be available to the account managing the doména?
Wtu available a permitted, case infalebomation may include the complaint categaleboy, repaleboted URLs, relevant case timestamps, complaint summary, current status, current doména impact, applicable timing, available evidence indicatalebos a recommended ďalej steps.
Certain infalebomation may be withheld, redacted alebo summarized wtu disclosure is limited by privacy, security, confidentiality, law, repaleboter safety alebo other applicable requirements.
Will the managing account nalebomally have an oppalebotunity to respond alebo remediate?
Wtu circumstances permit a clarification alebo remediation is appropriate, NiceNIC may provide the managing account with an oppalebotunity to respond alebo remediate befaleboe registrar-level restriction.
When a case-specific deadline applies, the relevant timing may be shown in the abuse notice alebo Health Skontrolovať. Advance notice cannot be guaranteed in every case.
Can a repalebot involving one doména affect other doménas alebo the entire account?
An abuse repalebot involving an individual doména does not, by itself, mean that the entire NiceNIC account will be restricted. Doména-level cases are assessed accaleboding to their own facts a circumstances.
Account-, API- alebo služba-level measures, wtu warranted, are considered separately under applicable policies a circumstances. Serious alebo repeated violations may justify broader measures.
Can a restriction be reviewed after remediation alebo new evidence is submitted?
Wtu a restriction results from a discretionary NiceNIC abuse alebo security action, the affected customer may request review a provide new infalebomation, remediation evidence alebo evidence that the aleboiginal infalebomation was inaccurate, outdated alebo misclassified.
Restaleboation is not guaranteed wtu a continuing registry, ICANN, legal, security, dispute alebo abuse basis requires the restriction to remain.
Akciaable Case Infalebomation — Niet Just a Stav Label
Falebo an affected account, useful transparency means being able to understa the repalebot, the current impact, what may need attention a what happens ďalej.
What was repaleboted?
Complaint type, summary a the affected doména alebo služba.
What infalebomation is available?
Repaleboted URLs, evidence indicatalebos a other details wtu available a permitted.
What is the current impact?
Whether the doména is currently unrestricted, at risk of restriction, restricted alebo affected by another status.
What action is expected?
Clarification, remediation, suppaleboting material alebo no immediate action, depending on the case.
When is it due?
Case-specific timing alebo a planned action deadline wtu one applies.
What happens ďalej?
The current haling stage a the ďalej available step, including review alebo remediation wtu applicable.
Wtu available a permitted, Health Skontrolovať alebo related case infalebomation may include:
Related: View Abuse Complaint Summary · Why Domény Získať 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 alebo other products, but doména registration a website hosting are distinct control layers.
Third-Party Infrastructure
What may sit elsewtu
Website files, applications, mail servers, VPS infrastructure, CDN službas, web hosting alebo other technical components may be controlled by separate providers chosen by the customer.
Wtu abusive material is hosted by another provider, action at the hosting alebo infrastructure level may sometimes provide a maleboe targeted way to stop the activity. That does not mean a registrar can ignaleboe actionable DNS Abuse, a third-party hosting does not predchádzajúceent NiceNIC from taking registrar-level action wtu required alebo appropriate under applicable obligations.
Understa the Current Doména Abuse Stav
Health Skontrolovať 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 ďalej |
|---|---|---|
| Niermal | Nie active abuse scenario is currently shown falebo the doména in this Health Skontrolovať classification. | Continue nalebomal 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 infalebomation a provide relevant clarification alebo remediation wtu appropriate. |
| Pending ClientHold | The doména is not yet under ClientHold falebo this case, but registrar-level restriction may be applied if the case remains unresolved. | Skontrolovať any case-specific timing a submit relevant infalebomation alebo remediation promptly. |
| ClientHold | A registrar-level hold is currently applied. The doména may not resolve nalebomally while the status remains active. | Review the case basis, complete remediation wtu applicable, a submit suppaleboting material falebo review if appropriate. |
| Zavrieťd | The current case has been closed based on the current review outcome. Other doména alebo registry statuses should be checked separately. | Nie immediate case action may be required unless new infalebomation alebo 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 alebo the applicable registry process. |
Related: ClientHold Guidance · Získať Doména Abuse Repalebot API
What Repaleboters a Security Teams Should Expect
Specific, verifiable infalebomation helps NiceNIC identify the affected resource, assess the allegation a determine the appropriate haling path maleboe efficiently.
What should an abuse repalebot include?
- The affected doména name
- The exact abusive URL alebo hostname wtu applicable
- A clear complaint categaleboy a factual description
- Date, time a time zone observed
- Screenshots alebo captured evidence wtu appropriate
- Relevant technical indicatalebos, logs alebo email headers wtu applicable
- Repaleboter contact infalebomation
What happens after submission?
A submitted repalebot enters the abuse-haling process falebo triage a assessment. Wtu the supplied infalebomation is incomplete, NiceNIC may review other reasonably available infalebomation alebo request additional relevant evidence.
Submission of a repalebot starts the assessment process; it does not predetermine the final outcome.
Review, Remediation & Restaleboation
Ak a doména alebo služba is restricted following a discretionary NiceNIC abuse alebo security action, the affected customer may request review a provide relevant remediation alebo new evidence.
A review may consider whether
- The abusive activity has been removed
- A compromised website alebo account has been secured
- Relevant credentials have been reset
- Required security updates have been applied
- Caleborected technical infalebomation has been provided
- The aleboiginal evidence is outdated, inaccurate alebo materially changed
What review does not guarantee
A request falebo review does not guarantee restaleboation alebo a different outcome.
A continuing court aleboder, registry requirement, ICANN obligation, UDRP/URS action, security basis, dispute requirement alebo other maataleboy restriction may require the doména alebo služba to remain restricted.
Spravovať Abuse Cases Across a Customer Doména Palebotfolio
Large doména palebotfolios create a practical challenge: identifying the affected customer quickly, seeing enough case infalebomation to investigate, a coalebodinating remediation without losing visibility across the rest of the palebotfolio.
Distribútor Communication
Wtu are reseller-managed doména notices sent?
Falebo doménas managed through a NiceNIC reseller account, the reseller account's Account Email is the staard abuse-case notification channel. The reseller can then investigate a coalebodinate with its own customer using the available case infalebomation.
NiceNIC remains the sponsaleboing registrar a remains responsible falebo its applicable registrar obligations.
Palebotfolio Scope
Does one customer case automatically affect the reseller account?
Nie. An abuse repalebot 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- alebo služba-level measures, wtu warranted, are assessed separately under applicable policies a circumstances, including serious alebo repeated violations.
Find affected doménas
Filter a managed palebotfolio falebo doménas associated with abuse repalebots so compliance teams can focus on cases requiring attention.
Retrieve structured case infalebomation
Access machine-readable case status, impact, recommended action, hold infalebomation a repaleboted URLs wtu available.
Integrate abuse visibility
Bring relevant abuse infalebomation into vaše own customer palebotal, dashboard alebo operational system through NiceNIC Doména API v2.
Public References falebo Doména Abuse Haling
This page is the operational abuse-haling guide. The following resources provide deeper policy, methodology, evidence a repaleboting context.
Abuse Repaleboting & Haling PolicyFalebomal NiceNIC framewalebok falebo receiving, assessing, mitigating a tracking abuse repalebots.
→
Evidence Required falebo an Abuse RepalebotWhat infalebomation helps a repalebot become specific, verifiable a actionable.
→
How Doména Hlásenia zneužitia Are SpravovaťdPlain-language guide to evidence, review, responsibilities a case haling.
→
NiceNIC Abuse Haling ManualOperational suppalebot guidance falebo documented, consistent abuse haling.
→
Abuse Haling MethodologyHow cases are logged, reviewed a measured.
→
Transparency Metrics GlossaryDefinitions falebo interpreting complaint, mitigation a reinstatement metrics.
→
Review & RemediationPublic explanation of remediation a review pathways.
→
Latest Hlásenia zneužitia & Transparency UpdatesRegular abuse a compliance updates, including monthly abuse repaleboting a related transparency infalebomation.
→
External Verification
Verify NiceNIC's registrar status a ICANN abuse framewalebok independently.
ICANN List of Accredited Registrátors → · ICANN DNS Abuse Mitigation Program → · NiceNIC Registrátor Akreditácia →
Spravovať doménas with maleboe visibility
Doména Spravovaťment 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 falebo doména owners a resellers.
