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 Technologies Inc.

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attackspam
Sep 25 15:53:06 xb3 sshd[19710]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-52-13-97-94.us-west-2.compute.amazonaws.com
Sep 25 15:53:08 xb3 sshd[19710]: Failed password for invalid user info from 52.13.97.94 port 45174 ssh2
Sep 25 15:53:08 xb3 sshd[19710]: Received disconnect from 52.13.97.94: 11: Bye Bye [preauth]
Sep 25 15:57:00 xb3 sshd[18308]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-52-13-97-94.us-west-2.compute.amazonaws.com
Sep 25 15:57:02 xb3 sshd[18308]: Failed password for invalid user temp from 52.13.97.94 port 60022 ssh2
Sep 25 15:57:02 xb3 sshd[18308]: Received disconnect from 52.13.97.94: 11: Bye Bye [preauth]
Sep 25 16:00:52 xb3 sshd[17151]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-52-13-97-94.us-west-2.compute.amazonaws.com
Sep 25 16:00:55 xb3 sshd[17151]: Failed password for invalid user student from 52.1........
-------------------------------
2019-09-27 08:52:13
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 52.13.97.94
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15280
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 340 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 27 08:52:08 CST 2019
;; MSG SIZE  rcvd: 115
Host info
94.97.13.52.in-addr.arpa domain name pointer ec2-52-13-97-94.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
94.97.13.52.in-addr.arpa	name = ec2-52-13-97-94.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
195.54.21.219 attack
Unauthorized connection attempt from IP address 195.54.21.219 on Port 445(SMB)
2019-06-29 22:38:31
92.119.160.151 attack
firewall-block, port(s): 27000/tcp
2019-06-29 22:17:30
92.118.37.86 attack
29.06.2019 12:42:04 Connection to port 1071 blocked by firewall
2019-06-29 22:13:58
189.254.143.50 attack
Unauthorized connection attempt from IP address 189.254.143.50 on Port 445(SMB)
2019-06-29 22:25:16
37.28.154.68 attackbotsspam
SSHAttack
2019-06-29 22:45:32
45.230.100.247 attackspam
Spam mails sent to address hacked/leaked from Nexus Mods in July 2013
2019-06-29 22:38:11
182.247.101.99 attackbots
Unauthorized connection attempt from IP address 182.247.101.99 on Port 445(SMB)
2019-06-29 22:31:06
51.15.244.99 attackbots
3389BruteforceFW21
2019-06-29 22:35:18
180.76.100.178 attackspam
Jun 29 14:57:55 tux-35-217 sshd\[17361\]: Invalid user tom from 180.76.100.178 port 39336
Jun 29 14:57:55 tux-35-217 sshd\[17361\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.100.178
Jun 29 14:57:58 tux-35-217 sshd\[17361\]: Failed password for invalid user tom from 180.76.100.178 port 39336 ssh2
Jun 29 14:58:53 tux-35-217 sshd\[17363\]: Invalid user deploy from 180.76.100.178 port 47120
Jun 29 14:58:53 tux-35-217 sshd\[17363\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.100.178
...
2019-06-29 22:39:39
142.0.70.36 attack
Unauthorized connection attempt from IP address 142.0.70.36 on Port 445(SMB)
2019-06-29 22:04:16
189.172.20.19 attack
Unauthorized connection attempt from IP address 189.172.20.19 on Port 445(SMB)
2019-06-29 22:47:17
177.23.61.120 attack
libpam_shield report: forced login attempt
2019-06-29 22:39:07
82.221.131.71 attackspambots
SSHAttack
2019-06-29 22:44:00
113.189.54.98 attackbotsspam
Unauthorized connection attempt from IP address 113.189.54.98 on Port 445(SMB)
2019-06-29 22:37:34
122.160.48.93 attack
Unauthorized connection attempt from IP address 122.160.48.93 on Port 445(SMB)
2019-06-29 22:51:04

Recently Reported IPs

67.55.92.90 41.239.90.151 169.1.34.102 91.215.244.12
200.82.95.206 37.32.125.58 14.231.219.118 104.197.214.101
104.236.177.83 129.191.251.130 10.156.52.164 120.142.166.238
66.249.66.145 213.0.244.28 149.171.142.9 172.68.201.17
113.184.52.202 177.85.119.204 58.3.174.19 103.218.237.78