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.
% 2025-11-10 12:51:43 (-03 -03:00)
inetnum: 181.212.0.0/16
status: allocated
aut-num: AS16629
owner: TELEFONICA EMPRESAS CHILE SA
ownerid: CL-TEEM-LACNIC
responsible: Technical Contact
address: Providencia, 119, Piso 8
address: 00 - Santiago -
country: CL
phone: +56 02 6912000 [7562]
owner-c: TCS5
tech-c: TCS5
abuse-c: TCS5
inetrev: 181.212.0.0/16
nserver: QIP1.REDIP.CL
nsstat: 20251108 AA
nslastaa: 20251108
nserver: QIP2.REDIP.CL
nsstat: 20251108 AA
nslastaa: 20251108
created: 20140612
changed: 20240126
nic-hdl: TCS5
person: Technical Contact Telefonica Chile
e-mail: tecnical.isp.movistar@gmail.com
address: Providencia, 111, Piso 3
address: 8320215 - santiago - Metropolitana
country: CL
phone: +56 26616815 [0000]
created: 20110502
changed: 20240418
% 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 <<>> 181.212.118.122
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62132
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;181.212.118.122. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025111000 1800 900 604800 86400
;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Nov 10 23:42:48 CST 2025
;; MSG SIZE rcvd: 108b'122.118.212.181.in-addr.arpa domain name pointer 181-212-118-122.baf.movistar.cl.
'Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
122.118.212.181.in-addr.arpa name = 181-212-118-122.baf.movistar.cl.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 103.1.93.63 | attackbotsspam | 2019-09-19T11:55:21.474206+01:00 suse sshd[19695]: Invalid user admin from 103.1.93.63 port 41201 2019-09-19T11:55:24.973893+01:00 suse sshd[19695]: error: PAM: User not known to the underlying authentication module for illegal user admin from 103.1.93.63 2019-09-19T11:55:21.474206+01:00 suse sshd[19695]: Invalid user admin from 103.1.93.63 port 41201 2019-09-19T11:55:24.973893+01:00 suse sshd[19695]: error: PAM: User not known to the underlying authentication module for illegal user admin from 103.1.93.63 2019-09-19T11:55:21.474206+01:00 suse sshd[19695]: Invalid user admin from 103.1.93.63 port 41201 2019-09-19T11:55:24.973893+01:00 suse sshd[19695]: error: PAM: User not known to the underlying authentication module for illegal user admin from 103.1.93.63 2019-09-19T11:55:24.975522+01:00 suse sshd[19695]: Failed keyboard-interactive/pam for invalid user admin from 103.1.93.63 port 41201 ssh2 ... |
2019-09-19 20:54:31 |
| 46.0.203.166 | attack | 2019-09-19T08:46:11.4004351495-001 sshd\[25976\]: Invalid user zaq12wsx from 46.0.203.166 port 56960 2019-09-19T08:46:11.4082681495-001 sshd\[25976\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.0.203.166 2019-09-19T08:46:13.6894171495-001 sshd\[25976\]: Failed password for invalid user zaq12wsx from 46.0.203.166 port 56960 ssh2 2019-09-19T08:50:29.6260991495-001 sshd\[26165\]: Invalid user 111111 from 46.0.203.166 port 44024 2019-09-19T08:50:29.6333441495-001 sshd\[26165\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.0.203.166 2019-09-19T08:50:31.3323711495-001 sshd\[26165\]: Failed password for invalid user 111111 from 46.0.203.166 port 44024 ssh2 ... |
2019-09-19 21:01:48 |
| 186.22.139.238 | attackbotsspam | Attempt to attack host OS, exploiting network vulnerabilities, on 19-09-2019 11:55:38. |
2019-09-19 21:09:12 |
| 103.89.90.196 | attack | Sep 19 13:59:27 andromeda postfix/smtpd\[26115\]: warning: unknown\[103.89.90.196\]: SASL LOGIN authentication failed: authentication failure Sep 19 13:59:28 andromeda postfix/smtpd\[26115\]: warning: unknown\[103.89.90.196\]: SASL LOGIN authentication failed: authentication failure Sep 19 13:59:30 andromeda postfix/smtpd\[26115\]: warning: unknown\[103.89.90.196\]: SASL LOGIN authentication failed: authentication failure Sep 19 13:59:31 andromeda postfix/smtpd\[26115\]: warning: unknown\[103.89.90.196\]: SASL LOGIN authentication failed: authentication failure Sep 19 13:59:32 andromeda postfix/smtpd\[26115\]: warning: unknown\[103.89.90.196\]: SASL LOGIN authentication failed: authentication failure |
2019-09-19 20:31:50 |
| 62.210.8.131 | attack | DATE:2019-09-19 12:56:13, IP:62.210.8.131, PORT:5900 - VNC brute force auth on a honeypot server (epe-dc) |
2019-09-19 20:48:58 |
| 104.128.69.146 | attackbotsspam | Sep 19 08:33:09 vps200512 sshd\[24154\]: Invalid user ftp from 104.128.69.146 Sep 19 08:33:09 vps200512 sshd\[24154\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.128.69.146 Sep 19 08:33:11 vps200512 sshd\[24154\]: Failed password for invalid user ftp from 104.128.69.146 port 36374 ssh2 Sep 19 08:37:16 vps200512 sshd\[24248\]: Invalid user phion from 104.128.69.146 Sep 19 08:37:16 vps200512 sshd\[24248\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.128.69.146 |
2019-09-19 20:40:00 |
| 165.227.9.145 | attack | Jan 17 08:31:46 vtv3 sshd\[9696\]: Invalid user rudo from 165.227.9.145 port 34512 Jan 17 08:31:46 vtv3 sshd\[9696\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.9.145 Jan 17 08:31:48 vtv3 sshd\[9696\]: Failed password for invalid user rudo from 165.227.9.145 port 34512 ssh2 Jan 17 08:35:58 vtv3 sshd\[10967\]: Invalid user sbin from 165.227.9.145 port 35028 Jan 17 08:35:58 vtv3 sshd\[10967\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.9.145 Jan 19 09:19:41 vtv3 sshd\[28257\]: Invalid user lidio from 165.227.9.145 port 46652 Jan 19 09:19:41 vtv3 sshd\[28257\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.9.145 Jan 19 09:19:43 vtv3 sshd\[28257\]: Failed password for invalid user lidio from 165.227.9.145 port 46652 ssh2 Jan 19 09:23:27 vtv3 sshd\[29738\]: Invalid user bot from 165.227.9.145 port 46576 Jan 19 09:23:27 vtv3 sshd\[29738\]: pam_unix\(ssh |
2019-09-19 20:30:13 |
| 58.62.207.51 | attack | Sep 19 12:44:11 apollo sshd\[2506\]: Invalid user white from 58.62.207.51Sep 19 12:44:12 apollo sshd\[2506\]: Failed password for invalid user white from 58.62.207.51 port 16132 ssh2Sep 19 12:56:13 apollo sshd\[2753\]: Invalid user oracle from 58.62.207.51 ... |
2019-09-19 20:46:14 |
| 104.250.105.118 | attack | Sep 19 14:16:35 ns37 sshd[22503]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.250.105.118 |
2019-09-19 21:02:46 |
| 210.212.162.140 | attack | Attempt to attack host OS, exploiting network vulnerabilities, on 19-09-2019 11:56:00. |
2019-09-19 20:50:06 |
| 187.130.75.23 | attackbots | Attempt to attack host OS, exploiting network vulnerabilities, on 19-09-2019 11:55:47. |
2019-09-19 21:07:39 |
| 162.247.74.217 | attackbotsspam | Sep 19 10:56:04 thevastnessof sshd[6471]: Failed password for root from 162.247.74.217 port 34004 ssh2 ... |
2019-09-19 20:53:13 |
| 185.158.0.161 | attackspam | 2019-09-19T11:55:15.741565+01:00 suse sshd[19664]: User root from 185.158.0.161 not allowed because not listed in AllowUsers 2019-09-19T11:55:18.586914+01:00 suse sshd[19664]: error: PAM: Authentication failure for illegal user root from 185.158.0.161 2019-09-19T11:55:15.741565+01:00 suse sshd[19664]: User root from 185.158.0.161 not allowed because not listed in AllowUsers 2019-09-19T11:55:18.586914+01:00 suse sshd[19664]: error: PAM: Authentication failure for illegal user root from 185.158.0.161 2019-09-19T11:55:15.741565+01:00 suse sshd[19664]: User root from 185.158.0.161 not allowed because not listed in AllowUsers 2019-09-19T11:55:18.586914+01:00 suse sshd[19664]: error: PAM: Authentication failure for illegal user root from 185.158.0.161 2019-09-19T11:55:18.588633+01:00 suse sshd[19664]: Failed keyboard-interactive/pam for invalid user root from 185.158.0.161 port 40609 ssh2 ... |
2019-09-19 20:58:56 |
| 188.54.142.61 | attackbotsspam | Attempt to attack host OS, exploiting network vulnerabilities, on 19-09-2019 11:55:48. |
2019-09-19 21:05:24 |
| 192.168.100.254 | attack | Attempt to attack host OS, exploiting network vulnerabilities, on 19-09-2019 13:49:13. |
2019-09-19 21:02:08 |