WHOIS
Lookup an IP or domain. Uses IANA referral first, then registry WHOIS.
### IANA response (whois.iana.org) % IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object refer: whois.lacnic.net inetnum: 200.0.0.0 - 200.255.255.255 organisation: LACNIC status: ALLOCATED whois: whois.lacnic.net changed: 2002-11 source: IANA ### Registry response (whois.lacnic.net) % IP Client: 2001:41d0:305:2100:0:0:0:5cfe % 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-03-25 11:29:34 (-03 -03:00) inetnum: 200.91.0.0/19 status: allocated aut-num: AS7004 owner: TELEFÓNICA CHILE S.A. ownerid: CL-TCSA41-LACNIC responsible: Technical Contact Telefonica Chile S.A. address: AVENIDA PROVIDENCIA, 111, COMUNA DE PROVIDENCIA address: 7500775 - SANTIAGO - RM country: CL phone: +56 2 3306932 owner-c: TCS5 tech-c: TCS5 abuse-c: TCS5 inetrev: 200.91.0.0/24 nserver: NSAUT.TIE.CL nsstat: 20260323 AA nslastaa: 20260323 inetrev: 200.91.16.0/24 nserver: NS1.GISC.CL [lame - not published] nsstat: 20260325 UH nslastaa: 20240915 nserver: NS2.GISC.CL [lame - not published] nsstat: 20260325 UH nslastaa: 20191225 inetrev: 200.91.17.0/24 nserver: NS1.GISC.CL [lame - not published] nsstat: 20260325 UH nslastaa: 20240914 nserver: NS2.GISC.CL [lame - not published] nsstat: 20260325 UH nslastaa: 20170601 inetrev: 200.91.18.0/24 nserver: NS1.GISC.CL [lame - not published] nsstat: 20260323 UH nslastaa: 20240916 nserver: NS2.GISC.CL [lame - not published] nsstat: 20260323 UH nslastaa: 20170603 inetrev: 200.91.19.0/24 nserver: NS1.GISC.CL [lame - not published] nsstat: 20260325 UH nslastaa: 20240915 nserver: NS2.GISC.CL [lame - not published] nsstat: 20260325 UH nslastaa: 20170531 inetrev: 200.91.28.0/24 nserver: ACCESS.INTERCITY.CL nsstat: 20260324 AA nslastaa: 20260324 nserver: MERLIN.INTERCITY.CL nsstat: 20260324 AA nslastaa: 20260324 inetrev: 200.91.7.0/24 nserver: ACCESS.INTERCITY.CL nsstat: 20260321 AA nslastaa: 20260321 nserver: MERLIN.INTERCITY.CL nsstat: 20260321 AA nslastaa: 20260321 inetrev: 200.91.3.0/24 nserver: MERLIN.INTERCITY.CL nsstat: 20260322 AA nslastaa: 20260322 inetrev: 200.91.14.0/24 nserver: ARMAGEDON.UDELMAR.CL [lame - not published] nsstat: 20260323 TIMEOUT nslastaa: 20130725 inetrev: 200.91.1.0/24 nserver: NSAUT.TIE.CL nsstat: 20260323 AA nslastaa: 20260323 inetrev: 200.91.4.0/24 nserver: ACCESS.INTERCITY.CL [lame - not published] nsstat: 20260323 UDN nslastaa: 20100808 nserver: MERLIN.INTERCITY.CL [lame - not published] nsstat: 20260323 UDN nslastaa: 20100803 inetrev: 200.91.24.0/24 nserver: NS.UTALCA.CL nsstat: 20260325 AA nslastaa: 20260325 inetrev: 200.91.25.0/24 nserver: NS.UTALCA.CL nsstat: 20260325 AA nslastaa: 20260325 inetrev: 200.91.26.0/24 nserver: NS.UTALCA.CL nsstat: 20260321 AA nslastaa: 20260321 inetrev: 200.91.15.0/24 nserver: NSAUT.TIE.CL nsstat: 20260324 AA nslastaa: 20260324 inetrev: 200.91.9.0/24 nserver: NSAUT.TIE.CL nsstat: 20260322 AA nslastaa: 20260322 inetrev: 200.91.30.0/24 nserver: NSAUT.TIE.CL nsstat: 20260325 AA nslastaa: 20260325 inetrev: 200.91.29.0/24 nserver: QIP1.REDIP.CL nsstat: 20260321 AA nslastaa: 20260321 inetrev: 200.91.12.0/24 nserver: NSAUT.TIE.CL nsstat: 20260324 AA nslastaa: 20260324 inetrev: 200.91.20.0/24 nserver: NSAUT.TIE.CL nsstat: 20260324 AA nslastaa: 20260324 inetrev: 200.91.13.0/24 nserver: NSAUT.TIE.CL nsstat: 20260324 AA nslastaa: 20260324 inetrev: 200.91.2.0/24 nserver: NSAUT.TIE.CL nsstat: 20260320 AA nslastaa: 20260320 inetrev: 200.91.5.0/24 nserver: NSAUT.TIE.CL nsstat: 20260324 AA nslastaa: 20260324 inetrev: 200.91.6.0/24 nserver: NSAUT.TIE.CL nsstat: 20260324 AA nslastaa: 20260324 inetrev: 200.91.8.0/24 nserver: NSAUT.TIE.CL nsstat: 20260323 AA nslastaa: 20260323 inetrev: 200.91.10.0/23 nserver: NSAUT.TIE.CL nsstat: 20260323 AA nslastaa: 20260323 inetrev: 200.91.21.0/24 nserver: NSAUT.TIE.CL nsstat: 20260322 AA nslastaa: 20260322 inetrev: 200.91.22.0/23 nserver: NSAUT.TIE.CL nsstat: 20260321 AA nslastaa: 20260321 inetrev: 200.91.31.0/24 nserver: NSAUT.TIE.CL nsstat: 20260325 AA nslastaa: 20260325 created: 20021008 changed: 20241223 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.
Frequently Asked Questions
What is WHOIS?
WHOIS is a protocol that queries databases to find the registered owner of a domain name or IP address. It reveals the registrar, registration dates, nameservers, and contact information associated with a domain or IP block.
Is WHOIS data always accurate?
Not always. Many domain registrars offer WHOIS privacy protection that replaces the registrant's personal details with proxy information. IP WHOIS data from Regional Internet Registries (RIRs) is generally more reliable than domain WHOIS data.
Can I use WHOIS to find who owns an IP address?
Yes. Enter any IP address into the WHOIS tool to find the organization that owns the IP block, the Regional Internet Registry (ARIN, RIPE, APNIC, etc.) that allocated it, and the network range it belongs to.
What is the difference between domain WHOIS and IP WHOIS?
Domain WHOIS shows registration details like the registrar, creation date, expiry date, and nameservers. IP WHOIS shows the network allocation, the organization that owns the IP block, and the abuse contact for reporting issues.
Why does WHOIS show privacy protection instead of real details?
Domain registrars offer WHOIS privacy services to protect registrants from spam, identity theft, and unwanted contact. GDPR regulations in Europe also require redaction of personal data from WHOIS records.
How often is WHOIS data updated?
WHOIS data is updated by the registrar or registry whenever changes are made to a domain or IP registration. Our tool queries the authoritative WHOIS server in real-time, with results cached for 7 days to reduce server load.
Related tools
- DNS Dig Lookup — query A, MX, NS, TXT and other DNS records
- DNS Privacy Check — test your DNS for leaks and encryption
- DNS Speed Test — benchmark DNS latency from your browser
- DNS servers by country
- Best private DNS