城市(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-2025, American Registry for Internet Numbers, Ltd.
#
NetRange: 54.144.0.0 - 54.221.255.255
CIDR: 54.208.0.0/13, 54.144.0.0/12, 54.192.0.0/12, 54.220.0.0/15, 54.160.0.0/11, 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
#
# 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.163.198.183
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 43590
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;54.163.198.183. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025101401 1800 900 604800 86400
;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Oct 15 00:02:02 CST 2025
;; MSG SIZE rcvd: 107183.198.163.54.in-addr.arpa domain name pointer ec2-54-163-198-183.compute-1.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
183.198.163.54.in-addr.arpa name = ec2-54-163-198-183.compute-1.amazonaws.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 49.88.112.114 | attack | Nov 11 07:14:55 web1 sshd\[13991\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.114 user=root Nov 11 07:14:57 web1 sshd\[13991\]: Failed password for root from 49.88.112.114 port 50740 ssh2 Nov 11 07:14:59 web1 sshd\[13991\]: Failed password for root from 49.88.112.114 port 50740 ssh2 Nov 11 07:15:01 web1 sshd\[13991\]: Failed password for root from 49.88.112.114 port 50740 ssh2 Nov 11 07:15:43 web1 sshd\[14087\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.114 user=root |
2019-11-12 01:30:59 |
| 109.87.187.240 | attack | Fail2Ban Ban Triggered |
2019-11-12 01:35:41 |
| 138.197.151.248 | attackbots | 2019-11-11T16:54:57.395769abusebot-7.cloudsearch.cf sshd\[18586\]: Invalid user ftptest from 138.197.151.248 port 39370 |
2019-11-12 00:58:29 |
| 111.240.251.74 | attackbots | php WP PHPmyadamin ABUSE blocked for 12h |
2019-11-12 00:56:43 |
| 90.84.241.185 | attackspam | Nov 11 16:56:46 serwer sshd\[28867\]: Invalid user ubuntu from 90.84.241.185 port 50852 Nov 11 16:56:46 serwer sshd\[28867\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=90.84.241.185 Nov 11 16:56:48 serwer sshd\[28867\]: Failed password for invalid user ubuntu from 90.84.241.185 port 50852 ssh2 ... |
2019-11-12 01:12:37 |
| 120.136.167.74 | attackspambots | Nov 11 15:53:46 eventyay sshd[4222]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.136.167.74 Nov 11 15:53:48 eventyay sshd[4222]: Failed password for invalid user nhi from 120.136.167.74 port 54873 ssh2 Nov 11 15:58:57 eventyay sshd[4288]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.136.167.74 ... |
2019-11-12 01:33:04 |
| 91.99.157.41 | attack | Connection by 91.99.157.41 on port: 5555 got caught by honeypot at 11/11/2019 1:44:00 PM |
2019-11-12 01:00:07 |
| 185.94.111.1 | attackspam | recursive dns scanner |
2019-11-12 00:59:22 |
| 223.243.29.102 | attackbots | Nov 11 15:57:17 game-panel sshd[26563]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.243.29.102 Nov 11 15:57:19 game-panel sshd[26563]: Failed password for invalid user kissell from 223.243.29.102 port 59256 ssh2 Nov 11 16:02:25 game-panel sshd[26719]: Failed password for sync from 223.243.29.102 port 39962 ssh2 |
2019-11-12 01:36:19 |
| 218.78.53.37 | attackbotsspam | SSH authentication failure x 6 reported by Fail2Ban ... |
2019-11-12 01:05:48 |
| 45.143.221.9 | attack | 45.143.221.9 was recorded 41 times by 26 hosts attempting to connect to the following ports: 5060. Incident counter (4h, 24h, all-time): 41, 127, 530 |
2019-11-12 01:34:33 |
| 154.221.27.156 | attackbotsspam | Nov 11 22:53:34 vibhu-HP-Z238-Microtower-Workstation sshd\[21418\]: Invalid user vivoli from 154.221.27.156 Nov 11 22:53:34 vibhu-HP-Z238-Microtower-Workstation sshd\[21418\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.221.27.156 Nov 11 22:53:35 vibhu-HP-Z238-Microtower-Workstation sshd\[21418\]: Failed password for invalid user vivoli from 154.221.27.156 port 44800 ssh2 Nov 11 22:57:39 vibhu-HP-Z238-Microtower-Workstation sshd\[21639\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.221.27.156 user=root Nov 11 22:57:41 vibhu-HP-Z238-Microtower-Workstation sshd\[21639\]: Failed password for root from 154.221.27.156 port 34857 ssh2 ... |
2019-11-12 01:29:11 |
| 196.202.168.130 | attack | SMB Server BruteForce Attack |
2019-11-12 01:34:57 |
| 104.248.115.231 | attack | IP attempted unauthorised action |
2019-11-12 01:10:46 |
| 2400:6180:0:d1::807:b001 | attackspam | WordPress login Brute force / Web App Attack on client site. |
2019-11-12 01:01:41 |