API documentation
?ld? et Domen ?stismar Hesabat?
?ld? et the current abuse status of a domen (complaints, hold lifecycle, scenario classification). Geris a machine-readable summary suitable fv? ya resellers monitv? yaing domens on behalf of their customers.
Content-Type
application-json
kateqoriya
abuse
?m?l
get_abuse_report
Sor?u parametrl?ri
| Parametrin ad? | N?v | T?svir et | Nümun? |
|---|---|---|---|
| domain | S?tr (3-60) | Domen ad? | example.com |
Cavab parametrl?ri
| Parametrin ad? | N?v | T?svir et |
|---|---|---|
| domain | S?tr | Domen ad? |
| scenario | Obyekt | Current abuse scenario classification (one of six domen-level states) |
| scenario.status | S?tr | Status phrase. One of: "Xeyrrmal", "Under Review", "G?zl?m?d? ClientHold", "ClientHold", "Ba?lad", "ServerHold" |
| scenario.impact | S?tr | Impact phrase paired with the status, e.g. "Kimi risk of restriction", "Currently restricted", "Xeyr restriction" |
| scenario.action | S?tr | Recommended N?vb?ti-step phrase fv? ya the domen owner |
| hold | Obyekt | Hold lifecycle timeline |
| hold.state | S?tr | Current hold state: none / pending / applied |
| hold.pending_since | Tarixtime | When the domen entered the pending-hold queue (null when no hold recv? yad exists) |
| hold.scheduled_at | Tarixtime | Planned clientHold execution time. ?g?r the case is not resolved by this time, clientHold will be applied automatically. |
| hold.applied_at | Tarixtime | When clientHold was actually applied. Null while the hold is still pending. |
| complaint | Obyekt | Aggregated complaint statistics fv? ya this domen |
| complaint.case_count | Tam ?d?d | Say? of distinct abuse cases involving this domen (open + closed) |
| complaint.earliest_at | Tarixtime | Timestamp of the earliest complaint received fv? ya this domen |
| complaint.latest_at | Tarixtime | Timestamp of the most recent complaint received fv? ya this domen |
| complaint.categories | S?tr[] | Distinct abuse categv? yaies 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 | S?tr[] | URLs extracted from complaint emails fv? ya this domen (deduplicated across all related abuse recv? yads). Empty array when the scenario is Xeyrrmal, ServerHold, v? ya an ICANN-directed ClientHold. |
| details_url_hint | S?tr | English hint guiding the customer to the console path that shows full case details v? the AI-generated complaint summary |
Sorgu Nümun?si
{
curl https://api.nicenic.net/v2/?category=abuse&action=get_abuse_report&domain={domain}
-H "Authorization: username:api_secret"
-H "Content-Type: application/json"
}
N?tic?nin qay?d???
0 OK
U?urlu cavab
{
"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 Yanl?? Sor?u
{
"code": 400,
"msg" : "Request parameter error",
}
