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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 138.121.50.21
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10732
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;138.121.50.21.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 14:35:19 CST 2022
;; MSG SIZE  rcvd: 106
Host info
21.50.121.138.in-addr.arpa domain name pointer 50-121-138-21.clientes.microtellinternet.com.br.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
21.50.121.138.in-addr.arpa	name = 50-121-138-21.clientes.microtellinternet.com.br.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
5.226.11.125 attack
Oct 16 16:01:22 mxgate1 postfix/postscreen[7584]: CONNECT from [5.226.11.125]:35673 to [176.31.12.44]:25
Oct 16 16:01:22 mxgate1 postfix/dnsblog[7748]: addr 5.226.11.125 listed by domain b.barracudacentral.org as 127.0.0.2
Oct 16 16:01:28 mxgate1 postfix/postscreen[7584]: PASS NEW [5.226.11.125]:35673
Oct 16 16:01:30 mxgate1 postfix/smtpd[8207]: connect from unknown[5.226.11.125]
Oct x@x
Oct 16 16:01:37 mxgate1 postfix/smtpd[8207]: disconnect from unknown[5.226.11.125] helo=1 mail=1 rcpt=0/1 quhostname=1 commands=3/4
Oct 16 21:16:35 mxgate1 postfix/postscreen[19323]: CONNECT from [5.226.11.125]:36946 to [176.31.12.44]:25
Oct 16 21:16:35 mxgate1 postfix/dnsblog[19346]: addr 5.226.11.125 listed by domain b.barracudacentral.org as 127.0.0.2
Oct 16 21:16:36 mxgate1 postfix/dnsblog[19343]: addr 5.226.11.125 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Oct 16 21:16:36 mxgate1 postfix/postscreen[19323]: DNSBL rank 2 for [5.226.11.125]:36946
Oct x@x
Oct 16 21:16:36 mxgate1........
-------------------------------
2019-10-17 04:59:11
193.70.2.117 attackbots
Oct 16 15:27:48 debian sshd\[31440\]: Invalid user ira from 193.70.2.117 port 56580
Oct 16 15:27:48 debian sshd\[31440\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.70.2.117
Oct 16 15:27:50 debian sshd\[31440\]: Failed password for invalid user ira from 193.70.2.117 port 56580 ssh2
...
2019-10-17 04:52:57
66.244.86.186 attackspambots
postfix (unknown user, SPF fail or relay access denied)
2019-10-17 04:33:33
139.59.9.251 attackbotsspam
WordPress wp-login brute force :: 139.59.9.251 0.184 BYPASS [17/Oct/2019:06:28:16  1100] [censored_1] "POST /wp-login.php HTTP/1.1" 200 3972 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-10-17 04:36:23
212.237.63.28 attack
Oct 16 10:27:52 php1 sshd\[12234\]: Invalid user asdf123\$ from 212.237.63.28
Oct 16 10:27:52 php1 sshd\[12234\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.237.63.28
Oct 16 10:27:54 php1 sshd\[12234\]: Failed password for invalid user asdf123\$ from 212.237.63.28 port 55710 ssh2
Oct 16 10:31:51 php1 sshd\[12572\]: Invalid user 123456 from 212.237.63.28
Oct 16 10:31:51 php1 sshd\[12572\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.237.63.28
2019-10-17 04:33:51
181.188.170.248 attack
Oct 16 21:15:13 mxgate1 postfix/postscreen[19323]: CONNECT from [181.188.170.248]:16023 to [176.31.12.44]:25
Oct 16 21:15:13 mxgate1 postfix/dnsblog[19342]: addr 181.188.170.248 listed by domain zen.spamhaus.org as 127.0.0.4
Oct 16 21:15:13 mxgate1 postfix/dnsblog[19342]: addr 181.188.170.248 listed by domain zen.spamhaus.org as 127.0.0.11
Oct 16 21:15:13 mxgate1 postfix/dnsblog[19343]: addr 181.188.170.248 listed by domain cbl.abuseat.org as 127.0.0.2
Oct 16 21:15:13 mxgate1 postfix/dnsblog[19344]: addr 181.188.170.248 listed by domain b.barracudacentral.org as 127.0.0.2
Oct 16 21:15:13 mxgate1 postfix/postscreen[19323]: PREGREET 24 after 0.24 from [181.188.170.248]:16023: EHLO [181.188.170.248]

Oct 16 21:15:14 mxgate1 postfix/postscreen[19323]: DNSBL rank 4 for [181.188.170.248]:16023
Oct x@x
Oct 16 21:15:15 mxgate1 postfix/postscreen[19323]: HANGUP after 0.84 from [181.188.170.248]:16023 in tests after SMTP handshake
Oct 16 21:15:15 mxgate1 postfix/postscreen[19323]........
-------------------------------
2019-10-17 04:55:40
112.216.129.138 attackbotsspam
Oct 16 21:24:24 xeon sshd[18106]: Failed password for root from 112.216.129.138 port 42652 ssh2
2019-10-17 04:45:21
47.91.105.138 attackspambots
Oct 16 22:24:56 mc1 kernel: \[2543866.463825\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=47.91.105.138 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=40089 PROTO=TCP SPT=51319 DPT=21176 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct 16 22:26:36 mc1 kernel: \[2543966.147514\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=47.91.105.138 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=47182 PROTO=TCP SPT=51319 DPT=20173 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct 16 22:30:20 mc1 kernel: \[2544190.032045\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=47.91.105.138 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=60039 PROTO=TCP SPT=51319 DPT=17000 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-10-17 04:30:59
167.71.45.56 attackbotsspam
Wordpress bruteforce
2019-10-17 04:20:38
80.93.187.117 attackbots
2019-10-16T20:54:50.845383mail.arvenenaske.de sshd[12487]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.93.187.117  user=r.r
2019-10-16T20:54:52.487100mail.arvenenaske.de sshd[12487]: Failed password for r.r from 80.93.187.117 port 59956 ssh2
2019-10-16T20:54:55.638958mail.arvenenaske.de sshd[12489]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.93.187.117  user=r.r
2019-10-16T20:54:57.636199mail.arvenenaske.de sshd[12489]: Failed password for r.r from 80.93.187.117 port 58858 ssh2
2019-10-16T20:55:01.775940mail.arvenenaske.de sshd[12491]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.93.187.117  user=r.r
2019-10-16T20:55:03.261688mail.arvenenaske.de sshd[12491]: Failed password for r.r from 80.93.187.117 port 57768 ssh2
2019-10-16T20:55:08.359827mail.arvenenaske.de sshd[12493]: Invalid user r.r123 from 80.93.187.117 port 56682
2019-10-1........
------------------------------
2019-10-17 04:44:53
156.209.100.192 attackbots
IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/156.209.100.192/ 
 EG - 1H : (87)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : EG 
 NAME ASN : ASN8452 
 
 IP : 156.209.100.192 
 
 CIDR : 156.209.64.0/18 
 
 PREFIX COUNT : 833 
 
 UNIQUE IP COUNT : 7610368 
 
 
 WYKRYTE ATAKI Z ASN8452 :  
  1H - 3 
  3H - 15 
  6H - 24 
 12H - 38 
 24H - 80 
 
 DateTime : 2019-10-16 21:28:27 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-10-17 04:26:21
101.78.209.39 attackbotsspam
Oct 16 17:24:18 ws12vmsma01 sshd[57680]: Failed password for root from 101.78.209.39 port 58166 ssh2
Oct 16 17:28:05 ws12vmsma01 sshd[58181]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.78.209.39  user=root
Oct 16 17:28:07 ws12vmsma01 sshd[58181]: Failed password for root from 101.78.209.39 port 49671 ssh2
...
2019-10-17 04:43:34
131.255.100.66 attackspambots
port scan and connect, tcp 1433 (ms-sql-s)
2019-10-17 04:42:40
158.69.222.2 attackspambots
Oct 16 19:27:51 *** sshd[7444]: User root from 158.69.222.2 not allowed because not listed in AllowUsers
2019-10-17 04:51:19
114.32.79.219 attackbots
Automatic report - Port Scan Attack
2019-10-17 04:34:32

Recently Reported IPs

138.121.237.229 138.122.154.172 138.118.243.46 138.118.81.110
138.122.190.145 138.121.155.37 138.121.66.215 138.122.20.82
138.122.36.237 138.122.36.48 138.122.39.198 138.122.36.205
138.122.4.251 138.122.37.83 138.122.6.211 138.122.6.69
138.122.6.214 138.122.6.198 138.122.4.34 138.122.39.94