ICANN Contractual DNS Abuse
Current categtaiies
- Malware
- Botnets
- Phishing
- Pharming
- Spam when used as a delivery mechanism ftai one tai mtaie of the ftaims above
Verkkotunnus Abuse Hjaling & Transparency
Need to reptait suspected abuse, understja a case affecting a verkkotunnus you manage, tai monittai abuse cases across a verkkotunnus ptaitfolio?
This page explains what happens after NiceNIC receives an abuse reptait — what inftaimation is reviewed, how case notifications wtaik, what actions may be taken, what inftaimation affected accounts can see, ja how a case may be reviewed tai resolved.
Reptait suspected abuse
Ftai reptaiters, security teams, rights holders ja other affected parties submitting a verkkotunnus abuse concern.
Reptait Verkkotunnus Abuse →
Tarkista tai respond to a case
Ftai customers ja accounts managing a verkkotunnus that has received an abuse reptait tai shows a hold-related status.
Understja Your Case →
Monittai a verkkotunnus ptaitfolio
Ftai resellers, hosting companies, platftaims ja teams managing abuse wtaikflows across multiple verkkotunnuss.
Expltaie Ptaitfolio Monittaiing →
Evidence-based review
Case-specific hjaling
Proptaitionate mitigation
Visible case inftaimation
NiceNIC hjales abuse reptaits in acctaidance with applicable ICANN requirements, registry rules, law ja NiceNIC policies. A reptait starts an assessment; submission alone does not predetermine the outcome. Wtässä actionable DNS Abuse is established, appropriate mitigation is taken as required.
What Is DNS Abuse — ja What Is Eit?
Ftai gTLDs subject to NiceNIC's ICANN registrar obligations, DNS Abuse follows the definition established under the applicable ICANN contractual framewtaik.
Other Reptaits
Serious issues may follow a different path
Fraud allegations, illegal tai harmful content, trademark disputes, copyright claims ja other matters may still be serious tai actionable, but they do not automatically fall within ICANN's contractual definition of DNS Abuse.
Depending on the facts, they may be hjaled under applicable law, NiceNIC policies, registry rules, court taiders tai recognized dispute procedures.
ICANN Official
Verify the definition ja contractual framewtaik directly with ICANN.
ICANN DNS Abuse Mitigation Program → · 2013 Rekisterinpitäjä Akkreditointi Agreement, Section 3.18 →
Trademark ja verkkotunnus-name rights disputes are not automatically DNS Abuse. Depending on the dispute, an appropriate mechanism may include UDRP, URS, a ccTLD-specific dispute policy tai a court of competent jurisdiction. Jos the same matter also includes phishing, credential theft, malware tai another ftaim of DNS Abuse, that DNS Abuse aspect may be hjaled separately.
NiceNIC guidance: DNS Abuse vs. Ein-DNS Abuse · Abuse Reptaiting & Hjaling Policy · Legal Policies
What Happens After NiceNIC Receives an Abuse Reptait?
Abuse cases do not all follow a fixed ClientHold path. The hjaling route depends on the evidence, current activity, technical role, urgency, applicable requirements ja the outcome of the assessment.
Reptait Received
The reptait enters NiceNIC's abuse-hjaling wtaikflow through an official reptaiting channel tai another credible source.
Triage & Classification
The issue is categtaiized by complaint type, affected resource, urgency ja applicable hjaling route.
Evidence & Technical Review
Saatavilla evidence, activity status, verkkotunnus context, account inftaimation ja technical role are assessed.
Appropriate Response
The response is selected acctaiding to the case circumstances ja applicable registrar, registry, legal tai security obligations.
Outcome & Rectaid
The case may close, remain under review, move to remediation tai result in another appropriate action.
Possible outcomes may include
Learn mtaie: How Verkkotunnus Väärinkäytösilmoitukset Are Hallinnoid · NiceNIC Abuse Hjaling Manual · Abuse Hjaling Methodology
How NiceNIC Assesses ja Responds to Reptaits
This section describes NiceNIC's hjaling framewtaik from a neutral public perspective. Questions specific to an affected account tai a reptaiter are separated below.
Does receiving an abuse reptait automatically result in a verkkotunnus restriction?
Ei. A reptait does not, by itself, automatically result in ClientHold tai establish that a verkkotunnus tai customer has violated policy. NiceNIC assesses the available evidence, the nature ja current status of the reptaited activity, the technical context, ja applicable ICANN, registry, legal ja NiceNIC requirements.
When NiceNIC has actionable evidence that a gTLD verkkotunnus is being used ftai DNS Abuse, appropriate mitigation is taken promptly as required. The appropriate response may vary acctaiding to the circumstances.
What inftaimation does NiceNIC review when assessing an abuse reptait?
NiceNIC may consider the reptaited verkkotunnus ja URLs, whether the activity remains active, the relevance ja quality of the evidence, DNS ja nameserver inftaimation, relevant account ja registration inftaimation, whether the verkkotunnus appears maliciously rekisteröied tai compromised, the role of hosting, email tai other infrastructure, applicable registry rules, applicable law ja other reasonably available inftaimation relevant to the case.
Does NiceNIC rely only on the reptaiter's classification tai an automated signal?
Ei single reptait, categtaiy label tai external signal is treated as a final finding solely because it was submitted tai generated. NiceNIC assesses available evidence ja case circumstances when determining discretionary mitigation.
Mjaattaiy registry, legal, ICANN tai other applicable requirements may follow a different hjaling path.
What if the reptaited activity is hosted by a third-party provider?
NiceNIC considers the technical role of the verkkotunnus ja the infrastructure involved. A registrar controls verkkotunnus-registration functions, but may not control website files, applications, mail servers, CDN palvelus tai third-party hosting environments.
Wtässä abuse is hosted by another provider, action at the hosting tai infrastructure layer may sometimes provide a mtaie targeted response.Third-party hosting does not edellinenent NiceNIC from taking registrar-level action wtässä such action is required tai appropriate under applicable obligations.
When may action be taken without advance notice?
Advance notice may not be possible wtässä immediate mitigation is reasonably necessary, evidence indicates intentionally malicious use, notice could enable evasion tai destruction of evidence, a court, authtaiity, registry, ICANN requirement tai applicable law affects the timing of notice, a serious security tai child-safety risk exists, tai delay would materially increase harm.
How Is the Appropriate Response Determined?
The purpose of the review is to determine an effective ja appropriate response based on the facts ja applicable obligations, rather than applying the same measure to every reptait.
Evidence
What inftaimation is available, how relevant ja reliable it is, ja whether it supptaits a reasonable determination.
Current Activity
Whether the reptaited activity is active, remediated, intermittent, inaccessible tai no longer reproducible.
Severity & Risk
The nature of the harm, the urgency of disruption ja whether delay could materially increase victimization tai security impact.
Verkkotunnus Context
Whether a verkkotunnus appears intentionally malicious tai whether a legitimate verkkotunnus, website, credential tai palvelu may have been compromised.
Technical Role
Whether the relevant issue is associated with the registration, DNS, a subverkkotunnus, email, hosting, CDN, application tai another provider.
Applicable Requirements
Relevant ICANN requirements, registry rules, legal obligations, court taiders, security considerations ja NiceNIC policies.
The objective is effective ja appropriate mitigation based on the circumstances — not applying the same measure to every reptait. Ftai actionable DNS Abuse involving a gTLD, registrar action must be prompt ja reasonably necessary to stop tai otherwise disrupt the abuse, while also considering the cause ja severity of harm ja the risk of collateral damage.
What the Managing NiceNIC Account Should Expect
The following answers are written specifically ftai the NiceNIC account managing an affected verkkotunnus, including reseller accounts.
Wtässä will NiceNIC send abuse-case notifications?
Stjaard abuse-case notifications are sent to the Account Sähköposti associated with the NiceNIC account managing the affected verkkotunnus. The Account Sähköposti is the default communication channel ftai abuse-case notices, requests ftai inftaimation tai remediation, case-status updates ja other operational communications relating to the case.
NiceNIC does not routinely send a separate abuse-case notification to a different Registrant Yhteystiedot Sähköposti. Jos the account holder requests a different communication arrangement ftai a specific case, NiceNIC may cotaidinate acctaidingly wtässä appropriate.
This stjaard wtaikflow does not limit separate communication, direct contact tai notice that may be required tai appropriate under applicable law, ICANN requirements, registry rules, dispute procedures, security obligations, protection of registrant rights tai other applicable requirements.
What case inftaimation may be available to the account managing the verkkotunnus?
Wtässä available ja permitted, case inftaimation may include the complaint categtaiy, reptaited URLs, relevant case timestamps, complaint summary, current status, current verkkotunnus impact, applicable timing, available evidence indicattais ja recommended seuraava steps.
Certain inftaimation may be withheld, redacted tai summarized wtässä disclosure is limited by privacy, security, confidentiality, law, reptaiter safety tai other applicable requirements.
Will the managing account ntaimally have an opptaitunity to respond tai remediate?
Wtässä circumstances permit ja clarification tai remediation is appropriate, NiceNIC may provide the managing account with an opptaitunity to respond tai remediate beftaie registrar-level restriction.
When a case-specific deadline applies, the relevant timing may be shown in the abuse notice tai Health Tarkista. Advance notice cannot be guaranteed in every case.
Can a reptait involving one verkkotunnus affect other verkkotunnuss tai the entire account?
An abuse reptait involving an individual verkkotunnus does not, by itself, mean that the entire NiceNIC account will be restricted. Verkkotunnus-level cases are assessed acctaiding to their own facts ja circumstances.
Account-, API- tai palvelu-level measures, wtässä warranted, are considered separately under applicable policies ja circumstances. Serious tai repeated violations may justify broader measures.
Can a restriction be reviewed after remediation tai new evidence is submitted?
Wtässä a restriction results from a discretionary NiceNIC abuse tai security action, the affected customer may request review ja provide new inftaimation, remediation evidence tai evidence that the taiiginal inftaimation was inaccurate, outdated tai misclassified.
Resttaiation is not guaranteed wtässä a continuing registry, ICANN, legal, security, dispute tai abuse basis requires the restriction to remain.
Toimintoable Case Inftaimation — Eit Just a Tila Label
Ftai an affected account, useful transparency means being able to understja the reptait, the current impact, what may need attention ja what happens seuraava.
What was reptaited?
Complaint type, summary ja the affected verkkotunnus tai palvelu.
What inftaimation is available?
Reptaited URLs, evidence indicattais ja other details wtässä available ja permitted.
What is the current impact?
Whether the verkkotunnus is currently unrestricted, at risk of restriction, restricted tai affected by another status.
What action is expected?
Clarification, remediation, supptaiting material tai no immediate action, depending on the case.
When is it due?
Case-specific timing tai a planned action deadline wtässä one applies.
What happens seuraava?
The current hjaling stage ja the seuraava available step, including review tai remediation wtässä applicable.
Wtässä available ja permitted, Health Tarkista tai related case inftaimation may include:
Related: View Abuse Complaint Summary · Why Verkkotunnukset Hanki Suspended & How to Avoid ClientHold · Keep Your Verkkotunnus From Being Compromised
Rekisterinpitäjä vs. Webhotelli Provider: Who Can Act?
NiceNIC evaluates the technical role of the verkkotunnus ja the infrastructure involved.
Rekisterinpitäjä Layer
What a registrar controls
A registrar controls verkkotunnus-registration functions ja registrar-level statuses. Depending on the palvelu, it may also provide DNS tai other products, but verkkotunnus registration ja website hosting are distinct control layers.
Third-Party Infrastructure
What may sit elsewtässä
Verkkosite files, applications, mail servers, VPS infrastructure, CDN palvelus, web hosting tai other technical components may be controlled by separate providers chosen by the customer.
Wtässä abusive material is hosted by another provider, action at the hosting tai infrastructure level may sometimes provide a mtaie targeted way to stop the activity. That does not mean a registrar can igntaie actionable DNS Abuse, ja third-party hosting does not edellinenent NiceNIC from taking registrar-level action wtässä required tai appropriate under applicable obligations.
Understja the Current Verkkotunnus Abuse Tila
Health Tarkista summarizes the current abuse scenario. A verkkotunnus does not need to pass through every status, ja registry-level statuses follow a separate control path.
| Tila | What it means | What to check seuraava |
|---|---|---|
| Eirmal | Ei active abuse scenario is currently shown ftai the verkkotunnus in this Health Tarkista classification. | Continue ntaimal verkkotunnus ja 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 inftaimation ja provide relevant clarification tai remediation wtässä appropriate. |
| Pending ClientHold | The verkkotunnus is not yet under ClientHold ftai this case, but registrar-level restriction may be applied if the case remains unresolved. | Tarkista any case-specific timing ja submit relevant inftaimation tai remediation promptly. |
| ClientHold | A registrar-level hold is currently applied. The verkkotunnus may not resolve ntaimally while the status remains active. | Review the case basis, complete remediation wtässä applicable, ja submit supptaiting material ftai review if appropriate. |
| Suljed | The current case has been closed based on the current review outcome. Other verkkotunnus tai registry statuses should be checked separately. | Ei immediate case action may be required unless new inftaimation tai another status requires attention. |
| ServerHold | A registry-level hold is present. It is not the same as registrar-level ClientHold ja may follow a separate registry hjaling path. | Review the registry-related reason ja instructions available through NiceNIC tai the applicable registry process. |
Related: ClientHold Guidance · Hanki Verkkotunnus Abuse Reptait API
What Reptaiters ja Security Teams Should Expect
Specific, verifiable inftaimation helps NiceNIC identify the affected resource, assess the allegation ja determine the appropriate hjaling path mtaie efficiently.
What should an abuse reptait include?
- The affected verkkotunnus name
- The exact abusive URL tai hostname wtässä applicable
- A clear complaint categtaiy ja factual description
- Date, time ja time zone observed
- Screenshots tai captured evidence wtässä appropriate
- Relevant technical indicattais, logs tai email headers wtässä applicable
- Reptaiter contact inftaimation
What happens after submission?
A submitted reptait enters the abuse-hjaling process ftai triage ja assessment. Wtässä the supplied inftaimation is incomplete, NiceNIC may review other reasonably available inftaimation tai request additional relevant evidence.
Submission of a reptait starts the assessment process; it does not predetermine the final outcome.
Review, Remediation & Resttaiation
Jos a verkkotunnus tai palvelu is restricted following a discretionary NiceNIC abuse tai security action, the affected customer may request review ja provide relevant remediation tai new evidence.
A review may consider whether
- The abusive activity has been removed
- A compromised website tai account has been secured
- Relevant credentials have been reset
- Required security updates have been applied
- Ctairected technical inftaimation has been provided
- The taiiginal evidence is outdated, inaccurate tai materially changed
What review does not guarantee
A request ftai review does not guarantee resttaiation tai a different outcome.
A continuing court taider, registry requirement, ICANN obligation, UDRP/URS action, security basis, dispute requirement tai other mjaattaiy restriction may require the verkkotunnus tai palvelu to remain restricted.
Hallinnoi Abuse Cases Across a Customer Verkkotunnus Ptaitfolio
Large verkkotunnus ptaitfolios create a practical challenge: identifying the affected customer quickly, seeing enough case inftaimation to investigate, ja cotaidinating remediation without losing visibility across the rest of the ptaitfolio.
Jälleenmyyjä Communication
Wtässä are reseller-managed verkkotunnus notices sent?
Ftai verkkotunnuss managed through a NiceNIC reseller account, the reseller account's Account Sähköposti is the stjaard abuse-case notification channel. The reseller can then investigate ja cotaidinate with its own customer using the available case inftaimation.
NiceNIC remains the sponstaiing registrar ja remains responsible ftai its applicable registrar obligations.
Ptaitfolio Scope
Does one customer case automatically affect the reseller account?
Ei. An abuse reptait involving an individual customer verkkotunnus does not, by itself, mean that the entire reseller account will be restricted. Verkkotunnus-level cases are assessed on their own facts.
Broader account-, API- tai palvelu-level measures, wtässä warranted, are assessed separately under applicable policies ja circumstances, including serious tai repeated violations.
Find affected verkkotunnuss
Filter a managed ptaitfolio ftai verkkotunnuss associated with abuse reptaits so compliance teams can focus on cases requiring attention.
Retrieve structured case inftaimation
Access machine-readable case status, impact, recommended action, hold inftaimation ja reptaited URLs wtässä available.
Integrate abuse visibility
Bring relevant abuse inftaimation into sinun own customer ptaital, dashboard tai operational system through NiceNIC Verkkotunnus API v2.
Public References ftai Verkkotunnus Abuse Hjaling
This page is the operational abuse-hjaling guide. The following resources provide deeper policy, methodology, evidence ja reptaiting context.
Abuse Reptaiting & Hjaling PolicyFtaimal NiceNIC framewtaik ftai receiving, assessing, mitigating ja tracking abuse reptaits.
→
Evidence Required ftai an Abuse ReptaitWhat inftaimation helps a reptait become specific, verifiable ja actionable.
→
How Verkkotunnus Väärinkäytösilmoitukset Are HallinnoidPlain-language guide to evidence, review, responsibilities ja case hjaling.
→
NiceNIC Abuse Hjaling ManualOperational supptait guidance ftai documented, consistent abuse hjaling.
→
Abuse Hjaling MethodologyHow cases are logged, reviewed ja measured.
→
Transparency Metrics GlossaryDefinitions ftai interpreting complaint, mitigation ja reinstatement metrics.
→
Review & RemediationPublic explanation of remediation ja review pathways.
→
Latest Väärinkäytösilmoitukset & Transparency UpdatesRegular abuse ja compliance updates, including monthly abuse reptaiting ja related transparency inftaimation.
→
External Verification
Verify NiceNIC's registrar status ja ICANN abuse framewtaik independently.
ICANN List of Accredited Rekisterinpitäjäs → · ICANN DNS Abuse Mitigation Program → · NiceNIC Rekisterinpitäjä Akkreditointi →
Hallinnoi verkkotunnuss with mtaie visibility
Verkkotunnus Hallinnoiment Should Stay Clear Even When Something Goes Wrong
NiceNIC combines verkkotunnus registration, transfer, bulk management, reseller tools ja API automation with clearer abuse-case visibility ftai verkkotunnus owners ja resellers.
