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

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.121.16.111 attackbots
Invalid user admin from 138.121.16.111 port 44172
2020-06-06 01:28:57
138.121.161.198 attackbotsspam
Feb 16 01:28:50 sd-53420 sshd\[31396\]: Invalid user gmodserver1 from 138.121.161.198
Feb 16 01:28:50 sd-53420 sshd\[31396\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.121.161.198
Feb 16 01:28:52 sd-53420 sshd\[31396\]: Failed password for invalid user gmodserver1 from 138.121.161.198 port 34128 ssh2
Feb 16 01:32:34 sd-53420 sshd\[31830\]: Invalid user osman from 138.121.161.198
Feb 16 01:32:34 sd-53420 sshd\[31830\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.121.161.198
...
2020-02-16 10:45:04
138.121.161.222 attack
Dec  9 07:39:33 * sshd[8908]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.121.161.222
Dec  9 07:39:35 * sshd[8908]: Failed password for invalid user pugin from 138.121.161.222 port 54959 ssh2
2019-12-09 14:52:21
138.121.161.198 attack
Sep 23 21:05:29 localhost sshd\[77474\]: Invalid user www from 138.121.161.198 port 45582
Sep 23 21:05:29 localhost sshd\[77474\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.121.161.198
Sep 23 21:05:31 localhost sshd\[77474\]: Failed password for invalid user www from 138.121.161.198 port 45582 ssh2
Sep 23 21:10:16 localhost sshd\[77674\]: Invalid user odroid from 138.121.161.198 port 36053
Sep 23 21:10:16 localhost sshd\[77674\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.121.161.198
...
2019-09-24 06:37:41
138.121.161.198 attackspam
Sep 14 10:37:54 lcdev sshd\[11567\]: Invalid user aDmin from 138.121.161.198
Sep 14 10:37:54 lcdev sshd\[11567\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.121.161.198
Sep 14 10:37:56 lcdev sshd\[11567\]: Failed password for invalid user aDmin from 138.121.161.198 port 57782 ssh2
Sep 14 10:42:42 lcdev sshd\[12047\]: Invalid user c_log from 138.121.161.198
Sep 14 10:42:42 lcdev sshd\[12047\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.121.161.198
2019-09-15 09:16:24
138.121.161.198 attack
2019-09-07T09:26:14.011765lon01.zurich-datacenter.net sshd\[29585\]: Invalid user testftp from 138.121.161.198 port 44623
2019-09-07T09:26:14.019383lon01.zurich-datacenter.net sshd\[29585\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.121.161.198
2019-09-07T09:26:16.633167lon01.zurich-datacenter.net sshd\[29585\]: Failed password for invalid user testftp from 138.121.161.198 port 44623 ssh2
2019-09-07T09:31:19.784407lon01.zurich-datacenter.net sshd\[29698\]: Invalid user ts3server from 138.121.161.198 port 36045
2019-09-07T09:31:19.790531lon01.zurich-datacenter.net sshd\[29698\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.121.161.198
...
2019-09-07 16:04:56
138.121.161.198 attack
Sep  3 04:19:20 bouncer sshd\[18354\]: Invalid user admin from 138.121.161.198 port 45456
Sep  3 04:19:20 bouncer sshd\[18354\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.121.161.198 
Sep  3 04:19:22 bouncer sshd\[18354\]: Failed password for invalid user admin from 138.121.161.198 port 45456 ssh2
...
2019-09-03 10:38:30
138.121.161.198 attackbots
Aug 30 11:46:04 aiointranet sshd\[17797\]: Invalid user chip from 138.121.161.198
Aug 30 11:46:04 aiointranet sshd\[17797\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.121.161.198
Aug 30 11:46:06 aiointranet sshd\[17797\]: Failed password for invalid user chip from 138.121.161.198 port 52856 ssh2
Aug 30 11:51:06 aiointranet sshd\[18191\]: Invalid user jack from 138.121.161.198
Aug 30 11:51:06 aiointranet sshd\[18191\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.121.161.198
2019-08-31 06:17:27
138.121.161.198 attack
ssh failed login
2019-08-24 03:24:21
138.121.161.198 attack
Aug 22 01:49:49 web1 sshd\[19295\]: Invalid user prueba from 138.121.161.198
Aug 22 01:49:49 web1 sshd\[19295\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.121.161.198
Aug 22 01:49:51 web1 sshd\[19295\]: Failed password for invalid user prueba from 138.121.161.198 port 53022 ssh2
Aug 22 01:55:09 web1 sshd\[19827\]: Invalid user abc123 from 138.121.161.198
Aug 22 01:55:09 web1 sshd\[19827\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.121.161.198
2019-08-22 19:56:37
138.121.161.198 attack
Invalid user it1 from 138.121.161.198 port 53798
2019-08-18 20:19:14
138.121.161.198 attackspambots
Aug 15 12:15:55 aiointranet sshd\[8122\]: Invalid user gao from 138.121.161.198
Aug 15 12:15:55 aiointranet sshd\[8122\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.121.161.198
Aug 15 12:15:57 aiointranet sshd\[8122\]: Failed password for invalid user gao from 138.121.161.198 port 44003 ssh2
Aug 15 12:20:55 aiointranet sshd\[8642\]: Invalid user gpadmin from 138.121.161.198
Aug 15 12:20:55 aiointranet sshd\[8642\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.121.161.198
2019-08-16 06:32:41
138.121.161.198 attackbots
Triggered by Fail2Ban at Vostok web server
2019-08-13 16:26:44
138.121.161.198 attackbots
Brute force SMTP login attempted.
...
2019-08-10 04:10:47
138.121.161.198 attackbots
Aug  8 19:28:03 ks10 sshd[3792]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.121.161.198 
Aug  8 19:28:05 ks10 sshd[3792]: Failed password for invalid user aria from 138.121.161.198 port 43246 ssh2
...
2019-08-09 02:44:41
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 138.121.16.219
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40571
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;138.121.16.219.			IN	A

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

;; Query time: 55 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 08 11:27:41 CST 2022
;; MSG SIZE  rcvd: 107
Host info
219.16.121.138.in-addr.arpa domain name pointer 219-16-121-138.static.microwebnet.com.br.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
219.16.121.138.in-addr.arpa	name = 219-16-121-138.static.microwebnet.com.br.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
189.124.68.225 attackbots
23/tcp
[2019-10-28]1pkt
2019-10-28 15:00:40
121.157.82.214 attackspambots
2019-10-28T06:17:16.040047abusebot-5.cloudsearch.cf sshd\[13172\]: Invalid user robert from 121.157.82.214 port 52726
2019-10-28T06:17:16.046980abusebot-5.cloudsearch.cf sshd\[13172\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.157.82.214
2019-10-28 14:36:42
49.232.92.95 attackbotsspam
SSH Brute-Force reported by Fail2Ban
2019-10-28 14:50:09
148.227.224.17 attack
(sshd) Failed SSH login from 148.227.224.17 (MX/Mexico/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct 28 04:39:57 server2 sshd[4112]: Invalid user icache from 148.227.224.17 port 52800
Oct 28 04:39:59 server2 sshd[4112]: Failed password for invalid user icache from 148.227.224.17 port 52800 ssh2
Oct 28 04:48:00 server2 sshd[4333]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.227.224.17  user=root
Oct 28 04:48:01 server2 sshd[4333]: Failed password for root from 148.227.224.17 port 59176 ssh2
Oct 28 04:52:39 server2 sshd[4447]: Invalid user peewee from 148.227.224.17 port 43366
2019-10-28 14:51:20
178.128.150.158 attackbots
(sshd) Failed SSH login from 178.128.150.158 (US/United States/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct 28 04:39:40 server2 sshd[4108]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.150.158  user=mysql
Oct 28 04:39:42 server2 sshd[4108]: Failed password for mysql from 178.128.150.158 port 35608 ssh2
Oct 28 04:49:36 server2 sshd[4363]: Invalid user cvsuser from 178.128.150.158 port 52796
Oct 28 04:49:38 server2 sshd[4363]: Failed password for invalid user cvsuser from 178.128.150.158 port 52796 ssh2
Oct 28 04:53:00 server2 sshd[4488]: Invalid user vz from 178.128.150.158 port 35076
2019-10-28 14:36:21
85.236.161.11 attackspambots
'IP reached maximum auth failures for a one day block'
2019-10-28 14:29:56
175.211.112.250 attackspambots
2019-10-28T03:01:49.820040Z fe27e2fae978 New connection: 175.211.112.250:58392 (172.17.0.3:2222) [session: fe27e2fae978]
2019-10-28T03:53:10.534874Z fc9868c3802c New connection: 175.211.112.250:46220 (172.17.0.3:2222) [session: fc9868c3802c]
2019-10-28 14:32:11
87.229.197.132 attackspam
445/tcp
[2019-10-28]1pkt
2019-10-28 15:03:08
59.25.197.138 attack
2019-10-28T05:02:57.947923abusebot-5.cloudsearch.cf sshd\[12351\]: Invalid user bjorn from 59.25.197.138 port 40622
2019-10-28 14:30:14
111.12.52.239 attack
Oct 27 23:52:46 Tower sshd[8924]: Connection from 111.12.52.239 port 43296 on 192.168.10.220 port 22
Oct 27 23:52:47 Tower sshd[8924]: Failed password for root from 111.12.52.239 port 43296 ssh2
Oct 27 23:52:48 Tower sshd[8924]: Received disconnect from 111.12.52.239 port 43296:11: Bye Bye [preauth]
Oct 27 23:52:48 Tower sshd[8924]: Disconnected from authenticating user root 111.12.52.239 port 43296 [preauth]
2019-10-28 14:42:27
2804:29b8:5029:9a48:ccf4:26c9:866c:5ea7 attackspam
C1,WP GET /wp-login.php
GET /wp-login.php
2019-10-28 14:35:52
88.228.43.96 attackbotsspam
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/88.228.43.96/ 
 
 TR - 1H : (82)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : TR 
 NAME ASN : ASN9121 
 
 IP : 88.228.43.96 
 
 CIDR : 88.228.32.0/19 
 
 PREFIX COUNT : 4577 
 
 UNIQUE IP COUNT : 6868736 
 
 
 ATTACKS DETECTED ASN9121 :  
  1H - 2 
  3H - 2 
  6H - 11 
 12H - 27 
 24H - 65 
 
 DateTime : 2019-10-28 04:52:29 
 
 INFO :  HACK ! - Looking for resource vulnerabilities Scan Detected and Blocked by ADMIN  - data recovery
2019-10-28 15:01:49
42.112.148.124 attackbotsspam
445/tcp
[2019-10-28]1pkt
2019-10-28 14:30:41
61.28.227.133 attack
Oct 28 07:06:21 sauna sshd[41738]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.28.227.133
Oct 28 07:06:23 sauna sshd[41738]: Failed password for invalid user pat from 61.28.227.133 port 59986 ssh2
...
2019-10-28 14:35:22
111.93.52.182 attackspam
Oct 27 20:44:32 web9 sshd\[14255\]: Invalid user sara from 111.93.52.182
Oct 27 20:44:32 web9 sshd\[14255\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.93.52.182
Oct 27 20:44:35 web9 sshd\[14255\]: Failed password for invalid user sara from 111.93.52.182 port 57483 ssh2
Oct 27 20:49:46 web9 sshd\[15032\]: Invalid user avahii from 111.93.52.182
Oct 27 20:49:46 web9 sshd\[15032\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.93.52.182
2019-10-28 15:01:10

Recently Reported IPs

79.106.211.86 177.249.170.114 91.98.13.95 204.217.192.175
123.4.162.68 182.121.162.93 222.160.142.218 185.183.107.155
3.108.247.196 117.247.182.250 146.185.201.34 42.227.181.10
202.40.180.109 134.249.207.152 201.171.226.244 112.39.102.213
115.86.222.219 103.68.43.152 93.186.117.3 80.244.39.38