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: 8593
Incidents (24h): 109
Attempts: 65437

Recently seen addresses

View latest 100

IP address	Score	Abuse type	Reported by	Lifecycle	DNSBL	Time since last attack
66.116.241.89	7.36	SSH Brute Force	Vulpelab	Monitoring	Not listed	34s
62.60.130.193	16.56	SSH Brute Force	Vulpelab	Monitoring	Not listed	3m
118.123.164.43	7.36	SSH Brute Force	Vulpelab	Monitoring	Not listed	16m
94.154.43.63	10.25	SSH Brute Force	Vulpelab	Monitoring	Not listed	33m
34.79.254.110	10.6	Scan SSH Brute Force	Vulpelab	Monitoring	Not listed	35m
35.233.122.247	7.93	SSH Brute Force	Vulpelab	Monitoring	Not listed	37m
64.62.197.151	6.4	SSH Brute Force	Vulpelab	Monitoring	Not listed	1h 33m
92.118.39.50	7.36	SSH Brute Force	Vulpelab	Monitoring	Not listed	1h 36m
65.49.1.232	2.4	Scan	Vulpelab	Monitoring	Not listed	1h 47m
92.118.39.49	7.36	SSH Brute Force	Vulpelab	Monitoring	Not listed	3h 4m
77.239.124.62	7.36	SSH Brute Force	Vulpelab	Monitoring	Not listed	3h 50m
168.144.129.40	1.5	Scan	Vulpelab	Monitoring	Not listed	4h 30m
115.140.161.61	7.36	SSH Brute Force	Vulpelab	Monitoring	Not listed	4h 41m
193.47.62.69	7.36	SSH Brute Force	Vulpelab	Monitoring	Not listed	4h 43m
181.28.101.14	7.36	SSH Brute Force	Vulpelab	Monitoring	Not listed	4h 49m

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.