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: Russian Federation

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:
IP Type Details Datetime
141.8.142.8 attack
(mod_security) mod_security (id:210740) triggered by 141.8.142.8 (RU/Russia/141-8-142-8.spider.yandex.com): 5 in the last 3600 secs
2020-09-01 16:26:50
141.8.142.157 attackbotsspam
[Sun Mar 22 20:00:03.538358 2020] [:error] [pid 21603:tid 139727231514368] [client 141.8.142.157:57267] [client 141.8.142.157] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "XndhUxnFXGtPZGixMNxsoAAAAh0"]
...
2020-03-23 01:02:32
141.8.142.60 attack
[Sat Mar 21 01:25:43.610942 2020] [:error] [pid 3790:tid 140719589320448] [client 141.8.142.60:65179] [client 141.8.142.60] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "XnUKpwSfYaBx8kyzBrm2LwAAALQ"]
...
2020-03-21 03:23:43
141.8.142.23 attackspam
[Fri Mar 20 23:27:32.054333 2020] [:error] [pid 2164:tid 140147611977472] [client 141.8.142.23:54455] [client 141.8.142.23] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "XnTu9C4o2dgKA24HFuSq9wAAAFo"]
...
2020-03-21 02:18:48
141.8.142.180 attack
[Thu Mar 19 01:09:39.567987 2020] [:error] [pid 21327:tid 139998034278144] [client 141.8.142.180:58741] [client 141.8.142.180] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "XnJj46fks8iqMveAsGOWFwAAAAI"]
...
2020-03-19 03:06:41
141.8.142.172 attackspambots
[Wed Mar 18 11:55:50.619904 2020] [:error] [pid 7238:tid 139937919776512] [client 141.8.142.172:54795] [client 141.8.142.172] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "XnGp1mRgp26zVn0yQ0hUowAAAOA"]
...
2020-03-18 14:58:10
141.8.142.1 attack
[Wed Mar 18 11:40:02.820155 2020] [:error] [pid 7238:tid 139937936561920] [client 141.8.142.1:63313] [client 141.8.142.1] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "XnGmImRgp26zVn0yQ0hLKQAAAN4"]
...
2020-03-18 13:55:32
141.8.142.23 attackspambots
[Fri Mar 13 14:57:50.528730 2020] [:error] [pid 5879:tid 140671184795392] [client 141.8.142.23:53161] [client 141.8.142.23] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "Xms8-rQ-QnNgbfQs7748mwAAAHI"]
...
2020-03-13 18:57:32
141.8.142.7 attack
RU - 1H : (182)  Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : RU 
 NAME ASN : ASN13238 
 
 IP : 141.8.142.7 
 
 CIDR : 141.8.128.0/20 
 
 PREFIX COUNT : 118 
 
 UNIQUE IP COUNT : 206080 
 
 
 WYKRYTE ATAKI Z ASN13238 :  
  1H - 3 
  3H - 3 
  6H - 3 
 12H - 5 
 24H - 12 
 
 INFO : Looking for resource vulnerabilities 403 Detected and Blocked by ADMIN  - data recovery 
  https://help-dysk.pl
