API documentation
取得 ドメイン 不正利用報(bào)告
取得 the current abuse status of a ドメイン (complaints, hold lifecycle, scenario classification). 戻るs a machine-readable summary suitable fまたは resellers monitまたはing ドメインs on behalf of their customers.
Content-Type
application-json
カテゴリ
abuse
アクション
get_abuse_report
リクエストパラメータ
| パラメータ名 | タイプ | 説明 | 例 |
|---|---|---|---|
| domain | 文字列 (3-60) | ドメイン名 | example.com |
レスポンスパラメータ
| パラメータ名 | タイプ | 説明 |
|---|---|---|
| domain | 文字列 | ドメイン名 |
| scenario | オブジェクト | Current abuse scenario classification (one of six ドメイン-level states) |
| scenario.status | 文字列 | ステータス phrase. One of: "いいえrmal", "Under Review", "保留中 ClientHold", "ClientHold", "閉じるd", "サーバーHold" |
| scenario.impact | 文字列 | Impact phrase paired with the status, e.g. "で risk of restriction", "Currently restricted", "いいえ restriction" |
| scenario.action | 文字列 | Recommended 次へ-step phrase fまたは the ドメイン owner |
| hold | オブジェクト | Hold lifecycle timeline |
| hold.state | 文字列 | Current hold state: none / pending / applied |
| hold.pending_since | 日付time | When the ドメイン entered the pending-hold queue (null when no hold recまたはd exists) |
| hold.scheduled_at | 日付time | Planned clientHold execution time. もし the case is not resolved by this time, clientHold will be applied automatically. |
| hold.applied_at | 日付time | When clientHold was actually applied. Null while the hold is still pending. |
| complaint | オブジェクト | Aggregated complaint statistics fまたは this ドメイン |
| complaint.case_count | 整數(shù) | 數(shù)量 of distinct abuse cases involving this ドメイン (open + closed) |
| complaint.earliest_at | 日付time | Timestamp of the earliest complaint received fまたは this ドメイン |
| complaint.latest_at | 日付time | Timestamp of the most recent complaint received fまたは this ドメイン |
| complaint.categories | 文字列[] | Distinct abuse categまたはies across all related cases, e.g. ["Phishing", "Malware"] |
| complaint.is_dns_abuse | Boolean | True when at least one case is classified as DNS Abuse |
| complaint.has_evidence | Boolean | True when at least one case has been confirmed to have sufficient evidence |
| complaint.reported_urls | 文字列[] | URLs extracted from complaint emails fまたは this ドメイン (deduplicated across all related abuse recまたはds). Empty array when the scenario is いいえrmal, サーバーHold、または an ICANN-directed ClientHold. |
| details_url_hint | 文字列 | English hint guiding the customer to the console path that shows full case details と the AI-generated complaint summary |
リクエスト例
{
curl https://api.nicenic.net/v2/?category=abuse&action=get_abuse_report&domain={domain}
-H "Authorization: username:api_secret"
-H "Content-Type: application/json"
}
返卻結(jié)果
0 OK
成功レスポンス
{
"code": 0,
"msg" : "success",
"data" : {
"domain": "example.com",
"scenario": {
"status": "Pending ClientHold",
"impact": "At risk of restriction",
"action": "Submit supporting materials now"
},
"hold": {
"state": "pending",
"pending_since": "2026-04-20 10:30:00",
"scheduled_at": "2026-04-22 10:30:00",
"applied_at": null
},
"complaint": {
"case_count": 3,
"earliest_at": "2026-03-12 09:14:00",
"latest_at": "2026-04-22 18:02:00",
"categories": ["Phishing", "Malware"],
"is_dns_abuse": true,
"has_evidence": true,
"reported_urls": [
"http://example.com/promo/win-iphone",
"http://example.com/dl/installer.exe"
]
},
"details_url_hint": "For full case details and the AI-generated complaint summary, sign in to www.unionroom.cn and go to My Account > My Products > Domain Name > Health Check."
}
}
400 不正なリクエスト
{
"code": 400,
"msg" : "Request parameter error",
}
