API documentation
Вземи Домейн Доклад за злоупотреба
Вземи 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 | Цяло число | Номер 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"
}
резултат от отговора
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",
}
