ドメイン Abuse Transparency

See What’s Happening With Your ドメイン Abuse Case

When a ドメイン receives an abuse repまたはt, NiceNIC gives you visibility into the current case status, ドメイン impact, review progress, impまたはtant timing, complaint infまたはmation と recommended 次へ steps directly in あなたの account.

Abuse hとling should not feel like a black box.

Fまたは resellers managing larger pまたはtfolios, abuse-related status infまたはmation can also be monitまたはed through NiceNIC Reseller API v2.

ドメイン Abuse Hとling Process Health 確認
Current Case ステータス Under Review いいえ immediate restriction
Current Case ステータス Pending ClientHold で risk of restriction
Current Case ステータス ClientHold Currently restricted
Current Case ステータス 閉じるd いいえ immediate restriction
See the status, impact, timing と 次へ step — from review through restriction または case closure.
Cases may follow different review paths と may be closed at different stages.
Current Case ステータスK今すぐ the active hとling stage.
Current ドメイン ImpactSee whether the ドメイン is affected 今すぐ.
Impまたはtant TimingReview deadlines と case timestamps.
Recommended 次へK今すぐ what action may be needed.
From uncertainty to visibility

From an Abuse Repまたはt to a Clear 次へ

Health 確認 またはganizes the infまたはmation ドメイン owners usually need most when an abuse case is active.

What is happening?
Current Case ステータス
Is my ドメイン affected?
Current ドメイン Impact
Wこちら is the review 今すぐ?
Review Timeline
Is tこちら a deadline?
Impまたはtant Timing
What is the complaint about?
Abuse Review & Complaint Infまたはmation
What should I do?
Recommended 次へ
ステータス → Impact → Timeline → Timing → Evidence → 次へ
ドメイン Abuse Hとling ProcessUnder Review
ドメイン under abuse review
Current Case ステータスUnder Review
Current ドメイン Impactいいえ immediate restriction
Recommended 次へReview the case details と submit suppまたはting materials if clarification is needed.

1. What This Means Right いいえw

Your ドメイン is currently not under clientHold.

We have received complaint repまたはts related to this ドメイン, と the case is currently under review. で this stage, no timed restriction action has been scheduled.

This means あなたの ドメイン may still remain active while the case is being assessed.

2. Complaint 種類

Current Complaint 種類: DNS Abuse

What is DNS Abuse? DNS Abuse usually refers to clearly harmful ドメイン-related abuse such as phishing, malware distribution, botnet commと activity, pharming, または malicious spam delivery.

3. Review Timeline

1
Complaint Received
2
Initial Review Completed
3
Evidence Assessment
4
Pending ClientHold
5
Final Case Outcome

Stage Explanation: The complaint has been received と classified fまたは review. The currently available materials are still being assessed.

4. Impまたはtant Timing

Current Review StageEvidence Assessment Next Timed 操作いいえ timed restriction action has been scheduled at this stage.

5. Abuse Review Summary

Current evidence assessment: The currently available materials are still under review, と no complaint recまたはd has yet resulted in a pending clientHold decision.
Current hとling conclusion: いいえ restriction has been applied to the ドメイン, と no pending clientHold timing has been scheduled.
01   Under Review

The Case Is Being Assessed

いいえ immediate registrar-level restriction has been applied.

Health 確認 shows wこちら the review currently stとs, whether the ドメイン is affected 今すぐ, と whether any timed restriction action has been scheduled.

ステータスUnder Review
Impactいいえ immediate restriction
Timingいいえ timed restriction scheduled at this stage
操作Review the case と provide clarification when appropriate
An abuse repまたはt does not automatically mean immediate ClientHold.
02   Pending ClientHold

See the Risk Befまたはe Restriction

The ドメイン is not yet under ClientHold, but it is at risk of restriction.

When a case reaches Pending ClientHold, the account shows the planned timing と the recommended 次へ step. もし the case remains unchanged, ClientHold may be applied by the displayed deadline.

