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: Brasília

Region: Distrito Federal

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:
% IP Client: 124.223.158.242
 % Copyright (c) Nic.br - Use of this data is governed by the Use and
% Privacy Policy at https://registro.br/upp . Distribution,
% commercialization, reproduction, and use for advertising or similar
% purposes are expressly prohibited.
% 2025-09-20T01:30:49-03:00 - 124.223.158.242

inetnum:     189.58.0.0/15
aut-num:     AS18881
abuse-c:     CSTBR
owner:       TELEF�NICA BRASIL S.A
ownerid:     02.558.157/0001-62
responsible: Diretoria de Planejamento e Tecnologia
owner-c:     ARITE
tech-c:      GVO6
inetrev:     189.59.66.0/24
nserver:     dns1.gvt.net.br
nsstat:      20250916 AA
nslastaa:    20250916
nserver:     dns2.gvt.net.br
nsstat:      20250916 AA
nslastaa:    20250916
nserver:     dns3.gvt.net.br
nsstat:      20250916 AA
nslastaa:    20250916
nserver:     dns4.gvt.net.br
nsstat:      20250916 AA
nslastaa:    20250916
created:     20070906
changed:     20160909

nic-hdl-br:  ARITE
person:      Administra��o Rede IP Telesp
created:     20080407
changed:     20230629

nic-hdl-br:  CSTBR
person:      CSIRT TELEFONICA BR
created:     20180713
changed:     20180713

nic-hdl-br:  GVO6
person:      GVT Operacao
created:     20010613
changed:     20220331

% Security and mail abuse issues should also be addressed to cert.br,
% respectivelly to cert@cert.br and mail-abuse@cert.br
%
% whois.registro.br only accepts exact match queries for domains,
% registrants, contacts, tickets, providers, IPs, and ASNs.
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 189.59.66.179
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21356
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;189.59.66.179.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Sep 20 12:30:50 CST 2025
;; MSG SIZE  rcvd: 106
Host info
179.66.59.189.in-addr.arpa domain name pointer corporativo179.static.gvt.net.br.
Nslookup info:
Server:		183.60.82.98
Address:	183.60.82.98#53

Non-authoritative answer:
179.66.59.189.in-addr.arpa	name = corporativo179.static.gvt.net.br.

Authoritative answers can be found from:

