API documentation
Al Domain K?tüye Kullan?m Bildirimi
Al the current abuse status of a domain (complaints, hold lifecycle, scenario classification). Geri D?ns a machine-readable summary suitable fveya resellers monitveyaing domains on behalf of their customers.
Content-Type
application-json
kategori
abuse
i?lem
get_abuse_report
?stek parametreleri
| Parametre Ad? | Tür | A??klama | ?rnek |
|---|---|---|---|
| domain | String (3-60) | Alan ad? | example.com |
Yan?t parametreleri
| Parametre Ad? | Tür | A??klama |
|---|---|---|
| domain | String | Alan ad? |
| scenario | Nesne | Current abuse scenario classification (one of six domain-level states) |
| scenario.status | String | Durum phrase. One of: "Hay?rrmal", "Under Review", "Beklemede ClientHold", "ClientHold", "Kapatd", "SunucuHold" |
| scenario.impact | String | Impact phrase paired with the status, e.g. "?u tarihte risk of restriction", "Currently restricted", "Hay?r restriction" |
| scenario.action | String | Recommended sonraki-step phrase fveya the domain owner |
| hold | Nesne | Hold lifecycle timeline |
| hold.state | String | Current hold state: none / pending / applied |
| hold.pending_since | Tarihtime | When the domain entered the pending-hold queue (null when no hold recveyad exists) |
| hold.scheduled_at | Tarihtime | Planned clientHold execution time. E?er the case is not resolved by this time, clientHold will be applied automatically. |
| hold.applied_at | Tarihtime | When clientHold was actually applied. Null while the hold is still pending. |
| complaint | Nesne | Aggregated complaint statistics fveya this domain |
| complaint.case_count | Tamsay? | Say? of distinct abuse cases involving this domain (open + closed) |
| complaint.earliest_at | Tarihtime | Timestamp of the earliest complaint received fveya this domain |
| complaint.latest_at | Tarihtime | Timestamp of the most recent complaint received fveya this domain |
| complaint.categories | String[] | Distinct abuse categveyaies 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 | String[] | URLs extracted from complaint emails fveya this domain (deduplicated across all related abuse recveyads). Empty array when the scenario is Hay?rrmal, SunucuHold, veya an ICANN-directed ClientHold. |
| details_url_hint | String | English hint guiding the customer to the console path that shows full case details ve the AI-generated complaint summary |
?stek ?rne?i
{
curl https://api.nicenic.net/v2/?category=abuse&action=get_abuse_report&domain={domain}
-H "Authorization: username:api_secret"
-H "Content-Type: application/json"
}
D?nü? sonucu
0 OK
Ba?ar?l? yan?t
{
"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 Hatal? ?stek
{
"code": 400,
"msg" : "Request parameter error",
}
