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: China

Internet Service Provider: Ningxia West Cloud Data Technology Co.Ltd.

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attackspambots
Dec 30 21:52:25 woof sshd[3964]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-52-83-200-52.cn-northwest-1.compute.amazonaws.com.cn  user=sync
Dec 30 21:52:27 woof sshd[3964]: Failed password for sync from 52.83.200.52 port 47458 ssh2
Dec 30 21:52:27 woof sshd[3964]: Received disconnect from 52.83.200.52: 11: Bye Bye [preauth]
Dec 30 22:09:16 woof sshd[6094]: Invalid user pilkington from 52.83.200.52
Dec 30 22:09:16 woof sshd[6094]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-52-83-200-52.cn-northwest-1.compute.amazonaws.com.cn
Dec 30 22:09:17 woof sshd[6094]: Failed password for invalid user pilkington from 52.83.200.52 port 40058 ssh2
Dec 30 22:09:18 woof sshd[6094]: Received disconnect from 52.83.200.52: 11: Bye Bye [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=52.83.200.52
2019-12-31 17:54:26
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 52.83.200.52
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42121
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 902 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Dec 31 17:54:21 CST 2019
;; MSG SIZE  rcvd: 116
Host info
52.200.83.52.in-addr.arpa domain name pointer ec2-52-83-200-52.cn-northwest-1.compute.amazonaws.com.cn.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
52.200.83.52.in-addr.arpa	name = ec2-52-83-200-52.cn-northwest-1.compute.amazonaws.com.cn.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
218.92.0.170 attackbots
[ssh] SSH attack
2019-11-26 14:07:01
92.53.77.152 attackspambots
92.53.77.152 was recorded 5 times by 5 hosts attempting to connect to the following ports: 3128,30670,45940,12950. Incident counter (4h, 24h, all-time): 5, 49, 445
2019-11-26 14:24:39
51.38.37.128 attackbotsspam
Nov 26 06:13:51 localhost sshd\[113237\]: Invalid user webmaster from 51.38.37.128 port 52426
Nov 26 06:13:51 localhost sshd\[113237\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.37.128
Nov 26 06:13:54 localhost sshd\[113237\]: Failed password for invalid user webmaster from 51.38.37.128 port 52426 ssh2
Nov 26 06:17:02 localhost sshd\[113364\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.37.128  user=root
Nov 26 06:17:05 localhost sshd\[113364\]: Failed password for root from 51.38.37.128 port 42278 ssh2
...
2019-11-26 14:20:22
196.52.43.94 attackspambots
20249/tcp 8531/tcp 86/tcp...
[2019-10-30/11-25]16pkt,14pt.(tcp),1pt.(udp)
2019-11-26 13:54:45
198.108.66.18 attackspambots
" "
2019-11-26 14:04:02
45.79.54.243 attackbots
22/tcp 5353/tcp 119/tcp...
[2019-10-31/11-26]21pkt,20pt.(tcp)
2019-11-26 13:56:18
118.173.129.175 attack
Unauthorised access (Nov 26) SRC=118.173.129.175 LEN=52 TTL=115 ID=18606 DF TCP DPT=445 WINDOW=8192 SYN
2019-11-26 13:53:26
222.186.175.182 attack
Nov 26 07:04:35 MK-Soft-Root1 sshd[23647]: Failed password for root from 222.186.175.182 port 32700 ssh2
Nov 26 07:04:38 MK-Soft-Root1 sshd[23647]: Failed password for root from 222.186.175.182 port 32700 ssh2
...
2019-11-26 14:05:17
78.128.113.123 attackbotsspam
Nov 26 06:58:17 mail postfix/smtpd[14644]: warning: unknown[78.128.113.123]: SASL PLAIN authentication failed: 
Nov 26 06:58:24 mail postfix/smtpd[14647]: warning: unknown[78.128.113.123]: SASL PLAIN authentication failed: 
Nov 26 07:00:00 mail postfix/smtpd[14491]: warning: unknown[78.128.113.123]: SASL PLAIN authentication failed:
2019-11-26 14:08:14
14.241.139.139 attackspam
445/tcp 445/tcp
[2019-11-03/26]2pkt
2019-11-26 14:28:05
112.85.42.72 attackspambots
2019-11-26T06:16:53.585224abusebot-8.cloudsearch.cf sshd\[31788\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.72  user=root
2019-11-26 14:24:18
3.83.212.250 attackspambots
3.83.212.250 was recorded 64 times by 17 hosts attempting to connect to the following ports: 2376,4243,2375,2377. Incident counter (4h, 24h, all-time): 64, 71, 71
2019-11-26 13:56:43
144.121.28.206 attackspam
Nov 25 19:28:21 hpm sshd\[30918\]: Invalid user 1qz2wx3ec from 144.121.28.206
Nov 25 19:28:21 hpm sshd\[30918\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.121.28.206
Nov 25 19:28:23 hpm sshd\[30918\]: Failed password for invalid user 1qz2wx3ec from 144.121.28.206 port 47172 ssh2
Nov 25 19:35:06 hpm sshd\[31456\]: Invalid user peoria from 144.121.28.206
Nov 25 19:35:06 hpm sshd\[31456\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.121.28.206
2019-11-26 14:15:25
218.92.0.188 attack
2019-11-26T06:31:37.103633abusebot-6.cloudsearch.cf sshd\[27213\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.188  user=root
2019-11-26 14:40:31
185.173.35.29 attack
88/tcp 3389/tcp 111/tcp...
[2019-09-26/11-26]44pkt,31pt.(tcp),4pt.(udp)
2019-11-26 14:05:41

Recently Reported IPs

1.58.113.211 180.246.148.150 124.228.74.179 116.239.105.171
1.59.223.55 60.7.229.44 175.140.5.50 110.17.3.13
106.13.226.170 73.74.189.214 120.227.166.48 60.219.147.191
62.210.28.57 46.191.180.147 49.145.227.195 125.72.107.185
182.140.235.143 125.227.38.167 48.184.60.81 117.194.34.49