Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: Ashburn

Region: Virginia

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
#
# 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.144.0.0/12, 54.208.0.0/13, 54.160.0.0/11, 54.220.0.0/15
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: 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

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


#
# 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 info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 54.166.112.195
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30904
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;54.166.112.195.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2026032901 1800 900 604800 86400

;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Mar 30 05:00:18 CST 2026
;; MSG SIZE  rcvd: 107
Host info
195.112.166.54.in-addr.arpa domain name pointer ec2-54-166-112-195.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
195.112.166.54.in-addr.arpa	name = ec2-54-166-112-195.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
58.59.7.151 attackspam
Mar  3 12:45:14 gw1 sshd[31128]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.59.7.151
Mar  3 12:45:17 gw1 sshd[31128]: Failed password for invalid user fisher from 58.59.7.151 port 35857 ssh2
...
2020-03-03 17:06:15
51.79.60.147 attack
MultiHost/MultiPort Probe, Scan, Hack -
2020-03-03 17:14:52
92.63.196.3 attackbotsspam
Mar  3 10:04:28 debian-2gb-nbg1-2 kernel: \[5485448.339821\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=92.63.196.3 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=53901 PROTO=TCP SPT=52646 DPT=3336 WINDOW=1024 RES=0x00 SYN URGP=0
2020-03-03 17:12:08
106.12.92.170 attackbots
Mar  3 09:51:28 localhost sshd\[23827\]: Invalid user postgres from 106.12.92.170 port 41772
Mar  3 09:51:28 localhost sshd\[23827\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.92.170
Mar  3 09:51:30 localhost sshd\[23827\]: Failed password for invalid user postgres from 106.12.92.170 port 41772 ssh2
2020-03-03 17:01:46
218.92.0.173 attackbotsspam
Mar  3 08:58:57 server sshd[760642]: Failed none for root from 218.92.0.173 port 38925 ssh2
Mar  3 08:58:59 server sshd[760642]: Failed password for root from 218.92.0.173 port 38925 ssh2
Mar  3 08:59:03 server sshd[760642]: Failed password for root from 218.92.0.173 port 38925 ssh2
2020-03-03 16:44:35
218.30.21.112 attack
Port probing on unauthorized port 1433
2020-03-03 17:07:01
103.37.234.142 attack
Mar  3 01:48:30 ws12vmsma01 sshd[20031]: Failed password for invalid user lijiang from 103.37.234.142 port 41210 ssh2
Mar  3 01:54:01 ws12vmsma01 sshd[20848]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.37.234.142  user=root
Mar  3 01:54:03 ws12vmsma01 sshd[20848]: Failed password for root from 103.37.234.142 port 46095 ssh2
...
2020-03-03 17:04:16
104.238.110.15 attackspambots
C1,WP GET /suche/wp-login.php
2020-03-03 17:01:12
200.38.231.161 attackbotsspam
Automatic report - Port Scan Attack
2020-03-03 16:42:43
185.26.156.55 attackbotsspam
Automatic report - XMLRPC Attack
2020-03-03 17:12:50
99.45.142.52 attackbots
Honeypot attack, port: 5555, PTR: 99-45-142-52.lightspeed.miamfl.sbcglobal.net.
2020-03-03 17:14:06
182.52.23.94 attackbotsspam
Honeypot attack, port: 445, PTR: node-4m6.pool-182-52.dynamic.totinternet.net.
2020-03-03 16:47:28
218.92.0.203 attackbotsspam
Mar  3 09:26:07 legacy sshd[8043]: Failed password for root from 218.92.0.203 port 36024 ssh2
Mar  3 09:27:03 legacy sshd[8052]: Failed password for root from 218.92.0.203 port 52634 ssh2
...
2020-03-03 16:36:11
82.192.62.82 attack
Honeypot attack, port: 81, PTR: tm.82.192.62.82.dc.telemach.net.
2020-03-03 16:37:34
46.39.178.146 attackbotsspam
Mar  2 22:37:27 wbs sshd\[25195\]: Invalid user aron from 46.39.178.146
Mar  2 22:37:27 wbs sshd\[25195\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip4-46-39-178-146.cust.nbox.cz
Mar  2 22:37:29 wbs sshd\[25195\]: Failed password for invalid user aron from 46.39.178.146 port 34506 ssh2
Mar  2 22:46:04 wbs sshd\[25988\]: Invalid user tharani from 46.39.178.146
Mar  2 22:46:04 wbs sshd\[25988\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip4-46-39-178-146.cust.nbox.cz
2020-03-03 17:02:04

Recently Reported IPs

2606:4700:10::6816:1328 34.226.190.36 2606:4700:10::6816:371d 2606:4700:10::6814:7659
2606:4700:10::6816:1274 2606:4700:10::6814:8350 2606:4700:10::ac43:740 2606:4700:10::6814:7251
66.132.172.223 98.84.153.117 34.22.172.118 2.57.122.112
104.248.53.88 5.187.35.142 198.235.24.243 111.229.157.251
2606:4700:10::ac43:2030 2606:4700:10::ac43:1700 2606:4700:10::6816:2667 2606:4700:10::6816:2631