API documentation
Obtenir Domini Informe d'abús
Obtenir the current abuse status of a domini (complaints, hold lifecycle, scenario classification). Tornars a machine-readable summary suitable fo resellers monitoing dominis on behalf of their customers.
Content-Type
application-json
categoria
abuse
acció
get_abuse_report
Paràmetres de la sol·licitud
| Nom del paràmetre | Tipus | Descripció | Exemple |
|---|---|---|---|
| domain | Text (3-60) | Nom de domini | example.com |
Paràmetres de resposta
| Nom del paràmetre | Tipus | Descripció |
|---|---|---|
| domain | Text | Nom de domini |
| scenario | Objecte | Current abuse scenario classification (one of six domini-level states) |
| scenario.status | Text | Estat phrase. One of: "Normal", "Under Review", "Pendent ClientHold", "ClientHold", "Tancad", "ServidorHold" |
| scenario.impact | Text | Impact phrase paired with the status, e.g. "A risk of restriction", "Currently restricted", "No restriction" |
| scenario.action | Text | Recommended següent-step phrase fo the domini owner |
| hold | Objecte | Hold lifecycle timeline |
| hold.state | Text | Current hold state: none / pending / applied |
| hold.pending_since | Datatime | When the domini entered the pending-hold queue (null when no hold recod exists) |
| hold.scheduled_at | Datatime | Planned clientHold execution time. Si the case is not resolved by this time, clientHold will be applied automatically. |
| hold.applied_at | Datatime | When clientHold was actually applied. Null while the hold is still pending. |
| complaint | Objecte | Aggregated complaint statistics fo this domini |
| complaint.case_count | Enter | Número of distinct abuse cases involving this domini (open + closed) |
| complaint.earliest_at | Datatime | Timestamp of the earliest complaint received fo this domini |
| complaint.latest_at | Datatime | Timestamp of the most recent complaint received fo this domini |
| complaint.categories | Text[] | Distinct abuse categoies 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 | Text[] | URLs extracted from complaint emails fo this domini (deduplicated across all related abuse recods). Empty array when the scenario is Normal, ServidorHold, o an ICANN-directed ClientHold. |
| details_url_hint | Text | English hint guiding the customer to the console path that shows full case details i the AI-generated complaint summary |
Exemple de sol·licitud
{
curl https://api.nicenic.net/v2/?category=abuse&action=get_abuse_report&domain={domain}
-H "Authorization: username:api_secret"
-H "Content-Type: application/json"
}
Resultat retornat
0 OK
Resposta correcta
{
"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 Sol·licitud incorrecta
{
"code": 400,
"msg" : "Request parameter error",
}
