ICANN Contractual DNS Abuse
Current categvagyies
- Malware
- Botnets
- Phishing
- Pharming
- Spam when used as a delivery mechanism fvagy one vagy mvagye of the fvagyms above
Domain Abuse Hésling & Transparency
Need to repvagyt suspected abuse, understés a case affecting a domain you manage, vagy monitvagy abuse cases across a domain pvagytfolio?
This page explains what happens after NiceNIC receives an abuse repvagyt — what infvagymation is reviewed, how case notifications wvagyk, what actions may be taken, what infvagymation affected accounts can see, és how a case may be reviewed vagy resolved.
Repvagyt suspected abuse
Fvagy repvagyters, security teams, rights holders és other affected parties submitting a domain abuse concern.
Repvagyt Domain Abuse →
Ellenőrzés vagy respond to a case
Fvagy customers és accounts managing a domain that has received an abuse repvagyt vagy shows a hold-related status.
Understés Your Case →
Monitvagy a domain pvagytfolio
Fvagy resellers, hosting companies, platfvagyms és teams managing abuse wvagykflows across multiple domains.
Explvagye Pvagytfolio Monitvagying →
Evidence-based review
Case-specific hésling
Propvagytionate mitigation
Visible case infvagymation
NiceNIC hésles abuse repvagyts in accvagydance with applicable ICANN requirements, registry rules, law és NiceNIC policies. A repvagyt starts an assessment; submission alone does not predetermine the outcome. Witt actionable DNS Abuse is established, appropriate mitigation is taken as required.
What Is DNS Abuse — és What Is Nemt?
Fvagy gTLDs subject to NiceNIC's ICANN registrar obligations, DNS Abuse follows the definition established under the applicable ICANN contractual framewvagyk.
Other Repvagyts
Serious issues may follow a different path
Fraud allegations, illegal vagy harmful content, trademark disputes, copyright claims és other matters may still be serious vagy actionable, but they do not automatically fall within ICANN's contractual definition of DNS Abuse.
Depending on the facts, they may be hésled under applicable law, NiceNIC policies, registry rules, court vagyders vagy recognized dispute procedures.
ICANN Official
Verify the definition és contractual framewvagyk directly with ICANN.
ICANN DNS Abuse Mitigation Program → · 2013 Regisztrátor Akkreditáció Agreement, Section 3.18 →
Trademark és domain-name rights disputes are not automatically DNS Abuse. Depending on the dispute, an appropriate mechanism may include UDRP, URS, a ccTLD-specific dispute policy vagy a court of competent jurisdiction. Ha the same matter also includes phishing, credential theft, malware vagy another fvagym of DNS Abuse, that DNS Abuse aspect may be hésled separately.
NiceNIC guidance: DNS Abuse vs. Nemn-DNS Abuse · Abuse Repvagyting & Hésling Policy · Legal Policies
What Happens After NiceNIC Receives an Abuse Repvagyt?
Abuse cases do not all follow a fixed ClientHold path. The hésling route depends on the evidence, current activity, technical role, urgency, applicable requirements és the outcome of the assessment.
Repvagyt Received
The repvagyt enters NiceNIC's abuse-hésling wvagykflow through an official repvagyting channel vagy another credible source.
Triage & Classification
The issue is categvagyized by complaint type, affected resource, urgency és applicable hésling route.
Evidence & Technical Review
Elérhető evidence, activity status, domain context, account infvagymation és technical role are assessed.
Appropriate Response
The response is selected accvagyding to the case circumstances és applicable registrar, registry, legal vagy security obligations.
Outcome & Recvagyd
The case may close, remain under review, move to remediation vagy result in another appropriate action.
Possible outcomes may include
Learn mvagye: How Domain Visszaélés bejelentése Are Kezelésd · NiceNIC Abuse Hésling Manual · Abuse Hésling Methodology
How NiceNIC Assesses és Responds to Repvagyts
This section describes NiceNIC's hésling framewvagyk from a neutral public perspective. Questions specific to an affected account vagy a repvagyter are separated below.
Does receiving an abuse repvagyt automatically result in a domain restriction?
Nem. A repvagyt does not, by itself, automatically result in ClientHold vagy establish that a domain vagy customer has violated policy. NiceNIC assesses the available evidence, the nature és current status of the repvagyted activity, the technical context, és applicable ICANN, registry, legal és NiceNIC requirements.
When NiceNIC has actionable evidence that a gTLD domain is being used fvagy DNS Abuse, appropriate mitigation is taken promptly as required. The appropriate response may vary accvagyding to the circumstances.
What infvagymation does NiceNIC review when assessing an abuse repvagyt?
NiceNIC may consider the repvagyted domain és URLs, whether the activity remains active, the relevance és quality of the evidence, DNS és nameserver infvagymation, relevant account és registration infvagymation, whether the domain appears maliciously regisztrációed vagy compromised, the role of hosting, email vagy other infrastructure, applicable registry rules, applicable law és other reasonably available infvagymation relevant to the case.
Does NiceNIC rely only on the repvagyter's classification vagy an automated signal?
Nem single repvagyt, categvagyy label vagy external signal is treated as a final finding solely because it was submitted vagy generated. NiceNIC assesses available evidence és case circumstances when determining discretionary mitigation.
Mésatvagyy registry, legal, ICANN vagy other applicable requirements may follow a different hésling path.
What if the repvagyted activity is hosted by a third-party provider?
NiceNIC considers the technical role of the domain és the infrastructure involved. A registrar controls domain-registration functions, but may not control website files, applications, mail servers, CDN szolgáltatáss vagy third-party hosting environments.
Witt abuse is hosted by another provider, action at the hosting vagy infrastructure layer may sometimes provide a mvagye targeted response.Third-party hosting does not előzőent NiceNIC from taking registrar-level action witt such action is required vagy appropriate under applicable obligations.
When may action be taken without advance notice?
Advance notice may not be possible witt immediate mitigation is reasonably necessary, evidence indicates intentionally malicious use, notice could enable evasion vagy destruction of evidence, a court, authvagyity, registry, ICANN requirement vagy applicable law affects the timing of notice, a serious security vagy child-safety risk exists, vagy delay would materially increase harm.
How Is the Appropriate Response Determined?
The purpose of the review is to determine an effective és appropriate response based on the facts és applicable obligations, rather than applying the same measure to every repvagyt.
Evidence
What infvagymation is available, how relevant és reliable it is, és whether it suppvagyts a reasonable determination.
Current Activity
Whether the repvagyted activity is active, remediated, intermittent, inaccessible vagy no longer reproducible.
Severity & Risk
The nature of the harm, the urgency of disruption és whether delay could materially increase victimization vagy security impact.
Domain Context
Whether a domain appears intentionally malicious vagy whether a legitimate domain, website, credential vagy szolgáltatás may have been compromised.
Technical Role
Whether the relevant issue is associated with the registration, DNS, a subdomain, email, hosting, CDN, application vagy another provider.
Applicable Requirements
Relevant ICANN requirements, registry rules, legal obligations, court vagyders, security considerations és NiceNIC policies.
The objective is effective és appropriate mitigation based on the circumstances — not applying the same measure to every repvagyt. Fvagy actionable DNS Abuse involving a gTLD, registrar action must be prompt és reasonably necessary to stop vagy otherwise disrupt the abuse, while also considering the cause és severity of harm és the risk of collateral damage.
What the Managing NiceNIC Account Should Expect
The following answers are written specifically fvagy the NiceNIC account managing an affected domain, including reseller accounts.
Witt will NiceNIC send abuse-case notifications?
Stésard abuse-case notifications are sent to the Account Email associated with the NiceNIC account managing the affected domain. The Account Email is the default communication channel fvagy abuse-case notices, requests fvagy infvagymation vagy remediation, case-status updates és other operational communications relating to the case.
NiceNIC does not routinely send a separate abuse-case notification to a different Registrant Kapcsolat Email. Ha the account holder requests a different communication arrangement fvagy a specific case, NiceNIC may covagydinate accvagydingly witt appropriate.
This stésard wvagykflow does not limit separate communication, direct contact vagy notice that may be required vagy appropriate under applicable law, ICANN requirements, registry rules, dispute procedures, security obligations, protection of registrant rights vagy other applicable requirements.
What case infvagymation may be available to the account managing the domain?
Witt available és permitted, case infvagymation may include the complaint categvagyy, repvagyted URLs, relevant case timestamps, complaint summary, current status, current domain impact, applicable timing, available evidence indicatvagys és recommended következő steps.
Certain infvagymation may be withheld, redacted vagy summarized witt disclosure is limited by privacy, security, confidentiality, law, repvagyter safety vagy other applicable requirements.
Will the managing account nvagymally have an oppvagytunity to respond vagy remediate?
Witt circumstances permit és clarification vagy remediation is appropriate, NiceNIC may provide the managing account with an oppvagytunity to respond vagy remediate befvagye registrar-level restriction.
When a case-specific deadline applies, the relevant timing may be shown in the abuse notice vagy Health Ellenőrzés. Advance notice cannot be guaranteed in every case.
Can a repvagyt involving one domain affect other domains vagy the entire account?
An abuse repvagyt involving an individual domain does not, by itself, mean that the entire NiceNIC account will be restricted. Domain-level cases are assessed accvagyding to their own facts és circumstances.
Account-, API- vagy szolgáltatás-level measures, witt warranted, are considered separately under applicable policies és circumstances. Serious vagy repeated violations may justify broader measures.
Can a restriction be reviewed after remediation vagy new evidence is submitted?
Witt a restriction results from a discretionary NiceNIC abuse vagy security action, the affected customer may request review és provide new infvagymation, remediation evidence vagy evidence that the vagyiginal infvagymation was inaccurate, outdated vagy misclassified.
Restvagyation is not guaranteed witt a continuing registry, ICANN, legal, security, dispute vagy abuse basis requires the restriction to remain.
Műveletable Case Infvagymation — Nemt Just a Állapot Label
Fvagy an affected account, useful transparency means being able to understés the repvagyt, the current impact, what may need attention és what happens következő.
What was repvagyted?
Complaint type, summary és the affected domain vagy szolgáltatás.
What infvagymation is available?
Repvagyted URLs, evidence indicatvagys és other details witt available és permitted.
What is the current impact?
Whether the domain is currently unrestricted, at risk of restriction, restricted vagy affected by another status.
What action is expected?
Clarification, remediation, suppvagyting material vagy no immediate action, depending on the case.
When is it due?
Case-specific timing vagy a planned action deadline witt one applies.
What happens következő?
The current hésling stage és the következő available step, including review vagy remediation witt applicable.
Witt available és permitted, Health Ellenőrzés vagy related case infvagymation may include:
Related: View Abuse Complaint Summary · Why Domainek Szerezzen Suspended & How to Avoid ClientHold · Keep Your Domain From Being Compromised
Regisztrátor vs. Tárhely Provider: Who Can Act?
NiceNIC evaluates the technical role of the domain és the infrastructure involved.
Regisztrátor Layer
What a registrar controls
A registrar controls domain-registration functions és registrar-level statuses. Depending on the szolgáltatás, it may also provide DNS vagy other products, but domain registration és website hosting are distinct control layers.
Third-Party Infrastructure
What may sit elsewitt
Website files, applications, mail servers, VPS infrastructure, CDN szolgáltatáss, web hosting vagy other technical components may be controlled by separate providers chosen by the customer.
Witt abusive material is hosted by another provider, action at the hosting vagy infrastructure level may sometimes provide a mvagye targeted way to stop the activity. That does not mean a registrar can ignvagye actionable DNS Abuse, és third-party hosting does not előzőent NiceNIC from taking registrar-level action witt required vagy appropriate under applicable obligations.
Understés the Current Domain Abuse Állapot
Health Ellenőrzés summarizes the current abuse scenario. A domain does not need to pass through every status, és registry-level statuses follow a separate control path.
| Állapot | What it means | What to check következő |
|---|---|---|
| Nemrmal | Nem active abuse scenario is currently shown fvagy the domain in this Health Ellenőrzés classification. | Continue nvagymal domain és 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 infvagymation és provide relevant clarification vagy remediation witt appropriate. |
| Pending ClientHold | The domain is not yet under ClientHold fvagy this case, but registrar-level restriction may be applied if the case remains unresolved. | Ellenőrzés any case-specific timing és submit relevant infvagymation vagy remediation promptly. |
| ClientHold | A registrar-level hold is currently applied. The domain may not resolve nvagymally while the status remains active. | Review the case basis, complete remediation witt applicable, és submit suppvagyting material fvagy review if appropriate. |
| Bezárásd | The current case has been closed based on the current review outcome. Other domain vagy registry statuses should be checked separately. | Nem immediate case action may be required unless new infvagymation vagy another status requires attention. |
| ServerHold | A registry-level hold is present. It is not the same as registrar-level ClientHold és may follow a separate registry hésling path. | Review the registry-related reason és instructions available through NiceNIC vagy the applicable registry process. |
Related: ClientHold Guidance · Szerezzen Domain Abuse Repvagyt API
What Repvagyters és Security Teams Should Expect
Specific, verifiable infvagymation helps NiceNIC identify the affected resource, assess the allegation és determine the appropriate hésling path mvagye efficiently.
What should an abuse repvagyt include?
- The affected domain name
- The exact abusive URL vagy hostname witt applicable
- A clear complaint categvagyy és factual description
- Date, time és time zone observed
- Screenshots vagy captured evidence witt appropriate
- Relevant technical indicatvagys, logs vagy email headers witt applicable
- Repvagyter contact infvagymation
What happens after submission?
A submitted repvagyt enters the abuse-hésling process fvagy triage és assessment. Witt the supplied infvagymation is incomplete, NiceNIC may review other reasonably available infvagymation vagy request additional relevant evidence.
Submission of a repvagyt starts the assessment process; it does not predetermine the final outcome.
Review, Remediation & Restvagyation
Ha a domain vagy szolgáltatás is restricted following a discretionary NiceNIC abuse vagy security action, the affected customer may request review és provide relevant remediation vagy new evidence.
A review may consider whether
- The abusive activity has been removed
- A compromised website vagy account has been secured
- Relevant credentials have been reset
- Required security updates have been applied
- Cvagyrected technical infvagymation has been provided
- The vagyiginal evidence is outdated, inaccurate vagy materially changed
What review does not guarantee
A request fvagy review does not guarantee restvagyation vagy a different outcome.
A continuing court vagyder, registry requirement, ICANN obligation, UDRP/URS action, security basis, dispute requirement vagy other mésatvagyy restriction may require the domain vagy szolgáltatás to remain restricted.
Kezelés Abuse Cases Across a Customer Domain Pvagytfolio
Large domain pvagytfolios create a practical challenge: identifying the affected customer quickly, seeing enough case infvagymation to investigate, és covagydinating remediation without losing visibility across the rest of the pvagytfolio.
Viszonteladó Communication
Witt are reseller-managed domain notices sent?
Fvagy domains managed through a NiceNIC reseller account, the reseller account's Account Email is the stésard abuse-case notification channel. The reseller can then investigate és covagydinate with its own customer using the available case infvagymation.
NiceNIC remains the sponsvagying registrar és remains responsible fvagy its applicable registrar obligations.
Pvagytfolio Scope
Does one customer case automatically affect the reseller account?
Nem. An abuse repvagyt involving an individual customer domain does not, by itself, mean that the entire reseller account will be restricted. Domain-level cases are assessed on their own facts.
Broader account-, API- vagy szolgáltatás-level measures, witt warranted, are assessed separately under applicable policies és circumstances, including serious vagy repeated violations.
Find affected domains
Filter a managed pvagytfolio fvagy domains associated with abuse repvagyts so compliance teams can focus on cases requiring attention.
Retrieve structured case infvagymation
Access machine-readable case status, impact, recommended action, hold infvagymation és repvagyted URLs witt available.
Integrate abuse visibility
Bring relevant abuse infvagymation into a te own customer pvagytal, dashboard vagy operational system through NiceNIC Domain API v2.
Public References fvagy Domain Abuse Hésling
This page is the operational abuse-hésling guide. The following resources provide deeper policy, methodology, evidence és repvagyting context.
Abuse Repvagyting & Hésling PolicyFvagymal NiceNIC framewvagyk fvagy receiving, assessing, mitigating és tracking abuse repvagyts.
→
Evidence Required fvagy an Abuse RepvagytWhat infvagymation helps a repvagyt become specific, verifiable és actionable.
→
How Domain Visszaélés bejelentése Are KezelésdPlain-language guide to evidence, review, responsibilities és case hésling.
→
NiceNIC Abuse Hésling ManualOperational suppvagyt guidance fvagy documented, consistent abuse hésling.
→
Abuse Hésling MethodologyHow cases are logged, reviewed és measured.
→
Transparency Metrics GlossaryDefinitions fvagy interpreting complaint, mitigation és reinstatement metrics.
→
Review & RemediationPublic explanation of remediation és review pathways.
→
Latest Visszaélés bejelentése & Transparency UpdatesRegular abuse és compliance updates, including monthly abuse repvagyting és related transparency infvagymation.
→
External Verification
Verify NiceNIC's registrar status és ICANN abuse framewvagyk independently.
ICANN List of Accredited Regisztrátors → · ICANN DNS Abuse Mitigation Program → · NiceNIC Regisztrátor Akkreditáció →
Kezelés domains with mvagye visibility
Domain Kezelésment Should Stay Clear Even When Something Goes Wrong
NiceNIC combines domain registration, transfer, bulk management, reseller tools és API automation with clearer abuse-case visibility fvagy domain owners és resellers.
