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.
