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:
IP Type Details Datetime
54.175.217.165 attack
RDP Bruteforce
2019-08-09 06:09:40
54.175.217.165 attackspambots
3389BruteforceFW21
2019-08-02 09:05:54
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 54.175.21.149
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 23628
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;54.175.21.149.			IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 26 01:30:56 CST 2025
;; MSG SIZE  rcvd: 106
Host info
149.21.175.54.in-addr.arpa domain name pointer ec2-54-175-21-149.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
149.21.175.54.in-addr.arpa	name = ec2-54-175-21-149.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
134.175.62.14 attackspam
Nov 10 10:51:22 roki sshd[17413]: refused connect from 134.175.62.14 (134.175.62.14)
Nov 10 14:14:33 roki sshd[31364]: refused connect from 134.175.62.14 (134.175.62.14)
Nov 10 17:20:43 roki sshd[12311]: refused connect from 134.175.62.14 (134.175.62.14)
Nov 10 21:52:58 roki sshd[32098]: refused connect from 134.175.62.14 (134.175.62.14)
Nov 11 10:08:48 roki sshd[18374]: refused connect from 134.175.62.14 (134.175.62.14)
...
2019-11-11 18:12:31
173.239.37.163 attack
Repeated brute force against a port
2019-11-11 18:06:37
140.143.72.21 attackbots
<6 unauthorized SSH connections
2019-11-11 18:26:15
104.37.47.7 attackspam
*Port Scan* detected from 104.37.47.7 (US/United States/104-37-47-7-host.colocrossing.com). 4 hits in the last 216 seconds
2019-11-11 18:19:56
118.89.249.95 attack
Nov 11 13:16:25 server sshd\[7286\]: Invalid user lichtenfels from 118.89.249.95
Nov 11 13:16:25 server sshd\[7286\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.89.249.95 
Nov 11 13:16:27 server sshd\[7286\]: Failed password for invalid user lichtenfels from 118.89.249.95 port 47482 ssh2
Nov 11 13:25:40 server sshd\[9885\]: Invalid user webmaster from 118.89.249.95
Nov 11 13:25:40 server sshd\[9885\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.89.249.95 
...
2019-11-11 18:34:27
206.189.52.160 attackbots
miraniessen.de 206.189.52.160 \[11/Nov/2019:07:25:28 +0100\] "POST /wp-login.php HTTP/1.1" 200 5974 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
miraniessen.de 206.189.52.160 \[11/Nov/2019:07:25:33 +0100\] "POST /wp-login.php HTTP/1.1" 200 5975 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-11-11 17:59:57
107.189.10.141 attackbotsspam
Invalid user fake from 107.189.10.141 port 55932
2019-11-11 17:58:11
51.38.68.83 attack
WordPress login Brute force / Web App Attack on client site.
2019-11-11 18:18:02
175.211.112.246 attackbots
2019-11-11T09:08:00.971412abusebot-5.cloudsearch.cf sshd\[2065\]: Invalid user robert from 175.211.112.246 port 38532
2019-11-11 18:08:21
86.38.171.149 attack
" "
2019-11-11 18:06:55
94.50.26.251 attackbots
Chat Spam
2019-11-11 18:26:40
196.195.254.211 attack
Connection by 196.195.254.211 on port: 23 got caught by honeypot at 11/11/2019 5:25:02 AM
2019-11-11 18:22:12
146.185.175.132 attackbots
Nov 11 08:03:33 vps666546 sshd\[3560\]: Invalid user wow from 146.185.175.132 port 33818
Nov 11 08:03:33 vps666546 sshd\[3560\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=146.185.175.132
Nov 11 08:03:36 vps666546 sshd\[3560\]: Failed password for invalid user wow from 146.185.175.132 port 33818 ssh2
Nov 11 08:07:20 vps666546 sshd\[3676\]: Invalid user bokbok from 146.185.175.132 port 44196
Nov 11 08:07:20 vps666546 sshd\[3676\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=146.185.175.132
...
2019-11-11 18:35:23
202.70.80.27 attack
(sshd) Failed SSH login from 202.70.80.27 (NP/Nepal/-/-/-/[AS23752 Nepal Telecommunications Corporation, Internet Services]): 1 in the last 3600 secs
2019-11-11 18:09:31
202.200.126.253 attack
Invalid user kayten from 202.200.126.253 port 59860
2019-11-11 18:15:56

Recently Reported IPs

220.174.152.97 122.1.87.65 79.154.251.8 161.83.54.195
187.190.185.184 227.239.66.119 109.18.85.172 98.244.14.88
180.247.204.229 221.210.229.223 5.67.31.203 131.30.33.105
129.33.255.235 3.68.237.193 216.63.148.198 137.153.75.203
233.89.125.83 243.28.57.14 209.199.93.198 239.62.41.42