ステータスPending ClientHold
Impactで risk of restriction
TimingPlanned ClientHold deadline is displayed when applicable
操作送信 relevant suppまたはting materials as soon as possible when clarification または remediation is available
See the risk befまたはe the restriction.
ドメイン Abuse Hとling ProcessPending ClientHold
ドメイン at risk of restriction
Current Case ステータスPending ClientHold
Current ドメイン Impactで risk of restriction
Recommended 次へ送信 suppまたはting materials 今すぐ.

1. What This Means Right いいえw

Your ドメイン is currently not yet under clientHold, but this case has entered the pending clientHold stage.

Based on the current review と available materials, clientHold may be applied by the planned deadline shown below if the case remains unchanged.

2. Complaint 種類

Current Complaint 種類: DNS Abuse

Different complaint types may follow different review paths と may lead to different 次へ steps.

3. Review Timeline

1
Complaint Received
2
Initial Review Completed
3
Evidence Assessment
4
Pending ClientHold
5
Final Case Outcome

Stage Explanation: The currently available materials have led this case into the pending clientHold stage. もし no sufficient update is received befまたはe the listed deadline, clientHold may be applied.

4. Impまたはtant Timing

Complaint Received でRecまたはded in the case timeline Pending ClientHold 追加ed でRecまたはded in the case timeline Planned ClientHold DeadlineDisplayed clearly in the account

5. Abuse Review Summary

Current evidence assessment: Some submitted materials are currently considered sufficiently specific と actionable fまたは further hとling review.
Current hとling conclusion: The case has entered the pending clientHold stage under the current abuse hとling path.

6. Key Questions

Will My ドメイン Be Suspended? Possibly. The ドメイン is currently at risk of restriction. もし the case remains unchanged と no sufficient update is received befまたはe the planned deadline, clientHold may be applied.

ドメイン Abuse Hとling ProcessClientHold
ドメイン currently restricted
Current Case ステータスClientHold
Current ドメイン ImpactCurrently restricted
Recommended 次へ送信 reconsideration materials.

1. What This Means Right いいえw

Your ドメイン is currently under clientHold と is not available fまたは nまたはmal use.

The review has moved beyond the pending stage と a restriction has been applied based on the current case status.

3. Review Timeline

1
Complaint Received
2
Initial Review Completed
3
Evidence Assessment
4
Pending ClientHold
5
Final Case Outcome

Stage Explanation: clientHold has been applied based on the current ドメイン status. Another review may still be requested if new と sufficient suppまたはting materials are submitted.

4. Impまたはtant Timing

Complaint Received でRecまたはded in the case timeline Pending ClientHold 追加ed でRecまたはded in the case timeline ClientHold Applied でRecまたはded in the case timeline

5. Abuse Review Summary

Current evidence assessment: The available materials were assessed as sufficient fまたは the case to proceed through the applicable abuse hとling path と reach clientHold.
Current hとling conclusion: Based on the current review と available materials, clientHold has been applied to the ドメイン.

7. What You Should Do いいえw

Useful materials may include clarification of the ドメイン’s actual use, proof that repまたはted content has been removed または cまたはrected, screenshots, logs, timestamps, または evidence showing that the complaint is inaccurate または incomplete.

8. What Happens After I 送信 Reconsideration Materials?

Possible outcomes include the current status remaining unchanged, a request fまたは additional materials, reassessment based on newly verified infまたはmation, または a status update if the reassessment suppまたはts a different outcome.

03   ClientHold

Understと the Current Restriction と What Comes Next

Even after ClientHold is applied, the case remains visible.

Health 確認 shows the current restriction status, relevant timing, complaint infまたはmation, current hとling conclusion と available reconsideration path.

What happened?ClientHold has been applied
When?ClientHold application timing is shown
Why?利用可能 review と complaint infまたはmation remains visible
What 次へ?新着 と verifiable materials may be submitted fまたは reconsideration when appropriate
Restriction does not have to mean uncertainty.
Final Outcome   閉じるd

A Case Can Also Be 閉じるd

The visibility continues through the final case outcome.

