Whois & RDAP Lookup
PROXIED.COM Dedicated mobile proxies 4G/5G proxies · No caps Dedicated 4G/5G mobile proxies · Direct from trusted sellers Mobile 4G/5G · Dedicated, no sharing Uptime 99.9% · 10 countries Data Unlimited · No caps Customers 20K+ · No middlemen Free/trial Explore marketTry free170.82.132.0/24
RDAPIP Range170.82.132.0 - 170.82.135.255
Handle170.82.132.0/22
Name520931
TypeALLOCATED
CountryBR
HolderAlares Cabo Servicos de Telecomunicacoes S.A.
Registered2016-12-22 15:43 UTC
Updated2026-01-27 19:22 UTC
RegistrantAlares Cabo Servicos de Telecomunicacoes S.A.
Admin ContactAnderson Mendes Jacopetti
Tech ContactAdm. de Redes - Cabo Telecom
Abuse Contact[email protected]
Statusactive
Registry RDAPhttp://rdap.arin.net
Raw WHOIS response
# # 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: 170.82.0.0 - 170.82.255.255 CIDR: 170.82.0.0/16 NetName: LACNIC-ERX-170-82-0-0 NetHandle: NET-170-82-0-0-1 Parent: NET170 (NET-170-0-0-0-0) NetType: Transferred to LACNIC OriginAS: Organization: Latin American and Caribbean IP address Regional Registry (LACNIC) RegDate: 2010-11-03 Updated: 2010-11-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/170.82.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: [email protected] OrgAbuseRef: https://rdap.arin.net/registry/entity/LWI100-ARIN OrgTechHandle: LACNIC-ARIN OrgTechName: LACNIC Whois Info OrgTechPhone: +598-2604-2222 OrgTechEmail: [email protected] 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. # % IP Client: 146.19.19.88 % 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. % 2026-07-31T01:27:50-03:00 - 146.19.19.88 inetnum: 170.82.132.0/22 aut-num: AS28220 abuse-c: TICTE2 owner: Alares Cabo Servicos de Telecomunicacoes S.A. ownerid: 02.952.192/0001-61 responsible: Denis Ferreira owner-c: ANMJA46 tech-c: ARCTE inetrev: 170.82.132.0/22 nserver: ns1.webbytelecom.com.br nsstat: 20260727 AA nslastaa: 20260727 nserver: ns2.webbytelecom.com.br nsstat: 20260727 AA nslastaa: 20260727 created: 20161222 changed: 20260127 nic-hdl-br: ANMJA46 person: Anderson Mendes Jacopetti created: 20251104 changed: 20251104 nic-hdl-br: ARCTE person: Adm. de Redes - Cabo Telecom created: 20080927 changed: 20251010 nic-hdl-br: TICTE2 person: Tratamento de Incidentes - Cabo Telecom created: 20131105 changed: 20211022 % Security and mail abuse issues should also be addressed to cert.br, % respectivelly to [email protected] and [email protected] % % whois.registro.br only accepts exact match queries for domains, % registrants, contacts, tickets, providers, IPs, and ASNs. % Query time: 1094 msec % WHEN: Fri Jul 31 04:27:50 UTC 2026
Raw RDAP JSON (registry) http://rdap.arin.net
{
"cidr0_cidrs": [
{
"length": "22",
"v4prefix": "170.82.132.0"
}
],
"country": "BR",
"endAddress": "170.82.135.255",
"entities": [
{
"entities": [
{
"events": [
{
"eventAction": "registration",
"eventDate": "2025-11-04T14:40:54Z"
},
{
"eventAction": "last changed",
"eventDate": "2025-11-04T14:44:57Z"
}
],
"handle": "ANMJA46",
"objectClassName": "entity",
"roles": [
"administrative"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"kind",
{},
"text",
"individual"
],
[
"fn",
{},
"text",
"Anderson Mendes Jacopetti"
],
[
"lang",
{},
"language-tag",
"pt"
]
]
]
}
],
"events": [
{
"eventAction": "registration",
"eventDate": "2000-04-05T12:00:00Z"
},
{
"eventAction": "last changed",
"eventDate": "2025-11-19T22:08:18Z"
}
],
"handle": "02952192000161",
"legalRepresentative": "Denis Ferreira",
"links": [
{
"href": "https://rdap.registro.br/entity/02952192000161",
"rel": "self",
"type": "application/rdap+json",
"value": "https://rdap.registro.br/entity/02952192000161"
}
],
"objectClassName": "entity",
"publicIds": [
{
"identifier": "02.952.192/0001-61",
"type": "cnpj"
}
],
"roles": [
"registrant"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"kind",
{},
"text",
"org"
],
[
"fn",
{},
"text",
"Alares Cabo Servicos de Telecomunicacoes S.A."
]
]
]
},
{
"events": [
{
"eventAction": "registration",
"eventDate": "2008-09-27T15:01:27Z"
},
{
"eventAction": "last changed",
"eventDate": "2025-10-10T13:34:06Z"
}
],
"handle": "ARCTE",
"objectClassName": "entity",
"roles": [
"technical"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"kind",
{},
"text",
"individual"
],
[
"fn",
{},
"text",
"Adm. de Redes - Cabo Telecom"
],
[
"lang",
{},
"language-tag",
"pt"
]
]
]
},
{
"events": [
{
"eventAction": "registration",
"eventDate": "2013-11-05T18:24:30Z"
},
{
"eventAction": "last changed",
"eventDate": "2021-10-22T19:51:37Z"
}
],
"handle": "TICTE2",
"objectClassName": "entity",
"roles": [
"abuse"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"kind",
{},
"text",
"individual"
],
[
"fn",
{},
"text",
"Tratamento de Incidentes - Cabo Telecom"
],
[
"lang",
{},
"language-tag",
"pt"
]
]
]
}
],
"events": [
{
"eventAction": "registration",
"eventDate": "2016-12-22T15:43:37Z"
},
{
"eventAction": "last changed",
"eventDate": "2026-01-27T19:22:59Z"
}
],
"handle": "170.82.132.0/22",
"ipVersion": "v4",
"links": [
{
"href": "https://rdap.registro.br/ip/170.82.132.0/22",
"rel": "self",
"type": "application/rdap+json",
"value": "https://rdap.registro.br/ip/170.82.132.0/22"
},
{
"href": "https://rdap.registro.br/domain/132.82.170.in-addr.arpa",
"rel": "related",
"type": "application/rdap+json",
"value": "https://rdap.registro.br/ip/170.82.132.0/22"
},
{
"href": "https://rdap.registro.br/domain/133.82.170.in-addr.arpa",
"rel": "related",
"type": "application/rdap+json",
"value": "https://rdap.registro.br/ip/170.82.132.0/22"
},
{
"href": "https://rdap.registro.br/domain/134.82.170.in-addr.arpa",
"rel": "related",
"type": "application/rdap+json",
"value": "https://rdap.registro.br/ip/170.82.132.0/22"
},
{
"href": "https://rdap.registro.br/domain/135.82.170.in-addr.arpa",
"rel": "related",
"type": "application/rdap+json",
"value": "https://rdap.registro.br/ip/170.82.132.0/22"
}
],
"name": "520931",
"nicbr_autnum": 28220,
"nicbr_reverseDelegations": [
{
"endAddress": "170.82.135.255",
"events": [
{
"eventAction": "registration",
"eventDate": "2025-05-21T11:53:41Z"
},
{
"eventAction": "last changed",
"eventDate": "2025-05-21T11:53:41Z"
}
],
"nameservers": [
{
"events": [
{
"eventAction": "delegation check",
"eventDate": "2026-07-27T12:00:00Z",
"status": [
"ns aa"
]
},
{
"eventAction": "last correct delegation check",
"eventDate": "2026-07-27T12:00:00Z"
}
],
"ldhName": "ns1.webbytelecom.com.br",
"objectClassName": "nameserver"
},
{
"events": [
{
"eventAction": "delegation check",
"eventDate": "2026-07-27T12:00:00Z",
"status": [
"ns aa"
]
},
{
"eventAction": "last correct delegation check",
"eventDate": "2026-07-27T12:00:00Z"
}
],
"ldhName": "ns2.webbytelecom.com.br",
"objectClassName": "nameserver"
}
],
"secureDNS": {
"delegationSigned": false
},
"startAddress": "170.82.132.0"
}
],
"notices": [
{
"description": [
"Copyright (c) Nic.br - Use of this data is governed by the Use and Privacy Policy. Distribution, commercialization, reproduction, and use for advertising or similar purposes are expressly prohibited.",
"2026-07-31T01:27:57-03:00 - 146.19.19.88"
],
"links": [
{
"href": "https://registro.br/upp",
"rel": "alternate",
"type": "text/html",
"value": "https://rdap.registro.br/ip/170.82.132.0/22"
}
],
"title": "Use and Privacy Policy"
}
],
"objectClassName": "ip network",
"port43": "whois.registro.br",
"rdapConformance": [
"rdap_level_0",
"nicbr_level_0",
"cidr0"
],
"remarks": [
{
"description": [
"Some of the data in this object has been removed."
],
"type": "object truncated due to server policy"
}
],
"startAddress": "170.82.132.0",
"status": [
"active"
],
"type": "ALLOCATED"
}Frequently asked questions
What is WHOIS?
WHOIS is a public directory that answers "who is responsible for this?" for domains, IP ranges and ASNs. It lists registration dates, the registrar, nameservers and contacts.
What is RDAP, and how does it differ?
RDAP is the modern replacement for WHOIS. It returns the same records in a structured, consistent format. We query RDAP first and fall back to classic WHOIS text when a registry has not adopted it yet.
What is the difference between a registrar and a registrant?
The registrar is the company you register and manage a domain through, such as xTom or GoDaddy. The registrant is the person or organization that actually holds the domain.
What are nameservers?
Nameservers answer DNS questions for a domain and decide which IP addresses the name resolves to. They also show which DNS provider the domain uses.
What is DNSSEC?
DNSSEC adds cryptographic signatures to DNS answers so they cannot be quietly altered in transit. "Signed" means the domain has it enabled, "unsigned" means it does not.
Why is the contact information redacted?
Privacy laws such as GDPR require registrars to hide most personal details in public records. The abuse contact is usually still shown, so a domain or network can be reported when something goes wrong.