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

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

;; QUESTION SECTION:
;141.0.11.220.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 09:16:37 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 220.11.0.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 220.11.0.141.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
119.126.162.60 attackbots
IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/119.126.162.60/ 
 CN - 1H : (553)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : CN 
 NAME ASN : ASN4134 
 
 IP : 119.126.162.60 
 
 CIDR : 119.124.0.0/14 
 
 PREFIX COUNT : 5430 
 
 UNIQUE IP COUNT : 106919680 
 
 
 WYKRYTE ATAKI Z ASN4134 :  
  1H - 4 
  3H - 19 
  6H - 43 
 12H - 80 
 24H - 195 
 
 DateTime : 2019-10-18 05:47:29 
 
 INFO : Server 403 - Looking for resource vulnerabilities Detected and Blocked by ADMIN  - data recovery
2019-10-18 17:31:43
217.218.21.242 attackspam
Automatic report - SSH Brute-Force Attack
2019-10-18 18:08:35
80.82.78.100 attackbots
18.10.2019 09:08:07 Connection to port 1157 blocked by firewall
2019-10-18 18:04:36
200.11.150.238 attackbots
Oct 18 11:23:38 tuxlinux sshd[43130]: Invalid user admin from 200.11.150.238 port 59531
Oct 18 11:23:38 tuxlinux sshd[43130]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.11.150.238 
Oct 18 11:23:38 tuxlinux sshd[43130]: Invalid user admin from 200.11.150.238 port 59531
Oct 18 11:23:38 tuxlinux sshd[43130]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.11.150.238 
Oct 18 11:23:38 tuxlinux sshd[43130]: Invalid user admin from 200.11.150.238 port 59531
Oct 18 11:23:38 tuxlinux sshd[43130]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.11.150.238 
Oct 18 11:23:40 tuxlinux sshd[43130]: Failed password for invalid user admin from 200.11.150.238 port 59531 ssh2
...
2019-10-18 18:10:47
62.234.96.175 attack
Oct 18 07:00:08 www5 sshd\[18362\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.96.175  user=root
Oct 18 07:00:10 www5 sshd\[18362\]: Failed password for root from 62.234.96.175 port 43226 ssh2
Oct 18 07:04:32 www5 sshd\[19326\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.96.175  user=root
...
2019-10-18 17:36:58
128.199.173.127 attackspambots
Invalid user plex from 128.199.173.127 port 52963
2019-10-18 17:32:29
201.6.99.139 attackspambots
2019-10-18T06:34:53.486083abusebot-5.cloudsearch.cf sshd\[16306\]: Invalid user ts3bot from 201.6.99.139 port 52081
2019-10-18 17:41:01
94.191.41.77 attack
Oct 18 09:18:38 meumeu sshd[14709]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.191.41.77 
Oct 18 09:18:40 meumeu sshd[14709]: Failed password for invalid user beth from 94.191.41.77 port 41816 ssh2
Oct 18 09:23:39 meumeu sshd[15409]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.191.41.77 
...
2019-10-18 18:05:00
222.91.151.24 attackspambots
$f2bV_matches
2019-10-18 17:54:38
89.219.10.226 attackbots
10/17/2019-23:46:09.420861 89.219.10.226 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-10-18 18:02:51
5.148.3.212 attackbots
Oct 18 06:49:56 vps691689 sshd[31090]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.148.3.212
Oct 18 06:49:58 vps691689 sshd[31090]: Failed password for invalid user localadmin from 5.148.3.212 port 40470 ssh2
Oct 18 06:54:07 vps691689 sshd[31110]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.148.3.212
...
2019-10-18 17:45:54
188.254.0.197 attack
(sshd) Failed SSH login from 188.254.0.197 (RU/Russia/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct 18 09:13:45 server2 sshd[24043]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.197  user=root
Oct 18 09:13:46 server2 sshd[24043]: Failed password for root from 188.254.0.197 port 53615 ssh2
Oct 18 09:22:00 server2 sshd[24272]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.197  user=root
Oct 18 09:22:02 server2 sshd[24272]: Failed password for root from 188.254.0.197 port 56449 ssh2
Oct 18 09:25:40 server2 sshd[24346]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.197  user=root
2019-10-18 17:44:26
54.36.150.190 attack
Automatic report - Banned IP Access
2019-10-18 17:59:38
31.163.151.99 attack
Fail2Ban Ban Triggered
2019-10-18 17:39:21
216.167.250.218 attackspambots
2019-10-18T05:23:48.575762abusebot-2.cloudsearch.cf sshd\[18641\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=smtp.onaping.org  user=root
2019-10-18 18:07:59

Recently Reported IPs

141.0.11.219 141.0.11.221 141.0.11.222 141.0.11.218
141.0.11.223 141.0.11.224 141.0.11.227 141.0.11.22
141.0.11.225 141.0.11.228 118.96.115.97 141.0.11.23
141.0.11.230 141.0.11.226 141.0.11.232 141.0.11.229
141.0.11.233 141.0.11.231 141.0.11.234 141.0.11.235