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

Internet Service Provider: Amazon Data Services India

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attack
May 22 23:03:17 server1 sshd\[6017\]: Invalid user dsj from 52.66.104.148
May 22 23:03:17 server1 sshd\[6017\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.66.104.148 
May 22 23:03:19 server1 sshd\[6017\]: Failed password for invalid user dsj from 52.66.104.148 port 47698 ssh2
May 22 23:05:32 server1 sshd\[6654\]: Invalid user pmc from 52.66.104.148
May 22 23:05:32 server1 sshd\[6654\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.66.104.148 
...
2020-05-23 13:27:27
attackbotsspam
May 21 19:05:06 vpn01 sshd[25654]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.66.104.148
May 21 19:05:08 vpn01 sshd[25654]: Failed password for invalid user yvv from 52.66.104.148 port 37852 ssh2
...
2020-05-22 02:06:02
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 52.66.104.148
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4386
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri May 22 02:05:58 CST 2020
;; MSG SIZE  rcvd: 117
Host info
148.104.66.52.in-addr.arpa domain name pointer ec2-52-66-104-148.ap-south-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
148.104.66.52.in-addr.arpa	name = ec2-52-66-104-148.ap-south-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
218.219.246.124 attackspam
Aug 18 15:54:53 DAAP sshd[20250]: Invalid user prueba from 218.219.246.124 port 44816
Aug 18 15:54:53 DAAP sshd[20250]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.219.246.124
Aug 18 15:54:53 DAAP sshd[20250]: Invalid user prueba from 218.219.246.124 port 44816
Aug 18 15:54:56 DAAP sshd[20250]: Failed password for invalid user prueba from 218.219.246.124 port 44816 ssh2
Aug 18 15:59:14 DAAP sshd[20290]: Invalid user Management from 218.219.246.124 port 45740
...
2019-08-19 03:07:47
112.85.42.94 attackbots
Aug 18 15:30:06 ny01 sshd[6240]: Failed password for root from 112.85.42.94 port 15542 ssh2
Aug 18 15:32:45 ny01 sshd[6465]: Failed password for root from 112.85.42.94 port 34987 ssh2
2019-08-19 03:35:34
171.8.199.77 attack
Aug 18 05:41:42 web1 sshd\[4185\]: Invalid user penelope from 171.8.199.77
Aug 18 05:41:42 web1 sshd\[4185\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.8.199.77
Aug 18 05:41:44 web1 sshd\[4185\]: Failed password for invalid user penelope from 171.8.199.77 port 56594 ssh2
Aug 18 05:48:08 web1 sshd\[4806\]: Invalid user lolo from 171.8.199.77
Aug 18 05:48:08 web1 sshd\[4806\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.8.199.77
2019-08-19 03:16:47
164.68.112.133 attackbots
Automatic report - SSH Brute-Force Attack
2019-08-19 03:13:54
115.29.5.66 attack
Aug 18 13:59:31 ms-srv sshd[17089]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.29.5.66  user=root
Aug 18 13:59:33 ms-srv sshd[17089]: Failed password for invalid user root from 115.29.5.66 port 42244 ssh2
2019-08-19 03:30:27
181.49.117.27 attackbotsspam
Fail2Ban Ban Triggered
2019-08-19 03:08:13
94.29.73.233 attackspambots
1,25-04/24 [bc01/m12] concatform PostRequest-Spammer scoring: maputo01_x2b
2019-08-19 03:24:13
116.72.129.118 attack
Automatic report - Port Scan Attack
2019-08-19 03:19:48
39.41.184.210 attackbots
php WP PHPmyadamin ABUSE blocked for 12h
2019-08-19 03:07:07
58.153.152.142 attackbots
SSHScan
2019-08-19 03:03:55
159.147.5.208 attackbotsspam
Aug 18 15:47:45 XXX sshd[13829]: Invalid user server from 159.147.5.208 port 57657
2019-08-19 03:12:53
188.166.235.171 attackbots
Aug 18 06:06:27 hanapaa sshd\[25808\]: Invalid user loice from 188.166.235.171
Aug 18 06:06:27 hanapaa sshd\[25808\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.235.171
Aug 18 06:06:29 hanapaa sshd\[25808\]: Failed password for invalid user loice from 188.166.235.171 port 43350 ssh2
Aug 18 06:11:21 hanapaa sshd\[26494\]: Invalid user csgo-server from 188.166.235.171
Aug 18 06:11:21 hanapaa sshd\[26494\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.235.171
2019-08-19 03:32:37
122.165.149.75 attackbots
Aug 18 13:13:35 aat-srv002 sshd[27181]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.165.149.75
Aug 18 13:13:37 aat-srv002 sshd[27181]: Failed password for invalid user guest3 from 122.165.149.75 port 35242 ssh2
Aug 18 13:18:52 aat-srv002 sshd[27323]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.165.149.75
Aug 18 13:18:53 aat-srv002 sshd[27323]: Failed password for invalid user zabbix from 122.165.149.75 port 52520 ssh2
...
2019-08-19 03:10:03
45.79.1.161 attack
firewall-block, port(s): 9042/tcp
2019-08-19 03:01:13
12.178.187.9 attack
firewall-block, port(s): 23/tcp
2019-08-19 03:07:26

Recently Reported IPs

196.155.145.224 22.165.54.58 60.15.39.25 121.97.177.197
200.24.14.7 29.99.4.190 209.205.127.4 109.243.243.46
195.201.187.104 224.166.118.103 244.9.33.23 188.34.23.81
181.112.142.226 93.56.96.205 84.19.38.49 0.195.150.150
166.97.31.239 125.104.109.129 198.133.182.50 224.132.144.29