2019-09-12 13:53:55
141.8.142.155 attackbotsspam
Jul 10 19:01:54   TCP Attack: SRC=141.8.142.155 DST=[Masked] LEN=258 TOS=0x08 PREC=0x20 TTL=44  DF PROTO=TCP SPT=49399 DPT=80 WINDOW=111 RES=0x00 ACK PSH URGP=0
2019-07-11 09:46:30
141.8.142.176 bots
看样子是yandex搜索引擎的可用性爬虫
141.8.142.176 - - [17/May/2019:17:29:40 +0800] "GET /check-ip/2804:14d:5a83:449f:5ab:f26:15e4:e7ce HTTP/1.1" 200 7939 "-" "Mozilla/5.0 (compatible; YandexAccessibilityBot/3.0; +http://yandex.com/bots)"
2019-05-17 17:33:15
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 141.8.142.76
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1836
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;141.8.142.76.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 12:17:19 CST 2022
;; MSG SIZE  rcvd: 105
Host info
76.142.8.141.in-addr.arpa domain name pointer 141-8-142-76.spider.yandex.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
76.142.8.141.in-addr.arpa	name = 141-8-142-76.spider.yandex.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
72.43.141.7 attackspambots
2019-12-06T13:46:40.729065  sshd[17900]: Invalid user guest from 72.43.141.7 port 2922
2019-12-06T13:46:40.743832  sshd[17900]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=72.43.141.7
2019-12-06T13:46:40.729065  sshd[17900]: Invalid user guest from 72.43.141.7 port 2922
2019-12-06T13:46:42.791020  sshd[17900]: Failed password for invalid user guest from 72.43.141.7 port 2922 ssh2
2019-12-06T13:54:55.780312  sshd[18006]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=72.43.141.7  user=root
2019-12-06T13:54:58.118162  sshd[18006]: Failed password for root from 72.43.141.7 port 1359 ssh2
...
2019-12-06 22:34:18
223.150.126.70 attackspambots
Scanning
2019-12-06 22:15:25
103.99.0.97 attackbotsspam
Dec  5 16:45:39 server sshd\[8950\]: Failed password for invalid user support from 103.99.0.97 port 57926 ssh2
Dec  6 07:49:48 server sshd\[32004\]: Invalid user support from 103.99.0.97
Dec  6 07:49:48 server sshd\[32004\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.99.0.97 
Dec  6 07:49:50 server sshd\[32004\]: Failed password for invalid user support from 103.99.0.97 port 58950 ssh2
Dec  6 11:46:14 server sshd\[32516\]: Invalid user support from 103.99.0.97
Dec  6 11:46:14 server sshd\[32516\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.99.0.97 
...
2019-12-06 22:02:51
123.201.66.160 attack
port scan and connect, tcp 1433 (ms-sql-s)
2019-12-06 22:20:51
175.197.77.3 attackspambots
Dec  6 04:27:24 wbs sshd\[7556\]: Invalid user ashley from 175.197.77.3
Dec  6 04:27:24 wbs sshd\[7556\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.197.77.3
Dec  6 04:27:27 wbs sshd\[7556\]: Failed password for invalid user ashley from 175.197.77.3 port 44441 ssh2
Dec  6 04:37:06 wbs sshd\[8506\]: Invalid user cooperacy from 175.197.77.3
Dec  6 04:37:06 wbs sshd\[8506\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.197.77.3
2019-12-06 22:38:59
210.92.91.223 attack
Dec  6 08:34:03 wh01 sshd[12454]: Invalid user skjersli from 210.92.91.223 port 36858
Dec  6 08:34:03 wh01 sshd[12454]: Failed password for invalid user skjersli from 210.92.91.223 port 36858 ssh2
Dec  6 08:34:03 wh01 sshd[12454]: Received disconnect from 210.92.91.223 port 36858:11: Bye Bye [preauth]
Dec  6 08:34:03 wh01 sshd[12454]: Disconnected from 210.92.91.223 port 36858 [preauth]
Dec  6 08:46:09 wh01 sshd[13760]: Invalid user zelisko from 210.92.91.223 port 41624
Dec  6 08:46:09 wh01 sshd[13760]: Failed password for invalid user zelisko from 210.92.91.223 port 41624 ssh2
Dec  6 08:46:10 wh01 sshd[13760]: Received disconnect from 210.92.91.223 port 41624:11: Bye Bye [preauth]
Dec  6 08:46:10 wh01 sshd[13760]: Disconnected from 210.92.91.223 port 41624 [preauth]
Dec  6 09:06:42 wh01 sshd[15734]: Invalid user doudna from 210.92.91.223 port 43016
Dec  6 09:06:42 wh01 sshd[15734]: Failed password for invalid user doudna from 210.92.91.223 port 43016 ssh2
Dec  6 09:06:42 wh01 sshd[157
2019-12-06 22:10:37
125.138.89.140 attackspam
$f2bV_matches
2019-12-06 22:39:59
106.54.48.29 attack
Dec  6 07:15:36 vps666546 sshd\[22227\]: Invalid user clara from 106.54.48.29 port 43208
Dec  6 07:15:36 vps666546 sshd\[22227\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.48.29
Dec  6 07:15:39 vps666546 sshd\[22227\]: Failed password for invalid user clara from 106.54.48.29 port 43208 ssh2
Dec  6 07:22:17 vps666546 sshd\[22522\]: Invalid user stackhouse from 106.54.48.29 port 48774
Dec  6 07:22:17 vps666546 sshd\[22522\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.48.29
...
2019-12-06 22:38:11
221.140.151.235 attack
Dec  6 02:49:14 php1 sshd\[28124\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.140.151.235  user=root
Dec  6 02:49:17 php1 sshd\[28124\]: Failed password for root from 221.140.151.235 port 47368 ssh2
Dec  6 02:55:38 php1 sshd\[28954\]: Invalid user izumi from 221.140.151.235
Dec  6 02:55:38 php1 sshd\[28954\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.140.151.235
Dec  6 02:55:40 php1 sshd\[28954\]: Failed password for invalid user izumi from 221.140.151.235 port 54402 ssh2
2019-12-06 22:45:28
117.92.16.34 attack
Dec  6 07:22:37 grey postfix/smtpd\[5417\]: NOQUEUE: reject: RCPT from unknown\[117.92.16.34\]: 554 5.7.1 Service unavailable\; Client host \[117.92.16.34\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[117.92.16.34\]\; from=\ to=\ proto=ESMTP helo=\
...
2019-12-06 22:19:17
94.177.213.114 attack
Dec  6 15:53:38 server sshd\[3185\]: Invalid user shakeri from 94.177.213.114
Dec  6 15:53:38 server sshd\[3185\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=mail.hypercube.hu 
Dec  6 15:53:41 server sshd\[3185\]: Failed password for invalid user shakeri from 94.177.213.114 port 37575 ssh2
Dec  6 15:59:40 server sshd\[4760\]: Invalid user xh from 94.177.213.114
Dec  6 15:59:40 server sshd\[4760\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=mail.hypercube.hu 
...
2019-12-06 22:30:02
121.166.81.15 attack
Dec  6 04:14:10 plusreed sshd[379]: Invalid user admin from 121.166.81.15
...
2019-12-06 22:43:46
115.159.25.60 attackbotsspam
Dec  6 18:31:58 gw1 sshd[21933]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.159.25.60
Dec  6 18:31:59 gw1 sshd[21933]: Failed password for invalid user content from 115.159.25.60 port 39524 ssh2
...
2019-12-06 22:09:03
192.241.183.220 attackbots
2019-12-06 10:59:42,122 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 192.241.183.220
2019-12-06 11:38:15,953 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 192.241.183.220
2019-12-06 12:12:37,362 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 192.241.183.220
2019-12-06 12:52:42,830 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 192.241.183.220
2019-12-06 13:33:14,649 fail2ban.actions        \[14488\]: NOTICE  \[sshd\] Ban 192.241.183.220
...
2019-12-06 22:29:15
167.99.226.184 attack
WordPress wp-login brute force :: 167.99.226.184 0.128 - [06/Dec/2019:12:31:02  0000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 1805 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" "HTTP/1.1"
2019-12-06 22:17:29

Recently Reported IPs

141.78.7.198 141.76.39.140 141.8.192.100 141.79.10.40
141.8.192.13 141.8.192.136 141.8.192.147 141.8.192.169
141.8.192.162 141.8.192.163 141.8.192.159 141.8.192.166
141.8.192.193 141.8.192.213 141.8.192.214 141.8.192.215
141.8.192.238 141.8.192.236 141.8.192.227 141.8.192.26