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 of America (the)

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

;; QUESTION SECTION:
;199.93.138.68.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 04 01:27:46 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 68.138.93.199.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 68.138.93.199.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
177.27.194.26 attack
Unauthorised access (Nov  4) SRC=177.27.194.26 LEN=44 TOS=0x10 PREC=0x40 TTL=50 ID=14185 TCP DPT=23 WINDOW=15138 SYN
2019-11-04 20:07:46
82.160.53.155 attack
Automatic report - Port Scan Attack
2019-11-04 19:36:13
188.165.200.46 attackbots
Automatic report - Banned IP Access
2019-11-04 19:54:21
62.234.96.175 attack
2019-11-04T06:58:24.654781abusebot-6.cloudsearch.cf sshd\[16874\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.96.175  user=root
2019-11-04 19:43:09
103.17.108.37 attack
xmlrpc attack
2019-11-04 19:47:37
185.86.164.101 attackspam
Wordpress attack
2019-11-04 19:42:50
185.64.52.42 attackbots
TCP Port Scanning
2019-11-04 19:42:05
77.42.85.157 attackbots
Portscan detected
2019-11-04 20:12:21
200.225.230.149 attackspambots
Port 1433 Scan
2019-11-04 20:05:25
66.249.64.212 attackspambots
Automatic report - Banned IP Access
2019-11-04 20:01:03
111.231.239.143 attackspam
Nov  4 13:15:45 server sshd\[26410\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.239.143  user=root
Nov  4 13:15:47 server sshd\[26410\]: Failed password for root from 111.231.239.143 port 53436 ssh2
Nov  4 13:29:39 server sshd\[29488\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.239.143  user=root
Nov  4 13:29:41 server sshd\[29488\]: Failed password for root from 111.231.239.143 port 50998 ssh2
Nov  4 13:34:27 server sshd\[30732\]: Invalid user idckj from 111.231.239.143
Nov  4 13:34:27 server sshd\[30732\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.239.143 
...
2019-11-04 19:52:44
175.140.23.248 attack
Invalid user cola from 175.140.23.248 port 21691
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.140.23.248
Failed password for invalid user cola from 175.140.23.248 port 21691 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.140.23.248  user=root
Failed password for root from 175.140.23.248 port 47910 ssh2
2019-11-04 19:57:43
195.123.242.188 attack
11/04/2019-07:23:31.076170 195.123.242.188 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-11-04 19:55:57
131.213.199.29 attackbotsspam
Open Proxy "ZEUS" node. GET "/wp-admin/admin-ajax.php", and get any others "ajax.php".
2019-11-04 20:11:11
101.78.151.178 attackbots
Automatic report - Banned IP Access
2019-11-04 19:56:41

Recently Reported IPs

68.225.8.240 175.114.68.60 50.52.207.133 101.114.92.66
154.230.48.140 80.14.135.12 87.187.103.8 3.5.130.184
99.243.67.235 59.196.68.131 129.150.15.180 5.180.187.106
235.119.146.99 80.190.97.180 97.180.0.12 35.152.129.218
60.14.204.30 20.15.102.114 14.16.109.155 234.24.17.109