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.
