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: IANA Special-Purpose Address

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

;; QUESTION SECTION:
;241.166.22.55.			IN	A

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

;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 22 02:03:28 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 55.22.166.241.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 55.22.166.241.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
148.70.250.207 attackspambots
vps1:pam-generic
2019-10-08 01:46:28
220.184.21.158 attack
Oct  7 13:40:02 host proftpd\[30122\]: 0.0.0.0 \(220.184.21.158\[220.184.21.158\]\) - USER anonymous: no such user found from 220.184.21.158 \[220.184.21.158\] to 62.210.146.38:21
...
2019-10-08 01:34:03
185.176.27.54 attackspam
firewall-block, port(s): 18184/tcp, 18185/tcp, 18186/tcp, 53494/tcp, 53495/tcp, 53496/tcp
2019-10-08 01:53:08
167.71.231.210 attackbotsspam
Oct  7 07:41:00 kapalua sshd\[21471\]: Invalid user Android-123 from 167.71.231.210
Oct  7 07:41:00 kapalua sshd\[21471\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.231.210
Oct  7 07:41:01 kapalua sshd\[21471\]: Failed password for invalid user Android-123 from 167.71.231.210 port 54634 ssh2
Oct  7 07:45:45 kapalua sshd\[21893\]: Invalid user Betrieb-123 from 167.71.231.210
Oct  7 07:45:45 kapalua sshd\[21893\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.231.210
2019-10-08 01:50:32
107.189.2.139 attack
WordPress wp-login brute force :: 107.189.2.139 0.116 BYPASS [07/Oct/2019:22:40:19  1100] [censored_1] "POST /wp-login.php HTTP/1.1" 200 3972 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-10-08 01:28:10
35.154.103.207 attackbotsspam
Oct  7 19:03:35 MK-Soft-VM7 sshd[17300]: Failed password for root from 35.154.103.207 port 25097 ssh2
...
2019-10-08 01:18:19
159.65.189.115 attack
Oct  7 17:39:57 venus sshd\[23940\]: Invalid user Triple123 from 159.65.189.115 port 54710
Oct  7 17:39:57 venus sshd\[23940\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.189.115
Oct  7 17:39:59 venus sshd\[23940\]: Failed password for invalid user Triple123 from 159.65.189.115 port 54710 ssh2
...
2019-10-08 01:53:30
206.41.186.46 attack
Automatic report - Banned IP Access
2019-10-08 01:50:18
190.64.141.18 attackbotsspam
SSH Brute-Force reported by Fail2Ban
2019-10-08 01:48:49
168.232.156.205 attackbots
Oct  7 07:22:34 hanapaa sshd\[23329\]: Invalid user Boca@321 from 168.232.156.205
Oct  7 07:22:34 hanapaa sshd\[23329\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.232.156.205
Oct  7 07:22:37 hanapaa sshd\[23329\]: Failed password for invalid user Boca@321 from 168.232.156.205 port 47940 ssh2
Oct  7 07:28:24 hanapaa sshd\[23880\]: Invalid user nhy65tgbvfr4 from 168.232.156.205
Oct  7 07:28:24 hanapaa sshd\[23880\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.232.156.205
2019-10-08 01:38:19
112.48.132.196 attack
Brute force attempt
2019-10-08 01:35:56
109.202.117.145 attack
Oct  7 16:32:08 h2177944 kernel: \[3334831.017071\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=109.202.117.145 DST=85.214.117.9 LEN=40 TOS=0x08 PREC=0x20 TTL=71 ID=65060 DF PROTO=TCP SPT=58655 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0 
Oct  7 16:50:54 h2177944 kernel: \[3335956.882819\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=109.202.117.145 DST=85.214.117.9 LEN=40 TOS=0x08 PREC=0x20 TTL=79 ID=58003 DF PROTO=TCP SPT=57289 DPT=22 WINDOW=29200 RES=0x00 SYN URGP=0 
Oct  7 16:58:55 h2177944 kernel: \[3336438.289464\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=109.202.117.145 DST=85.214.117.9 LEN=40 TOS=0x08 PREC=0x20 TTL=55 ID=48896 DF PROTO=TCP SPT=62360 DPT=80 WINDOW=29200 RES=0x00 SYN URGP=0 
Oct  7 17:01:36 h2177944 kernel: \[3336598.516156\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=109.202.117.145 DST=85.214.117.9 LEN=40 TOS=0x08 PREC=0x20 TTL=69 ID=2383 DF PROTO=TCP SPT=51424 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0 
Oct  7 17:05:56 h2177944 kernel: \[3336859.032451\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=109.202.117.145 D
2019-10-08 01:52:11
185.101.105.194 attack
19/10/7@07:39:17: FAIL: IoT-Telnet address from=185.101.105.194
19/10/7@07:39:17: FAIL: IoT-Telnet address from=185.101.105.194
19/10/7@07:39:17: FAIL: IoT-Telnet address from=185.101.105.194
...
2019-10-08 01:53:45
27.105.197.176 attackspambots
firewall-block, port(s): 445/tcp
2019-10-08 01:35:27
91.121.114.69 attackbotsspam
Oct  7 19:41:32 minden010 sshd[20529]: Failed password for root from 91.121.114.69 port 32854 ssh2
Oct  7 19:44:56 minden010 sshd[22367]: Failed password for root from 91.121.114.69 port 43602 ssh2
...
2019-10-08 01:54:29

Recently Reported IPs

206.94.98.237 142.156.164.180 64.73.18.39 7.8.134.148
178.210.66.141 95.4.6.244 47.178.141.62 237.78.13.33
229.195.161.23 67.246.230.153 85.124.250.96 91.52.26.234
63.55.17.199 119.239.148.220 159.172.255.205 47.94.58.240
93.123.166.23 147.145.144.206 41.255.254.225 212.174.0.1