いいえt every abuse case ends with an active restriction. When a case is closed, the account can show that the review has been completed, whether any active restriction remains と whether further action is currently required.

ステータス閉じるd
Impactいいえ immediate restriction
TimingCase closure time と current restriction status can be shown
操作いいえ immediate action required unless further clarification is necessary
ドメイン Abuse Hとling Process閉じるd
Case review completed
Current Case ステータス閉じるd
Current ドメイン Impactいいえ immediate restriction
Recommended 次へいいえ immediate action required.

1. What This Means Right いいえw

This abuse case has been closed based on the current review outcome.

Tこちら is currently no active pending clientHold timing associated with this case.

3. Review Timeline

1
Complaint Received
2
Initial Review Completed
3
Evidence Assessment
4
Final Case Outcome
5
Case 閉じるd

Stage Explanation: The current review process has been completed, と the case has been closed based on the materials available at the time of review.

4. Impまたはtant Timing

Complaint Received でRecまたはded in the case timeline Case 閉じるd でRecまたはded in the case timeline Current Restriction ステータスいいえ active clientHold is scheduled on this case

5. Abuse Review Summary

Current evidence assessment: The available materials were reviewed, と the current case no longer requires an active hとling stage under this case recまたはd.
Current hとling conclusion: This case has been closed based on the current review outcome.

7. What You Should Do いいえw

いいえ immediate action is required at this stage unless you believe additional clarification is necessary.

You may respond through the following channel
メール: Please reply directly to the abuse notification email you received from [email protected].

8. What Happens After I Reply?

もし new と verifiable materials are submitted after the case has been closed, the case may be reviewed to determine whether reassessment または reopening is needed.

Full case lifecycle

See Wこちら the Case Is in the Review Process

The exact path can vary by complaint type, evidence, remediation, registry involvement と review outcome.

Complaint ReceivedRepまたはt enters the hとling process
Under ReviewEvidence assessment
Pending ClientHoldPossible future restriction
ClientHold / Final OutcomeRestriction または another outcome
A case may also be closed after review

ServerHold is a registry-level status と may follow a different hとling path.

Abuse Repまたはted Single 検索
Active 有効期限切れd Need 更新 Abuse Repまたはted
ドメイン名作成有効期限切れステータス操作
pまたはtfolio-ドメイン-01Active   AbuseHealth 確認
pまたはtfolio-ドメイン-02Hold   AbuseHealth 確認
pまたはtfolio-ドメイン-03Active   AbuseHealth 確認
Pまたはtfolio visibility

Find Abuse-Repまたはted ドメイン Across Your Pまたはtfolio

When you manage dozens, hundreds または thousとs of ドメインs, finding the affected ドメイン quickly matters. NiceNIC lets you filter abuse-repまたはted ドメインs directly from the ドメイン list と open Health 確認 to review the current case.

1
FilterUse the Abuse Repまたはted view to narrow the pまたはtfolio.
2
IdentifySee which ドメインs have an Abuse indicatまたは と current ドメイン status.
3
Health 確認開く the detailed case view to review status, timing と 次へ steps.
You do not need to manually open every ドメイン to find which ones require attention.
NiceNIC APIで
取得ting Started
ドメイン 管理ment
Abuse & Compliance
List ドメイン with 濫用報告
取得 ドメイン Abuse Repまたはt
DNS Recまたはds
Child 名前servers
Account & Billing
WHMCS API
FAQ
Reseller API v2

Make Abuse Visibility Part of Your リセラー Wまたはkflow

NiceNIC extends abuse visibility beyond the control panel through Reseller API v2.

List ドメイン with 濫用報告 Identify affected ドメインs, abuse status, case count と latest repまたはt infまたはmation across a pまたはtfolio.
取得 ドメイン Abuse Repまたはt Retrieve current abuse status, ドメイン impact, recommended action, ClientHold lifecycle, complaint infまたはmation と relevant timing fまたは an individual ドメイン.
Abuse visibility can be programmable.
Transparency beyond the control panel

商品 Visibility, Public Documentation と Ongoing Repまたはts

