fail2ban bad ip database: ip 104.131.79.34

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

ip: 104.131.79.34
hostname: 104.131.79.34
country: [??] UNKNOWN
first reported: 20.11.2018 22:32.20 GMT+0100
last reported: 29.11.2018 14:27.08 GMT+0100
time period: 8d 15h 54m 48s
total reports: 10
reported by: 4 host(s)
filter(s): sshd (7)
ssh (3)
tor exit node no
badips.com db
Lookup
  

port scan of '104.131.79.34':

[-hide]
# Nmap 6.40 scan initiated Tue Nov 20 22:33:01 2018 as: /usr/bin/nmap -sU -sS -O 104.131.79.34
Nmap scan report for 104.131.79.34
Host is up (0.080s latency).
Not shown: 1000 open|filtered ports, 991 filtered ports
PORT    STATE SERVICE
22/tcp  open  ssh
25/tcp  open  smtp
80/tcp  open  http
110/tcp open  pop3
143/tcp open  imap
443/tcp open  https
587/tcp open  submission
993/tcp open  imaps
995/tcp open  pop3s
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.26 - 2.6.35 (94%), Linux 3.0 (93%), Linux 2.6.32 (93%), Linux 2.6.32 - 3.9 (93%), Linux 3.0 - 3.9 (93%), Linux 2.6.32 - 3.6 (92%), Linux 2.6.23 - 2.6.38 (90%), Linux 3.8 (90%), Crestron XPanel control system (89%), Netgear DG834G WAP or Western Digital WD TV media player (89%)
No exact OS matches for host (test conditions non-ideal).

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