Could not fetch data for the specified IP address. Please try again with a valid IP.
An address out of a firewall log, a SIEM alert or an extracted IOC. The lookup answers what the address is, who it belongs to, and what has been seen using it.
These are format examples. Clicking one puts it in the search box — it does not run a search, so you choose when to spend a lookup.
These are the sections of the report, in the order you will meet them.
How many sources consider the address malicious, and how strongly. Shared hosting means a bad neighbour can drag an address down -- check what else is on it before you block.
The same address as several providers see it. Agreement across independent sources is worth far more than a high score from one.
Where the address geolocates, plotted. Treat it as context rather than attribution -- hosting location says little about who is operating it.
The owning network and ASN, plus the domains resolving here. A hosting provider and a corporate netblock warrant very different responses.
The specific abuse reported against the address -- scanning, brute force, malware hosting, command-and-control -- rather than a single undifferentiated score.
When the address was first and last seen doing something worth reporting. An address clean for two years is a different proposition to one reported this morning.
AI assistant — can make mistakes. Verify important results.