IP reputation

Look up an IP address

AttackHistory records incidents and attempts from participating collectors, then scores reputation and may publish qualifying addresses to DNSBL. A report is not automatically a ban.

Example lookup: 185.192.162.139

Currently listed: 0
Incidents: 5108
Incidents (24h): 80
Attempts: 35189

Recently seen addresses

View latest 100

IP address	Score	Abuse type	Reported by	Lifecycle	DNSBL	Time since last attack
62.60.130.193	16.22	SSH Brute Force	Vulpelab	Monitoring	Not listed	0s
156.238.239.147	7.93	SSH Brute Force	Vulpelab	Monitoring	Not listed	0s
154.83.16.14	7.93	SSH Brute Force	Vulpelab	Monitoring	Not listed	2m
43.135.38.86	7.36	SSH Brute Force	Vulpelab	Monitoring	Not listed	8m
88.147.30.59	8.33	SSH Brute Force	Vulpelab	Monitoring	Not listed	17m
80.94.95.115	15.29	SSH Brute Force	Vulpelab	Monitoring	Not listed	35m
77.239.124.181	7.36	SSH Brute Force	Vulpelab	Monitoring	Not listed	46m
138.226.239.234	7.93	SSH Brute Force	Vulpelab	Monitoring	Not listed	53m
64.23.218.208	1.73	Scan	Vulpelab	Monitoring	Not listed	56m
138.226.239.233	7.93	SSH Brute Force	Vulpelab	Monitoring	Not listed	1h 39m
92.118.39.77	7.36	SSH Brute Force	Vulpelab	Monitoring	Not listed	1h 44m
84.13.137.144	7.93	SSH Brute Force	Vulpelab	Monitoring	Not listed	1h 56m
195.178.191.5	7.93	SSH Brute Force	Vulpelab	Monitoring	Not listed	3h 22m
64.226.106.55	7.36	SSH Brute Force	Vulpelab	Monitoring	Not listed	3h 22m
65.49.1.52	2.4	Scan	Vulpelab	Monitoring	Not listed	3h 23m

Integrations

Report with a collector secret. Look up with a customer API key. Fail2Ban can send observations without installing a local daemon.

Manage API keys Latest

Public pages show a redacted summary. One public display name per account and event types may appear. Private server names, collector secrets, ahk_ keys, and VL- keys do not.