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

;; QUESTION SECTION:
;53.4.85.154.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 22 16:05:10 CST 2025
;; MSG SIZE  rcvd: 104
Host info
Host 154.85.4.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 154.85.4.53.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
62.235.157.62 attackbots
Jul 26 10:26:35 own sshd[1647]: Invalid user pi from 62.235.157.62
Jul 26 10:26:35 own sshd[1648]: Invalid user pi from 62.235.157.62
Jul 26 10:26:35 own sshd[1647]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.235.157.62
Jul 26 10:26:35 own sshd[1648]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.235.157.62
Jul 26 10:26:37 own sshd[1647]: Failed password for invalid user pi from 62.235.157.62 port 49789 ssh2
Jul 26 10:26:37 own sshd[1648]: Failed password for invalid user pi from 62.235.157.62 port 49791 ssh2
Jul 26 10:26:37 own sshd[1647]: Connection closed by 62.235.157.62 port 49789 [preauth]
Jul 26 10:26:37 own sshd[1648]: Connection closed by 62.235.157.62 port 49791 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=62.235.157.62
2019-07-27 01:43:51
206.189.137.113 attackbots
2019-07-26T18:04:43.592347abusebot-5.cloudsearch.cf sshd\[18928\]: Invalid user zimbra from 206.189.137.113 port 43014
2019-07-27 02:12:18
115.94.204.156 attackbotsspam
Jul 26 21:18:03 yabzik sshd[14206]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.94.204.156
Jul 26 21:18:05 yabzik sshd[14206]: Failed password for invalid user spark from 115.94.204.156 port 33438 ssh2
Jul 26 21:23:18 yabzik sshd[15927]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.94.204.156
2019-07-27 02:23:48
175.107.61.129 attack
Honeypot triggered via portsentry
2019-07-27 01:55:43
151.80.41.64 attackbots
ssh failed login
2019-07-27 02:27:42
54.83.54.37 attackspambots
Bot ignores robot.txt restrictions
2019-07-27 01:42:24
178.216.49.60 attack
Automatic report - Banned IP Access
2019-07-27 02:12:48
110.88.208.192 attackbots
Jul 26 18:53:45 mail sshd\[31046\]: Failed password for invalid user mxuser from 110.88.208.192 port 65311 ssh2
Jul 26 19:10:26 mail sshd\[31501\]: Invalid user test1 from 110.88.208.192 port 12967
...
2019-07-27 02:22:17
198.48.133.231 attack
Jul 26 18:36:14 debian sshd\[13279\]: Invalid user jesse from 198.48.133.231 port 35784
Jul 26 18:36:15 debian sshd\[13279\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.48.133.231
...
2019-07-27 01:38:48
47.107.254.226 attack
DATE:2019-07-26 12:56:15, IP:47.107.254.226, PORT:ssh SSH brute force auth (ermes)
2019-07-27 02:04:48
184.164.150.144 attackbotsspam
Lines containing failures of 184.164.150.144
Jul 23 02:40:04 MAKserver05 postfix/postscreen[17378]: CONNECT from [184.164.150.144]:34031 to [5.9.147.207]:25
Jul 23 02:40:05 MAKserver05 postfix/dnsblog[17381]: addr 184.164.150.144 listed by domain zen.spamhaus.org as 127.0.0.3
Jul 23 02:40:10 MAKserver05 postfix/postscreen[17378]: DNSBL rank 2 for [184.164.150.144]:34031
Jul x@x
Jul 23 02:40:11 MAKserver05 postfix/postscreen[17378]: DISCONNECT [184.164.150.144]:34031
Jul 26 10:36:13 MAKserver05 postfix/postscreen[18384]: CONNECT from [184.164.150.144]:45941 to [5.9.147.207]:25
Jul 26 10:36:13 MAKserver05 postfix/dnsblog[18387]: addr 184.164.150.144 listed by domain zen.spamhaus.org as 127.0.0.3
Jul 26 10:36:13 MAKserver05 postfix/dnsblog[18385]: addr 184.164.150.144 listed by domain b.barracudacentral.org as 127.0.0.2
Jul 26 10:36:19 MAKserver05 postfix/postscreen[18384]: DNSBL rank 3 for [184.164.150.144]:45941
Jul x@x
Jul 26 10:36:20 MAKserver05 postfix/postscreen[18384........
------------------------------
2019-07-27 02:19:55
78.171.164.11 attackspambots
Unauthorised access (Jul 26) SRC=78.171.164.11 LEN=52 TTL=113 ID=4396 DF TCP DPT=445 WINDOW=8192 SYN
2019-07-27 02:04:17
37.139.20.33 attackbots
Jul 26 19:19:05 OPSO sshd\[4458\]: Invalid user almacen from 37.139.20.33 port 45202
Jul 26 19:19:05 OPSO sshd\[4458\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.139.20.33
Jul 26 19:19:07 OPSO sshd\[4458\]: Failed password for invalid user almacen from 37.139.20.33 port 45202 ssh2
Jul 26 19:23:20 OPSO sshd\[5518\]: Invalid user cj from 37.139.20.33 port 41562
Jul 26 19:23:20 OPSO sshd\[5518\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.139.20.33
2019-07-27 01:25:24
186.219.248.43 attackbots
Automatic report - Port Scan Attack
2019-07-27 02:26:20
49.81.199.216 attack
[Aegis] @ 2019-07-26 09:55:03  0100 -> Sendmail rejected message.
2019-07-27 02:10:31

Recently Reported IPs

211.69.50.231 137.13.19.140 65.209.156.11 74.203.17.111
251.44.29.140 234.11.208.201 202.141.98.251 20.65.42.74
74.83.82.59 116.49.138.231 169.112.121.8 205.70.42.182
162.161.17.196 138.88.66.180 129.201.57.123 229.43.114.37
125.136.174.78 55.152.184.18 184.27.17.254 189.7.169.118