城市(city): Ashburn
省份(region): Virginia
国家(country): United States
运营商(isp): 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.
#
NetRange: 54.144.0.0 - 54.221.255.255
CIDR: 54.160.0.0/11, 54.144.0.0/12, 54.220.0.0/15, 54.192.0.0/12, 54.216.0.0/14, 54.208.0.0/13
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
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
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
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
OrgDNSHandle: DNS1131-ARIN
OrgDNSName: DNS
OrgDNSPhone: +1-202-555-0000
OrgDNSEmail: ipmanagement+dns@amazon.com
OrgDNSRef: https://rdap.arin.net/registry/entity/DNS1131-ARIN
#
# 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.167.96.173
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 49023
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;54.167.96.173. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026080101 1800 900 604800 86400
;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Aug 02 08:30:26 CST 2026
;; MSG SIZE rcvd: 106173.96.167.54.in-addr.arpa domain name pointer ec2-54-167-96-173.compute-1.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
173.96.167.54.in-addr.arpa name = ec2-54-167-96-173.compute-1.amazonaws.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 51.89.21.206 | attackspambots | 02/24/2020-12:30:53.580652 51.89.21.206 Protocol: 17 ET SCAN Sipvicious Scan |
2020-02-24 19:31:34 |
| 178.62.86.214 | attack | WordPress login Brute force / Web App Attack on client site. |
2020-02-24 20:05:41 |
| 103.94.129.17 | attackspambots | Feb 23 23:21:48 php1 sshd\[26060\]: Invalid user test from 103.94.129.17 Feb 23 23:21:48 php1 sshd\[26060\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.94.129.17 Feb 23 23:21:50 php1 sshd\[26060\]: Failed password for invalid user test from 103.94.129.17 port 41284 ssh2 Feb 23 23:26:16 php1 sshd\[26639\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.94.129.17 user=mysql Feb 23 23:26:17 php1 sshd\[26639\]: Failed password for mysql from 103.94.129.17 port 54285 ssh2 |
2020-02-24 19:34:25 |
| 183.83.76.16 | attackbotsspam | Unauthorized connection attempt detected from IP address 183.83.76.16 to port 445 |
2020-02-24 19:43:33 |
| 192.241.237.157 | attack | suspicious action Mon, 24 Feb 2020 01:44:36 -0300 |
2020-02-24 20:09:57 |
| 116.104.121.63 | attack | suspicious action Mon, 24 Feb 2020 01:45:32 -0300 |
2020-02-24 19:34:11 |
| 46.101.88.10 | attack | Feb 24 **REMOVED** sshd\[19485\]: Invalid user oracle from 46.101.88.10 Feb 24 **REMOVED** sshd\[19514\]: Invalid user rootcamp from 46.101.88.10 Feb 24 **REMOVED** sshd\[19589\]: Invalid user mysql from 46.101.88.10 |
2020-02-24 19:42:59 |
| 176.31.116.214 | attack | Feb 24 12:33:06 lnxweb62 sshd[24355]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.31.116.214 Feb 24 12:33:06 lnxweb62 sshd[24355]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.31.116.214 Feb 24 12:33:07 lnxweb62 sshd[24355]: Failed password for invalid user tifkai from 176.31.116.214 port 44561 ssh2 |
2020-02-24 19:56:13 |
| 207.180.193.140 | attack | Feb 24 11:09:20 MK-Soft-VM3 sshd[4598]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=207.180.193.140 Feb 24 11:09:22 MK-Soft-VM3 sshd[4598]: Failed password for invalid user dev from 207.180.193.140 port 43130 ssh2 ... |
2020-02-24 20:07:30 |
| 180.243.199.193 | attackbots | Unauthorized connection attempt from IP address 180.243.199.193 on Port 445(SMB) |
2020-02-24 19:40:44 |
| 129.205.210.90 | attack | suspicious action Mon, 24 Feb 2020 01:44:41 -0300 |
2020-02-24 20:06:32 |
| 46.101.117.31 | attackbotsspam | Feb 24 09:27:36 debian-2gb-nbg1-2 kernel: \[4792057.421977\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=46.101.117.31 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=54321 PROTO=TCP SPT=45986 DPT=8088 WINDOW=65535 RES=0x00 SYN URGP=0 |
2020-02-24 19:31:20 |
| 192.241.231.118 | attack | 02/23/2020-23:45:18.488894 192.241.231.118 Protocol: 17 GPL RPC portmap listing UDP 111 |
2020-02-24 19:45:26 |
| 218.249.40.241 | attack | ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic |
2020-02-24 19:49:24 |
| 61.133.215.6 | attackbotsspam | 02/23/2020-23:45:04.869866 61.133.215.6 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433 |
2020-02-24 19:59:34 |