fail2ban bad ip database: ip 202.69.73.114

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

ip: 202.69.73.114
hostname: 202.69.73.114
country: [HK] Hong Kong
first reported: 24.09.2018 00:27.10 GMT+0100
last reported: 22.01.2019 07:44.15 GMT+0100
time period: 120d 08h 17m 05s
total reports: 10
reported by: 3 host(s)
filter(s): sshd (6)
ssh (4)
tor exit node no
badips.com db
Lookup
  

port scan of '202.69.73.114':

[-hide]
# Nmap 6.40 scan initiated Mon Sep 24 00:28:02 2018 as: /usr/bin/nmap -sU -sS -O 202.69.73.114
Nmap scan report for 202.69.73.114
Host is up (0.18s latency).
Not shown: 998 filtered ports, 996 open|filtered ports
PORT     STATE  SERVICE
113/tcp  closed ident
443/tcp  open   https
500/udp  closed isakmp
520/udp  closed route
2000/udp closed cisco-sccp
4500/udp closed nat-t-ike
Device type: general purpose|firewall|storage-misc
Running (JUST GUESSING): Linux 3.X|2.6.X (95%), Fortinet embedded (86%), Axcient embedded (86%)
OS CPE: cpe:/o:linux:linux_kernel:3 cpe:/o:linux:linux_kernel:2.6
Aggressive OS guesses: Linux 3.2 - 3.6 (95%), Linux 2.6.32 - 2.6.39 (93%), Linux 2.6.32 (91%), Linux 2.6.32 - 2.6.33 (89%), Linux 2.6.38 (89%), Linux 2.6.31 (88%), Linux 2.6.18 - 2.6.22 (88%), Linux 2.6.32 - 3.0 (87%), Linux 3.5 (87%), Linux 3.0 - 3.9 (87%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 9 hops

OS detection performed. Please report any incorrect results at http://nmap.org/submit/ .
# Nmap done at Mon Sep 24 00:28:33 2018 -- 1 IP address (1 host up) scanned in 31.91 seconds
Σ = 40 | Δt = 0.003216028213501s