A resource is blocklisted: respond to an incident

Examine the basis

Open the available incident on your verified resource. Compare identifier, period, public explanation and evidence. A shared IP or hosting relationship does not mean the infrastructure owner is the offender.

Respond

Choose acknowledgement, remediation, dispute or recheck. Describe your actions and attach suitable evidence. Disclose private customer data through the relevant request and permission workflow; a public comment is not a disclosure channel.

Await moderation

An investigation's public-list candidate goes through a separate review. An owner response does not automatically remove an entry: moderators check the basis, changes and validity. Follow status, reasons and updates. Feed consumers must honour revocation and expiry rather than treat entries as permanent blocks.