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

;; QUESTION SECTION:
;52.89.40.140.			IN	A

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

;; Query time: 34 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Mar 13 17:42:42 CST 2025
;; MSG SIZE  rcvd: 105
Host info
140.40.89.52.in-addr.arpa domain name pointer ec2-52-89-40-140.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
140.40.89.52.in-addr.arpa	name = ec2-52-89-40-140.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
111.67.206.4 attack
SSH brute force attempt
2020-04-26 04:11:08
194.31.244.26 attack
Apr 25 22:00:25 debian-2gb-nbg1-2 kernel: \[10103763.529713\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=194.31.244.26 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=1429 PROTO=TCP SPT=57719 DPT=33778 WINDOW=1024 RES=0x00 SYN URGP=0
2020-04-26 04:20:20
159.89.145.59 attackbots
Apr 25 14:19:27 firewall sshd[10561]: Invalid user leviomri from 159.89.145.59
Apr 25 14:19:30 firewall sshd[10561]: Failed password for invalid user leviomri from 159.89.145.59 port 46696 ssh2
Apr 25 14:23:21 firewall sshd[10626]: Invalid user bella from 159.89.145.59
...
2020-04-26 04:25:19
178.154.200.63 attackbots
Unauthorized connection attempt, very violent continuous attack! IP address disabled!
2020-04-26 03:56:15
189.208.63.38 attack
Automatic report - Port Scan Attack
2020-04-26 04:25:54
106.12.69.35 attackspam
SSH auth scanning - multiple failed logins
2020-04-26 04:14:01
198.108.67.42 attack
port
2020-04-26 04:01:49
162.243.50.8 attack
Apr 25 14:21:32 ip-172-31-61-156 sshd[6827]: Invalid user madssen from 162.243.50.8
Apr 25 14:21:33 ip-172-31-61-156 sshd[6827]: Failed password for invalid user madssen from 162.243.50.8 port 34640 ssh2
Apr 25 14:21:32 ip-172-31-61-156 sshd[6827]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.243.50.8
Apr 25 14:21:32 ip-172-31-61-156 sshd[6827]: Invalid user madssen from 162.243.50.8
Apr 25 14:21:33 ip-172-31-61-156 sshd[6827]: Failed password for invalid user madssen from 162.243.50.8 port 34640 ssh2
...
2020-04-26 04:28:41
69.157.55.137 attack
Invalid user user from 69.157.55.137 port 45568
2020-04-26 04:16:38
200.195.171.74 attackbots
Invalid user vx from 200.195.171.74 port 43436
2020-04-26 04:13:09
162.243.130.8 attackspam
firewall-block, port(s): 5672/tcp
2020-04-26 04:13:37
168.232.130.125 attackspam
Port probing on unauthorized port 22
2020-04-26 03:51:29
189.173.30.89 attack
Unauthorized connection attempt detected from IP address 189.173.30.89 to port 4567
2020-04-26 04:22:04
142.93.68.181 attackbotsspam
04/25/2020-15:11:05.174508 142.93.68.181 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-04-26 04:08:42
151.76.149.81 attackspam
" "
2020-04-26 04:06:12

Recently Reported IPs

167.166.248.63 28.1.210.201 77.18.242.157 67.199.21.5
225.134.102.3 234.230.51.174 85.39.239.129 53.214.8.191
217.195.50.235 75.20.136.1 69.147.242.94 235.234.82.215
150.158.60.143 219.82.92.140 206.191.87.128 243.13.30.215
36.126.104.226 72.136.145.49 60.67.15.230 143.160.21.144