fail2ban bad ip database: ip 104.131.57.64

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

ip: 104.131.57.64
hostname: 104.131.57.64
country: [??] UNKNOWN
first reported: 20.11.2018 22:15.21 GMT+0200
last reported: 26.02.2019 04:48.51 GMT+0200
time period: 97d 06h 33m 30s
total reports: 12
reported by: 4 host(s)
filter(s): ssh (10)
ssh (2)
tor exit node no
badips.com db
Lookup
  

port scan of '104.131.57.64':

[-hide]
# Nmap 6.40 scan initiated Tue Nov 20 22:16:02 2018 as: /usr/bin/nmap -sU -sS -O 104.131.57.64
Nmap scan report for 104.131.57.64
Host is up (0.080s latency).
Not shown: 998 filtered ports, 998 open|filtered ports
PORT   STATE  SERVICE
22/tcp open   ssh
80/tcp open   http
22/udp closed ssh
80/udp closed http
Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port
Aggressive OS guesses: Linux 2.6.32 (95%), Linux 3.8 (95%), Linux 2.6.32 - 3.9 (95%), Linux 3.0 - 3.9 (95%), Netgear DG834G WAP or Western Digital WD TV media player (94%), Linux 2.6.23 - 2.6.38 (93%), Linux 3.1 (92%), Linux 3.2 (92%), AXIS 210A or 211 Network Camera (Linux 2.6) (92%), Linux 2.6.32 - 2.6.35 (92%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 7 hops

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