fail2ban bad ip database: ip 144.217.85.183

| ip database | live view | stats | report | help | api key:

ip: 144.217.85.183
hostname: 183.ip-144-217-85.net
country: [US] United States
first reported: 16.06.2018 11:15.21 GMT+0200
last reported: 27.05.2019 05:19.55 GMT+0200
time period: 344d 18h 04m 34s
total reports: 11
reported by: 3 host(s)
filter(s): ssh (11)
tor exit node no
badips.com db
Lookup
  

port scan of '144.217.85.183':

[-hide]
# Nmap 6.40 scan initiated Sat Jun 16 11:16:02 2018 as: /usr/bin/nmap -sU -sS -O 144.217.85.183
Nmap scan report for 183.ip-144-217-85.net (144.217.85.183)
Host is up (0.10s latency).
Not shown: 996 filtered ports, 990 open|filtered ports
PORT     STATE  SERVICE
21/tcp   closed ftp
22/tcp   open   ssh
80/tcp   closed http
9998/tcp open   distinct32
21/udp   closed ftp
22/udp   closed ssh
9020/udp closed tambora
9103/udp closed bacula-sd
9199/udp closed unknown
9200/udp closed wap-wsp
9370/udp closed unknown
9876/udp closed sd
9877/udp closed unknown
9950/udp closed apc-9950
Aggressive OS guesses: Linux 2.6.26 - 2.6.35 (94%), Linux 3.0 - 3.9 (94%), Linux 2.6.23 - 2.6.38 (93%), Linux 3.0 (93%), Linux 2.6.32 (92%), Netgear DG834G WAP or Western Digital WD TV media player (91%), Linux 2.6.32 - 3.9 (91%), Linux 2.6.8 - 2.6.27 (91%), HP P2000 G3 NAS device (91%), Linux 2.6.22 (90%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 11 hops

OS detection performed. Please report any incorrect results at http://nmap.org/submit/ .
# Nmap done at Sat Jun 16 11:16:32 2018 -- 1 IP address (1 host up) scanned in 30.68 seconds
Σ = 126 | Δt = 0.0042130947113037s