Eleven minutes after our team at NiceNIC received a phishing report, we had three reports about the same domain. The first flagged phishing. The second described suspected phishing and fraud. The third raised a different possibility: the domain might be serving as a command-and-control (C2) panel for information-stealing malware.
By then, our system had already scheduled the domain for suspension. The third report appeared in the complaint log, which also showed that a hold was pending. The schedule remained in place overnight. The following afternoon, our team brought the suspension forward and sent the reporter an update.
When we reviewed the case, we wanted to understand what happened between those two events. The reporter had supplied new information while there was still time to change the decision. We compared the complaint history with the domain status log to see when that change actually took effect on our side.
Reconstructing the timeline
The complaint log records when reports arrive, when our team sends a reply, and when we issue a suspension instruction. The domain status log records changes our system observes in the domain's Extensible Provisioning Protocol (EPP) status. We used both because a reply to a reporter, an instruction to suspend, and a recorded domain hold are three distinct events.
| Time (UTC+8) | Recorded event |
|---|---|
| Nov 18, 2026, 22:57:49 | The first phishing report entered the complaint system. The system subsequently scheduled the domain for suspension. |
| Nov 18, 23:09:00 | A second report described suspected phishing and fraud involving the same domain. |
| Nov 18, 23:09:09 | The third report described a possible malware control panel. The complaint log still showed the existing suspension schedule. |
| Nov 19, 17:10:08 | Our team issued an immediate suspension instruction and sent an update to the reporter. |
| Nov 19, 17:11:00 | During synchronization, our system observed a registry-side serverHold. The registry's original action time is unknown. |
| Nov 19, 17:11:01 | The domain status log recorded NiceNIC's addition of clientHold. |
The registrar hold was recorded 18 hours and 13 minutes after the first report. The complaint log does not separately timestamp the start or completion of manual review. We can say how long the malware report had been on file when we acted. We cannot assign that entire interval to an investigation.
Why the third report mattered
The first two reports gave our team a reason to investigate how the domain was being used against people who visited it. The third raised a separate question: could the domain also be part of the infrastructure used to control information-stealing malware?
That was an allegation requiring verification. The use of the term C2 in a report does not, by itself, establish that devices were infected or that the reported panel was active. It does give the person reviewing the case a specific question to examine. Evidence supporting that allegation could change how urgently the registrar needs to act.
This is where the existing suspension schedule mattered. Anyone reading the complaint history could see that an action had already been arranged. What the schedule could not tell them was whether its timing still made sense in light of the latest report. By the time our team issued the immediate suspension instruction, the malware allegation had been on file for about 18 hours. Looking back, we should have reassessed the schedule when that report arrived.
What the two hold entries tell us
The final two rows of the timeline are easy to misread. A registrar can set clientHold, and a registry can set serverHold. Either status requires the registry to withhold the domain's DNS delegation. RFC 5731, Section 2.3
In this case, our complaint log records the team's instruction at 17:10:08. At 17:11:00, our system synchronized the domain status and observed serverHold. The registry may have set that status earlier. At 17:11:01, our log recorded the addition of our own registrar-side hold.
That sequence answers a narrow question with confidence: our team issued the instruction before our system recorded the registry hold, and the registrar-side hold appears in the status history. It leaves two other questions open: when the registry first acted, and when the reported service became unreachable to a particular user. Neither can be reconstructed from these logs alone.
What our team is changing
Our team has decided to change how we handle these follow-up reports.
When a further report concerns a domain already scheduled for suspension, we will examine what it adds to the case. A report that describes a different use of the domain, supplies new evidence of ongoing harm, or materially changes the assessed risk warrants a fresh look at the timing. If we verify ongoing high-risk abuse that warrants domain-level suspension, we will apply clientHold immediately.
Our October 2026 Abuse Report gives an aggregate view of complaint handling. This case exposed a question that a monthly average cannot answer: what happens when the evidence changes after a decision has been made? Here, the reporter had already identified the new concern. The next decision belonged to our team.
Top comments (0)