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",
}
