fail2ban bad ip database: ip 206.81.24.64

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

ip: 206.81.24.64
hostname: 206.81.24.64
country: [US] United States
first reported: 20.11.2018 20:39.06 GMT+0100
last reported: 30.11.2018 00:24.35 GMT+0100
time period: 9d 03h 45m 29s
total reports: 11
reported by: 3 host(s)
filter(s): ssh (4)
sshd (7)
tor exit node no
badips.com db
Lookup
  

port scan of '206.81.24.64':

[-hide]
# Nmap 6.40 scan initiated Tue Nov 20 20:40:03 2018 as: /usr/bin/nmap -sU -sS -O 206.81.24.64
Nmap scan report for 206.81.24.64
Host is up (0.0062s latency).
Not shown: 997 open|filtered ports, 996 filtered ports
PORT     STATE  SERVICE
22/tcp   open   ssh
80/tcp   open   http
443/tcp  open   https
1022/tcp closed exp2
80/udp   closed http
443/udp  closed https
1022/udp closed exp2
Aggressive OS guesses: Linux 3.0 - 3.9 (94%), Linux 2.6.22 - 2.6.36 (93%), Netgear DG834G WAP or Western Digital WD TV media player (92%), Linux 2.6.32 - 3.9 (92%), Linux 2.6.26 - 2.6.35 (92%), Linux 3.0 (91%), Linux 2.6.18 (91%), HP P2000 G3 NAS device (91%), Ubiquiti AirMax NanoStation WAP (Linux 2.6.32) (91%), OpenWrt Kamikaze 7.09 (Linux 2.6.22) (91%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 6 hops

OS detection performed. Please report any incorrect results at http://nmap.org/submit/ .
# Nmap done at Tue Nov 20 20:40:42 2018 -- 1 IP address (1 host up) scanned in 39.97 seconds
Σ = 7 | Δt = 0.0047430992126465s