City: unknown
Region: unknown
Country: Peru
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b'#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
NetRange: 161.131.0.0 - 161.132.255.255
CIDR: 161.132.0.0/16, 161.131.0.0/16
NetName: LACNIC-ERX-161-131-0-0
NetHandle: NET-161-131-0-0-1
Parent: NET161 (NET-161-0-0-0-0)
NetType: Transferred to LACNIC
OriginAS:
Organization: Latin American and Caribbean IP address Regional Registry (LACNIC)
RegDate: 2004-02-18
Updated: 2007-12-17
Comment: This IP address range is under LACNIC responsibility
Comment: for further allocations to users in LACNIC region.
Comment: Please see http://www.lacnic.net/ for further details,
Comment: or check the WHOIS server located at http://whois.lacnic.net
Ref: https://rdap.arin.net/registry/ip/161.131.0.0
ResourceLink: http://lacnic.net/cgi-bin/lacnic/whois
ResourceLink: whois.lacnic.net
OrgName: Latin American and Caribbean IP address Regional Registry
OrgId: LACNIC
Address: Rambla Republica de Mexico 6125
City: Montevideo
StateProv:
PostalCode: 11400
Country: UY
RegDate: 2002-07-27
Updated: 2018-03-15
Ref: https://rdap.arin.net/registry/entity/LACNIC
ReferralServer: whois://whois.lacnic.net
ResourceLink: http://lacnic.net/cgi-bin/lacnic/whois
OrgAbuseHandle: LWI100-ARIN
OrgAbuseName: LACNIC Whois Info
OrgAbusePhone: +598-2604-2222
OrgAbuseEmail: abuse@lacnic.net
OrgAbuseRef: https://rdap.arin.net/registry/entity/LWI100-ARIN
OrgTechHandle: LACNIC-ARIN
OrgTechName: LACNIC Whois Info
OrgTechPhone: +598-2604-2222
OrgTechEmail: whois-contact@lacnic.net
OrgTechRef: https://rdap.arin.net/registry/entity/LACNIC-ARIN
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
Found a referral to whois.lacnic.net.
% IP Client: 8.214.16.196
% 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-06-25 03:05:45 (-03 -03:00)
inetnum: 161.132.0.0/16
status: assigned
aut-num: N/A
owner: Red Cientifica Peruana
ownerid: PE-RCPE4-LACNIC
responsible: Ruben Rodriguez
address: Jiron Gonzales Prada, 585,
address: L27 - Lima -
country: PE
phone: +51 1 7020138
owner-c: RUR4
tech-c: RUR4
abuse-c: RUR4
inetrev: 161.132.0.0/16
nserver: ICHU.RCP.NET.PE
nsstat: 20260622 AA
nslastaa: 20260622
nserver: NS.RCP.NET.PE
nsstat: 20260622 AA
nslastaa: 20260622
created: 19920824
changed: 20020110
nic-hdl: RUR4
person: Ruben Rodriguez
e-mail: rrodriguez@rcp.pe
address: Av. La Paz 1049, 585, -
address: 15074 - Lima, Miraflores - Lima
country: PE
phone: +51 17020138 [0000]
created: 20090722
changed: 20260305
% 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 <<>> 161.132.53.68
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51124
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;161.132.53.68. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026062500 1800 900 604800 86400
;; Query time: 5 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jun 25 14:00:29 CST 2026
;; MSG SIZE rcvd: 106Host 68.53.132.161.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 68.53.132.161.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 145.239.88.43 | attackbots | Sep 6 16:21:42 SilenceServices sshd[10285]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.88.43 Sep 6 16:21:44 SilenceServices sshd[10285]: Failed password for invalid user daniel from 145.239.88.43 port 49346 ssh2 Sep 6 16:25:56 SilenceServices sshd[11871]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=145.239.88.43 |
2019-09-07 04:05:03 |
| 206.189.122.133 | attackbotsspam | Sep 6 17:46:44 game-panel sshd[27456]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.122.133 Sep 6 17:46:46 game-panel sshd[27456]: Failed password for invalid user demo1 from 206.189.122.133 port 50072 ssh2 Sep 6 17:51:04 game-panel sshd[27653]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.122.133 |
2019-09-07 03:49:01 |
| 190.134.35.73 | attackspam | Automatic report - Port Scan Attack |
2019-09-07 04:00:44 |
| 167.71.5.49 | attackbots | Sep 6 22:18:42 meumeu sshd[9936]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.5.49 Sep 6 22:18:44 meumeu sshd[9936]: Failed password for invalid user 123 from 167.71.5.49 port 61549 ssh2 Sep 6 22:22:46 meumeu sshd[10438]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.5.49 ... |
2019-09-07 04:24:22 |
| 134.175.80.27 | attackbots | Sep 6 21:15:23 areeb-Workstation sshd[6409]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.80.27 Sep 6 21:15:25 areeb-Workstation sshd[6409]: Failed password for invalid user ubuntu from 134.175.80.27 port 37006 ssh2 ... |
2019-09-07 04:18:24 |
| 159.65.70.218 | attack | SSH Brute Force |
2019-09-07 04:25:12 |
| 91.223.136.228 | attackbotsspam | Chat Spam |
2019-09-07 03:46:08 |
| 185.235.244.251 | attackspam | firewall-block, port(s): 2508/tcp, 2879/tcp, 4040/tcp, 4680/tcp, 5610/tcp, 5643/tcp, 5712/tcp, 8169/tcp, 8601/tcp, 9434/tcp, 9876/tcp, 10002/tcp, 10203/tcp, 10432/tcp, 11511/tcp, 16116/tcp, 18108/tcp |
2019-09-07 03:47:03 |
| 60.183.249.196 | attack | SSH invalid-user multiple login try |
2019-09-07 04:11:50 |
| 176.118.51.74 | attack | Chat Spam |
2019-09-07 04:03:23 |
| 42.117.20.176 | attackspam | Honeypot attack, port: 23, PTR: PTR record not found |
2019-09-07 04:32:39 |
| 46.101.26.63 | attackbotsspam | Sep 6 10:12:30 kapalua sshd\[25004\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.26.63 user=root Sep 6 10:12:32 kapalua sshd\[25004\]: Failed password for root from 46.101.26.63 port 46882 ssh2 Sep 6 10:16:42 kapalua sshd\[25527\]: Invalid user admin from 46.101.26.63 Sep 6 10:16:42 kapalua sshd\[25527\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.101.26.63 Sep 6 10:16:44 kapalua sshd\[25527\]: Failed password for invalid user admin from 46.101.26.63 port 39958 ssh2 |
2019-09-07 04:29:50 |
| 178.128.87.28 | attackspam | Sep 6 21:41:49 lenivpn01 kernel: \[31724.455400\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:2f:6c:1b:d2:74:7f:6e:37:e3:08:00 SRC=178.128.87.28 DST=195.201.121.15 LEN=60 TOS=0x00 PREC=0x40 TTL=51 ID=49129 DF PROTO=TCP SPT=46746 DPT=22 WINDOW=14600 RES=0x00 SYN URGP=0 Sep 6 21:41:50 lenivpn01 kernel: \[31725.455034\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:2f:6c:1b:d2:74:7f:6e:37:e3:08:00 SRC=178.128.87.28 DST=195.201.121.15 LEN=60 TOS=0x00 PREC=0x40 TTL=51 ID=49130 DF PROTO=TCP SPT=46746 DPT=22 WINDOW=14600 RES=0x00 SYN URGP=0 Sep 6 21:41:52 lenivpn01 kernel: \[31727.454977\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:2f:6c:1b:d2:74:7f:6e:37:e3:08:00 SRC=178.128.87.28 DST=195.201.121.15 LEN=60 TOS=0x00 PREC=0x40 TTL=51 ID=49131 DF PROTO=TCP SPT=46746 DPT=22 WINDOW=14600 RES=0x00 SYN URGP=0 ... |
2019-09-07 03:52:58 |
| 159.89.229.244 | attackbots | Sep 6 15:49:22 xtremcommunity sshd\[27655\]: Invalid user P@$$word from 159.89.229.244 port 43200 Sep 6 15:49:22 xtremcommunity sshd\[27655\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.229.244 Sep 6 15:49:24 xtremcommunity sshd\[27655\]: Failed password for invalid user P@$$word from 159.89.229.244 port 43200 ssh2 Sep 6 15:53:51 xtremcommunity sshd\[27788\]: Invalid user abc123 from 159.89.229.244 port 58518 Sep 6 15:53:51 xtremcommunity sshd\[27788\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.229.244 ... |
2019-09-07 03:58:13 |
| 195.154.38.177 | attackbots | Sep 6 20:13:32 hcbbdb sshd\[28260\]: Invalid user asteriskuser from 195.154.38.177 Sep 6 20:13:32 hcbbdb sshd\[28260\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.154.38.177 Sep 6 20:13:33 hcbbdb sshd\[28260\]: Failed password for invalid user asteriskuser from 195.154.38.177 port 33220 ssh2 Sep 6 20:17:20 hcbbdb sshd\[28668\]: Invalid user testuser from 195.154.38.177 Sep 6 20:17:20 hcbbdb sshd\[28668\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.154.38.177 |
2019-09-07 04:17:29 |