fail2ban bad ip database: ip 174.90.202.1

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

ip: 174.90.202.1
hostname: 174.90.202.1
country: [CA] Canada
first reported: 18.11.2018 11:24.46 GMT+0200
last reported: 14.12.2018 18:24.46 GMT+0200
time period: 26d 07h
total reports: 11
reported by: 2 host(s)
filter(s): ssh (6)
ssh (5)
tor exit node no
badips.com db
Lookup
  

port scan of '174.90.202.1':

[-hide]
# Nmap 6.40 scan initiated Sun Nov 18 11:25:02 2018 as: /usr/bin/nmap -sU -sS -O 174.90.202.1
Nmap scan report for 174.90.202.1
Host is up (0.20s latency).
Not shown: 993 closed ports, 992 filtered ports
PORT      STATE         SERVICE
21/tcp    open          ftp
22/tcp    open          ssh
80/tcp    open          http
443/tcp   open          https
3389/tcp  open          ms-wbt-server
5901/tcp  open          vnc-1
6001/tcp  open          X11:1
8888/tcp  open          sun-answerbook
53/udp    open|filtered domain
67/udp    open|filtered dhcps
68/udp    open|filtered dhcpc
123/udp   open          ntp
631/udp   open|filtered ipp
5353/udp  open|filtered zeroconf
20004/udp open|filtered unknown
Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port
Aggressive OS guesses: Linux 3.2.0 (94%), Linux 2.6.18 - 2.6.22 (93%), IPFire firewall 2.11 (Linux 2.6.32) (89%), Linux 3.2.38 (89%), DD-WRT v24-sp1 (Linux 2.4) (88%), Linux 2.6.32 (88%), Linux 3.2 - 3.6 (88%), Tomato 1.27 - 1.28 (Linux 2.4.20) (87%), Linux 2.6.31 - 2.6.32 (87%), IGEL UD3 thin client (Linux 2.6) (86%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 20 hops

OS detection performed. Please report any incorrect results at http://nmap.org/submit/ .
# Nmap done at Sun Nov 18 11:43:48 2018 -- 1 IP address (1 host up) scanned in 1127.15 seconds
Σ = 37 | Δt = 0.0034599304199219s