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

;; QUESTION SECTION:
;201.139.90.2.			IN	A

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

;; Query time: 67 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 16:33:36 CST 2022
;; MSG SIZE  rcvd: 105
Host info
2.90.139.201.in-addr.arpa domain name pointer 201-139-90-2.microtechnet.com.br.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
2.90.139.201.in-addr.arpa	name = 201-139-90-2.microtechnet.com.br.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
171.8.168.90 attackspambots
Honeypot attack, port: 445, PTR: 8.171.broad.ha.dynamic.163data.com.cn.
2020-04-18 23:43:22
112.207.31.186 attack
Unauthorized connection attempt from IP address 112.207.31.186 on Port 445(SMB)
2020-04-18 23:27:37
222.186.190.14 attack
"fail2ban match"
2020-04-18 23:44:54
188.166.246.46 attack
Tried sshing with brute force.
2020-04-18 23:34:53
192.200.207.131 attackbots
Apr 18 13:55:52 [host] sshd[3892]: pam_unix(sshd:a
Apr 18 13:55:55 [host] sshd[3892]: Failed password
Apr 18 14:00:40 [host] sshd[4016]: Invalid user pv
2020-04-18 23:25:05
112.218.230.85 attackspam
20/4/18@08:00:43: FAIL: IoT-Telnet address from=112.218.230.85
...
2020-04-18 23:22:53
171.231.244.12 attack
Tried to hack email account
2020-04-19 00:09:50
157.245.75.179 attackspam
" "
2020-04-18 23:51:02
117.50.63.228 attack
SSH brute-force: detected 9 distinct usernames within a 24-hour window.
2020-04-18 23:22:30
184.105.139.79 attackbotsspam
Port probing on unauthorized port 8080
2020-04-18 23:56:21
27.71.121.117 attackbotsspam
Apr 18 14:00:16 andromeda sshd\[57092\]: Invalid user admin from 27.71.121.117 port 23906
Apr 18 14:00:16 andromeda sshd\[57092\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.71.121.117
Apr 18 14:00:18 andromeda sshd\[57092\]: Failed password for invalid user admin from 27.71.121.117 port 23906 ssh2
2020-04-18 23:55:36
112.85.42.88 attack
Unauthorized connection attempt detected from IP address 112.85.42.88 to port 22
2020-04-18 23:57:23
216.83.52.120 attack
Apr 18 17:52:21 vpn01 sshd[31534]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=216.83.52.120
Apr 18 17:52:23 vpn01 sshd[31534]: Failed password for invalid user em from 216.83.52.120 port 18753 ssh2
...
2020-04-18 23:52:56
134.175.178.118 attackbots
Apr 18 16:41:31 piServer sshd[3449]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.178.118 
Apr 18 16:41:33 piServer sshd[3449]: Failed password for invalid user s from 134.175.178.118 port 35160 ssh2
Apr 18 16:44:41 piServer sshd[3671]: Failed password for root from 134.175.178.118 port 40490 ssh2
...
2020-04-18 23:30:18
192.241.237.141 attack
firewall-block, port(s): 873/tcp
2020-04-18 23:55:55

Recently Reported IPs

201.137.43.131 201.140.0.227 201.140.0.74 201.140.10.143
201.140.20.215 201.140.14.149 201.140.14.42 201.14.129.96
201.140.14.177 201.14.27.99 201.140.14.241 201.140.215.65
201.140.7.174 201.140.235.45 201.141.112.11 201.140.8.31
201.140.7.24 201.141.208.225 201.141.174.88 201.141.209.245