City: Santiago
Region: Region Metropolitana (RM)
Country: Chile
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
% 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-09-14 13:18:37 (Z Z)
inetnum: 201.148.104.0/22
status: allocated
aut-num: N/A
owner: HOSTING.CL
ownerid: CL-HOST-LACNIC
responsible: Alcadio Almarza
address: Flor de azucena, 73, las condes
address: 8320000 - Santiago - RM
country: CL
phone: +56 224110321 [0000]
owner-c: ALA126
tech-c: ALA126
abuse-c: FAC103
inetrev: 201.148.104.0/22
nserver: DNS1.TODOHOSTING.CL
nsstat: 20260911 AA
nslastaa: 20260911
nserver: DNS2.TODOHOSTING.CL
nsstat: 20260911 AA
nslastaa: 20260911
created: 20140710
changed: 20240806
nic-hdl: ALA126
person: Alcadio Almarza
e-mail: alcadio@hosting.cl
address: flor de azucena, 73, las condes
address: 8320000 - santiago - las condes
country: CL
phone: +56 0949877821 [0000]
created: 20170427
changed: 20250528
nic-hdl: FAC103
person: Fabian Castillo
e-mail: operaciones@hosting.cl
address: Flor de Azucena, 73,
address: 7550000 - Santiago -
country: CL
phone: +56 987281267
created: 20190214
changed: 20250908
% whois.lacnic.net accepts only direct match queries.
% Types of queries are: POCs, ownerid, CIDR blocks, IP
% and AS numbers.
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 201.148.104.110
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 399
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;201.148.104.110. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026091400 1800 900 604800 86400
;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Sep 14 21:18:37 CST 2026
;; MSG SIZE rcvd: 108
b'110.104.148.201.in-addr.arpa domain name pointer 105106new.dedicados.cl.
'
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
110.104.148.201.in-addr.arpa name = 105106new.dedicados.cl.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 41.225.16.156 | attackspambots | SSH Invalid Login |
2020-07-21 07:00:39 |
| 37.49.230.211 | attackspambots |
|
2020-07-21 07:24:45 |
| 45.55.184.78 | attackbots | 1622. On Jul 20 2020 experienced a Brute Force SSH login attempt -> 88 unique times by 45.55.184.78. |
2020-07-21 07:09:40 |
| 51.222.48.59 | attackbotsspam | Jul 21 00:47:30 nextcloud sshd\[13837\]: Invalid user zhangkun from 51.222.48.59 Jul 21 00:47:30 nextcloud sshd\[13837\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.222.48.59 Jul 21 00:47:32 nextcloud sshd\[13837\]: Failed password for invalid user zhangkun from 51.222.48.59 port 46426 ssh2 |
2020-07-21 07:17:05 |
| 186.84.172.25 | attackbots | Jul 20 22:42:03 h2427292 sshd\[20029\]: Invalid user zhg from 186.84.172.25 Jul 20 22:42:03 h2427292 sshd\[20029\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.84.172.25 Jul 20 22:42:05 h2427292 sshd\[20029\]: Failed password for invalid user zhg from 186.84.172.25 port 46352 ssh2 ... |
2020-07-21 07:13:19 |
| 40.122.44.9 | attack | " " |
2020-07-21 06:56:07 |
| 201.249.50.74 | attackbots | Jul 21 00:46:09 vpn01 sshd[14996]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.249.50.74 Jul 21 00:46:12 vpn01 sshd[14996]: Failed password for invalid user odoo from 201.249.50.74 port 36737 ssh2 ... |
2020-07-21 07:11:21 |
| 41.165.88.132 | attack | $f2bV_matches |
2020-07-21 07:14:10 |
| 184.168.46.186 | attackbots | C2,WP GET /oldsite/wp-includes/wlwmanifest.xml |
2020-07-21 07:22:56 |
| 190.85.54.158 | attack | 1035. On Jul 20 2020 experienced a Brute Force SSH login attempt -> 1 unique times by 190.85.54.158. |
2020-07-21 07:07:51 |
| 167.172.243.126 | attack | Invalid user nag from 167.172.243.126 port 34910 |
2020-07-21 07:25:22 |
| 111.72.196.37 | attack | Jul 20 23:53:55 srv01 postfix/smtpd\[6360\]: warning: unknown\[111.72.196.37\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 20 23:57:24 srv01 postfix/smtpd\[5783\]: warning: unknown\[111.72.196.37\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 21 00:00:52 srv01 postfix/smtpd\[8728\]: warning: unknown\[111.72.196.37\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 21 00:04:21 srv01 postfix/smtpd\[8737\]: warning: unknown\[111.72.196.37\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 21 00:11:17 srv01 postfix/smtpd\[32712\]: warning: unknown\[111.72.196.37\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-07-21 07:23:14 |
| 139.162.247.56 | attackbots |
|
2020-07-21 07:26:26 |
| 193.122.163.81 | attack | Jul 21 00:49:04 vpn01 sshd[15040]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.122.163.81 Jul 21 00:49:05 vpn01 sshd[15040]: Failed password for invalid user moritz from 193.122.163.81 port 38106 ssh2 ... |
2020-07-21 07:28:56 |
| 31.129.68.164 | attackbotsspam | SSH Invalid Login |
2020-07-21 07:09:59 |