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
attackspambots
Sending out Netflix spam from IP 54.240.14.174 
(amazon.com / amazonaws.com) 

I have NEVER been a Netflix customer and
never asked for this junk. 

The website spammed out is 

https://www.netflix.com/signup/creditoption?nftoken=BQAbAAEBEA77T6CHfer3tv8qolkSAduAkLFC%2FFYUyiUS4Sdi62TDOAptLP7WiMxUQK74rIuN%2BRXrWDnwU8vxCNSC2khWG0ZmflN2tsqMsqNHMDWRdKmlf6XFVqwlgd%2BFLY2Nz88IH4y3pcuOeFYD5X9L4G9ZZfbRHvrmZF%2FjsAyUI1f5mpTFg3eEFWfNQayYDiVrbb%2FU65EF%2B0XXrVI0T4jKa2zmCB8w5g%3D%3D&lnktrk=EMP&g=AEF2F71097E503EBEB44921E2720235C64526E40&lkid=URL_SIGNUP_CREDIT
IPs: 54.69.16.110, 54.70.73.70, 54.149.101.155,
54.201.91.38, 54.213.182.74, 52.37.77.112,
52.41.20.47, 52.41.193.16
(amazon.com / amazonaws.com) 

amazon are pure scumbags who allow their 
customers to send out spam and do nothing 
about it! 
Report via email and website at 
https://support.aws.amazon.com/#/contacts/report-abuse
2019-09-26 17:14:27
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 52.41.20.47
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24407
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 50 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Sep 26 17:14:24 CST 2019
;; MSG SIZE  rcvd: 115
Host info
47.20.41.52.in-addr.arpa domain name pointer ec2-52-41-20-47.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
47.20.41.52.in-addr.arpa	name = ec2-52-41-20-47.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
145.239.89.243 attackspam
Aug 27 19:36:16 localhost sshd\[34809\]: Invalid user fj from 145.239.89.243 port 59200
Aug 27 19:36:16 localhost sshd\[34809\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.89.243
Aug 27 19:36:18 localhost sshd\[34809\]: Failed password for invalid user fj from 145.239.89.243 port 59200 ssh2
Aug 27 19:41:37 localhost sshd\[35022\]: Invalid user test0 from 145.239.89.243 port 32800
Aug 27 19:41:37 localhost sshd\[35022\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.89.243
...
2019-08-28 03:51:11
104.248.128.217 attackbotsspam
Aug 27 09:37:30 hanapaa sshd\[17945\]: Invalid user adolph from 104.248.128.217
Aug 27 09:37:30 hanapaa sshd\[17945\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.128.217
Aug 27 09:37:33 hanapaa sshd\[17945\]: Failed password for invalid user adolph from 104.248.128.217 port 39786 ssh2
Aug 27 09:41:29 hanapaa sshd\[18380\]: Invalid user inactive from 104.248.128.217
Aug 27 09:41:29 hanapaa sshd\[18380\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.128.217
2019-08-28 03:57:20
213.251.185.51 attack
Aug 27 21:39:26 ns3110291 sshd\[2232\]: Invalid user xq from 213.251.185.51
Aug 27 21:39:28 ns3110291 sshd\[2232\]: Failed password for invalid user xq from 213.251.185.51 port 58990 ssh2
Aug 27 21:43:47 ns3110291 sshd\[2567\]: Invalid user students from 213.251.185.51
Aug 27 21:43:49 ns3110291 sshd\[2567\]: Failed password for invalid user students from 213.251.185.51 port 50780 ssh2
Aug 27 21:48:03 ns3110291 sshd\[3038\]: Invalid user pentaho from 213.251.185.51
...
2019-08-28 03:52:16
189.50.133.10 attackspambots
Aug 27 19:36:01 web8 sshd\[5104\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.50.133.10  user=root
Aug 27 19:36:04 web8 sshd\[5104\]: Failed password for root from 189.50.133.10 port 36178 ssh2
Aug 27 19:41:30 web8 sshd\[7874\]: Invalid user kathleen from 189.50.133.10
Aug 27 19:41:30 web8 sshd\[7874\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.50.133.10
Aug 27 19:41:32 web8 sshd\[7874\]: Failed password for invalid user kathleen from 189.50.133.10 port 54274 ssh2
2019-08-28 03:54:56
176.122.128.217 attack
Invalid user percy from 176.122.128.217 port 33946
2019-08-28 03:37:41
171.244.36.103 attackbots
Automated report - ssh fail2ban:
Aug 27 16:51:27 authentication failure 
Aug 27 16:51:29 wrong password, user=ubuntu, port=37988, ssh2
Aug 27 16:57:33 authentication failure
2019-08-28 03:21:39
185.132.53.30 attackbots
Aug 27 15:41:29 TORMINT sshd\[13556\]: Invalid user teamspeak from 185.132.53.30
Aug 27 15:41:30 TORMINT sshd\[13556\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.132.53.30
Aug 27 15:41:32 TORMINT sshd\[13556\]: Failed password for invalid user teamspeak from 185.132.53.30 port 58414 ssh2
...
2019-08-28 03:53:51
157.230.251.115 attackspambots
Invalid user nagiosuser from 157.230.251.115 port 34954
2019-08-28 03:31:56
193.90.12.117 attackbotsspam
Aug 27 04:35:43 eddieflores sshd\[25120\]: Invalid user user from 193.90.12.117
Aug 27 04:35:43 eddieflores sshd\[25120\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.90.12.117
Aug 27 04:35:45 eddieflores sshd\[25120\]: Failed password for invalid user user from 193.90.12.117 port 43432 ssh2
Aug 27 04:35:48 eddieflores sshd\[25120\]: Failed password for invalid user user from 193.90.12.117 port 43432 ssh2
Aug 27 04:35:50 eddieflores sshd\[25120\]: Failed password for invalid user user from 193.90.12.117 port 43432 ssh2
2019-08-28 03:37:01
94.23.6.187 attackspam
Aug 27 22:37:34 yabzik sshd[18401]: Failed password for messagebus from 94.23.6.187 port 49179 ssh2
Aug 27 22:41:38 yabzik sshd[19842]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.23.6.187
Aug 27 22:41:40 yabzik sshd[19842]: Failed password for invalid user alex from 94.23.6.187 port 44647 ssh2
2019-08-28 03:49:51
78.187.206.121 attack
Automatic report - Port Scan Attack
2019-08-28 03:43:30
80.211.51.116 attackspambots
Aug 27 09:37:40 php1 sshd\[30504\]: Invalid user ann from 80.211.51.116
Aug 27 09:37:40 php1 sshd\[30504\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.51.116
Aug 27 09:37:43 php1 sshd\[30504\]: Failed password for invalid user ann from 80.211.51.116 port 42274 ssh2
Aug 27 09:41:43 php1 sshd\[30905\]: Invalid user stunnel4 from 80.211.51.116
Aug 27 09:41:43 php1 sshd\[30905\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.51.116
2019-08-28 03:48:17
198.144.176.89 attackbots
Registration form abuse
2019-08-28 03:52:34
41.224.59.78 attackspambots
Automatic report - Banned IP Access
2019-08-28 03:33:44
5.135.244.117 attackspam
Aug 28 01:22:19 lcl-usvr-02 sshd[26608]: Invalid user user2 from 5.135.244.117 port 36226
Aug 28 01:22:19 lcl-usvr-02 sshd[26608]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.135.244.117
Aug 28 01:22:19 lcl-usvr-02 sshd[26608]: Invalid user user2 from 5.135.244.117 port 36226
Aug 28 01:22:21 lcl-usvr-02 sshd[26608]: Failed password for invalid user user2 from 5.135.244.117 port 36226 ssh2
Aug 28 01:26:18 lcl-usvr-02 sshd[27507]: Invalid user wv from 5.135.244.117 port 55918
...
2019-08-28 03:30:30

Recently Reported IPs

88.204.218.130 85.15.82.99 77.82.206.218 52.37.77.112
49.148.189.139 36.90.255.241 36.85.117.183 36.83.176.23
36.75.140.89 223.205.235.63 127.81.247.173 39.134.21.5
213.131.62.230 119.96.227.19 118.69.78.29 27.123.215.222
212.98.162.206 202.86.189.194 189.147.110.167 188.162.234.146