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: unknown

Region: unknown

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;54.204.64.164.			IN	A

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

;; Query time: 109 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Oct 15 15:39:36 CST 2019
;; MSG SIZE  rcvd: 117
Host info
164.64.204.54.in-addr.arpa domain name pointer ec2-54-204-64-164.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
164.64.204.54.in-addr.arpa	name = ec2-54-204-64-164.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
162.243.158.198 attackspambots
Fail2Ban Ban Triggered (2)
2020-04-14 12:58:36
51.77.240.244 attackbots
20 attempts against mh-misbehave-ban on beach
2020-04-14 12:59:44
45.55.173.225 attackbotsspam
Wordpress malicious attack:[sshd]
2020-04-14 13:12:58
119.201.4.249 attack
Honeypot Attack, Port 23
2020-04-14 13:31:39
202.79.24.8 attack
20/4/13@23:54:28: FAIL: Alarm-Network address from=202.79.24.8
20/4/13@23:54:28: FAIL: Alarm-Network address from=202.79.24.8
...
2020-04-14 12:56:24
185.175.93.105 attackspambots
Apr 14 06:59:20 debian-2gb-nbg1-2 kernel: \[9099351.035971\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.175.93.105 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=34904 PROTO=TCP SPT=57257 DPT=57075 WINDOW=1024 RES=0x00 SYN URGP=0
2020-04-14 13:32:06
220.166.63.47 attackbots
Apr 14 07:24:53 OPSO sshd\[30164\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.166.63.47  user=root
Apr 14 07:24:55 OPSO sshd\[30164\]: Failed password for root from 220.166.63.47 port 62776 ssh2
Apr 14 07:28:41 OPSO sshd\[31082\]: Invalid user isaiah from 220.166.63.47 port 62194
Apr 14 07:28:41 OPSO sshd\[31082\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.166.63.47
Apr 14 07:28:43 OPSO sshd\[31082\]: Failed password for invalid user isaiah from 220.166.63.47 port 62194 ssh2
2020-04-14 13:30:05
36.79.186.240 attack
Unauthorized connection attempt detected from IP address 36.79.186.240 to port 445
2020-04-14 13:36:00
154.245.52.77 attackbots
Repeated attempts against wp-login
2020-04-14 13:28:27
125.166.185.226 attackbotsspam
ID_MAINT-TELKOMNET_<177>1586836418 [1:2010935:3] ET SCAN Suspicious inbound to MSSQL port 1433 [Classification: Potentially Bad Traffic] [Priority: 2]:  {TCP} 125.166.185.226:49267
2020-04-14 13:32:53
189.135.77.202 attack
Apr 13 23:56:34 Tower sshd[44088]: Connection from 189.135.77.202 port 42576 on 192.168.10.220 port 22 rdomain ""
Apr 13 23:56:35 Tower sshd[44088]: Invalid user user7 from 189.135.77.202 port 42576
Apr 13 23:56:35 Tower sshd[44088]: error: Could not get shadow information for NOUSER
Apr 13 23:56:35 Tower sshd[44088]: Failed password for invalid user user7 from 189.135.77.202 port 42576 ssh2
Apr 13 23:56:35 Tower sshd[44088]: Received disconnect from 189.135.77.202 port 42576:11: Bye Bye [preauth]
Apr 13 23:56:35 Tower sshd[44088]: Disconnected from invalid user user7 189.135.77.202 port 42576 [preauth]
2020-04-14 12:53:32
104.227.139.186 attackspam
Apr 13 19:07:50 wbs sshd\[18975\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.227.139.186  user=root
Apr 13 19:07:52 wbs sshd\[18975\]: Failed password for root from 104.227.139.186 port 52024 ssh2
Apr 13 19:11:31 wbs sshd\[19328\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.227.139.186  user=root
Apr 13 19:11:32 wbs sshd\[19328\]: Failed password for root from 104.227.139.186 port 32864 ssh2
Apr 13 19:15:23 wbs sshd\[19641\]: Invalid user guest from 104.227.139.186
2020-04-14 13:37:06
111.229.28.34 attackbots
Apr 14 05:31:50 h2646465 sshd[7136]: Invalid user postdrop from 111.229.28.34
Apr 14 05:31:50 h2646465 sshd[7136]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.28.34
Apr 14 05:31:50 h2646465 sshd[7136]: Invalid user postdrop from 111.229.28.34
Apr 14 05:31:52 h2646465 sshd[7136]: Failed password for invalid user postdrop from 111.229.28.34 port 41484 ssh2
Apr 14 05:43:24 h2646465 sshd[8455]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.28.34  user=root
Apr 14 05:43:26 h2646465 sshd[8455]: Failed password for root from 111.229.28.34 port 42970 ssh2
Apr 14 05:48:29 h2646465 sshd[9102]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.28.34  user=root
Apr 14 05:48:31 h2646465 sshd[9102]: Failed password for root from 111.229.28.34 port 41996 ssh2
Apr 14 05:53:43 h2646465 sshd[9716]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rh
2020-04-14 13:28:49
134.175.176.97 attack
Apr 14 05:49:44 ns381471 sshd[17619]: Failed password for lp from 134.175.176.97 port 56932 ssh2
2020-04-14 12:58:15
137.226.113.10 attack
137.226.113.10
2020-04-14 12:57:11

Recently Reported IPs

21.58.74.103 195.222.65.62 45.130.255.216 51.75.25.38
210.76.251.98 117.6.78.253 220.180.121.6 106.13.125.248
194.135.86.170 18.139.27.76 193.8.80.129 190.175.180.22
122.114.170.197 193.42.118.91 198.71.238.5 35.51.247.227
114.221.125.217 126.16.255.252 130.168.117.23 91.192.170.0