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

Region: Thüringen

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

;; QUESTION SECTION:
;141.54.2.106.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 05 05:34:27 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 106.2.54.141.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 106.2.54.141.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
182.61.148.125 attackbots
Tried sshing with brute force.
2019-11-02 22:57:57
185.26.99.7 attackbotsspam
slow and persistent scanner
2019-11-02 22:56:11
41.87.80.26 attack
Nov  2 15:24:50 vps01 sshd[17198]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.87.80.26
Nov  2 15:24:52 vps01 sshd[17198]: Failed password for invalid user 123Lobster from 41.87.80.26 port 30540 ssh2
2019-11-02 23:10:37
51.38.37.128 attackbotsspam
Nov  2 15:05:08 SilenceServices sshd[19198]: Failed password for root from 51.38.37.128 port 41486 ssh2
Nov  2 15:08:34 SilenceServices sshd[21385]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.37.128
Nov  2 15:08:36 SilenceServices sshd[21385]: Failed password for invalid user pos from 51.38.37.128 port 60439 ssh2
2019-11-02 22:38:47
139.198.4.44 attack
vulcan
2019-11-02 22:54:26
104.42.158.117 attackspam
2019-11-02T11:51:11.532316hub.schaetter.us sshd\[24299\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.42.158.117  user=root
2019-11-02T11:51:13.247598hub.schaetter.us sshd\[24299\]: Failed password for root from 104.42.158.117 port 50976 ssh2
2019-11-02T11:55:53.967212hub.schaetter.us sshd\[24332\]: Invalid user centos from 104.42.158.117 port 50976
2019-11-02T11:55:53.979984hub.schaetter.us sshd\[24332\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.42.158.117
2019-11-02T11:55:56.076211hub.schaetter.us sshd\[24332\]: Failed password for invalid user centos from 104.42.158.117 port 50976 ssh2
...
2019-11-02 22:51:02
150.42.44.11 attackbotsspam
Invalid user pi from 150.42.44.11 port 37184
Invalid user pi from 150.42.44.11 port 37190
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.42.44.11
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.42.44.11
Failed password for invalid user pi from 150.42.44.11 port 37184 ssh2
2019-11-02 23:02:43
3.232.116.75 attackbots
De meest effectieve manier om geld te verdienen met Bitcoin
2019-11-02 22:55:37
103.215.82.188 attackbots
Nov  2 14:55:30 server sshd\[12549\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.215.82.188  user=root
Nov  2 14:55:31 server sshd\[12545\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.215.82.188  user=root
Nov  2 14:55:31 server sshd\[12556\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.215.82.188  user=root
Nov  2 14:55:32 server sshd\[12549\]: Failed password for root from 103.215.82.188 port 17952 ssh2
Nov  2 14:55:32 server sshd\[12554\]: Received disconnect from 103.215.82.188: 3: com.jcraft.jsch.JSchException: Auth fail
...
2019-11-02 23:10:03
156.96.153.26 attackbots
Lines containing failures of 156.96.153.26
Oct 30 15:44:47 shared09 sshd[23767]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=156.96.153.26  user=r.r
Oct 30 15:44:48 shared09 sshd[23767]: Failed password for r.r from 156.96.153.26 port 42472 ssh2
Oct 30 15:44:48 shared09 sshd[23767]: Received disconnect from 156.96.153.26 port 42472:11: Bye Bye [preauth]
Oct 30 15:44:48 shared09 sshd[23767]: Disconnected from authenticating user r.r 156.96.153.26 port 42472 [preauth]
Oct 30 16:03:12 shared09 sshd[29595]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=156.96.153.26  user=r.r
Oct 30 16:03:14 shared09 sshd[29595]: Failed password for r.r from 156.96.153.26 port 51922 ssh2
Oct 30 16:03:14 shared09 sshd[29595]: Received disconnect from 156.96.153.26 port 51922:11: Bye Bye [preauth]
Oct 30 16:03:14 shared09 sshd[29595]: Disconnected from authenticating user r.r 156.96.153.26 port 51922 [preauth........
------------------------------
2019-11-02 22:58:29
61.153.215.122 attackbotsspam
Nov  2 12:55:09 xeon cyrus/imap[50893]: badlogin: [61.153.215.122] plain [SASL(-13): authentication failure: Password verification failed]
2019-11-02 22:47:47
89.22.52.17 attackspambots
11/02/2019-14:52:47.876502 89.22.52.17 Protocol: 6 ET POLICY Cleartext WordPress Login
2019-11-02 23:12:33
190.98.111.90 attackbotsspam
Lines containing failures of 190.98.111.90
Nov  2 12:48:09 shared06 sshd[19880]: Invalid user admin from 190.98.111.90 port 35527
Nov  2 12:48:09 shared06 sshd[19880]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.98.111.90
Nov  2 12:48:11 shared06 sshd[19880]: Failed password for invalid user admin from 190.98.111.90 port 35527 ssh2
Nov  2 12:48:11 shared06 sshd[19880]: Connection closed by invalid user admin 190.98.111.90 port 35527 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=190.98.111.90
2019-11-02 22:38:00
198.108.67.34 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-02 23:11:53
95.85.68.67 attackbotsspam
Ein möglicherweise gefährlicher Request.Form-Wert wurde vom Client (mp$ContentZone$TxtMessage="
2019-11-02 23:06:40

Recently Reported IPs

202.246.191.36 157.195.9.200 144.180.152.41 69.110.206.112
84.104.51.122 117.11.22.9 43.200.44.90 73.240.65.91
225.6.93.147 38.62.206.202 151.243.120.10 50.204.54.168
89.19.36.63 118.155.36.122 230.31.171.179 37.64.198.158
33.181.126.253 150.153.9.20 81.41.103.41 163.135.98.61