isIPsafe

Acceptable Use and Reporting Policy

Last updated 25 October 2026

isipsafe only works if people can trust what is in it. This policy explains what you may report, how, and what will get your reports removed or your access withdrawn. It forms part of our Terms of Service.

Report this

  • Traffic you observed on systems you run or are responsible for.
  • Activity that was clearly hostile or abusive: password guessing, exploit attempts, scanning for vulnerabilities, spam, phishing, flooding, fraud.
  • Activity that matches the categories you choose. If nothing fits, use the closest general category (Hacking, Exploited Host) and explain in the comment.

Do not report this

  • Addresses you have not seen misbehave yourself, including addresses copied from another list or feed.
  • Addresses you want to harm for personal, commercial or political reasons.
  • Normal traffic you happen to dislike, such as legitimate search engine crawlers that respect robots.txt, a single failed login, or a monitoring service you signed up for.
  • Your own infrastructure, your proxy, CDN or load balancer. Check that your logs record the real client address.
  • Addresses you are authorised to test, as a way of getting them blocked.

Profiles

  • Use a display name, logo and description that belong to you or your organisation. No impersonation, and no one else's trade marks without permission.
  • No offensive, unlawful or misleading content, and no advertising beyond a link to your own website.
  • We may hide or remove profile content, or switch a profile off, if it breaks these rules.

Comments

  • Keep them factual: what happened, when, how often. Log excerpts are ideal.
  • Remove personal data: your hostnames, usernames, customer details, email addresses or anything identifying a person other than the reported address.
  • No abuse, threats, defamatory statements, malware, links to malicious content, or advertising.

Automated reporting

Automation is welcome, and most reports arrive that way. Tune it so that it only fires on clear abuse (for example, several failed logins rather than one), uses accurate categories, and does not send more than one report per address per incident. If your automation goes wrong and sends bad data, use clear-address or tell us so we can clean up.

Using the Service

  • Do not try to get around rate limits, for example with multiple accounts or rotating addresses.
  • Do not scrape the website. The API returns the same data in a friendlier format.
  • Do not probe, scan or attack the Service itself. If you find a security problem, report it through the contact form; we will not take action against good-faith research that respects users' privacy and does not degrade the Service.
  • Do not use the data to harass, stalk or discriminate against people.
  • Use the data to protect your own systems (or the systems you run for your employer or clients). Do not resell it, redistribute it, or build products or services on it, directly or indirectly, without our written authorisation. See section 6 of the Terms of Service and the EULA; to ask for a licence, contact us.

What happens if you break the rules

We may remove reports, reduce the weight of your future reports, revoke your API key, block your addresses or close your account, depending on how serious the problem is. Where we can, we will tell you why.

If you are listed

If your address has been reported and you think the reports are wrong, contact us with the topic "False positive / delisting". Tell us the address, what runs on it, and why you believe the reports are mistaken. We review every request and will remove reports that break this policy. Scores also fall by themselves as reports age.