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

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

;; QUESTION SECTION:
;53.17.189.54.			IN	A

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

;; Query time: 49 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 12 03:13:07 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 54.189.17.53.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 54.189.17.53.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
103.214.189.201 attackspam
Unauthorized connection attempt from IP address 103.214.189.201 on Port 445(SMB)
2019-07-07 01:03:50
182.75.248.254 attackspam
Jul  6 15:26:23 tux-35-217 sshd\[10087\]: Invalid user uftp from 182.75.248.254 port 39176
Jul  6 15:26:23 tux-35-217 sshd\[10087\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.75.248.254
Jul  6 15:26:25 tux-35-217 sshd\[10087\]: Failed password for invalid user uftp from 182.75.248.254 port 39176 ssh2
Jul  6 15:29:04 tux-35-217 sshd\[10096\]: Invalid user zhanghua from 182.75.248.254 port 35682
Jul  6 15:29:04 tux-35-217 sshd\[10096\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.75.248.254
...
2019-07-07 01:38:17
51.38.34.110 attackbotsspam
DATE:2019-07-06 15:30:09, IP:51.38.34.110, PORT:ssh brute force auth on SSH service (patata)
2019-07-07 01:12:28
41.0.169.97 attackbotsspam
Jul  5 12:41:52 eola postfix/smtpd[25322]: connect from unknown[41.0.169.97]
Jul  5 12:41:53 eola postfix/smtpd[25322]: lost connection after AUTH from unknown[41.0.169.97]
Jul  5 12:41:53 eola postfix/smtpd[25322]: disconnect from unknown[41.0.169.97] ehlo=1 auth=0/1 commands=1/2
Jul  5 12:41:53 eola postfix/smtpd[25322]: connect from unknown[41.0.169.97]
Jul  5 12:41:54 eola postfix/smtpd[25322]: lost connection after AUTH from unknown[41.0.169.97]
Jul  5 12:41:54 eola postfix/smtpd[25322]: disconnect from unknown[41.0.169.97] ehlo=1 auth=0/1 commands=1/2
Jul  5 12:41:54 eola postfix/smtpd[25322]: connect from unknown[41.0.169.97]
Jul  5 12:41:55 eola postfix/smtpd[25322]: lost connection after AUTH from unknown[41.0.169.97]
Jul  5 12:41:55 eola postfix/smtpd[25322]: disconnect from unknown[41.0.169.97] ehlo=1 auth=0/1 commands=1/2
Jul  5 12:41:55 eola postfix/smtpd[25322]: connect from unknown[41.0.169.97]
Jul  5 12:41:56 eola postfix/smtpd[25322]: lost connection af........
-------------------------------
2019-07-07 01:54:30
202.161.76.124 attackbotsspam
kp-sea2-01 recorded 2 login violations from 202.161.76.124 and was blocked at 2019-07-06 13:29:19. 202.161.76.124 has been blocked on 0 previous occasions. 202.161.76.124's first attempt was recorded at 2019-07-06 13:29:19
2019-07-07 01:33:43
177.154.238.173 attackspambots
Brute force attempt
2019-07-07 01:22:36
182.74.44.202 attack
Unauthorized connection attempt from IP address 182.74.44.202 on Port 445(SMB)
2019-07-07 01:16:08
139.59.78.236 attackspambots
SSH invalid-user multiple login attempts
2019-07-07 01:03:30
193.112.48.179 attackbots
Reported by AbuseIPDB proxy server.
2019-07-07 01:47:32
115.74.211.101 attack
Unauthorized connection attempt from IP address 115.74.211.101 on Port 445(SMB)
2019-07-07 01:06:54
134.73.161.217 attackbotsspam
Jul  6 11:31:11 myhostname sshd[32131]: Invalid user linux from 134.73.161.217
Jul  6 11:31:11 myhostname sshd[32131]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.73.161.217
Jul  6 11:31:12 myhostname sshd[32131]: Failed password for invalid user linux from 134.73.161.217 port 55614 ssh2
Jul  6 11:31:12 myhostname sshd[32131]: Received disconnect from 134.73.161.217 port 55614:11: Bye Bye [preauth]
Jul  6 11:31:12 myhostname sshd[32131]: Disconnected from 134.73.161.217 port 55614 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=134.73.161.217
2019-07-07 01:44:53
217.148.55.254 attackbotsspam
WordPress wp-login brute force :: 217.148.55.254 0.084 BYPASS [06/Jul/2019:23:29:02  1000] www.[censored_4] "POST /wp-login.php HTTP/1.1" 200 3538 "https://[censored_4]/wp-login.php" "Mozilla/5.0 (Windows NT 6.0; rv:34.0) Gecko/20100101 Firefox/34.0"
2019-07-07 01:39:36
168.253.75.188 attackbots
Unauthorized IMAP connection attempt.
2019-07-07 01:55:27
148.72.232.158 attack
Automatic report generated by Wazuh
2019-07-07 01:46:05
112.222.29.147 attackbots
Jul  6 16:15:12 vps647732 sshd[2115]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.222.29.147
Jul  6 16:15:14 vps647732 sshd[2115]: Failed password for invalid user ws from 112.222.29.147 port 51244 ssh2
...
2019-07-07 01:53:59

Recently Reported IPs

18.49.184.80 132.25.29.251 68.197.39.229 94.18.24.138
6.104.103.70 217.199.209.161 7.75.223.51 172.91.64.243
109.143.109.11 141.237.240.189 89.197.37.170 115.118.8.68
119.90.80.65 147.195.153.63 36.44.218.231 253.253.101.223
45.120.240.204 206.128.228.249 11.18.163.52 249.144.232.61