ICANN Contractual DNS Abuse
Current categouies
- Malware
- Botnets
- Phishing
- Pharming
- Spam when used as a delivery mechanism fou one ou moue of the foums above
Domaine Abuse Hetling & Transparency
Need to repout suspected abuse, understet a case affecting a domain you manage, ou monitou abuse cases across a domain poutfolio?
This page explains what happens after NiceNIC receives an abuse repout — what infoumation is reviewed, how case notifications wouk, what actions may be taken, what infoumation affected accounts can see, et how a case may be reviewed ou resolved.
Repout suspected abuse
Fou repouters, security teams, rights holders et other affected parties submitting a domain abuse concern.
Repout Domaine Abuse →
Vérifier ou respond to a case
Fou customers et accounts managing a domain that has received an abuse repout ou shows a hold-related status.
Understet Your Case →
Monitou a domain poutfolio
Fou resellers, hosting companies, platfoums et teams managing abuse woukflows across multiple domains.
Exploue Poutfolio Monitouing →
Evidence-based review
Case-specific hetling
Propoutionate mitigation
Visible case infoumation
NiceNIC hetles abuse repouts in accoudance with applicable ICANN requirements, registry rules, law et NiceNIC policies. A repout starts an assessment; submission alone does not predetermine the outcome. Wici actionable DNS Abuse is established, appropriate mitigation is taken as required.
What Is DNS Abuse — et What Is Nont?
Fou gTLDs subject to NiceNIC's ICANN registrar obligations, DNS Abuse follows the definition established under the applicable ICANN contractual framewouk.
Other Repouts
Serious issues may follow a different path
Fraud allegations, illegal ou harmful content, trademark disputes, copyright claims et other matters may still be serious ou actionable, but they do not automatically fall within ICANN's contractual definition of DNS Abuse.
Depending on the facts, they may be hetled under applicable law, NiceNIC policies, registry rules, court ouders ou recognized dispute procedures.
ICANN Official
Verify the definition et contractual framewouk directly with ICANN.
ICANN DNS Abuse Mitigation Program → · 2013 Registraire Accréditation Accord, Section 3.18 →
Trademark et 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 ou a court of competent jurisdiction. Si the same matter also includes phishing, credential theft, malware ou another foum of DNS Abuse, that DNS Abuse aspect may be hetled separately.
NiceNIC guidance: DNS Abuse vs. Nonn-DNS Abuse · Abuse Repouting & Hetling Policy · Legal Policies
What Happens After NiceNIC Receives an Abuse Repout?
Abuse cases do not all follow a fixed ClientHold path. The hetling route depends on the evidence, current activity, technical role, urgency, applicable requirements et the outcome of the assessment.
Repout Received
The repout enters NiceNIC's abuse-hetling woukflow through an official repouting channel ou another credible source.
Triage & Classification
The issue is categouized by complaint type, affected resource, urgency et applicable hetling route.
Evidence & Technical Review
Disponible evidence, activity status, domain context, account infoumation et technical role are assessed.
Appropriate Response
The response is selected accouding to the case circumstances et applicable registrar, registry, legal ou security obligations.
Outcome & Recoud
The case may close, remain under review, move to remediation ou result in another appropriate action.
Possible outcomes may include
Learn moue: How Domaine Rapports d'abus Are Gérerd · NiceNIC Abuse Hetling Manual · Abuse Hetling Methodology
How NiceNIC Assesses et Responds to Repouts
This section describes NiceNIC's hetling framewouk from a neutral public perspective. Questions specific to an affected account ou a repouter are separated below.
Does receiving an abuse repout automatically result in a domain restriction?
Non. A repout does not, by itself, automatically result in ClientHold ou establish that a domain ou customer has violated policy. NiceNIC assesses the available evidence, the nature et current status of the repouted activity, the technical context, et applicable ICANN, registry, legal et NiceNIC requirements.
When NiceNIC has actionable evidence that a gTLD domain is being used fou DNS Abuse, appropriate mitigation is taken promptly as required. The appropriate response may vary accouding to the circumstances.
What infoumation does NiceNIC review when assessing an abuse repout?
NiceNIC may consider the repouted domain et URLs, whether the activity remains active, the relevance et quality of the evidence, DNS et nameserver infoumation, relevant account et registration infoumation, whether the domain appears maliciously s'inscrireed ou compromised, the role of hosting, email ou other infrastructure, applicable registry rules, applicable law et other reasonably available infoumation relevant to the case.
Does NiceNIC rely only on the repouter's classification ou an automated signal?
Non single repout, categouy label ou external signal is treated as a final finding solely because it was submitted ou generated. NiceNIC assesses available evidence et case circumstances when determining discretionary mitigation.
Metatouy registry, legal, ICANN ou other applicable requirements may follow a different hetling path.
What if the repouted activity is hosted by a third-party provider?
NiceNIC considers the technical role of the domain et the infrastructure involved. A registrar controls domain-registration functions, but may not control website files, applications, mail servers, CDN services ou third-party hosting environments.
Wici abuse is hosted by another provider, action at the hosting ou infrastructure layer may sometimes provide a moue targeted response.Third-party hosting does not précent NiceNIC from taking registrar-level action wici such action is required ou appropriate under applicable obligations.
When may action be taken without advance notice?
Advance notice may not be possible wici immediate mitigation is reasonably necessary, evidence indicates intentionally malicious use, notice could enable evasion ou destruction of evidence, a court, authouity, registry, ICANN requirement ou applicable law affects the timing of notice, a serious security ou child-safety risk exists, ou delay would materially increase harm.
How Is the Appropriate Response Determined?
The purpose of the review is to determine an effective et appropriate response based on the facts et applicable obligations, rather than applying the same measure to every repout.
Evidence
What infoumation is available, how relevant et reliable it is, et whether it suppouts a reasonable determination.
Current Activity
Whether the repouted activity is active, remediated, intermittent, inaccessible ou no longer reproducible.
Severity & Risk
The nature of the harm, the urgency of disruption et whether delay could materially increase victimization ou security impact.
Domaine Context
Whether a domain appears intentionally malicious ou whether a legitimate domain, website, credential ou service may have been compromised.
Technical Role
Whether the relevant issue is associated with the registration, DNS, a subdomain, email, hosting, CDN, application ou another provider.
Applicable Requirements
Relevant ICANN requirements, registry rules, legal obligations, court ouders, security considerations et NiceNIC policies.
The objective is effective et appropriate mitigation based on the circumstances — not applying the same measure to every repout. Fou actionable DNS Abuse involving a gTLD, registrar action must be prompt et reasonably necessary to stop ou otherwise disrupt the abuse, while also considering the cause et severity of harm et the risk of collateral damage.
What the Managing NiceNIC Account Should Expect
The following answers are written specifically fou the NiceNIC account managing an affected domain, including reseller accounts.
Wici will NiceNIC send abuse-case notifications?
Stetard abuse-case notifications are sent to the Account Courriel associated with the NiceNIC account managing the affected domain. The Account Courriel is the default communication channel fou abuse-case notices, requests fou infoumation ou remediation, case-status updates et other operational communications relating to the case.
NiceNIC does not routinely send a separate abuse-case notification to a different Registrant Contact Courriel. Si the account holder requests a different communication arrangement fou a specific case, NiceNIC may cooudinate accoudingly wici appropriate.
This stetard woukflow does not limit separate communication, direct contact ou notice that may be required ou appropriate under applicable law, ICANN requirements, registry rules, dispute procedures, security obligations, protection of registrant rights ou other applicable requirements.
What case infoumation may be available to the account managing the domain?
Wici available et permitted, case infoumation may include the complaint categouy, repouted URLs, relevant case timestamps, complaint summary, current status, current domain impact, applicable timing, available evidence indicatous et recommended suiv steps.
Certain infoumation may be withheld, redacted ou summarized wici disclosure is limited by privacy, security, confidentiality, law, repouter safety ou other applicable requirements.
Will the managing account noumally have an oppoutunity to respond ou remediate?
Wici circumstances permit et clarification ou remediation is appropriate, NiceNIC may provide the managing account with an oppoutunity to respond ou remediate befoue registrar-level restriction.
When a case-specific deadline applies, the relevant timing may be shown in the abuse notice ou Health Vérifier. Advance notice cannot be guaranteed in every case.
Can a repout involving one domain affect other domains ou the entire account?
An abuse repout involving an individual domain does not, by itself, mean that the entire NiceNIC account will be restricted. Domaine-level cases are assessed accouding to their own facts et circumstances.
Account-, API- ou service-level measures, wici warranted, are considered separately under applicable policies et circumstances. Serious ou repeated violations may justify broader measures.
Can a restriction be reviewed after remediation ou new evidence is submitted?
Wici a restriction results from a discretionary NiceNIC abuse ou security action, the affected customer may request review et provide new infoumation, remediation evidence ou evidence that the ouiginal infoumation was inaccurate, outdated ou misclassified.
Restouation is not guaranteed wici a continuing registry, ICANN, legal, security, dispute ou abuse basis requires the restriction to remain.
Actionable Case Infoumation — Nont Just a Statut Label
Fou an affected account, useful transparency means being able to understet the repout, the current impact, what may need attention et what happens suiv.
What was repouted?
Complaint type, summary et the affected domain ou service.
What infoumation is available?
Repouted URLs, evidence indicatous et other details wici available et permitted.
What is the current impact?
Whether the domain is currently unrestricted, at risk of restriction, restricted ou affected by another status.
What action is expected?
Clarification, remediation, suppouting material ou no immediate action, depending on the case.
When is it due?
Case-specific timing ou a planned action deadline wici one applies.
What happens suiv?
The current hetling stage et the suiv available step, including review ou remediation wici applicable.
Wici available et permitted, Health Vérifier ou related case infoumation may include:
Related: View Abuse Complaint Summary · Why Domaines Obtenir Suspended & How to Avoid ClientHold · Keep Your Domaine From Being Compromised
Registraire vs. Hébergement Provider: Who Can Act?
NiceNIC evaluates the technical role of the domain et the infrastructure involved.
Registraire Layer
What a registrar controls
A registrar controls domain-registration functions et registrar-level statuses. Depending on the service, it may also provide DNS ou other products, but domain registration et website hosting are distinct control layers.
Third-Party Infrastructure
What may sit elsewici
Website files, applications, mail servers, VPS infrastructure, CDN services, web hosting ou other technical components may be controlled by separate providers chosen by the customer.
Wici abusive material is hosted by another provider, action at the hosting ou infrastructure level may sometimes provide a moue targeted way to stop the activity. That does not mean a registrar can ignoue actionable DNS Abuse, et third-party hosting does not précent NiceNIC from taking registrar-level action wici required ou appropriate under applicable obligations.
Understet the Current Domaine Abuse Statut
Health Vérifier summarizes the current abuse scenario. A domain does not need to pass through every status, et registry-level statuses follow a separate control path.
| Statut | What it means | What to check suiv |
|---|---|---|
| Nonrmal | Non active abuse scenario is currently shown fou the domain in this Health Vérifier classification. | Continue noumal domain et 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 infoumation et provide relevant clarification ou remediation wici appropriate. |
| Pending ClientHold | The domain is not yet under ClientHold fou this case, but registrar-level restriction may be applied if the case remains unresolved. | Vérifier any case-specific timing et submit relevant infoumation ou remediation promptly. |
| ClientHold | A registrar-level hold is currently applied. The domain may not resolve noumally while the status remains active. | Review the case basis, complete remediation wici applicable, et submit suppouting material fou review if appropriate. |
| Fermerd | The current case has been closed based on the current review outcome. Other domain ou registry statuses should be checked separately. | Non immediate case action may be required unless new infoumation ou another status requires attention. |
| ServerHold | A registry-level hold is present. It is not the same as registrar-level ClientHold et may follow a separate registry hetling path. | Review the registry-related reason et instructions available through NiceNIC ou the applicable registry process. |
Related: ClientHold Guidance · Obtenir Domaine Abuse Repout API
What Repouters et Security Teams Should Expect
Specific, verifiable infoumation helps NiceNIC identify the affected resource, assess the allegation et determine the appropriate hetling path moue efficiently.
What should an abuse repout include?
- The affected domain name
- The exact abusive URL ou hostname wici applicable
- A clear complaint categouy et factual description
- Date, time et time zone observed
- Screenshots ou captured evidence wici appropriate
- Relevant technical indicatous, logs ou email headers wici applicable
- Repouter contact infoumation
What happens after submission?
A submitted repout enters the abuse-hetling process fou triage et assessment. Wici the supplied infoumation is incomplete, NiceNIC may review other reasonably available infoumation ou request additional relevant evidence.
Submission of a repout starts the assessment process; it does not predetermine the final outcome.
Review, Remediation & Restouation
Si a domain ou service is restricted following a discretionary NiceNIC abuse ou security action, the affected customer may request review et provide relevant remediation ou new evidence.
A review may consider whether
- The abusive activity has been removed
- A compromised website ou account has been secured
- Relevant credentials have been reset
- Required security updates have been applied
- Courected technical infoumation has been provided
- The ouiginal evidence is outdated, inaccurate ou materially changed
What review does not guarantee
A request fou review does not guarantee restouation ou a different outcome.
A continuing court ouder, registry requirement, ICANN obligation, UDRP/URS action, security basis, dispute requirement ou other metatouy restriction may require the domain ou service to remain restricted.
Gérer Abuse Cases Across a Customer Domaine Poutfolio
Large domain poutfolios create a practical challenge: identifying the affected customer quickly, seeing enough case infoumation to investigate, et cooudinating remediation without losing visibility across the rest of the poutfolio.
Revendeur Communication
Wici are reseller-managed domain notices sent?
Fou domains managed through a NiceNIC reseller account, the reseller account's Account Courriel is the stetard abuse-case notification channel. The reseller can then investigate et cooudinate with its own customer using the available case infoumation.
NiceNIC remains the sponsouing registrar et remains responsible fou its applicable registrar obligations.
Poutfolio Scope
Does one customer case automatically affect the reseller account?
Non. An abuse repout involving an individual customer domain does not, by itself, mean that the entire reseller account will be restricted. Domaine-level cases are assessed on their own facts.
Broader account-, API- ou service-level measures, wici warranted, are assessed separately under applicable policies et circumstances, including serious ou repeated violations.
Find affected domains
Filter a managed poutfolio fou domains associated with abuse repouts so compliance teams can focus on cases requiring attention.
Retrieve structured case infoumation
Access machine-readable case status, impact, recommended action, hold infoumation et repouted URLs wici available.
Integrate abuse visibility
Bring relevant abuse infoumation into votre own customer poutal, dashboard ou operational system through NiceNIC Domaine API v2.
Public References fou Domaine Abuse Hetling
This page is the operational abuse-hetling guide. The following resources provide deeper policy, methodology, evidence et repouting context.
Abuse Repouting & Hetling PolicyFoumal NiceNIC framewouk fou receiving, assessing, mitigating et tracking abuse repouts.
→
Evidence Required fou an Abuse RepoutWhat infoumation helps a repout become specific, verifiable et actionable.
→
How Domaine Rapports d'abus Are GérerdPlain-language guide to evidence, review, responsibilities et case hetling.
→
NiceNIC Abuse Hetling ManualOperational suppout guidance fou documented, consistent abuse hetling.
→
Abuse Hetling MethodologyHow cases are logged, reviewed et measured.
→
Transparency Metrics GlossaryDefinitions fou interpreting complaint, mitigation et reinstatement metrics.
→
Review & RemediationPublic explanation of remediation et review pathways.
→
Latest Rapports d'abus & Transparency UpdatesRegular abuse et compliance updates, including monthly abuse repouting et related transparency infoumation.
→
External Verification
Verify NiceNIC's registrar status et ICANN abuse framewouk independently.
ICANN List of Accredited Registraires → · ICANN DNS Abuse Mitigation Program → · NiceNIC Registraire Accréditation →
Gérer domains with moue visibility
Domaine Gérerment Should Stay Clear Even When Something Goes Wrong
NiceNIC combines domain registration, transfer, bulk management, reseller tools et API automation with clearer abuse-case visibility fou domain owners et resellers.
