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

Region: Sao Paulo

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;189.69.48.57.			IN	A

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

;; Query time: 42 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Apr 11 05:44:01 CST 2020
;; MSG SIZE  rcvd: 116
Host info
57.48.69.189.in-addr.arpa domain name pointer 189-69-48-57.dsl.telesp.net.br.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
57.48.69.189.in-addr.arpa	name = 189-69-48-57.dsl.telesp.net.br.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
210.211.116.204 attackbotsspam
May 11 11:29:54 ns381471 sshd[29873]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.211.116.204
May 11 11:29:56 ns381471 sshd[29873]: Failed password for invalid user natasa from 210.211.116.204 port 56001 ssh2
2020-05-11 17:36:42
54.38.65.55 attack
May 11 10:14:56 electroncash sshd[1051]: Failed password for root from 54.38.65.55 port 37384 ssh2
May 11 10:17:58 electroncash sshd[1917]: Invalid user fan from 54.38.65.55 port 37188
May 11 10:17:58 electroncash sshd[1917]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.38.65.55 
May 11 10:17:58 electroncash sshd[1917]: Invalid user fan from 54.38.65.55 port 37188
May 11 10:18:00 electroncash sshd[1917]: Failed password for invalid user fan from 54.38.65.55 port 37188 ssh2
...
2020-05-11 17:38:46
104.236.151.120 attackbots
SSH Brute-Force attacks
2020-05-11 18:13:12
189.7.129.60 attackbots
DATE:2020-05-11 11:03:50, IP:189.7.129.60, PORT:ssh SSH brute force auth (docker-dc)
2020-05-11 18:04:29
82.212.97.139 attack
SSH Brute-Force. Ports scanning.
2020-05-11 17:57:59
190.44.187.174 attackspambots
Invalid user tomcat from 190.44.187.174 port 49571
2020-05-11 17:53:21
187.174.149.2 attack
May 11 08:38:41 mail.srvfarm.net postfix/smtpd[3339774]: warning: unknown[187.174.149.2]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May 11 08:38:41 mail.srvfarm.net postfix/smtpd[3339774]: lost connection after AUTH from unknown[187.174.149.2]
May 11 08:44:04 mail.srvfarm.net postfix/smtpd[3339005]: warning: unknown[187.174.149.2]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
May 11 08:44:04 mail.srvfarm.net postfix/smtpd[3339005]: lost connection after AUTH from unknown[187.174.149.2]
May 11 08:44:49 mail.srvfarm.net postfix/smtpd[3339105]: warning: unknown[187.174.149.2]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2020-05-11 17:56:49
139.199.248.199 attackbotsspam
2020-05-11T01:51:56.5588361495-001 sshd[8470]: Invalid user deploy from 139.199.248.199 port 39900
2020-05-11T01:51:56.5619931495-001 sshd[8470]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.248.199
2020-05-11T01:51:56.5588361495-001 sshd[8470]: Invalid user deploy from 139.199.248.199 port 39900
2020-05-11T01:51:58.9218441495-001 sshd[8470]: Failed password for invalid user deploy from 139.199.248.199 port 39900 ssh2
2020-05-11T01:55:23.6887601495-001 sshd[8636]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.248.199  user=games
2020-05-11T01:55:26.1336171495-001 sshd[8636]: Failed password for games from 139.199.248.199 port 39900 ssh2
...
2020-05-11 18:06:13
103.221.252.46 attackspam
SSH brute-force attempt
2020-05-11 18:07:26
49.233.92.34 attack
May 11 04:43:27 ws22vmsma01 sshd[74185]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.92.34
May 11 04:43:30 ws22vmsma01 sshd[74185]: Failed password for invalid user ubuntu from 49.233.92.34 port 38618 ssh2
...
2020-05-11 17:54:35
210.22.155.2 attackspambots
May 11 05:46:55 electroncash sshd[47294]: Failed password for invalid user root2 from 210.22.155.2 port 33756 ssh2
May 11 05:50:02 electroncash sshd[48225]: Invalid user admin from 210.22.155.2 port 53478
May 11 05:50:02 electroncash sshd[48225]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.22.155.2 
May 11 05:50:02 electroncash sshd[48225]: Invalid user admin from 210.22.155.2 port 53478
May 11 05:50:04 electroncash sshd[48225]: Failed password for invalid user admin from 210.22.155.2 port 53478 ssh2
...
2020-05-11 17:53:10
177.68.156.24 attack
2020-05-11T05:49:08.279205shield sshd\[15423\]: Invalid user wkproxy from 177.68.156.24 port 11257
2020-05-11T05:49:08.282868shield sshd\[15423\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=mail.idesa.com.br
2020-05-11T05:49:10.916517shield sshd\[15423\]: Failed password for invalid user wkproxy from 177.68.156.24 port 11257 ssh2
2020-05-11T05:51:30.360518shield sshd\[16195\]: Invalid user developer from 177.68.156.24 port 57542
2020-05-11T05:51:30.364437shield sshd\[16195\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=mail.idesa.com.br
2020-05-11 17:36:30
106.13.185.97 attackbotsspam
May 11 08:49:19 xeon sshd[48348]: Failed password for invalid user su from 106.13.185.97 port 52026 ssh2
2020-05-11 17:51:55
59.27.124.26 attackspambots
May 11 10:13:54 vps333114 sshd[18386]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.27.124.26
May 11 10:13:56 vps333114 sshd[18386]: Failed password for invalid user bot from 59.27.124.26 port 56458 ssh2
...
2020-05-11 17:54:19
80.82.78.100 attack
80.82.78.100 was recorded 8 times by 5 hosts attempting to connect to the following ports: 6346,5351. Incident counter (4h, 24h, all-time): 8, 60, 26434
2020-05-11 18:08:56

Recently Reported IPs

181.140.134.149 123.0.203.197 39.51.105.134 50.91.193.16
81.168.153.250 3.85.33.179 4.7.57.73 107.51.23.57
73.81.243.176 175.93.216.211 67.118.149.152 50.65.218.171
218.200.235.178 79.184.86.195 188.255.155.53 190.253.49.117
185.43.68.162 80.149.74.148 52.81.30.98 200.24.87.117