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: Medellín

Region: Antioquia

Country: Colombia

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
 
% Joint Whois - whois.lacnic.net
%  This server accepts single ASN, IPv4 or IPv6 queries

% LACNIC resource: whois.lacnic.net


% Copyright LACNIC lacnic.net
%  The data below is provided for information purposes
%  and to assist persons in obtaining information about or
%  related to AS and IP numbers registrations
%  By submitting a whois query, you agree to use this data
%  only for lawful purposes.
%  2026-08-15 21:00:37 (-03 -03:00)

inetnum:     179.32.0.0/15
status:      allocated
aut-num:     N/A
owner:       COLOMBIA TELECOMUNICACIONES S.A. ESP BIC
ownerid:     CO-CTSE-LACNIC
responsible: Administradores Internet Colombia
address:     Transversal 60, 114, A 55
address:     N - BOGOTA - Cu
country:     CO
phone:       +57  17050000 [0000]
owner-c:     CTE7
tech-c:      CTE7
abuse-c:     CTE7
inetrev:     179.32.0.0/15
nserver:     DNS5.TELECOM.COM.CO
nsstat:      20260814 AA
nslastaa:    20260814
nserver:     DNS.TELECOM.COM.CO
nsstat:      20260814 AA
nslastaa:    20260814
created:     20130827
changed:     20260723

nic-hdl:     CTE7
person:      Grupo de Administradores Internet
e-mail:      hostmaster.co@telefonica.com
address:     Transversal, 60, 114 A, 55
address:     571111 - BOGOTA DC - CU
country:     CO
phone:       +57 1 7050000 [71360]
created:     20140220
changed:     20240312

% whois.lacnic.net accepts only direct match queries.
% Types of queries are: POCs, ownerid, CIDR blocks, IP
% and AS numbers.
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 179.32.39.99
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 5398
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;179.32.39.99.			IN	A

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

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Aug 16 08:00:37 CST 2026
;; MSG SIZE  rcvd: 105
Host info
Host 99.39.32.179.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 99.39.32.179.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
219.142.140.2 attack
Jan 11 12:19:42 firewall sshd[27743]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.142.140.2
Jan 11 12:19:42 firewall sshd[27743]: Invalid user ubuntu from 219.142.140.2
Jan 11 12:19:43 firewall sshd[27743]: Failed password for invalid user ubuntu from 219.142.140.2 port 60886 ssh2
...
2020-01-12 02:45:54
124.30.44.214 attackspambots
$f2bV_matches
2020-01-12 02:45:07
123.206.174.26 attack
$f2bV_matches
2020-01-12 03:04:50
123.207.153.52 attackspam
2020-01-11T18:00:43.096725shield sshd\[20236\]: Invalid user ts2 from 123.207.153.52 port 39200
2020-01-11T18:00:43.102752shield sshd\[20236\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.207.153.52
2020-01-11T18:00:45.378353shield sshd\[20236\]: Failed password for invalid user ts2 from 123.207.153.52 port 39200 ssh2
2020-01-11T18:02:01.075460shield sshd\[20844\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.207.153.52  user=root
2020-01-11T18:02:03.059457shield sshd\[20844\]: Failed password for root from 123.207.153.52 port 47682 ssh2
2020-01-12 03:01:13
125.124.152.59 attackbotsspam
Unauthorized connection attempt detected from IP address 125.124.152.59 to port 2220 [J]
2020-01-12 02:41:09
124.195.244.126 attackbotsspam
$f2bV_matches
2020-01-12 02:48:02
123.207.107.183 attackbots
$f2bV_matches
2020-01-12 03:03:18
123.207.142.31 attackspam
$f2bV_matches
2020-01-12 03:02:56
178.112.245.86 attackspambots
Jan 11 14:07:41 zulu412 sshd\[26633\]: Invalid user malaquias from 178.112.245.86 port 51952
Jan 11 14:07:41 zulu412 sshd\[26633\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.112.245.86
Jan 11 14:07:43 zulu412 sshd\[26633\]: Failed password for invalid user malaquias from 178.112.245.86 port 51952 ssh2
...
2020-01-12 03:09:56
128.199.100.225 attackbots
Automatic report - Banned IP Access
2020-01-12 02:32:48
123.207.88.97 attackbotsspam
$f2bV_matches
2020-01-12 02:58:03
128.199.104.242 attack
Jan 11 14:57:33 firewall sshd[31089]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.104.242
Jan 11 14:57:33 firewall sshd[31089]: Invalid user !"#$%& from 128.199.104.242
Jan 11 14:57:35 firewall sshd[31089]: Failed password for invalid user !"#$%& from 128.199.104.242 port 44812 ssh2
...
2020-01-12 02:31:36
124.161.231.150 attack
$f2bV_matches
2020-01-12 02:48:49
124.153.75.28 attackspambots
$f2bV_matches
2020-01-12 02:53:04
112.85.42.174 attackspambots
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.174  user=root
Failed password for root from 112.85.42.174 port 56414 ssh2
Failed password for root from 112.85.42.174 port 56414 ssh2
Failed password for root from 112.85.42.174 port 56414 ssh2
Failed password for root from 112.85.42.174 port 56414 ssh2
2020-01-12 02:35:59

Recently Reported IPs

52.167.144.66 180.102.110.177 184.73.137.109 100.59.45.97
110.77.248.139 2606:4700:10::6814:7994 158.158.121.155 20.24.67.246
154.83.197.7 45.148.10.5 5.175.73.158 188.166.30.57
142.93.131.126 134.209.195.140 121.229.156.27 2606:4700:10::6816:423d
61.163.172.141 60.31.24.179 58.255.237.73 42.176.204.139