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.220.0.0/15, 54.208.0.0/13, 54.216.0.0/14, 54.160.0.0/11, 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: 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
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
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
# end
# start
NetRange: 54.151.0.0 - 54.151.127.255
CIDR: 54.151.0.0/17
NetName: AMAZON-SFO
NetHandle: NET-54-151-0-0-1
Parent: AMAZON (NET-54-144-0-0-1)
NetType: Reallocated
OriginAS:
Organization: Amazon.com, Inc. (AMAZO-48)
RegDate: 2018-07-20
Updated: 2018-07-20
Ref: https://rdap.arin.net/registry/ip/54.151.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
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
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
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
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
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
# 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.151.57.110
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4821
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;54.151.57.110. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025092601 1800 900 604800 86400
;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Sep 27 12:33:48 CST 2025
;; MSG SIZE rcvd: 106
110.57.151.54.in-addr.arpa domain name pointer ec2-54-151-57-110.us-west-1.compute.amazonaws.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
110.57.151.54.in-addr.arpa name = ec2-54-151-57-110.us-west-1.compute.amazonaws.com.
Authoritative answers can be found from:
IP | Type | Details | Datetime |
---|---|---|---|
184.75.208.140 | attackbots | TCP Port Scanning |
2019-12-18 14:28:20 |
3.209.83.101 | attackspambots | Port scan on 1 port(s): 53 |
2019-12-18 14:24:37 |
178.125.154.111 | attackbots | [portscan] Port scan |
2019-12-18 14:47:13 |
222.186.180.6 | attackbots | Dec 17 20:30:09 wbs sshd\[26079\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.6 user=root Dec 17 20:30:11 wbs sshd\[26079\]: Failed password for root from 222.186.180.6 port 47234 ssh2 Dec 17 20:30:14 wbs sshd\[26079\]: Failed password for root from 222.186.180.6 port 47234 ssh2 Dec 17 20:30:27 wbs sshd\[26103\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.6 user=root Dec 17 20:30:29 wbs sshd\[26103\]: Failed password for root from 222.186.180.6 port 57816 ssh2 |
2019-12-18 14:43:45 |
40.92.22.60 | attack | Dec 18 07:57:44 debian-2gb-vpn-nbg1-1 kernel: [1023429.859186] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=40.92.22.60 DST=78.46.192.101 LEN=52 TOS=0x02 PREC=0x00 TTL=104 ID=8903 DF PROTO=TCP SPT=62653 DPT=25 WINDOW=8192 RES=0x00 CWR ECE SYN URGP=0 |
2019-12-18 14:15:00 |
52.183.39.228 | attackspambots | Dec 18 07:23:27 sip sshd[26884]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.183.39.228 Dec 18 07:23:29 sip sshd[26884]: Failed password for invalid user asterisk from 52.183.39.228 port 45852 ssh2 Dec 18 07:30:24 sip sshd[26925]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.183.39.228 |
2019-12-18 14:59:48 |
1.201.140.126 | attackspambots | Dec 18 07:23:30 sd-53420 sshd\[32567\]: Invalid user home from 1.201.140.126 Dec 18 07:23:30 sd-53420 sshd\[32567\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.201.140.126 Dec 18 07:23:32 sd-53420 sshd\[32567\]: Failed password for invalid user home from 1.201.140.126 port 54320 ssh2 Dec 18 07:30:28 sd-53420 sshd\[2934\]: Invalid user guest from 1.201.140.126 Dec 18 07:30:28 sd-53420 sshd\[2934\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.201.140.126 ... |
2019-12-18 14:53:15 |
180.168.36.86 | attackbotsspam | Invalid user name from 180.168.36.86 port 3240 |
2019-12-18 14:18:14 |
107.170.235.19 | attackbots | Dec 18 07:17:01 hell sshd[2267]: Failed password for bin from 107.170.235.19 port 60700 ssh2 ... |
2019-12-18 14:50:38 |
218.75.207.11 | attack | Dec 18 11:30:26 gw1 sshd[4918]: Failed password for root from 218.75.207.11 port 35021 ssh2 Dec 18 11:30:28 gw1 sshd[4918]: Failed password for root from 218.75.207.11 port 35021 ssh2 ... |
2019-12-18 14:44:08 |
148.72.64.192 | attack | Automatic report - XMLRPC Attack |
2019-12-18 14:56:31 |
138.68.82.220 | attackbotsspam | 2019-12-18T07:38:04.532571scmdmz1 sshd[32609]: Invalid user card from 138.68.82.220 port 37240 2019-12-18T07:38:04.535071scmdmz1 sshd[32609]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.82.220 2019-12-18T07:38:04.532571scmdmz1 sshd[32609]: Invalid user card from 138.68.82.220 port 37240 2019-12-18T07:38:06.688383scmdmz1 sshd[32609]: Failed password for invalid user card from 138.68.82.220 port 37240 ssh2 2019-12-18T07:43:13.163624scmdmz1 sshd[640]: Invalid user biyangka from 138.68.82.220 port 45230 ... |
2019-12-18 14:48:41 |
41.221.161.14 | attackbotsspam | 0,70-10/02 [bc00/m01] PostRequest-Spammer scoring: madrid |
2019-12-18 14:52:46 |
113.161.5.253 | attackbotsspam | Unauthorised access (Dec 18) SRC=113.161.5.253 LEN=52 TTL=118 ID=8422 DF TCP DPT=445 WINDOW=8192 SYN |
2019-12-18 14:23:51 |
193.70.88.213 | attackbots | Dec 17 20:37:34 wbs sshd\[26826\]: Invalid user ssh from 193.70.88.213 Dec 17 20:37:34 wbs sshd\[26826\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.ip-193-70-88.eu Dec 17 20:37:36 wbs sshd\[26826\]: Failed password for invalid user ssh from 193.70.88.213 port 33810 ssh2 Dec 17 20:45:39 wbs sshd\[27763\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.ip-193-70-88.eu user=root Dec 17 20:45:41 wbs sshd\[27763\]: Failed password for root from 193.70.88.213 port 47604 ssh2 |
2019-12-18 14:54:27 |