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 States

Internet Service Provider: Amazon Data Services NoVa

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attack
2019-10-30T21:32:17.461724abusebot-2.cloudsearch.cf sshd\[10351\]: Invalid user admin from 3.85.43.139 port 59310
2019-10-31 05:38:49
attackspam
Oct 30 11:29:11 srv01 sshd[11530]: Invalid user roo from 3.85.43.139
Oct 30 11:29:11 srv01 sshd[11530]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ec2-3-85-43-139.compute-1.amazonaws.com
Oct 30 11:29:11 srv01 sshd[11530]: Invalid user roo from 3.85.43.139
Oct 30 11:29:13 srv01 sshd[11530]: Failed password for invalid user roo from 3.85.43.139 port 46930 ssh2
Oct 30 11:33:01 srv01 sshd[11670]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ec2-3-85-43-139.compute-1.amazonaws.com  user=root
Oct 30 11:33:03 srv01 sshd[11670]: Failed password for root from 3.85.43.139 port 60374 ssh2
...
2019-10-30 18:33:52
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 3.85.43.139
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61914
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 113 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Oct 30 18:33:49 CST 2019
;; MSG SIZE  rcvd: 115
Host info
139.43.85.3.in-addr.arpa domain name pointer ec2-3-85-43-139.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
139.43.85.3.in-addr.arpa	name = ec2-3-85-43-139.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
142.44.218.192 attack
Dec 25 16:23:26 s1 sshd\[29639\]: Invalid user jcobs from 142.44.218.192 port 48052
Dec 25 16:23:26 s1 sshd\[29639\]: Failed password for invalid user jcobs from 142.44.218.192 port 48052 ssh2
Dec 25 16:25:33 s1 sshd\[30504\]: Invalid user childree from 142.44.218.192 port 42136
Dec 25 16:25:33 s1 sshd\[30504\]: Failed password for invalid user childree from 142.44.218.192 port 42136 ssh2
Dec 25 16:27:47 s1 sshd\[30601\]: User root from 142.44.218.192 not allowed because not listed in AllowUsers
Dec 25 16:27:47 s1 sshd\[30601\]: Failed password for invalid user root from 142.44.218.192 port 36214 ssh2
...
2019-12-26 03:12:40
203.24.110.23 attackbots
Unauthorized connection attempt detected from IP address 203.24.110.23 to port 445
2019-12-26 03:20:45
91.121.222.204 attack
Automatic report - SSH Brute-Force Attack
2019-12-26 03:24:11
51.75.31.33 attackbots
2019-12-25T16:57:30.279368abusebot-2.cloudsearch.cf sshd[4997]: Invalid user backup from 51.75.31.33 port 49028
2019-12-25T16:57:30.285476abusebot-2.cloudsearch.cf sshd[4997]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=33.ip-51-75-31.eu
2019-12-25T16:57:30.279368abusebot-2.cloudsearch.cf sshd[4997]: Invalid user backup from 51.75.31.33 port 49028
2019-12-25T16:57:32.199006abusebot-2.cloudsearch.cf sshd[4997]: Failed password for invalid user backup from 51.75.31.33 port 49028 ssh2
2019-12-25T16:59:35.156248abusebot-2.cloudsearch.cf sshd[5002]: Invalid user info2 from 51.75.31.33 port 36934
2019-12-25T16:59:35.162419abusebot-2.cloudsearch.cf sshd[5002]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=33.ip-51-75-31.eu
2019-12-25T16:59:35.156248abusebot-2.cloudsearch.cf sshd[5002]: Invalid user info2 from 51.75.31.33 port 36934
2019-12-25T16:59:37.570528abusebot-2.cloudsearch.cf sshd[5002]: Failed passwo
...
2019-12-26 03:19:57
103.140.54.146 attackbotsspam
SSH/22 MH Probe, BF, Hack -
2019-12-26 03:10:12
211.33.221.81 attack
IP blocked
2019-12-26 03:10:58
182.127.243.219 attackspam
HTTP/80/443 Probe, BF, WP, Hack -
2019-12-26 03:08:11
101.71.2.137 attackbots
Dec 25 18:56:13 mail sshd[535]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.71.2.137  user=root
Dec 25 18:56:15 mail sshd[535]: Failed password for root from 101.71.2.137 port 35434 ssh2
Dec 25 19:33:19 mail sshd[5461]: Invalid user webmaster from 101.71.2.137
Dec 25 19:33:19 mail sshd[5461]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.71.2.137
Dec 25 19:33:19 mail sshd[5461]: Invalid user webmaster from 101.71.2.137
Dec 25 19:33:22 mail sshd[5461]: Failed password for invalid user webmaster from 101.71.2.137 port 58922 ssh2
...
2019-12-26 03:39:21
188.13.167.103 attackbotsspam
Dec 25 17:30:55 vpn01 sshd[16607]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.13.167.103
Dec 25 17:30:58 vpn01 sshd[16607]: Failed password for invalid user lisa from 188.13.167.103 port 58624 ssh2
...
2019-12-26 03:13:00
222.92.139.158 attackbots
Dec 24 19:03:41 server sshd\[22732\]: Invalid user poliwoda from 222.92.139.158
Dec 24 19:03:41 server sshd\[22732\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.92.139.158 
Dec 24 19:03:44 server sshd\[22732\]: Failed password for invalid user poliwoda from 222.92.139.158 port 33524 ssh2
Dec 25 17:50:53 server sshd\[23068\]: Invalid user edu from 222.92.139.158
Dec 25 17:50:53 server sshd\[23068\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.92.139.158 
...
2019-12-26 03:22:13
106.13.143.111 attack
$f2bV_matches
2019-12-26 03:31:59
222.252.27.231 attackspam
Unauthorised access (Dec 25) SRC=222.252.27.231 LEN=48 PREC=0x20 TTL=116 ID=2691 DF TCP DPT=445 WINDOW=8192 SYN
2019-12-26 03:13:17
37.26.136.213 attackspambots
Unauthorized connection attempt detected from IP address 37.26.136.213 to port 445
2019-12-26 03:12:05
175.184.166.14 attackspam
HTTP/80/443 Probe, BF, WP, Hack -
2019-12-26 03:19:34
175.6.68.118 attack
HTTP/80/443 Probe, BF, WP, Hack -
2019-12-26 03:16:10

Recently Reported IPs

86.112.155.72 253.40.120.63 88.104.90.224 208.73.89.161
45.206.135.56 19.220.95.63 165.11.174.231 246.8.89.118
163.172.176.16 205.98.97.152 207.239.126.185 170.202.34.8
187.143.76.164 132.255.61.2 177.208.178.203 46.215.166.75
2.230.63.105 79.50.137.178 139.53.116.70 89.208.157.171