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

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
194.50.142.254 attackproxy
Fraud connect
2024-07-09 12:52:34
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 194.50.14.96
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52287
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;194.50.14.96.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 14 08:00:28 CST 2022
;; MSG SIZE  rcvd: 105
Host info
96.14.50.194.in-addr.arpa domain name pointer cgn-pool-194-50-14-96.tis-dialog.ru.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
96.14.50.194.in-addr.arpa	name = cgn-pool-194-50-14-96.tis-dialog.ru.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
2001:41d0:800:1548::9696 attackspam
MYH,DEF GET /wp-login.php
2019-08-11 13:43:03
144.138.102.124 attackspam
Aug 11 02:16:08 www sshd\[151108\]: Invalid user ubuntu from 144.138.102.124
Aug 11 02:16:08 www sshd\[151108\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.138.102.124
Aug 11 02:16:10 www sshd\[151108\]: Failed password for invalid user ubuntu from 144.138.102.124 port 51698 ssh2
...
2019-08-11 13:44:51
80.211.116.102 attack
Aug 11 07:26:19 vps647732 sshd[21834]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.116.102
Aug 11 07:26:21 vps647732 sshd[21834]: Failed password for invalid user wm from 80.211.116.102 port 59121 ssh2
...
2019-08-11 13:41:20
60.162.47.13 attackbots
Aug 11 01:04:41 django sshd[94707]: reveeclipse mapping checking getaddrinfo for 13.47.162.60.broad.tz.zj.dynamic.163data.com.cn [60.162.47.13] failed - POSSIBLE BREAK-IN ATTEMPT!
Aug 11 01:04:42 django sshd[94707]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=60.162.47.13  user=r.r
Aug 11 01:04:44 django sshd[94707]: Failed password for r.r from 60.162.47.13 port 41644 ssh2
Aug 11 01:04:47 django sshd[94707]: Failed password for r.r from 60.162.47.13 port 41644 ssh2
Aug 11 01:04:49 django sshd[94707]: Failed password for r.r from 60.162.47.13 port 41644 ssh2
Aug 11 01:04:51 django sshd[94707]: Failed password for r.r from 60.162.47.13 port 41644 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=60.162.47.13
2019-08-11 13:09:41
107.170.48.143 attackspam
C2,WP GET /wp-login.php
2019-08-11 13:11:10
185.56.81.7 attackbots
08/11/2019-00:41:38.412612 185.56.81.7 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-08-11 13:03:53
116.31.116.2 attackbots
Aug 10 23:00:25 aragorn sshd[28969]: Invalid user j from 116.31.116.2
Aug 10 23:00:26 aragorn sshd[29008]: Invalid user j from 116.31.116.2
Aug 10 23:00:26 aragorn sshd[29010]: Invalid user j from 116.31.116.2
Aug 10 23:00:27 aragorn sshd[29011]: Invalid user sybase from 116.31.116.2
...
2019-08-11 13:45:28
141.98.81.38 attackspambots
08/10/2019-20:44:38.430536 141.98.81.38 Protocol: 6 ET COMPROMISED Known Compromised or Hostile Host Traffic group 5
2019-08-11 13:28:08
82.109.61.235 attack
SSH bruteforce (Triggered fail2ban)
2019-08-11 13:57:37
220.120.109.166 attackspambots
Jan 18 07:27:46 motanud sshd\[10711\]: Invalid user olivia from 220.120.109.166 port 58736
Jan 18 07:27:46 motanud sshd\[10711\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.120.109.166
Jan 18 07:27:49 motanud sshd\[10711\]: Failed password for invalid user olivia from 220.120.109.166 port 58736 ssh2
2019-08-11 13:24:08
159.89.111.136 attack
Aug 11 07:52:58 localhost sshd\[8012\]: Invalid user nn from 159.89.111.136 port 54886
Aug 11 07:52:58 localhost sshd\[8012\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.111.136
Aug 11 07:53:01 localhost sshd\[8012\]: Failed password for invalid user nn from 159.89.111.136 port 54886 ssh2
2019-08-11 13:54:40
148.70.103.187 attackbotsspam
Automatic report
2019-08-11 13:08:25
162.243.142.193 attack
2019-08-11T01:56:53.620402abusebot-5.cloudsearch.cf sshd\[22674\]: Invalid user midha from 162.243.142.193 port 37950
2019-08-11 13:10:09
177.67.105.7 attack
Aug 11 02:58:09 cp sshd[14383]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.67.105.7
2019-08-11 13:17:51
120.52.152.17 attack
11.08.2019 03:01:46 Connection to port 636 blocked by firewall
2019-08-11 13:37:46

Recently Reported IPs

194.50.13.31 194.44.86.42 194.50.15.88 194.50.15.183
194.50.14.70 194.58.175.209 194.56.189.38 194.58.182.207
194.59.170.45 194.59.164.99 194.59.164.90 194.60.254.35
194.61.88.138 194.65.71.166 194.85.134.190 194.8.47.120
194.87.52.194 194.87.238.159 194.87.52.238 194.99.104.183