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 of America (the)

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 <<>> 52.89.8.21
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 18009
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;52.89.8.21.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 16 16:37:51 CST 2025
;; MSG SIZE  rcvd: 103
Host info
21.8.89.52.in-addr.arpa domain name pointer ec2-52-89-8-21.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
21.8.89.52.in-addr.arpa	name = ec2-52-89-8-21.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
159.203.201.183 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-22 02:05:55
179.162.241.215 attack
Nov 21 17:34:59 server sshd\[15168\]: Invalid user ftb from 179.162.241.215
Nov 21 17:34:59 server sshd\[15168\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.162.241.215 
Nov 21 17:35:01 server sshd\[15168\]: Failed password for invalid user ftb from 179.162.241.215 port 54052 ssh2
Nov 21 17:52:34 server sshd\[19589\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.162.241.215  user=root
Nov 21 17:52:37 server sshd\[19589\]: Failed password for root from 179.162.241.215 port 39738 ssh2
...
2019-11-22 02:07:33
218.92.0.155 attackbots
SSH authentication failure x 6 reported by Fail2Ban
...
2019-11-22 01:56:50
180.188.16.113 attackbots
Honeypot attack, port: 445, PTR: PTR record not found
2019-11-22 01:58:07
159.65.133.212 attackbots
Automatic report - Banned IP Access
2019-11-22 01:35:08
221.167.38.194 attack
Honeypot attack, port: 23, PTR: PTR record not found
2019-11-22 02:09:06
124.74.111.206 attackbotsspam
Honeypot attack, port: 23, PTR: PTR record not found
2019-11-22 02:00:55
109.94.125.98 attack
Honeypot attack, port: 23, PTR: PTR record not found
2019-11-22 02:07:51
211.195.117.212 attackbotsspam
fail2ban
2019-11-22 01:36:51
95.213.177.126 attackspambots
Port scan on 1 port(s): 8080
2019-11-22 01:43:12
142.4.211.5 attackspam
Invalid user heddell from 142.4.211.5 port 38002
2019-11-22 02:02:37
165.22.138.68 attackbots
$f2bV_matches
2019-11-22 01:49:56
153.193.248.1 attack
Honeypot attack, port: 23, PTR: p180001-ipngn200304gifu.gifu.ocn.ne.jp.
2019-11-22 01:42:29
163.172.218.246 attackspam
Nov 21 12:53:38 TORMINT sshd\[24079\]: Invalid user gonzaga from 163.172.218.246
Nov 21 12:53:38 TORMINT sshd\[24079\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.218.246
Nov 21 12:53:41 TORMINT sshd\[24079\]: Failed password for invalid user gonzaga from 163.172.218.246 port 58113 ssh2
...
2019-11-22 02:00:02
185.143.223.152 attackspam
185.143.223.152 was recorded 9 times by 3 hosts attempting to connect to the following ports: 34043,34833,34245,34863,34591,34666,34955,34019. Incident counter (4h, 24h, all-time): 9, 60, 163
2019-11-22 01:32:38

Recently Reported IPs

227.146.206.181 138.145.186.178 217.88.176.193 237.33.224.247
89.16.50.238 22.141.219.226 244.88.206.140 141.167.175.234
40.120.166.246 115.148.180.237 67.42.36.33 130.164.34.136
195.53.198.66 148.217.19.92 229.58.85.220 55.46.227.231
96.8.226.97 196.191.100.148 66.253.204.192 50.173.173.218