Related IP info:
Related comments:
IP Type Details Datetime
140.249.22.238 attack
SSH brute force
2020-04-10 08:02:16
51.77.97.181 attack
09.04.2020 23:56:06 - RDP Login Fail Detected by 
https://www.elinox.de/RDP-Wächter
2020-04-10 07:38:36
188.166.109.87 attackspam
Apr 10 00:58:25 pve sshd[13303]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.109.87 
Apr 10 00:58:27 pve sshd[13303]: Failed password for invalid user user from 188.166.109.87 port 33180 ssh2
Apr 10 01:03:04 pve sshd[14025]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.109.87
2020-04-10 07:36:13
186.136.95.137 attack
Apr  9 10:33:46 XXX sshd[50261]: Invalid user app from 186.136.95.137 port 60309
2020-04-10 08:04:15
122.170.5.123 attackbots
Apr 10 06:45:23 itv-usvr-01 sshd[11671]: Invalid user odoo from 122.170.5.123
Apr 10 06:45:23 itv-usvr-01 sshd[11671]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.170.5.123
Apr 10 06:45:23 itv-usvr-01 sshd[11671]: Invalid user odoo from 122.170.5.123
Apr 10 06:45:25 itv-usvr-01 sshd[11671]: Failed password for invalid user odoo from 122.170.5.123 port 47038 ssh2
Apr 10 06:54:51 itv-usvr-01 sshd[12058]: Invalid user postgres from 122.170.5.123
2020-04-10 08:02:33
191.239.245.229 attackspambots
(sshd) Failed SSH login from 191.239.245.229 (BR/Brazil/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: Apr  9 18:54:18 host sshd[85063]: Invalid user hzc from 191.239.245.229 port 54900
2020-04-10 07:47:50
43.226.69.237 attackbotsspam
2020-04-10 00:13:00,924 fail2ban.actions: WARNING [ssh] Ban 43.226.69.237
2020-04-10 07:39:42
222.186.175.212 attack
2020-04-09T23:37:04.946217abusebot-7.cloudsearch.cf sshd[23799]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.212  user=root
2020-04-09T23:37:06.874338abusebot-7.cloudsearch.cf sshd[23799]: Failed password for root from 222.186.175.212 port 31054 ssh2
2020-04-09T23:37:10.232466abusebot-7.cloudsearch.cf sshd[23799]: Failed password for root from 222.186.175.212 port 31054 ssh2
2020-04-09T23:37:04.946217abusebot-7.cloudsearch.cf sshd[23799]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.212  user=root
2020-04-09T23:37:06.874338abusebot-7.cloudsearch.cf sshd[23799]: Failed password for root from 222.186.175.212 port 31054 ssh2
2020-04-09T23:37:10.232466abusebot-7.cloudsearch.cf sshd[23799]: Failed password for root from 222.186.175.212 port 31054 ssh2
2020-04-09T23:37:04.946217abusebot-7.cloudsearch.cf sshd[23799]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 
...
2020-04-10 07:43:45
129.211.46.112 attackspam
Apr 10 01:01:06 vps sshd[11674]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.46.112 
Apr 10 01:01:09 vps sshd[11674]: Failed password for invalid user lorenza from 129.211.46.112 port 55930 ssh2
Apr 10 01:04:23 vps sshd[11863]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.46.112 
...
2020-04-10 07:49:50
180.167.225.118 attack
Apr 10 01:13:44 sso sshd[6434]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.167.225.118
Apr 10 01:13:47 sso sshd[6434]: Failed password for invalid user test from 180.167.225.118 port 51332 ssh2
...
2020-04-10 08:04:47
51.91.159.152 attackbots
$f2bV_matches
2020-04-10 08:01:43
84.39.244.131 attack
Automatic report - Port Scan Attack
2020-04-10 08:03:56
185.53.88.39 attack
Apr 10 01:09:01 debian-2gb-nbg1-2 kernel: \[8732751.886720\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.53.88.39 DST=195.201.40.59 LEN=439 TOS=0x00 PREC=0x00 TTL=54 ID=2806 DF PROTO=UDP SPT=5083 DPT=5060 LEN=419
2020-04-10 07:30:20
114.79.146.115 attackspambots
Apr 10 01:20:45 ArkNodeAT sshd\[17907\]: Invalid user minecraft from 114.79.146.115
Apr 10 01:20:45 ArkNodeAT sshd\[17907\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.79.146.115
Apr 10 01:20:48 ArkNodeAT sshd\[17907\]: Failed password for invalid user minecraft from 114.79.146.115 port 57534 ssh2
2020-04-10 07:50:10
51.89.138.148 attackspam
Apr  9 23:50:47 vps sshd[671611]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.89.138.148
Apr  9 23:50:48 vps sshd[671611]: Failed password for invalid user vika from 51.89.138.148 port 41840 ssh2
Apr  9 23:55:21 vps sshd[696847]: Invalid user deploy from 51.89.138.148 port 50166
Apr  9 23:55:21 vps sshd[696847]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.89.138.148
Apr  9 23:55:23 vps sshd[696847]: Failed password for invalid user deploy from 51.89.138.148 port 50166 ssh2
...
2020-04-10 07:59:39

Recently Reported IPs

103.116.72.4 45.156.128.157 45.156.128.158 45.156.128.156
45.156.128.159 20.102.108.84 228.86.6.1 2001:2d8:e511:6ea4:89f8:9f92:a57:6b71
2001:506:6000:12f:69:235:120:187 159.89.44.21 185.247.137.204 60.13.138.140
222.90.212.246 211.145.71.32 2.85.117.45 20.171.207.102
195.181.89.33 9.13.85.5 167.68.42.168 185.246.87.99