fail2ban bad ip database: ip 200.6.136.184

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

ip: 200.6.136.184
hostname: 200.6.136.184
country: [??] UNKNOWN
first reported: 22.10.2018 11:35.55 GMT+0100
last reported: 29.11.2018 13:09.03 GMT+0100
time period: 38d 02h 33m 08s
total reports: 3
reported by: 2 host(s)
filter(s): sshd (2)
ssh (1)
tor exit node no
badips.com db
Lookup
  

port scan of '200.6.136.184':

[-hide]
# Nmap 6.40 scan initiated Mon Oct 22 11:36:01 2018 as: /usr/bin/nmap -sU -sS -O 200.6.136.184
Nmap scan report for 200.6.136.184
Host is up (0.23s latency).
Not shown: 997 open|filtered ports, 986 filtered ports
PORT     STATE  SERVICE
22/tcp   open   ssh
80/tcp   open   http
81/tcp   open   hosts2-ns
82/tcp   open   xfer
83/tcp   open   mit-ml-dev
554/tcp  open   rtsp
555/tcp  open   dsf
8000/tcp open   http-alt
8001/tcp open   vcom-tunnel
8002/tcp open   teradataordbms
8080/tcp open   http-proxy
8200/tcp closed trivnet1
9010/tcp open   sdr
9011/tcp closed unknown
22/udp   closed ssh
161/udp  closed snmp
8000/udp closed irdmi
Aggressive OS guesses: HP P2000 G3 NAS device (89%), Ubiquiti AirMax NanoStation WAP (Linux 2.6.32) (88%), Linux 3.0 (88%), OpenWrt 12.09-rc1 Attitude Adjustment (Linux 3.3 - 3.7) (88%), Linux 2.6.26 - 2.6.35 (88%), Linux 2.6.32 - 3.4.1 (88%), Netgear DG834G WAP or Western Digital WD TV media player (88%), Linux 3.0 - 3.9 (88%), Linux 3.3 (88%), Linux 2.6.38 (88%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 12 hops

OS detection performed. Please report any incorrect results at http://nmap.org/submit/ .
# Nmap done at Mon Oct 22 11:36:36 2018 -- 1 IP address (1 host up) scanned in 34.85 seconds
Σ = 15 | Δt = 0.0045690536499023s