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-2026, American Registry for Internet Numbers, Ltd.
#
# start
NetRange: 54.144.0.0 - 54.221.255.255
CIDR: 54.220.0.0/15, 54.160.0.0/11, 54.216.0.0/14, 54.208.0.0/13, 54.192.0.0/12, 54.144.0.0/12
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: 2026-04-17
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: 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
OrgDNSHandle: DNS1131-ARIN
OrgDNSName: DNS
OrgDNSPhone: +1-202-555-0000
OrgDNSEmail: ipmanagement+dns@amazon.com
OrgDNSRef: https://rdap.arin.net/registry/entity/DNS1131-ARIN
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
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
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
# end
# start
NetRange: 54.193.0.0 - 54.193.255.255
CIDR: 54.193.0.0/16
NetName: AMAZO-ZSFO4
NetHandle: NET-54-193-0-0-1
Parent: AMAZON (NET-54-144-0-0-1)
NetType: Reallocated
OriginAS:
Organization: Amazon.com, Inc. (AMAZO-48)
RegDate: 2013-11-06
Updated: 2021-02-10
Ref: https://rdap.arin.net/registry/ip/54.193.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: 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
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
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
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
# 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-2026, American Registry for Internet Numbers, Ltd.
#; <<>> DiG 9.10.3-P4-Ubuntu <<>> 54.193.234.83
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 45827
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;54.193.234.83. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026052700 1800 900 604800 86400
;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed May 27 21:00:55 CST 2026
;; MSG SIZE rcvd: 10683.234.193.54.in-addr.arpa domain name pointer ec2-54-193-234-83.us-west-1.compute.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
83.234.193.54.in-addr.arpa name = ec2-54-193-234-83.us-west-1.compute.amazonaws.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 139.199.113.140 | attackbotsspam | Oct 5 09:07:43 vmanager6029 sshd\[14931\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.113.140 user=root Oct 5 09:07:44 vmanager6029 sshd\[14931\]: Failed password for root from 139.199.113.140 port 39850 ssh2 Oct 5 09:11:46 vmanager6029 sshd\[15073\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.113.140 user=root |
2019-10-05 15:17:15 |
| 114.34.211.150 | attack | Honeypot attack, port: 23, PTR: 114-34-211-150.HINET-IP.hinet.net. |
2019-10-05 15:33:59 |
| 13.81.69.78 | attackbotsspam | SSH Bruteforce |
2019-10-05 15:10:39 |
| 101.124.6.112 | attackbotsspam | Oct 4 20:25:01 hpm sshd\[12221\]: Invalid user P@ss@2016 from 101.124.6.112 Oct 4 20:25:01 hpm sshd\[12221\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.124.6.112 Oct 4 20:25:04 hpm sshd\[12221\]: Failed password for invalid user P@ss@2016 from 101.124.6.112 port 37346 ssh2 Oct 4 20:29:09 hpm sshd\[12571\]: Invalid user Compiler_123 from 101.124.6.112 Oct 4 20:29:09 hpm sshd\[12571\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.124.6.112 |
2019-10-05 15:21:34 |
| 117.55.241.3 | attack | Oct 5 08:26:23 vmanager6029 sshd\[14140\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.55.241.3 user=root Oct 5 08:26:25 vmanager6029 sshd\[14140\]: Failed password for root from 117.55.241.3 port 43006 ssh2 Oct 5 08:31:05 vmanager6029 sshd\[14214\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.55.241.3 user=root |
2019-10-05 15:32:40 |
| 113.161.65.119 | attackbots | Oct 5 04:40:37 ip-172-31-1-72 sshd\[20728\]: Invalid user pi from 113.161.65.119 Oct 5 04:40:37 ip-172-31-1-72 sshd\[20730\]: Invalid user pi from 113.161.65.119 Oct 5 04:40:37 ip-172-31-1-72 sshd\[20728\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.161.65.119 Oct 5 04:40:37 ip-172-31-1-72 sshd\[20730\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.161.65.119 Oct 5 04:40:39 ip-172-31-1-72 sshd\[20728\]: Failed password for invalid user pi from 113.161.65.119 port 41632 ssh2 |
2019-10-05 15:19:10 |
| 191.6.207.59 | attack | Automatic report - XMLRPC Attack |
2019-10-05 15:05:20 |
| 183.82.100.141 | attack | Oct 5 08:50:20 vpn01 sshd[13760]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.82.100.141 Oct 5 08:50:23 vpn01 sshd[13760]: Failed password for invalid user Active123 from 183.82.100.141 port 36646 ssh2 ... |
2019-10-05 15:24:10 |
| 58.217.41.129 | attackspambots | Honeypot attack, port: 23, PTR: PTR record not found |
2019-10-05 15:36:56 |
| 185.147.80.150 | attackspam | Oct 4 20:37:32 kapalua sshd\[31378\]: Invalid user Welcome\#123 from 185.147.80.150 Oct 4 20:37:32 kapalua sshd\[31378\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=150-tilogmed-147.reizigersvilla.nl Oct 4 20:37:34 kapalua sshd\[31378\]: Failed password for invalid user Welcome\#123 from 185.147.80.150 port 43598 ssh2 Oct 4 20:41:39 kapalua sshd\[31873\]: Invalid user Brain@123 from 185.147.80.150 Oct 4 20:41:39 kapalua sshd\[31873\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=150-tilogmed-147.reizigersvilla.nl |
2019-10-05 15:20:35 |
| 27.124.11.2 | attackbotsspam | firewall-block, port(s): 8080/tcp |
2019-10-05 15:33:06 |
| 83.162.199.163 | attackbots | Too many connections or unauthorized access detected from Arctic banned ip |
2019-10-05 15:14:44 |
| 118.25.27.67 | attackbots | 2019-10-05T06:30:48.062211abusebot-3.cloudsearch.cf sshd\[22963\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.25.27.67 user=root |
2019-10-05 15:00:48 |
| 54.37.154.113 | attackbotsspam | $f2bV_matches |
2019-10-05 15:03:41 |
| 112.73.74.59 | attack | Oct 5 08:26:56 vps01 sshd[20773]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.73.74.59 Oct 5 08:26:58 vps01 sshd[20773]: Failed password for invalid user 123Hotel from 112.73.74.59 port 37088 ssh2 |
2019-10-05 15:20:11 |