52.53.221.181 Threat Intelligence and Host Information

General

IP Address
52.53.221.181
IPv4 Address
Location
🇺🇸 San Jose, United States
US
Network
AS16509
AMAZON-02
Threat Score
15/100
Low Risk
Attack Intelligence
Open Ports Detected
22
Geographic Location
Country
United States
City
San Jose
Region
California
Coordinates
37.3388, -121.8916
Network Information
ASN
AS16509
Organization
AMAZON-02
Network
AS16509 AMAZON-02
WHOIS Information
NetRange
52.0.0.0 - 52.79.255.255
CIDR
52.64.0.0/12, 52.0.0.0/10
NetName
AT-88-Z
NetHandle
NET-52-0-0-0-1
Parent
NET52 (NET-52-0-0-0-0)
NetType
Direct Allocation
OriginAS
Organization
Amazon Technologies Inc. (AT-88-Z)
RegDate
2011-12-08
Updated
2024-01-24
Comment
* Your contact details (phone and email) Without these we will be unable to identify the correct owner of the IP address at that point in time.
Ref
https://rdap.arin.net/registry/entity/AT-88-Z
OrgName
Amazon Technologies Inc.
OrgId
AT-88-Z
Address
410 Terry Ave N.
City
Seattle
StateProv
WA
PostalCode
98109
Country
US
OrgNOCHandle
AANO1-ARIN
OrgNOCName
Amazon AWS Network Operations
OrgNOCPhone
+1-206-555-0000
OrgNOCEmail
amzn-noc-contact@amazon.com
OrgNOCRef
https://rdap.arin.net/registry/entity/AANO1-ARIN

  • Country: United States
  • Network: AS16509 amazon.com inc
  • Noticed: 1 times
  • Protocols Attacked: Anonymous Proxy
  • Passive DNS Results: qr.lytecharging.com www.lyte.menu lyte.menu lyte.city test-web-2.lytecharging.com www.lyte.city

Malware Detected on Host

Count: 1 bfc4f154f169e6540981def808c3a3259e94a44c9df05f7f58b93c2530ee9065

CVEs Detected

CVE-2007-2627 CVE-2007-5800 CVE-2008-1982 CVE-2008-4625 CVE-2008-4732 CVE-2008-4733 CVE-2008-4734 CVE-2008-5752 CVE-2008-6811 CVE-2008-7040 CVE-2008-7175 CVE-2009-0968 CVE-2009-2122 CVE-2009-2143 CVE-2009-2144 CVE-2009-2383 CVE-2009-2396 CVE-2009-2852 CVE-2009-3703 CVE-2009-4168 CVE-2009-4169 CVE-2009-4170 CVE-2009-4424 CVE-2009-4672 CVE-2009-4748 CVE-2010-0673 CVE-2010-1186 CVE-2010-2924 CVE-2010-3977 CVE-2010-4277 CVE-2010-4402 CVE-2010-4403 CVE-2010-4518 CVE-2010-4630 CVE-2010-4637 CVE-2010-4747 CVE-2010-4779 CVE-2010-4825 CVE-2010-4839 CVE-2010-4875 CVE-2011-0641 CVE-2011-0740 CVE-2011-0759 CVE-2011-0760 CVE-2011-1047 CVE-2011-1669 CVE-2011-3850 CVE-2011-3851 CVE-2011-3852 CVE-2011-3853 CVE-2011-3854 CVE-2011-3855 CVE-2011-3856 CVE-2011-3857 CVE-2011-3858 CVE-2011-3859 CVE-2011-3860 CVE-2011-3861 CVE-2011-3862 CVE-2011-3863 CVE-2011-3864 CVE-2011-3865 CVE-2011-3981 CVE-2011-4562 CVE-2011-4568 CVE-2011-4646 CVE-2011-4669 CVE-2011-4671 CVE-2011-4673 CVE-2011-4803 CVE-2011-5051 CVE-2011-5082 CVE-2012-0895 CVE-2012-0896 CVE-2012-0898 CVE-2012-0934 CVE-2012-1010 CVE-2012-1011 CVE-2012-1067 CVE-2012-1068 CVE-2012-1205 CVE-2012-1785 CVE-2012-1786 CVE-2012-2759 CVE-2012-2912 CVE-2012-2913 CVE-2012-2916 CVE-2012-2917 CVE-2012-2920 CVE-2013-5918 CVE-2018-16843 CVE-2018-16844 CVE-2018-16845 CVE-2018-19296 CVE-2019-16780 CVE-2019-16781 CVE-2019-17669 CVE-2019-17670 CVE-2019-17671 CVE-2019-17672 CVE-2019-17673 CVE-2019-17674 CVE-2019-17675 CVE-2019-20041 CVE-2019-20042 CVE-2019-20043 CVE-2019-20372 CVE-2019-9511 CVE-2019-9513 CVE-2019-9516 CVE-2020-11025 CVE-2020-11026 CVE-2020-11027 CVE-2020-11028 CVE-2020-11029 CVE-2020-11030 CVE-2020-25286 CVE-2020-26596 CVE-2020-28032 CVE-2020-28033 CVE-2020-28034 CVE-2020-28035 CVE-2020-28036 CVE-2020-28037 CVE-2020-28038 CVE-2020-28039 CVE-2020-28040 CVE-2020-36326 CVE-2020-4046 CVE-2020-4047 CVE-2020-4048 CVE-2020-4049 CVE-2020-4050 CVE-2021-23017 CVE-2021-29450 CVE-2021-3618 CVE-2021-39200 CVE-2021-39201 CVE-2021-44223 CVE-2022-21661 CVE-2022-21662 CVE-2022-21663 CVE-2022-21664 CVE-2022-3590 CVE-2022-43497 CVE-2022-43500 CVE-2022-43504 CVE-2023-22622 CVE-2023-2745 CVE-2023-39999 CVE-2023-44487 CVE-2023-5561

Disclaimer
This page contains threat intelligence information for the IPv4 address 52.53.221.181 and was generated either as a result of observed malicious activity or as an information gathering exercise to assist with enrichment of security events and context. All information is gathered passively through aggregation of public sources, or observations through activity upon honeynets. The host score is calculated through a series of statistically weighted values and machine learning which takes into account metadata such as host information, frequency, volume and global distribution of malicious activity, association with other known malicious hosts or networks, proxying or anonymising behaviour such as with tor exit nodes, residential proxies or VPN services, and many other attributes. These values are historical and indicative only - and should not be taken to be an accurate representation of the users, businesses or networks in which they reside.