52.66.15.160 reported as spam14 websites attacked, discovered May 26, 2017, last activity Jun 04, 2017 23:16:19.
CleanTalk API response. Learn more about API.
Check IP Addresses, Email, Subnet, Domain for Spam in BlackList DataBase
52.66.15.160 Details
| Network | 52.66.0.0/19parent network: 52.66.0.0/16 |
|---|---|
| DNS name | ec2-52-66-15-160.ap-south-1.compute.amazonaws.com |
| AS number | 16509 |
| Org name | Amazon.com, Inc. |
| Country | United States |
| Address | - |
| Phone | - |
| Website | aws.amazon.com |
| Spam rate | 19.05% |
| Hosted websites on 52.66.15.160 | |
Why CleanTalk? It's simple.
Growth of registrations/visitors
Convenient registration/commenting forms increase the number of registrations. Real-Time Email Address Existence Validation to increase your conversion rate.
Save time and resources
Our service allows you to focus your time on developing and improving the website and business, without being distracted by extraneous tasks.
Visitor loyalty
Your visitors are more loyal and not annoyed guessing characters or puzzles. They become your regular visitors.
Have you ever wondered how to stop spam?
Let us show you how
It's easier than you think
52.66.15.160 spam attacks, abuse log
The log shows up to 50 last spam activities
52.66.15.160 Status
| Service | Status | Updated |
|---|---|---|
| Anti-Spam protection | Not in list | Jun 05, 2017 04:16:19 |
| SpamFireWall [?] | Not in list | Jun 05, 2017 04:16:19 |
| WordPress Security FireWall [?] | Not in list | - |
| Type of attacks | Spam | - |
Blacklisted - a sender will be rejected by CleanTalk. Suspicious - a sender might be rejected by CleanTalk. The address will be included in Security FireWall if it is present in SpamFireWall and the option "Use CleanTalk database of dangerous IP addresses." is turned on in Security settings.
52.66.0.0/19 recently detected spam active IP addresses
| # | Address (DNS name) | Detected | Last seen | Attacked sites |
|---|---|---|---|---|
| 1 | 52.66.16.246 | Dec 01, 2019 04:12:29 | Dec 06, 2019 23:03:13 | 4 |
| 2 | 52.66.18.215(ec2-52-66-18-215.ap-south-1.compute.amazonaws.com) | Oct 08, 2016 10:48:17 | Oct 10, 2016 05:49:06 | 14 |
| 3 | 52.66.20.97(ec2-52-66-20-97.ap-south-1.compute.amazonaws.com) | Oct 07, 2016 21:58:03 | Oct 17, 2016 17:48:57 | 32 |
| 4 | 52.66.20.148(ec2-52-66-20-148.ap-south-1.compute.amazonaws.com) | Aug 31, 2017 19:29:25 | Sep 21, 2017 10:06:54 | 9 |
| 5 | 52.66.21.12(ec2-52-66-21-12.ap-south-1.compute.amazonaws.com) | Oct 08, 2016 09:55:29 | Oct 09, 2016 07:47:20 | 8 |
| 6 | 52.66.22.82(ec2-52-66-22-82.ap-south-1.compute.amazonaws.com) | Jan 12, 2019 07:43:31 | Jan 13, 2019 15:05:16 | 3 |
| 7 | 52.66.23.242(ec2-52-66-23-242.ap-south-1.compute.amazonaws.com) | Mar 24, 2019 14:02:27 | Apr 16, 2019 19:01:17 | 77 |
| 8 | 52.66.25.65(ec2-52-66-25-65.ap-south-1.compute.amazonaws.com) | Nov 02, 2016 12:06:59 | Nov 05, 2016 15:18:20 | 5 |
| 9 | 52.66.30.194(ec2-52-66-30-194.ap-south-1.compute.amazonaws.com) | May 18, 2018 23:29:55 | May 27, 2018 05:12:43 | 14 |
| 10 | 52.66.31.106(ec2-52-66-31-106.ap-south-1.compute.amazonaws.com) | Jun 19, 2019 21:16:06 | Sep 22, 2019 09:47:27 | 4 |