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: United States

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
142.93.214.20 attackbotsspam
Unauthorized connection attempt detected from IP address 142.93.214.20 to port 2220 [J]
2020-02-03 05:47:36
142.93.214.20 attack
Unauthorized connection attempt detected from IP address 142.93.214.20 to port 2220 [J]
2020-02-02 14:14:06
142.93.214.20 attackspambots
SSH Brute-Force attacks
2020-01-11 23:01:06
142.93.214.20 attackspambots
2019-12-24T19:42:47.691176shield sshd\[17651\]: Invalid user manjul from 142.93.214.20 port 41604
2019-12-24T19:42:47.695731shield sshd\[17651\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.214.20
2019-12-24T19:42:49.483794shield sshd\[17651\]: Failed password for invalid user manjul from 142.93.214.20 port 41604 ssh2
2019-12-24T19:45:30.306333shield sshd\[18230\]: Invalid user 123456 from 142.93.214.20 port 36402
2019-12-24T19:45:30.311080shield sshd\[18230\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.214.20
2019-12-25 06:50:31
142.93.214.20 attackspambots
Brute-force attempt banned
2019-12-21 17:28:08
142.93.214.20 attackspam
SSH brute-force: detected 10 distinct usernames within a 24-hour window.
2019-12-21 05:15:01
142.93.214.20 attack
Dec 19 17:35:42 sd-53420 sshd\[18450\]: User root from 142.93.214.20 not allowed because none of user's groups are listed in AllowGroups
Dec 19 17:35:42 sd-53420 sshd\[18450\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.214.20  user=root
Dec 19 17:35:44 sd-53420 sshd\[18450\]: Failed password for invalid user root from 142.93.214.20 port 36492 ssh2
Dec 19 17:41:48 sd-53420 sshd\[20750\]: User root from 142.93.214.20 not allowed because none of user's groups are listed in AllowGroups
Dec 19 17:41:48 sd-53420 sshd\[20750\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.214.20  user=root
...
2019-12-20 03:54:45
142.93.214.20 attackspam
SSH Bruteforce attempt
2019-12-16 14:10:34
142.93.214.20 attackspam
Dec 10 22:36:35 server sshd\[31964\]: Invalid user guest from 142.93.214.20
Dec 10 22:36:35 server sshd\[31964\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.214.20 
Dec 10 22:36:37 server sshd\[31964\]: Failed password for invalid user guest from 142.93.214.20 port 57346 ssh2
Dec 10 22:43:41 server sshd\[1288\]: Invalid user tanja from 142.93.214.20
Dec 10 22:43:41 server sshd\[1288\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.214.20 
...
2019-12-11 07:16:23
142.93.214.20 attackbotsspam
Dec  6 10:07:04 root sshd[13156]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.214.20 
Dec  6 10:07:06 root sshd[13156]: Failed password for invalid user test from 142.93.214.20 port 43690 ssh2
Dec  6 10:13:25 root sshd[13340]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.214.20 
...
2019-12-06 17:17:54
142.93.214.20 attack
Invalid user hilliary from 142.93.214.20 port 41734
2019-11-26 16:49:53
142.93.214.20 attackspambots
Brute-force attempt banned
2019-11-19 03:35:00
142.93.214.20 attackspam
Invalid user guest from 142.93.214.20 port 45864
2019-11-11 22:14:33
142.93.214.20 attackspam
Nov 10 09:35:09 web9 sshd\[14364\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.214.20  user=root
Nov 10 09:35:12 web9 sshd\[14364\]: Failed password for root from 142.93.214.20 port 52310 ssh2
Nov 10 09:41:58 web9 sshd\[15476\]: Invalid user  from 142.93.214.20
Nov 10 09:41:58 web9 sshd\[15476\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.214.20
Nov 10 09:42:00 web9 sshd\[15476\]: Failed password for invalid user  from 142.93.214.20 port 33376 ssh2
2019-11-11 03:52:19
142.93.214.20 attackspambots
Nov  8 07:22:30 minden010 sshd[10581]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.214.20
Nov  8 07:22:32 minden010 sshd[10581]: Failed password for invalid user All from 142.93.214.20 port 45216 ssh2
Nov  8 07:26:46 minden010 sshd[11427]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.214.20
...
2019-11-08 17:57:21
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 142.93.214.108
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 47099
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;142.93.214.108.			IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 12:23:50 CST 2022
;; MSG SIZE  rcvd: 107
Host info
108.214.93.142.in-addr.arpa domain name pointer 416242.cloudwaysapps.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
108.214.93.142.in-addr.arpa	name = 416242.cloudwaysapps.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
112.85.42.227 attackspambots
Jan  7 17:08:32 TORMINT sshd\[789\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.227  user=root
Jan  7 17:08:34 TORMINT sshd\[789\]: Failed password for root from 112.85.42.227 port 13685 ssh2
Jan  7 17:09:34 TORMINT sshd\[852\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.227  user=root
...
2020-01-08 06:26:08
212.92.105.237 attack
RDP Bruteforce
2020-01-08 06:28:27
222.186.173.142 attackbotsspam
Jan  7 22:16:42 hcbbdb sshd\[8555\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.142  user=root
Jan  7 22:16:45 hcbbdb sshd\[8555\]: Failed password for root from 222.186.173.142 port 64350 ssh2
Jan  7 22:17:07 hcbbdb sshd\[8599\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.142  user=root
Jan  7 22:17:09 hcbbdb sshd\[8599\]: Failed password for root from 222.186.173.142 port 45080 ssh2
Jan  7 22:17:12 hcbbdb sshd\[8599\]: Failed password for root from 222.186.173.142 port 45080 ssh2
2020-01-08 06:25:12
62.150.134.233 attack
Jan  7 18:32:30 vps46666688 sshd[10863]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.150.134.233
Jan  7 18:32:33 vps46666688 sshd[10863]: Failed password for invalid user web from 62.150.134.233 port 37416 ssh2
...
2020-01-08 06:15:23
49.88.112.66 attackbots
Jan  7 18:20:12 firewall sshd[13781]: Failed password for root from 49.88.112.66 port 23034 ssh2
Jan  7 18:20:15 firewall sshd[13781]: Failed password for root from 49.88.112.66 port 23034 ssh2
Jan  7 18:20:17 firewall sshd[13781]: Failed password for root from 49.88.112.66 port 23034 ssh2
...
2020-01-08 05:53:49
159.65.4.64 attackbotsspam
Unauthorized connection attempt detected from IP address 159.65.4.64 to port 2220 [J]
2020-01-08 06:06:12
176.38.149.77 attackbotsspam
Jan  7 22:47:56 XXX sshd[7934]: Invalid user RPM from 176.38.149.77 port 56029
2020-01-08 06:12:06
157.245.4.75 attack
Unauthorized connection attempt detected from IP address 157.245.4.75 to port 7999 [J]
2020-01-08 05:55:13
222.186.190.2 attack
Jan  7 23:21:27 MK-Soft-Root2 sshd[24159]: Failed password for root from 222.186.190.2 port 38590 ssh2
Jan  7 23:21:31 MK-Soft-Root2 sshd[24159]: Failed password for root from 222.186.190.2 port 38590 ssh2
...
2020-01-08 06:29:38
116.62.78.254 attackbots
FTP Brute-Force reported by Fail2Ban
2020-01-08 06:25:27
1.20.210.209 attackbots
01/07/2020-22:20:01.559461 1.20.210.209 Protocol: 6 ET POLICY Cleartext WordPress Login
2020-01-08 06:06:54
118.24.30.97 attackbots
Unauthorized connection attempt detected from IP address 118.24.30.97 to port 2220 [J]
2020-01-08 06:12:22
203.147.0.10 attackbots
Jan  7 22:19:44 debian-2gb-nbg1-2 kernel: \[691301.456825\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=203.147.0.10 DST=195.201.40.59 LEN=40 TOS=0x08 PREC=0x20 TTL=238 ID=39623 PROTO=TCP SPT=43561 DPT=1433 WINDOW=1024 RES=0x00 SYN URGP=0 
Jan  7 22:19:44 debian-2gb-nbg1-2 kernel: \[691301.471963\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=203.147.0.10 DST=195.201.40.59 LEN=40 TOS=0x08 PREC=0x20 TTL=238 ID=39623 PROTO=TCP SPT=43561 DPT=1433 WINDOW=1024 RES=0x00 SYN URGP=0
2020-01-08 06:16:59
92.169.103.184 attack
Jan  7 23:12:16 ns381471 sshd[13602]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.169.103.184
Jan  7 23:12:18 ns381471 sshd[13602]: Failed password for invalid user zwt from 92.169.103.184 port 58036 ssh2
2020-01-08 06:13:56
218.92.0.165 attackbotsspam
Jan  7 22:56:01 amit sshd\[15959\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.165  user=root
Jan  7 22:56:03 amit sshd\[15959\]: Failed password for root from 218.92.0.165 port 12403 ssh2
Jan  7 22:56:07 amit sshd\[15959\]: Failed password for root from 218.92.0.165 port 12403 ssh2
...
2020-01-08 06:05:20

Recently Reported IPs

142.93.213.69 142.93.214.190 142.93.214.224 142.93.216.10
142.93.216.117 142.93.217.20 142.93.216.168 142.93.218.214
142.93.218.1 142.93.217.89 142.93.218.240 142.93.218.49
208.92.128.233 142.93.219.110 142.93.219.162 142.93.218.64
142.93.220.100 142.93.222.127 142.93.222.143 142.93.222.223