fail2ban bad ip database: ip 203.6.149.134

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

ip: 203.6.149.134
hostname: 203.6.149.134
country: [ID] Indonesia
first reported: 30.09.2018 21:39.51 GMT+0200
last reported: 07.03.2019 07:51.51 GMT+0200
time period: 157d 11h 12m
total reports: 11
reported by: 2 host(s)
filter(s): apache-nokiddies (1)
ssh (5)
tor exit node no
badips.com db
Lookup
  

port scan of '203.6.149.134':

[-hide]
# Nmap 6.40 scan initiated Sun Sep 30 21:40:03 2018 as: /usr/bin/nmap -sU -sS -O 203.6.149.134
Nmap scan report for 203.6.149.134
Host is up (0.21s latency).
Not shown: 1989 closed ports
PORT      STATE         SERVICE
22/tcp    filtered      ssh
23/tcp    filtered      telnet
80/tcp    open          http
111/tcp   open          rpcbind
443/tcp   open          https
8000/tcp  open          http-alt
8001/tcp  open          vcom-tunnel
10001/tcp open          scp-config
111/udp   open          rpcbind
123/udp   open|filtered ntp
161/udp   open          snmp
Aggressive OS guesses: Linux 2.6.32 - 3.9 (94%), Linux 3.0 - 3.9 (92%), Linux 2.6.32 - 3.2 (91%), Netgear DG834G WAP or Western Digital WD TV media player (91%), Linux 2.6.32 (90%), Linux 3.2 (89%), Comtrend CT536 wireless ADSL router (89%), Linux 3.8 (89%), Linux 3.1 (88%), Linux 2.6.35 (88%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 11 hops

OS detection performed. Please report any incorrect results at http://nmap.org/submit/ .
# Nmap done at Sun Sep 30 21:57:09 2018 -- 1 IP address (1 host up) scanned in 1026.71 seconds
Σ = 42 | Δt = 0.0075829029083252s