fail2ban bad ip database: ip 103.115.164.117

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

ip: 103.115.164.117
hostname: 103.115.164.117
country: [??] UNKNOWN
first reported: 20.11.2018 18:32.41 GMT+0100
last reported: 30.11.2018 17:55.32 GMT+0100
time period: 9d 23h 22m 51s
total reports: 4
reported by: 2 host(s)
filter(s): ssh (1)
sshd (3)
tor exit node no
badips.com db
Lookup
  

port scan of '103.115.164.117':

[-hide]
# Nmap 6.40 scan initiated Tue Nov 20 18:33:02 2018 as: /usr/bin/nmap -sU -sS -O 103.115.164.117
Nmap scan report for 103.115.164.117
Host is up (0.18s latency).
Not shown: 1991 closed ports
PORT     STATE         SERVICE
21/tcp   open          ftp
22/tcp   open          ssh
23/tcp   filtered      telnet
445/tcp  filtered      microsoft-ds
4321/tcp filtered      rwhois
5432/tcp open          postgresql
20/udp   open|filtered ftp-data
22/udp   open|filtered ssh
80/udp   open|filtered http
Aggressive OS guesses: Linux 2.6.26 - 2.6.35 (91%), Linux 3.0 - 3.9 (91%), Linux 2.6.23 - 2.6.38 (90%), Linux 2.6.32 - 2.6.39 (90%), Linux 2.6.37 (90%), Android 4.1.1 (89%), Linux 2.6.35 (89%), Linux 2.6.32 (89%), Linux 2.6.22 (89%), Linux 2.6.32 - 3.9 (88%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 14 hops

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