City: Ashburn
Region: Virginia
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.
#
NetRange: 54.144.0.0 - 54.221.255.255
CIDR: 54.192.0.0/12, 54.216.0.0/14, 54.220.0.0/15, 54.208.0.0/13, 54.144.0.0/12, 54.160.0.0/11
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.97.12
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2605
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;54.167.97.12. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026081601 1800 900 604800 86400
;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Aug 17 08:30:29 CST 2026
;; MSG SIZE rcvd: 10512.97.167.54.in-addr.arpa domain name pointer ec2-54-167-97-12.compute-1.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
12.97.167.54.in-addr.arpa name = ec2-54-167-97-12.compute-1.amazonaws.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 118.167.113.210 | attack | port 23 attempt blocked |
2019-09-11 14:28:24 |
| 77.42.117.214 | attackbotsspam | Automatic report - Port Scan Attack |
2019-09-11 14:07:03 |
| 108.179.205.203 | attackspambots | Sep 10 20:17:03 hpm sshd\[28941\]: Invalid user user from 108.179.205.203 Sep 10 20:17:03 hpm sshd\[28941\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=108.179.205.203 Sep 10 20:17:05 hpm sshd\[28941\]: Failed password for invalid user user from 108.179.205.203 port 51512 ssh2 Sep 10 20:22:51 hpm sshd\[29456\]: Invalid user letmein from 108.179.205.203 Sep 10 20:22:51 hpm sshd\[29456\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=108.179.205.203 |
2019-09-11 14:38:38 |
| 117.50.49.74 | attackspam | Sep 10 17:52:02 web1 sshd\[21024\]: Invalid user sinusbot from 117.50.49.74 Sep 10 17:52:02 web1 sshd\[21024\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.50.49.74 Sep 10 17:52:04 web1 sshd\[21024\]: Failed password for invalid user sinusbot from 117.50.49.74 port 50555 ssh2 Sep 10 17:55:43 web1 sshd\[21377\]: Invalid user admin from 117.50.49.74 Sep 10 17:55:43 web1 sshd\[21377\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.50.49.74 |
2019-09-11 14:13:07 |
| 142.44.163.100 | attackspam | WordPress login Brute force / Web App Attack on client site. |
2019-09-11 14:08:30 |
| 185.176.27.14 | attack | firewall-block, port(s): 34083/tcp |
2019-09-11 13:54:22 |
| 89.186.8.251 | attackspambots | SASL PLAIN auth failed: ruser=... |
2019-09-11 13:45:42 |
| 107.173.193.195 | botsattackproxy | IP address [107.173.193.195] of has been blocked by VPN_SERVER |
2019-09-11 13:58:47 |
| 216.155.94.51 | attackbots | Sep 11 11:34:34 webhost01 sshd[7569]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=216.155.94.51 Sep 11 11:34:36 webhost01 sshd[7569]: Failed password for invalid user sammy from 216.155.94.51 port 57627 ssh2 ... |
2019-09-11 13:48:06 |
| 182.76.6.222 | attack | Sep 11 01:33:02 vps200512 sshd\[20212\]: Invalid user test from 182.76.6.222 Sep 11 01:33:02 vps200512 sshd\[20212\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.76.6.222 Sep 11 01:33:04 vps200512 sshd\[20212\]: Failed password for invalid user test from 182.76.6.222 port 47364 ssh2 Sep 11 01:39:46 vps200512 sshd\[20421\]: Invalid user admin123 from 182.76.6.222 Sep 11 01:39:46 vps200512 sshd\[20421\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.76.6.222 |
2019-09-11 13:56:12 |
| 206.189.119.73 | attack | Sep 10 19:26:41 hiderm sshd\[17480\]: Invalid user q1w2e3r4t5 from 206.189.119.73 Sep 10 19:26:41 hiderm sshd\[17480\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.119.73 Sep 10 19:26:43 hiderm sshd\[17480\]: Failed password for invalid user q1w2e3r4t5 from 206.189.119.73 port 55688 ssh2 Sep 10 19:32:05 hiderm sshd\[17924\]: Invalid user admin12345 from 206.189.119.73 Sep 10 19:32:05 hiderm sshd\[17924\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.119.73 |
2019-09-11 13:51:19 |
| 89.36.215.248 | attackbots | Sep 10 22:08:48 thevastnessof sshd[17747]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.36.215.248 ... |
2019-09-11 13:54:54 |
| 118.167.45.216 | attackbotsspam | port 23 attempt blocked |
2019-09-11 14:39:19 |
| 106.12.206.70 | attack | Sep 10 20:22:15 sachi sshd\[24903\]: Invalid user team from 106.12.206.70 Sep 10 20:22:15 sachi sshd\[24903\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.206.70 Sep 10 20:22:17 sachi sshd\[24903\]: Failed password for invalid user team from 106.12.206.70 port 57350 ssh2 Sep 10 20:27:22 sachi sshd\[25351\]: Invalid user testsite from 106.12.206.70 Sep 10 20:27:23 sachi sshd\[25351\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.206.70 |
2019-09-11 14:29:16 |
| 112.195.165.23 | attack | Sep 10 19:36:54 lcdev sshd\[301\]: Invalid user 1234qwer from 112.195.165.23 Sep 10 19:36:54 lcdev sshd\[301\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.195.165.23 Sep 10 19:36:56 lcdev sshd\[301\]: Failed password for invalid user 1234qwer from 112.195.165.23 port 36300 ssh2 Sep 10 19:42:06 lcdev sshd\[908\]: Invalid user 1234 from 112.195.165.23 Sep 10 19:42:06 lcdev sshd\[908\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.195.165.23 |
2019-09-11 14:01:11 |