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

;; QUESTION SECTION:
;162.55.166.41.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 22:58:26 CST 2022
;; MSG SIZE  rcvd: 106
Host info
41.166.55.162.in-addr.arpa domain name pointer static.41.166.55.162.clients.your-server.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
41.166.55.162.in-addr.arpa	name = static.41.166.55.162.clients.your-server.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
111.230.219.156 attack
Invalid user zym from 111.230.219.156 port 40174
2020-05-16 07:37:07
109.184.153.138 attackspam
0,45-05/24 [bc02/m06] PostRequest-Spammer scoring: Lusaka01
2020-05-16 07:48:13
139.155.6.244 attackspam
May 15 16:58:48 server1 sshd\[12642\]: Invalid user root@47 from 139.155.6.244
May 15 16:58:48 server1 sshd\[12642\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.6.244 
May 15 16:58:51 server1 sshd\[12642\]: Failed password for invalid user root@47 from 139.155.6.244 port 59422 ssh2
May 15 17:05:12 server1 sshd\[14478\]: Invalid user deploy from 139.155.6.244
May 15 17:05:12 server1 sshd\[14478\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.6.244 
...
2020-05-16 07:23:53
141.98.80.44 attack
Auto Fail2Ban report, multiple SMTP login attempts.
2020-05-16 07:28:11
79.124.62.246 attackspambots
SSH Bruteforce attempt
2020-05-16 07:34:40
14.240.238.106 attackspam
Port probing on unauthorized port 8080
2020-05-16 07:22:58
106.13.207.113 attackspam
$f2bV_matches
2020-05-16 07:32:09
116.196.105.232 attackbots
Unauthorized access or intrusion attempt detected from Thor banned IP
2020-05-16 07:39:11
182.20.204.199 attackbotsspam
2020-05-15T21:54:23.161923shield sshd\[16309\]: Invalid user admin from 182.20.204.199 port 44726
2020-05-15T21:54:23.171287shield sshd\[16309\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=199.net182020204.t-com.ne.jp
2020-05-15T21:54:25.388593shield sshd\[16309\]: Failed password for invalid user admin from 182.20.204.199 port 44726 ssh2
2020-05-15T21:57:39.890086shield sshd\[16948\]: Invalid user radio from 182.20.204.199 port 36216
2020-05-15T21:57:39.897528shield sshd\[16948\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=199.net182020204.t-com.ne.jp
2020-05-16 07:46:58
139.162.123.29 attack
Port scan: Attack repeated for 24 hours
2020-05-16 07:25:41
36.108.168.81 attack
SASL PLAIN auth failed: ruser=...
2020-05-16 07:22:44
31.168.241.114 attack
Port probing on unauthorized port 81
2020-05-16 07:29:33
183.221.243.216 attack
Invalid user ubuntu from 183.221.243.216 port 53462
2020-05-16 07:43:05
151.16.37.184 attack
SSH Invalid Login
2020-05-16 07:16:46
117.34.210.106 attackspam
Invalid user mobil from 117.34.210.106 port 60854
2020-05-16 07:36:36

Recently Reported IPs

139.155.239.81 137.184.188.133 200.32.80.51 192.177.186.123
190.9.17.231 77.227.129.90 117.15.221.178 91.188.246.225
154.201.44.163 170.233.46.128 150.95.83.201 198.98.60.170
117.199.210.217 43.134.0.214 109.165.205.182 83.171.253.209
185.239.56.201 177.249.168.208 182.127.140.250 109.238.180.201