Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: United Kingdom

Internet Service Provider: Telecity Customer - Idila Doo in Lon

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attack
Oct  8 03:47:01 web8 sshd\[11473\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.85.70.20  user=root
Oct  8 03:47:03 web8 sshd\[11473\]: Failed password for root from 80.85.70.20 port 42260 ssh2
Oct  8 03:50:18 web8 sshd\[12997\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.85.70.20  user=root
Oct  8 03:50:21 web8 sshd\[12997\]: Failed password for root from 80.85.70.20 port 52640 ssh2
Oct  8 03:53:23 web8 sshd\[14432\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.85.70.20  user=root
2019-10-08 17:06:14
attack
Oct  7 02:02:25 tdfoods sshd\[4522\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.85.70.20  user=root
Oct  7 02:02:27 tdfoods sshd\[4522\]: Failed password for root from 80.85.70.20 port 41652 ssh2
Oct  7 02:05:40 tdfoods sshd\[4762\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.85.70.20  user=root
Oct  7 02:05:43 tdfoods sshd\[4762\]: Failed password for root from 80.85.70.20 port 53444 ssh2
Oct  7 02:09:07 tdfoods sshd\[5170\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.85.70.20  user=root
2019-10-07 20:10:15
attackbots
detected by Fail2Ban
2019-10-07 16:17:52
attackbots
Oct  7 03:22:40 areeb-Workstation sshd[12208]: Failed password for root from 80.85.70.20 port 40226 ssh2
...
2019-10-07 05:59:31
attackspam
Oct  6 02:40:44 hanapaa sshd\[10789\]: Invalid user Qq@123 from 80.85.70.20
Oct  6 02:40:45 hanapaa sshd\[10789\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.85.70.20
Oct  6 02:40:47 hanapaa sshd\[10789\]: Failed password for invalid user Qq@123 from 80.85.70.20 port 40384 ssh2
Oct  6 02:44:05 hanapaa sshd\[11067\]: Invalid user xsw2ZAQ! from 80.85.70.20
Oct  6 02:44:05 hanapaa sshd\[11067\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.85.70.20
2019-10-07 02:36:14
attackspam
Sep 24 05:54:17 auw2 sshd\[25004\]: Invalid user g from 80.85.70.20
Sep 24 05:54:17 auw2 sshd\[25004\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.85.70.20
Sep 24 05:54:20 auw2 sshd\[25004\]: Failed password for invalid user g from 80.85.70.20 port 32938 ssh2
Sep 24 05:57:45 auw2 sshd\[25324\]: Invalid user ass from 80.85.70.20
Sep 24 05:57:45 auw2 sshd\[25324\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.85.70.20
2019-09-25 00:12:16
attack
$f2bV_matches
2019-09-22 23:19:03
attackbotsspam
Sep 11 19:58:18 web1 sshd\[6124\]: Invalid user 1 from 80.85.70.20
Sep 11 19:58:18 web1 sshd\[6124\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.85.70.20
Sep 11 19:58:21 web1 sshd\[6124\]: Failed password for invalid user 1 from 80.85.70.20 port 57690 ssh2
Sep 11 20:03:34 web1 sshd\[6541\]: Invalid user tester123 from 80.85.70.20
Sep 11 20:03:34 web1 sshd\[6541\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.85.70.20
2019-09-12 14:08:17
attackspam
Sep  8 23:21:15 vtv3 sshd\[22333\]: Invalid user guest from 80.85.70.20 port 35596
Sep  8 23:21:15 vtv3 sshd\[22333\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.85.70.20
Sep  8 23:21:17 vtv3 sshd\[22333\]: Failed password for invalid user guest from 80.85.70.20 port 35596 ssh2
Sep  8 23:26:00 vtv3 sshd\[24668\]: Invalid user tester from 80.85.70.20 port 53704
Sep  8 23:26:00 vtv3 sshd\[24668\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.85.70.20
Sep  8 23:39:57 vtv3 sshd\[31372\]: Invalid user ubuntu from 80.85.70.20 port 55182
Sep  8 23:39:57 vtv3 sshd\[31372\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.85.70.20
Sep  8 23:39:59 vtv3 sshd\[31372\]: Failed password for invalid user ubuntu from 80.85.70.20 port 55182 ssh2
Sep  8 23:44:48 vtv3 sshd\[1322\]: Invalid user ftpuser from 80.85.70.20 port 48910
Sep  8 23:44:48 vtv3 sshd\[1322\]: pam_unix\(sshd:auth\
2019-09-09 21:43:17
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 80.85.70.20
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10947
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;80.85.70.20.			IN	A

;; AUTHORITY SECTION:
.			3600	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2019090900 1800 900 604800 86400

;; Query time: 3 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Mon Sep 09 21:42:50 CST 2019
;; MSG SIZE  rcvd: 115
Host info
20.70.85.80.in-addr.arpa domain name pointer fairplay.playbest.de.
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

Non-authoritative answer:
20.70.85.80.in-addr.arpa	name = fairplay.playbest.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
58.221.7.174 attack
Unauthorized connection attempt detected from IP address 58.221.7.174 to port 2220 [J]
2020-02-05 21:00:58
77.243.15.186 attack
Unauthorized connection attempt detected from IP address 77.243.15.186 to port 80 [J]
2020-02-05 20:58:41
187.3.248.130 attack
Unauthorized connection attempt detected from IP address 187.3.248.130 to port 2220 [J]
2020-02-05 20:44:33
117.200.171.250 attack
Unauthorized connection attempt detected from IP address 117.200.171.250 to port 23 [J]
2020-02-05 20:27:37
84.52.97.249 attackspam
Unauthorized connection attempt detected from IP address 84.52.97.249 to port 80 [J]
2020-02-05 20:34:21
148.153.12.198 attack
Unauthorized connection attempt detected from IP address 148.153.12.198 to port 1433 [J]
2020-02-05 20:24:15
89.29.213.33 attack
Unauthorized connection attempt detected from IP address 89.29.213.33 to port 23 [J]
2020-02-05 20:57:41
150.109.164.133 attackbots
Unauthorized connection attempt detected from IP address 150.109.164.133 to port 5061 [J]
2020-02-05 20:47:41
82.81.25.188 attackspambots
Unauthorized connection attempt detected from IP address 82.81.25.188 to port 81 [J]
2020-02-05 20:58:02
122.51.116.103 attackspam
Unauthorized connection attempt detected from IP address 122.51.116.103 to port 8080 [J]
2020-02-05 20:26:22
93.115.120.140 attack
Unauthorized connection attempt detected from IP address 93.115.120.140 to port 23 [J]
2020-02-05 20:55:36
45.233.169.6 attackspam
Unauthorized connection attempt detected from IP address 45.233.169.6 to port 23 [J]
2020-02-05 21:03:26
91.237.182.34 attackspambots
Unauthorized connection attempt detected from IP address 91.237.182.34 to port 8080 [J]
2020-02-05 20:56:56
170.253.60.36 attack
Unauthorized connection attempt detected from IP address 170.253.60.36 to port 23 [J]
2020-02-05 20:46:31
112.35.133.231 attack
Unauthorized connection attempt detected from IP address 112.35.133.231 to port 6380 [J]
2020-02-05 20:28:48

Recently Reported IPs

180.252.208.70 45.126.96.192 79.98.91.42 157.245.4.129
110.78.155.244 177.40.123.149 171.5.52.185 241.241.41.206
85.221.250.147 210.37.67.50 113.180.113.250 210.110.155.132
23.190.126.246 37.107.90.71 191.44.202.39 131.18.45.248
230.205.103.224 183.184.112.116 46.149.95.116 115.75.68.6