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

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
138.68.168.137 attackspambots
2020-03-24T18:24:04.338629shield sshd\[1720\]: Invalid user testuser from 138.68.168.137 port 41348
2020-03-24T18:24:04.342343shield sshd\[1720\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137
2020-03-24T18:24:06.326852shield sshd\[1720\]: Failed password for invalid user testuser from 138.68.168.137 port 41348 ssh2
2020-03-24T18:31:58.513381shield sshd\[3346\]: Invalid user jeanie from 138.68.168.137 port 59402
2020-03-24T18:31:58.516640shield sshd\[3346\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137
2020-03-25 02:52:35
138.68.168.137 attackspambots
2020-03-24T18:07:52.907199shield sshd\[30137\]: Invalid user gy from 138.68.168.137 port 33476
2020-03-24T18:07:52.913682shield sshd\[30137\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137
2020-03-24T18:07:55.128671shield sshd\[30137\]: Failed password for invalid user gy from 138.68.168.137 port 33476 ssh2
2020-03-24T18:11:50.402980shield sshd\[31146\]: Invalid user office from 138.68.168.137 port 42502
2020-03-24T18:11:50.410060shield sshd\[31146\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137
2020-03-25 02:18:32
138.68.168.137 attackbotsspam
2020-03-23T15:38:43.121143abusebot-7.cloudsearch.cf sshd[19459]: Invalid user newsletter from 138.68.168.137 port 35472
2020-03-23T15:38:43.126340abusebot-7.cloudsearch.cf sshd[19459]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137
2020-03-23T15:38:43.121143abusebot-7.cloudsearch.cf sshd[19459]: Invalid user newsletter from 138.68.168.137 port 35472
2020-03-23T15:38:44.916504abusebot-7.cloudsearch.cf sshd[19459]: Failed password for invalid user newsletter from 138.68.168.137 port 35472 ssh2
2020-03-23T15:47:18.433090abusebot-7.cloudsearch.cf sshd[20039]: Invalid user vix from 138.68.168.137 port 51306
2020-03-23T15:47:18.438580abusebot-7.cloudsearch.cf sshd[20039]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137
2020-03-23T15:47:18.433090abusebot-7.cloudsearch.cf sshd[20039]: Invalid user vix from 138.68.168.137 port 51306
2020-03-23T15:47:20.595192abusebot-7.cloudsearch.cf s
...
2020-03-24 02:02:33
138.68.168.137 attack
Mar 12 16:58:35 lanister sshd[28250]: Failed password for invalid user paul from 138.68.168.137 port 37160 ssh2
Mar 12 17:11:50 lanister sshd[28520]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137  user=root
Mar 12 17:11:53 lanister sshd[28520]: Failed password for root from 138.68.168.137 port 39500 ssh2
Mar 12 17:16:49 lanister sshd[28595]: Invalid user jira from 138.68.168.137
2020-03-13 05:41:53
138.68.168.137 attackbots
Mar  4 17:26:34 hcbbdb sshd\[8947\]: Invalid user plegrand from 138.68.168.137
Mar  4 17:26:34 hcbbdb sshd\[8947\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137
Mar  4 17:26:37 hcbbdb sshd\[8947\]: Failed password for invalid user plegrand from 138.68.168.137 port 53114 ssh2
Mar  4 17:35:44 hcbbdb sshd\[9933\]: Invalid user sshvpn from 138.68.168.137
Mar  4 17:35:44 hcbbdb sshd\[9933\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137
2020-03-05 01:43:06
138.68.168.137 attackspam
Feb 28 23:37:06 ns381471 sshd[5202]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137
Feb 28 23:37:08 ns381471 sshd[5202]: Failed password for invalid user php from 138.68.168.137 port 39826 ssh2
2020-02-29 06:46:39
138.68.168.137 attack
Feb 27 19:10:22 web1 sshd\[15937\]: Invalid user deployer from 138.68.168.137
Feb 27 19:10:22 web1 sshd\[15937\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137
Feb 27 19:10:24 web1 sshd\[15937\]: Failed password for invalid user deployer from 138.68.168.137 port 38600 ssh2
Feb 27 19:17:16 web1 sshd\[16908\]: Invalid user wangxue from 138.68.168.137
Feb 27 19:17:16 web1 sshd\[16908\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137
2020-02-28 13:29:17
138.68.168.137 attackspambots
Feb 11 14:48:11 nextcloud sshd\[20955\]: Invalid user sqn from 138.68.168.137
Feb 11 14:48:11 nextcloud sshd\[20955\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137
Feb 11 14:48:13 nextcloud sshd\[20955\]: Failed password for invalid user sqn from 138.68.168.137 port 37670 ssh2
2020-02-11 22:39:50
138.68.168.137 attack
Invalid user vidushi from 138.68.168.137 port 50096
2020-02-02 15:32:13
138.68.168.137 attackspam
Dec 19 03:24:30 dallas01 sshd[28204]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137
Dec 19 03:24:32 dallas01 sshd[28204]: Failed password for invalid user guenter from 138.68.168.137 port 60208 ssh2
Dec 19 03:29:37 dallas01 sshd[31708]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137
2020-01-28 04:14:22
138.68.168.137 attackspam
Jan 24 05:52:15 vps691689 sshd[23745]: Failed password for root from 138.68.168.137 port 55866 ssh2
Jan 24 05:55:04 vps691689 sshd[23888]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137
...
2020-01-24 13:08:12
138.68.168.137 attack
Dec 27 21:42:07 cavern sshd[31147]: Failed password for root from 138.68.168.137 port 50310 ssh2
2019-12-28 05:11:14
138.68.168.137 attackbots
Dec 22 20:00:47 server sshd\[5095\]: Invalid user traub from 138.68.168.137
Dec 22 20:00:47 server sshd\[5095\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137 
Dec 22 20:00:49 server sshd\[5095\]: Failed password for invalid user traub from 138.68.168.137 port 44168 ssh2
Dec 22 20:06:59 server sshd\[6636\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.168.137  user=ftp
Dec 22 20:07:01 server sshd\[6636\]: Failed password for ftp from 138.68.168.137 port 36478 ssh2
...
2019-12-23 01:07:16
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 138.68.168.85
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 5062
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;138.68.168.85.			IN	A

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

;; Query time: 125 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 07:51:55 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 85.168.68.138.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 85.168.68.138.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
111.53.162.198 attack
Unauthorized connection attempt detected from IP address 111.53.162.198 to port 23
2020-05-13 00:10:30
85.185.222.73 attackspambots
Unauthorized connection attempt detected from IP address 85.185.222.73 to port 8080
2020-05-13 00:15:05
190.107.235.143 attack
Unauthorized connection attempt detected from IP address 190.107.235.143 to port 23
2020-05-13 00:35:53
199.114.229.35 attackbots
Unauthorized connection attempt detected from IP address 199.114.229.35 to port 23
2020-05-13 00:33:47
49.143.32.6 attack
Unauthorized connection attempt detected from IP address 49.143.32.6 to port 80
2020-05-13 00:26:14
43.230.144.66 attackspambots
Unauthorized connection attempt detected from IP address 43.230.144.66 to port 1433
2020-05-13 01:06:59
37.49.227.109 attackbots
" "
2020-05-13 01:08:10
201.229.41.49 attackbots
Unauthorized connection attempt detected from IP address 201.229.41.49 to port 88
2020-05-13 00:31:01
97.100.28.67 attackspam
Unauthorized connection attempt detected from IP address 97.100.28.67 to port 4567
2020-05-13 00:51:36
82.48.6.152 attackspam
Unauthorized connection attempt detected from IP address 82.48.6.152 to port 83
2020-05-13 00:15:33
45.164.234.6 attackspambots
port scan and connect, tcp 23 (telnet)
2020-05-13 01:05:56
95.132.252.172 attack
Unauthorized connection attempt detected from IP address 95.132.252.172 to port 23
2020-05-13 00:52:12
81.215.212.192 attackbots
Port probing on unauthorized port 23
2020-05-13 00:57:04
189.135.184.145 attackbotsspam
Unauthorized connection attempt detected from IP address 189.135.184.145 to port 23
2020-05-13 01:17:51
2.183.108.242 attackbotsspam
Unauthorized connection attempt detected from IP address 2.183.108.242 to port 80
2020-05-13 01:11:28

Recently Reported IPs

138.68.168.136 138.68.168.60 138.68.168.64 118.179.45.61
138.68.169.112 138.68.169.200 138.68.169.53 138.68.169.18
138.68.169.118 138.68.169.192 138.68.169.232 138.68.169.8
138.68.169.59 138.68.169.77 138.68.17.193 118.179.46.19
138.68.170.11 138.68.17.248 138.68.170.117 138.68.170.200