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.128.185 attackbotsspam
Automatic report generated by Wazuh
2020-09-19 20:38:31
138.68.128.185 attack
138.68.128.185 - - [19/Sep/2020:04:55:55 +0100] "POST /wp-login.php HTTP/1.1" 200 2265 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
138.68.128.185 - - [19/Sep/2020:04:56:06 +0100] "POST /wp-login.php HTTP/1.1" 200 2183 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
138.68.128.185 - - [19/Sep/2020:04:56:11 +0100] "POST /xmlrpc.php HTTP/1.1" 403 219 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-09-19 12:35:07
138.68.128.185 attack
SSH 2020-09-19 00:41:12	138.68.128.185	139.99.53.101	>	GET	www.materialhandling.web.id	/wp-login.php	HTTP/1.1	-	-
2020-09-19 00:41:18	138.68.128.185	139.99.53.101	>	POST	www.materialhandling.web.id	/wp-login.php	HTTP/1.1	-	-
2020-09-19 02:33:05	138.68.128.185	139.99.53.101	>	POST	karsagroup.co.id	/wp-login.php	HTTP/1.1	-	-
2020-09-19 04:12:14
138.68.128.164 attackbots
Wordpress malicious attack:[octablocked]
2020-04-20 12:18:59
138.68.128.80 attackspambots
2019-09-23T17:02:39.893960abusebot-7.cloudsearch.cf sshd\[31323\]: Invalid user 123456 from 138.68.128.80 port 49924
2019-09-24 01:03:07
138.68.128.80 attack
Sep 22 04:52:22 hpm sshd\[2647\]: Invalid user nt from 138.68.128.80
Sep 22 04:52:22 hpm sshd\[2647\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.128.80
Sep 22 04:52:24 hpm sshd\[2647\]: Failed password for invalid user nt from 138.68.128.80 port 48258 ssh2
Sep 22 04:56:33 hpm sshd\[2975\]: Invalid user test from 138.68.128.80
Sep 22 04:56:33 hpm sshd\[2975\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.128.80
2019-09-23 01:03:56
138.68.128.80 attack
Sep 17 13:52:08 webhost01 sshd[22153]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.128.80
Sep 17 13:52:10 webhost01 sshd[22153]: Failed password for invalid user anon from 138.68.128.80 port 52078 ssh2
...
2019-09-17 15:08:48
138.68.128.80 attack
Sep 12 23:13:03 eventyay sshd[14993]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.128.80
Sep 12 23:13:05 eventyay sshd[14993]: Failed password for invalid user 123321 from 138.68.128.80 port 56800 ssh2
Sep 12 23:18:30 eventyay sshd[15139]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.128.80
...
2019-09-13 05:22:46
138.68.128.80 attack
" "
2019-09-04 01:56:50
138.68.128.80 attackbots
Aug 31 15:16:59 plex sshd[16973]: Invalid user dattesh from 138.68.128.80 port 34686
2019-08-31 21:20:11
138.68.128.80 attackbots
Aug 31 13:40:58 plex sshd[14114]: Invalid user ankesh from 138.68.128.80 port 58948
2019-08-31 19:41:08
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 138.68.128.113
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 18908
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;138.68.128.113.			IN	A

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

;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 07:51:10 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 113.128.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 113.128.68.138.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
189.69.87.214 attackbotsspam
IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/189.69.87.214/ 
 BR - 1H : (263)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : BR 
 NAME ASN : ASN27699 
 
 IP : 189.69.87.214 
 
 CIDR : 189.69.0.0/16 
 
 PREFIX COUNT : 267 
 
 UNIQUE IP COUNT : 6569728 
 
 
 WYKRYTE ATAKI Z ASN27699 :  
  1H - 4 
  3H - 15 
  6H - 26 
 12H - 60 
 24H - 112 
 
 DateTime : 2019-10-09 21:45:51 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-10-10 04:54:45
159.192.144.203 attack
Oct  9 23:13:51 vps01 sshd[5646]: Failed password for root from 159.192.144.203 port 58034 ssh2
2019-10-10 05:21:58
117.62.57.53 attackspam
Oct  9 15:40:43 esmtp postfix/smtpd[25021]: lost connection after AUTH from unknown[117.62.57.53]
Oct  9 15:40:44 esmtp postfix/smtpd[24997]: lost connection after AUTH from unknown[117.62.57.53]
Oct  9 15:40:46 esmtp postfix/smtpd[25021]: lost connection after AUTH from unknown[117.62.57.53]
Oct  9 15:40:47 esmtp postfix/smtpd[24997]: lost connection after AUTH from unknown[117.62.57.53]
Oct  9 15:40:49 esmtp postfix/smtpd[25014]: lost connection after AUTH from unknown[117.62.57.53]

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=117.62.57.53
2019-10-10 04:53:05
185.36.81.248 attackspambots
Oct  9 18:37:59 heicom postfix/smtpd\[25737\]: warning: unknown\[185.36.81.248\]: SASL LOGIN authentication failed: authentication failure
Oct  9 19:03:11 heicom postfix/smtpd\[26022\]: warning: unknown\[185.36.81.248\]: SASL LOGIN authentication failed: authentication failure
Oct  9 19:28:30 heicom postfix/smtpd\[27002\]: warning: unknown\[185.36.81.248\]: SASL LOGIN authentication failed: authentication failure
Oct  9 19:53:31 heicom postfix/smtpd\[27002\]: warning: unknown\[185.36.81.248\]: SASL LOGIN authentication failed: authentication failure
Oct  9 20:18:51 heicom postfix/smtpd\[27208\]: warning: unknown\[185.36.81.248\]: SASL LOGIN authentication failed: authentication failure
...
2019-10-10 04:59:22
104.244.72.221 attackspambots
2019-10-09T20:31:14.701937abusebot.cloudsearch.cf sshd\[28969\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.244.72.221  user=root
2019-10-10 04:56:55
49.72.20.46 attackbotsspam
Oct  9 15:25:58 esmtp postfix/smtpd[24816]: lost connection after AUTH from unknown[49.72.20.46]
Oct  9 15:26:00 esmtp postfix/smtpd[24798]: lost connection after AUTH from unknown[49.72.20.46]
Oct  9 15:26:01 esmtp postfix/smtpd[24798]: lost connection after AUTH from unknown[49.72.20.46]
Oct  9 15:26:02 esmtp postfix/smtpd[24798]: lost connection after AUTH from unknown[49.72.20.46]
Oct  9 15:26:04 esmtp postfix/smtpd[24798]: lost connection after AUTH from unknown[49.72.20.46]

........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=49.72.20.46
2019-10-10 05:01:29
186.10.17.84 attack
Oct  9 23:28:35 pkdns2 sshd\[54866\]: Invalid user Qwerty1@3 from 186.10.17.84Oct  9 23:28:37 pkdns2 sshd\[54866\]: Failed password for invalid user Qwerty1@3 from 186.10.17.84 port 49692 ssh2Oct  9 23:32:50 pkdns2 sshd\[55075\]: Invalid user 6tfc5rdx from 186.10.17.84Oct  9 23:32:53 pkdns2 sshd\[55075\]: Failed password for invalid user 6tfc5rdx from 186.10.17.84 port 60506 ssh2Oct  9 23:37:06 pkdns2 sshd\[55284\]: Invalid user Partial@123 from 186.10.17.84Oct  9 23:37:08 pkdns2 sshd\[55284\]: Failed password for invalid user Partial@123 from 186.10.17.84 port 43104 ssh2
...
2019-10-10 04:58:31
176.9.221.118 attackspambots
[portscan] Port scan
2019-10-10 05:06:49
41.82.187.233 attackspam
Lines containing failures of 41.82.187.233
/var/log/apache/pucorp.org.log:41.82.187.233 - - [09/Oct/2019:21:27:55 +0200] "GET / HTTP/1.1" 301 636 "-" "Mozilla/4.0 (compatible; MSIE 5.0; Windows NT; DigExt; DTS Agent"


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=41.82.187.233
2019-10-10 05:22:11
177.68.148.10 attackbotsspam
2019-10-09T20:48:53.285280abusebot.cloudsearch.cf sshd\[29361\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.68.148.10  user=root
2019-10-10 05:10:10
103.21.218.242 attackspambots
Unauthorized SSH login attempts
2019-10-10 05:31:18
49.233.77.182 attackspam
PHP DIESCAN Information Disclosure Vulnerability
2019-10-10 05:11:43
222.186.30.59 attackspam
Oct  9 20:46:05 ip-172-31-62-245 sshd\[28709\]: Failed password for root from 222.186.30.59 port 14050 ssh2\
Oct  9 20:46:07 ip-172-31-62-245 sshd\[28709\]: Failed password for root from 222.186.30.59 port 14050 ssh2\
Oct  9 20:46:10 ip-172-31-62-245 sshd\[28709\]: Failed password for root from 222.186.30.59 port 14050 ssh2\
Oct  9 20:46:22 ip-172-31-62-245 sshd\[28719\]: Failed password for root from 222.186.30.59 port 59267 ssh2\
Oct  9 20:46:42 ip-172-31-62-245 sshd\[28726\]: Failed password for root from 222.186.30.59 port 56747 ssh2\
2019-10-10 05:01:48
154.8.185.122 attack
Oct  9 22:52:31 SilenceServices sshd[12631]: Failed password for root from 154.8.185.122 port 53020 ssh2
Oct  9 22:56:39 SilenceServices sshd[13752]: Failed password for root from 154.8.185.122 port 59600 ssh2
2019-10-10 05:24:19
217.12.84.142 attackspambots
scan r
2019-10-10 04:52:05

Recently Reported IPs

138.68.128.245 138.68.128.94 138.68.13.78 138.68.129.167
138.68.129.219 118.179.36.123 138.68.130.246 138.68.130.69
138.68.131.161 138.68.132.156 138.68.131.205 138.68.132.167
138.68.132.43 138.68.132.250 138.68.131.209 138.68.131.163
138.68.130.35 138.68.131.188 138.68.133.169 138.68.133.253