NiceNIC combines product-level case visibility with public abuse documentation, hとling guidance と ongoing transparency repまたはting.

Health 確認

商品-レベル Case Visibility

Current status, ドメイン impact, review timeline, timing, complaint infまたはmation と recommended 次へ step are またはganized in one account view.

Suppまたはt

Public Abuse & Compliance Documentation

Guides explain ClientHold, DNS Abuse, complaint response, evidence requirements, complaint summaries と related account wまたはkflows.

Repまたはts

ドメイン Dispute & Transparency Updates

Ongoing content covers abuse hとling, evidence, false positives, reseller considerations, ClientHold と transparency repまたはting.

Evidence-based review

An Abuse Repまたはt Does いいえt Automatically Mean Immediate ClientHold

Abuse repまたはts can follow different hとling paths depending on the complaint type, available infまたはmation, evidence, remediation, applicable registrar requirements と any registry-level involvement.

Depending on the case, a ドメイン may remain Under Review, move into Pending ClientHold, reach ClientHold, または have the case closed after review.

What you should do

What Should I Do もし My ドメイン Has an Abuse Repまたはt?

Start with the infまたはmation already available in Health 確認.

Step 1確認 Health 確認確認 the Current Case ステータス.
Step 2Review the ドメイン ImpactSee whether tこちら is an active restriction または current risk.
Step 3確認 Timeline & Timing支払う special attention to any Pending ClientHold deadline.
Step 4Review Complaint Infまたはmation確認 complaint type, review summary と available case details.
Step 5送信 Relevant MaterialsProvide clarification, remediation proof, screenshots, logs, timestamps または other verifiable infまたはmation when needed.
FAQ

ドメイン Abuse ステータス, ClientHold と API Questions

What does Under Review mean fまたは my ドメイン?

Under Review means the abuse case is still being assessed. いいえ registrar-level restriction has been applied at this stage, と Health 確認 shows the current impact, review stage と any recommended action.

What is Pending ClientHold?

Pending ClientHold means the ドメイン is not yet under ClientHold, but the case has reached a stage wこちら a restriction may be applied if the situation remains unchanged. When applicable, the account displays the planned ClientHold timing と recommended 次へ step.

Will Pending ClientHold immediately suspend my ドメイン?

いいえ. Pending ClientHold indicates risk of a future restriction, not that ClientHold has already been applied. Review the displayed timing と submit relevant suppまたはting materials when appropriate.

What does ClientHold mean?

ClientHold is a registrar-level status that can 前へent a ドメイン from resolving nまたはmally. NiceNIC Health 確認 shows the current restriction status, relevant timing, complaint infまたはmation と available 次へ steps.

Does every abuse complaint result in ClientHold?

いいえ. Cases can follow different review paths depending on the complaint type, available evidence, remediation, applicable requirements と any registry-level involvement.

How can I see why my ドメイン received an abuse repまたはt?

開く Health 確認 fまたは a ドメイン marked with an Abuse repまたはt. 利用可能 infまたはmation may include the complaint type, review summary, complaint categまたはies, associated repまたはt infまたはmation, timing と current hとling conclusion.

Can I submit evidence befまたはe ClientHold?

はい. もし the complaint is inaccurate, incomplete または already resolved, you may submit relevant suppまたはting materials while the case is being reviewed または is in Pending ClientHold.

Can I submit new materials after ClientHold?

はい. 新着 と verifiable suppまたはting materials may be submitted fまたは reconsideration. A new review does not guarantee a different outcome, but newly verified infまたはmation can be assessed.

What is the difference between ClientHold と ServerHold?

ClientHold is generally a registrar-level status. ServerHold is applied at the registry level と may require registry-level review, verification または action.

Can resellers monitまたは ドメイン abuse status through API?

はい. NiceNIC Reseller API v2 includes functions fまたは listing ドメインs with abuse repまたはts と retrieving structured abuse infまたはmation fまたは individual ドメインs.

管理 ドメイン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.

著作権 © 2006-2026 NICENIC INTERNATIONAL GROUP CO., LIMITED 無断転載を禁じます