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

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

;; QUESTION SECTION:
;195.93.212.135.			IN	A

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

;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 04:23:18 CST 2025
;; MSG SIZE  rcvd: 107
Host info
135.212.93.195.in-addr.arpa domain name pointer setka.od.ua.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
135.212.93.195.in-addr.arpa	name = setka.od.ua.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
203.195.152.247 attackspam
2019-09-28T14:10:56.142823abusebot-2.cloudsearch.cf sshd\[2470\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.195.152.247  user=shutdown
2019-09-28 22:32:41
43.241.73.90 attack
xmlrpc attack
2019-09-28 22:36:48
52.165.80.73 attack
Unauthorized SSH login attempts
2019-09-28 22:16:09
92.119.160.141 attackbots
Port scan on 3 port(s): 6548 23333 51011
2019-09-28 22:11:29
64.76.6.126 attack
Sep 28 14:25:41 game-panel sshd[29672]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.76.6.126
Sep 28 14:25:43 game-panel sshd[29672]: Failed password for invalid user toor from 64.76.6.126 port 38301 ssh2
Sep 28 14:33:27 game-panel sshd[29909]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.76.6.126
2019-09-28 22:38:37
217.243.172.58 attackspam
Sep 28 13:44:08 hcbbdb sshd\[9896\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.243.172.58  user=root
Sep 28 13:44:10 hcbbdb sshd\[9896\]: Failed password for root from 217.243.172.58 port 41092 ssh2
Sep 28 13:48:05 hcbbdb sshd\[10304\]: Invalid user tomcat from 217.243.172.58
Sep 28 13:48:05 hcbbdb sshd\[10304\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.243.172.58
Sep 28 13:48:08 hcbbdb sshd\[10304\]: Failed password for invalid user tomcat from 217.243.172.58 port 52568 ssh2
2019-09-28 22:13:18
201.140.111.58 attackspam
Triggered by Fail2Ban at Vostok web server
2019-09-28 22:40:48
130.61.72.90 attack
Sep 28 16:58:15 pkdns2 sshd\[42703\]: Invalid user cnc from 130.61.72.90Sep 28 16:58:18 pkdns2 sshd\[42703\]: Failed password for invalid user cnc from 130.61.72.90 port 35382 ssh2Sep 28 17:02:14 pkdns2 sshd\[42900\]: Invalid user tir from 130.61.72.90Sep 28 17:02:16 pkdns2 sshd\[42900\]: Failed password for invalid user tir from 130.61.72.90 port 47870 ssh2Sep 28 17:06:08 pkdns2 sshd\[43135\]: Invalid user hidden from 130.61.72.90Sep 28 17:06:10 pkdns2 sshd\[43135\]: Failed password for invalid user hidden from 130.61.72.90 port 60358 ssh2
...
2019-09-28 22:42:00
182.61.162.54 attackspambots
Sep 28 04:27:22 hcbb sshd\[15147\]: Invalid user uw from 182.61.162.54
Sep 28 04:27:22 hcbb sshd\[15147\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.162.54
Sep 28 04:27:24 hcbb sshd\[15147\]: Failed password for invalid user uw from 182.61.162.54 port 46376 ssh2
Sep 28 04:32:28 hcbb sshd\[15568\]: Invalid user service from 182.61.162.54
Sep 28 04:32:28 hcbb sshd\[15568\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.162.54
2019-09-28 22:43:43
192.228.100.220 attackspam
'IP reached maximum auth failures for a one day block'
2019-09-28 22:22:16
222.186.42.163 attack
2019-09-28T15:38:47.912863+01:00 suse sshd[30785]: User root from 222.186.42.163 not allowed because not listed in AllowUsers
2019-09-28T15:38:51.660823+01:00 suse sshd[30785]: error: PAM: Authentication failure for illegal user root from 222.186.42.163
2019-09-28T15:38:47.912863+01:00 suse sshd[30785]: User root from 222.186.42.163 not allowed because not listed in AllowUsers
2019-09-28T15:38:51.660823+01:00 suse sshd[30785]: error: PAM: Authentication failure for illegal user root from 222.186.42.163
2019-09-28T15:38:47.912863+01:00 suse sshd[30785]: User root from 222.186.42.163 not allowed because not listed in AllowUsers
2019-09-28T15:38:51.660823+01:00 suse sshd[30785]: error: PAM: Authentication failure for illegal user root from 222.186.42.163
2019-09-28T15:38:51.683447+01:00 suse sshd[30785]: Failed keyboard-interactive/pam for invalid user root from 222.186.42.163 port 55956 ssh2
...
2019-09-28 22:42:47
222.186.42.15 attack
SSH Brute Force, server-1 sshd[23013]: Failed password for root from 222.186.42.15 port 24098 ssh2
2019-09-28 22:15:36
123.21.218.189 attack
Sep 28 14:33:09 [munged] sshd[19965]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.21.218.189
2019-09-28 22:49:57
222.186.15.217 attackbots
Sep 28 16:15:13 jane sshd[22297]: Failed password for root from 222.186.15.217 port 40749 ssh2
Sep 28 16:15:16 jane sshd[22297]: Failed password for root from 222.186.15.217 port 40749 ssh2
...
2019-09-28 22:19:14
62.141.44.95 attackbots
Automatic report - SSH Brute-Force Attack
2019-09-28 22:18:10

Recently Reported IPs

63.181.180.233 159.45.111.222 17.104.184.218 148.141.191.31
4.210.42.75 147.169.40.73 51.81.122.249 254.217.16.83
79.2.161.203 38.188.106.80 192.98.153.9 191.184.24.250
145.235.165.253 218.201.177.92 204.129.134.217 141.59.194.49
195.121.100.147 14.60.254.61 250.39.33.138 242.208.26.121