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 of America

Internet Service Provider: Amazon Technologies Inc.

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attackbots
Jun  4 11:39:34 xxxx sshd[25436]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-52-14-59-248.us-east-2.compute.amazonaws.com  user=r.r
Jun  4 11:39:35 xxxx sshd[25436]: Failed password for r.r from 52.14.59.248 port 21368 ssh2
Jun  4 12:00:08 xxxx sshd[25467]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-52-14-59-248.us-east-2.compute.amazonaws.com  user=r.r
Jun  4 12:00:10 xxxx sshd[25467]: Failed password for r.r from 52.14.59.248 port 53392 ssh2
Jun  4 12:04:19 xxxx sshd[25475]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-52-14-59-248.us-east-2.compute.amazonaws.com  user=r.r
Jun  4 12:04:21 xxxx sshd[25475]: Failed password for r.r from 52.14.59.248 port 59752 ssh2
Jun  4 12:08:28 xxxx sshd[25481]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-52-14-59-248.us-east-2.compute.amazonaw........
-------------------------------
2020-06-07 20:21:58
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 52.14.59.248
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17585
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 173 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jun 07 20:21:54 CST 2020
;; MSG SIZE  rcvd: 116
Host info
248.59.14.52.in-addr.arpa domain name pointer ec2-52-14-59-248.us-east-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
248.59.14.52.in-addr.arpa	name = ec2-52-14-59-248.us-east-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
2001:2002:d9d0:d399::22 attackspam
Bruteforce detected by fail2ban
2020-10-12 17:01:01
112.85.42.91 attack
Oct 12 11:06:38 santamaria sshd\[13214\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.91  user=root
Oct 12 11:06:40 santamaria sshd\[13214\]: Failed password for root from 112.85.42.91 port 18528 ssh2
Oct 12 11:06:56 santamaria sshd\[13218\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.91  user=root
...
2020-10-12 17:09:39
37.224.51.251 attack
Oct 12 06:20:55 ncomp sshd[12273]: Invalid user doctor from 37.224.51.251 port 35420
Oct 12 06:20:55 ncomp sshd[12273]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.224.51.251
Oct 12 06:20:55 ncomp sshd[12273]: Invalid user doctor from 37.224.51.251 port 35420
Oct 12 06:20:56 ncomp sshd[12273]: Failed password for invalid user doctor from 37.224.51.251 port 35420 ssh2
2020-10-12 17:22:33
37.247.209.178 attackspambots
DATE:2020-10-12 10:42:02, IP:37.247.209.178, PORT:ssh SSH brute force auth (docker-dc)
2020-10-12 16:55:13
138.117.177.82 attack
Oct 12 10:27:48 haigwepa sshd[4631]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.117.177.82 
Oct 12 10:27:50 haigwepa sshd[4631]: Failed password for invalid user ahmed from 138.117.177.82 port 54331 ssh2
...
2020-10-12 17:13:32
106.12.33.28 attack
(sshd) Failed SSH login from 106.12.33.28 (US/United States/-): 5 in the last 3600 secs
2020-10-12 17:10:33
187.95.11.195 attackbots
web-1 [ssh_2] SSH Attack
2020-10-12 17:23:59
125.91.126.92 attack
[N3.H3.VM3] Port Scanner Detected Blocked by UFW
2020-10-12 17:20:45
45.55.52.145 attack
Oct 12 08:11:35 xeon sshd[43682]: Failed password for root from 45.55.52.145 port 43538 ssh2
2020-10-12 17:05:41
142.93.212.91 attack
Oct 12 10:23:09 localhost sshd\[19098\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.212.91  user=root
Oct 12 10:23:11 localhost sshd\[19098\]: Failed password for root from 142.93.212.91 port 59394 ssh2
Oct 12 10:27:27 localhost sshd\[19552\]: Invalid user sanjeev from 142.93.212.91
Oct 12 10:27:27 localhost sshd\[19552\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.212.91
Oct 12 10:27:29 localhost sshd\[19552\]: Failed password for invalid user sanjeev from 142.93.212.91 port 36984 ssh2
...
2020-10-12 17:20:25
45.118.151.85 attackbots
"$f2bV_matches"
2020-10-12 17:10:46
61.240.148.53 attackbots
Oct 12 09:10:47 ajax sshd[6140]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.240.148.53 
Oct 12 09:10:50 ajax sshd[6140]: Failed password for invalid user hasegawa from 61.240.148.53 port 48406 ssh2
2020-10-12 16:52:40
83.240.184.171 attack
Unauthorized connection attempt from IP address 83.240.184.171 on port 3389
2020-10-12 16:46:36
45.40.198.93 attackspambots
$f2bV_matches
2020-10-12 16:47:26
192.35.168.127 attackspambots
1602449154 - 10/11/2020 22:45:54 Host: 192.35.168.127/192.35.168.127 Port: 53 UDP Blocked
...
2020-10-12 17:08:39

Recently Reported IPs

81.243.0.119 85.60.108.212 202.187.148.191 41.212.220.212
121.60.119.70 45.132.226.38 170.254.231.114 90.219.250.51
79.127.48.141 130.237.30.65 54.37.224.62 35.223.9.162
106.12.126.54 167.172.138.53 62.234.15.218 118.173.139.232
113.173.239.127 192.241.155.247 123.25.121.243 51.91.74.182