City: San Jose
Region: California
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2025, American Registry for Internet Numbers, Ltd.
#
# start
NetRange: 54.144.0.0 - 54.221.255.255
CIDR: 54.160.0.0/11, 54.192.0.0/12, 54.144.0.0/12, 54.208.0.0/13, 54.220.0.0/15, 54.216.0.0/14
NetName: AMAZON
NetHandle: NET-54-144-0-0-1
Parent: NET54 (NET-54-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Amazon Technologies Inc. (AT-88-Z)
RegDate: 2014-10-23
Updated: 2021-02-10
Ref: https://rdap.arin.net/registry/ip/54.144.0.0
OrgName: Amazon Technologies Inc.
OrgId: AT-88-Z
Address: 410 Terry Ave N.
City: Seattle
StateProv: WA
PostalCode: 98109
Country: US
RegDate: 2011-12-08
Updated: 2024-01-24
Comment: All abuse reports MUST include:
Comment: * src IP
Comment: * dest IP (your IP)
Comment: * dest port
Comment: * Accurate date/timestamp and timezone of activity
Comment: * Intensity/frequency (short log extracts)
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
OrgRoutingHandle: ARMP-ARIN
OrgRoutingName: AWS RPKI Management POC
OrgRoutingPhone: +1-206-555-0000
OrgRoutingEmail: aws-rpki-routing-poc@amazon.com
OrgRoutingRef: https://rdap.arin.net/registry/entity/ARMP-ARIN
OrgRoutingHandle: IPROU3-ARIN
OrgRoutingName: IP Routing
OrgRoutingPhone: +1-206-555-0000
OrgRoutingEmail: aws-routing-poc@amazon.com
OrgRoutingRef: https://rdap.arin.net/registry/entity/IPROU3-ARIN
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
OrgTechHandle: ANO24-ARIN
OrgTechName: Amazon EC2 Network Operations
OrgTechPhone: +1-206-555-0000
OrgTechEmail: amzn-noc-contact@amazon.com
OrgTechRef: https://rdap.arin.net/registry/entity/ANO24-ARIN
OrgAbuseHandle: AEA8-ARIN
OrgAbuseName: Amazon EC2 Abuse
OrgAbusePhone: +1-206-555-0000
OrgAbuseEmail: trustandsafety@support.aws.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/AEA8-ARIN
# end
# start
NetRange: 54.176.0.0 - 54.177.255.255
CIDR: 54.176.0.0/15
NetName: AMAZON-SFO
NetHandle: NET-54-176-0-0-2
Parent: AMAZON (NET-54-144-0-0-1)
NetType: Reallocated
OriginAS:
Organization: Amazon.com, Inc. (AMAZO-48)
RegDate: 2020-04-16
Updated: 2021-02-10
Ref: https://rdap.arin.net/registry/ip/54.176.0.0
OrgName: Amazon.com, Inc.
OrgId: AMAZO-48
Address: 1200 12th Ave South
City: Seattle
StateProv: WA
PostalCode: 98144
Country: US
RegDate: 2011-08-11
Updated: 2021-07-22
Comment: The activity you have detected originates from a dynamic hosting environment.
Comment: For fastest response, please submit abuse reports at http://aws-portal.amazon.com/gp/aws/html-forms-controller/contactus/AWSAbuse
Comment: For more information regarding EC2 see:
Comment: http://ec2.amazonaws.com/
Comment: All reports MUST include:
Comment: * src IP
Comment: * dest IP (your IP)
Comment: * dest port
Comment: * Accurate date/timestamp and timezone of activity
Comment: * Intensity/frequency (short log extracts)
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/AMAZO-48
OrgRoutingHandle: ARMP-ARIN
OrgRoutingName: AWS RPKI Management POC
OrgRoutingPhone: +1-206-555-0000
OrgRoutingEmail: aws-rpki-routing-poc@amazon.com
OrgRoutingRef: https://rdap.arin.net/registry/entity/ARMP-ARIN
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
OrgRoutingHandle: IPROU3-ARIN
OrgRoutingName: IP Routing
OrgRoutingPhone: +1-206-555-0000
OrgRoutingEmail: aws-routing-poc@amazon.com
OrgRoutingRef: https://rdap.arin.net/registry/entity/IPROU3-ARIN
OrgTechHandle: ANO24-ARIN
OrgTechName: Amazon EC2 Network Operations
OrgTechPhone: +1-206-555-0000
OrgTechEmail: amzn-noc-contact@amazon.com
OrgTechRef: https://rdap.arin.net/registry/entity/ANO24-ARIN
OrgAbuseHandle: AEA8-ARIN
OrgAbuseName: Amazon EC2 Abuse
OrgAbusePhone: +1-206-555-0000
OrgAbuseEmail: trustandsafety@support.aws.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/AEA8-ARIN
# end
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2025, American Registry for Internet Numbers, Ltd.
#; <<>> DiG 9.10.3-P4-Ubuntu <<>> 54.176.49.81
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42288
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;54.176.49.81. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025113001 1800 900 604800 86400
;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Dec 01 10:30:49 CST 2025
;; MSG SIZE rcvd: 10581.49.176.54.in-addr.arpa domain name pointer ec2-54-176-49-81.us-west-1.compute.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
81.49.176.54.in-addr.arpa name = ec2-54-176-49-81.us-west-1.compute.amazonaws.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 185.143.223.81 | attack | Nov 10 09:56:17 h2177944 kernel: \[6251750.875937\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.143.223.81 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=17556 PROTO=TCP SPT=53588 DPT=2207 WINDOW=1024 RES=0x00 SYN URGP=0 Nov 10 10:07:41 h2177944 kernel: \[6252435.424221\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.143.223.81 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=43449 PROTO=TCP SPT=53588 DPT=62817 WINDOW=1024 RES=0x00 SYN URGP=0 Nov 10 10:07:57 h2177944 kernel: \[6252450.973972\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.143.223.81 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=42693 PROTO=TCP SPT=53588 DPT=41807 WINDOW=1024 RES=0x00 SYN URGP=0 Nov 10 10:24:42 h2177944 kernel: \[6253456.309303\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.143.223.81 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=25053 PROTO=TCP SPT=53588 DPT=39618 WINDOW=1024 RES=0x00 SYN URGP=0 Nov 10 10:26:26 h2177944 kernel: \[6253559.858001\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.143.223.81 DST=85.2 |
2019-11-10 17:57:39 |
| 52.27.50.232 | attackbots | Automatic report - Web App Attack |
2019-11-10 17:36:05 |
| 51.75.123.107 | attackspambots | Lines containing failures of 51.75.123.107 Nov 8 21:35:50 MAKserver06 sshd[27244]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.123.107 user=r.r Nov 8 21:35:51 MAKserver06 sshd[27244]: Failed password for r.r from 51.75.123.107 port 56776 ssh2 Nov 8 21:35:52 MAKserver06 sshd[27244]: Received disconnect from 51.75.123.107 port 56776:11: Bye Bye [preauth] Nov 8 21:35:52 MAKserver06 sshd[27244]: Disconnected from authenticating user r.r 51.75.123.107 port 56776 [preauth] Nov 8 21:47:55 MAKserver06 sshd[3786]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.123.107 user=r.r Nov 8 21:47:57 MAKserver06 sshd[3786]: Failed password for r.r from 51.75.123.107 port 54702 ssh2 Nov 8 21:47:59 MAKserver06 sshd[3786]: Received disconnect from 51.75.123.107 port 54702:11: Bye Bye [preauth] Nov 8 21:47:59 MAKserver06 sshd[3786]: Disconnected from authenticating user r.r 51.75.123.107........ ------------------------------ |
2019-11-10 17:48:01 |
| 51.158.67.13 | attackbotsspam | Nov 10 09:38:40 localhost sshd\[32621\]: Invalid user testing from 51.158.67.13 port 38264 Nov 10 09:38:40 localhost sshd\[32621\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.158.67.13 Nov 10 09:38:42 localhost sshd\[32621\]: Failed password for invalid user testing from 51.158.67.13 port 38264 ssh2 ... |
2019-11-10 18:04:09 |
| 106.54.239.60 | attackspambots | Nov 10 10:18:48 ns41 sshd[30114]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.239.60 |
2019-11-10 17:37:29 |
| 49.235.189.191 | attackspambots | $f2bV_matches |
2019-11-10 18:05:12 |
| 212.30.52.243 | attackbots | Nov 10 09:39:28 root sshd[24640]: Failed password for root from 212.30.52.243 port 42735 ssh2 Nov 10 09:43:30 root sshd[24693]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.30.52.243 Nov 10 09:43:32 root sshd[24693]: Failed password for invalid user jill from 212.30.52.243 port 33654 ssh2 ... |
2019-11-10 17:53:50 |
| 113.118.87.103 | attackbots | 2019-11-10 07:19:57 H=(Automation-cheap.com) [113.118.87.103]:64485 I=[10.100.18.23]:25 sender verify fail for |
2019-11-10 17:59:34 |
| 5.2.158.227 | attackbotsspam | Nov 10 09:50:56 web8 sshd\[26110\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.2.158.227 user=root Nov 10 09:50:59 web8 sshd\[26110\]: Failed password for root from 5.2.158.227 port 43555 ssh2 Nov 10 09:55:57 web8 sshd\[28645\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.2.158.227 user=root Nov 10 09:55:59 web8 sshd\[28645\]: Failed password for root from 5.2.158.227 port 19554 ssh2 Nov 10 10:00:50 web8 sshd\[30873\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.2.158.227 user=root |
2019-11-10 18:07:23 |
| 142.93.174.47 | attackspambots | Nov 10 09:29:39 MainVPS sshd[4111]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.174.47 user=root Nov 10 09:29:40 MainVPS sshd[4111]: Failed password for root from 142.93.174.47 port 59926 ssh2 Nov 10 09:33:00 MainVPS sshd[10339]: Invalid user operator from 142.93.174.47 port 40486 Nov 10 09:33:00 MainVPS sshd[10339]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.174.47 Nov 10 09:33:00 MainVPS sshd[10339]: Invalid user operator from 142.93.174.47 port 40486 Nov 10 09:33:03 MainVPS sshd[10339]: Failed password for invalid user operator from 142.93.174.47 port 40486 ssh2 ... |
2019-11-10 17:56:42 |
| 36.80.48.9 | attackspambots | $f2bV_matches |
2019-11-10 18:06:52 |
| 37.45.70.89 | attackspam | failed_logins |
2019-11-10 18:11:47 |
| 200.122.249.203 | attackbotsspam | web-1 [ssh] SSH Attack |
2019-11-10 18:04:24 |
| 182.61.133.172 | attackspam | Nov 10 10:00:26 srv-ubuntu-dev3 sshd[2950]: Invalid user 123 from 182.61.133.172 Nov 10 10:00:26 srv-ubuntu-dev3 sshd[2950]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.133.172 Nov 10 10:00:26 srv-ubuntu-dev3 sshd[2950]: Invalid user 123 from 182.61.133.172 Nov 10 10:00:28 srv-ubuntu-dev3 sshd[2950]: Failed password for invalid user 123 from 182.61.133.172 port 36856 ssh2 Nov 10 10:05:27 srv-ubuntu-dev3 sshd[3388]: Invalid user P@55W0rd from 182.61.133.172 Nov 10 10:05:27 srv-ubuntu-dev3 sshd[3388]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.133.172 Nov 10 10:05:27 srv-ubuntu-dev3 sshd[3388]: Invalid user P@55W0rd from 182.61.133.172 Nov 10 10:05:29 srv-ubuntu-dev3 sshd[3388]: Failed password for invalid user P@55W0rd from 182.61.133.172 port 44234 ssh2 Nov 10 10:10:25 srv-ubuntu-dev3 sshd[3970]: Invalid user rootCAV from 182.61.133.172 ... |
2019-11-10 17:34:38 |
| 178.128.52.97 | attackbotsspam | CyberHackers.eu > SSH Bruteforce attempt! |
2019-11-10 17:39:18 |