IP Whois
Network registration, geolocation, and abuse contact information.
Network Information
Network Information
The range of IP addresses allocated as a single block. NetRange shows start/end IPs (192.0.2.0 - 192.0.2.255), CIDR uses slash notation (192.0.2.0/24).
How to Interpret
/24 = 256 IPs (small organizations), /22 = 1,024 IPs (larger businesses), /16 = 65,536 IPs (large ISPs), /8 = 16.7 million IPs (extremely large).
Network Information
The range of IP addresses allocated as a single block. NetRange shows start/end IPs (192.0.2.0 - 192.0.2.255), CIDR uses slash notation (192.0.2.0/24).
How to Interpret
/24 = 256 IPs (small organizations), /22 = 1,024 IPs (larger businesses), /16 = 65,536 IPs (large ISPs), /8 = 16.7 million IPs (extremely large).
Organization
Organization
The legal entity that controls this IP address block. This is the actual owner or operator of the network infrastructure.
How to Interpret
ISP names (Comcast, AT&T) indicate residential/business customers. Cloud providers (Amazon, Microsoft) indicate hosting infrastructure. Direct organizations operate their own networks.
Organization
The legal entity that controls this IP address block. This is the actual owner or operator of the network infrastructure.
How to Interpret
ISP names (Comcast, AT&T) indicate residential/business customers. Cloud providers (Amazon, Microsoft) indicate hosting infrastructure. Direct organizations operate their own networks.
Geolocation
Geolocation
Physical location where the IP address is being used, determined by geolocation databases. This differs from WHOIS registration data, which shows ownership.
What You'll See
- City, region, and country of the server/device
- Coordinates with link to map
- Timezone and postal code
- ISP and organization operating at that location
- Security flags: Proxy, VPN, Tor, Hosting/Datacenter
Diagnostic Value
- Identify actual server location for latency/compliance
- Detect VPNs, proxies, and hosting providers
- Verify expected geographic distribution
- Identify datacenter vs residential traffic
How to Interpret
WHOIS shows who OWNS the IP (organizational registration). Geolocation shows where it's USED (physical server location). A Lithuanian company can own IPs used in Phoenix datacenter.
History
IP geolocation databases emerged in the early 2000s. Accuracy improved dramatically with commercial services like MaxMind. Modern services achieve city-level accuracy for 80%+ of IPs.
Geolocation
Physical location where the IP address is being used, determined by geolocation databases. This differs from WHOIS registration data, which shows ownership.
What You'll See
- City, region, and country of the server/device
- Coordinates with link to map
- Timezone and postal code
- ISP and organization operating at that location
- Security flags: Proxy, VPN, Tor, Hosting/Datacenter
Diagnostic Value
- Identify actual server location for latency/compliance
- Detect VPNs, proxies, and hosting providers
- Verify expected geographic distribution
- Identify datacenter vs residential traffic
How to Interpret
WHOIS shows who OWNS the IP (organizational registration). Geolocation shows where it's USED (physical server location). A Lithuanian company can own IPs used in Phoenix datacenter.
History
IP geolocation databases emerged in the early 2000s. Accuracy improved dramatically with commercial services like MaxMind. Modern services achieve city-level accuracy for 80%+ of IPs.
Contacts
Contacts
Email address for reporting network abuse, spam, hacking attempts, or security incidents originating from this IP block.
How to Interpret
[email protected] indicates a dedicated team. Generic contacts (noc@, security@) may be monitored but less specialized.
Contacts
Email address for reporting network abuse, spam, hacking attempts, or security incidents originating from this IP block.
How to Interpret
[email protected] indicates a dedicated team. Generic contacts (noc@, security@) may be monitored but less specialized.
Registration
Registration
IP WHOIS provides registration information for IP address blocks, revealing who owns and operates specific IP addresses. Unlike domain WHOIS (website ownership), IP WHOIS focuses on network infrastructure.
History
The RIR system was established in the 1990s to manage growing demand. IANA allocated the final IPv4 blocks to RIRs in 2011, leading to IPv6 adoption and IPv4 address trading markets.
Registration
IP WHOIS provides registration information for IP address blocks, revealing who owns and operates specific IP addresses. Unlike domain WHOIS (website ownership), IP WHOIS focuses on network infrastructure.
History
The RIR system was established in the 1990s to manage growing demand. IANA allocated the final IPv4 blocks to RIRs in 2011, leading to IPv6 adoption and IPv4 address trading markets.
% [whois.apnic.net] % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html % Information related to '2400:cb00:2000::/36' % Abuse contact for '2400:cb00:2000::/36' is '[email protected]' inet6num: 2400:cb00:2000::/36 netname: CLOUDFLARE_2400_CB00_2000_36 descr: Cloudflare, Inc. descr: 101 Townsend Street, San Francisco CA 94107 country: US admin-c: CTC17-AP tech-c: CTC17-AP abuse-c: AC1914-AP status: ALLOCATED NON-PORTABLE mnt-by: MAINT-CLOUDFLARE-AP mnt-irt: IRT-CLOUDFLARE-AP last-modified: 2021-01-13T23:48:09Z source: APNIC irt: IRT-CLOUDFLARE-AP address: Cloudflare, Inc. address: 101 Townsend Street, San Francisco CA 94107 e-mail: [email protected] abuse-mailbox: [email protected] admin-c: CTC15-AP tech-c: CTC15-AP auth: # Filtered remarks: [email protected] was validated on 2026-03-25 remarks: [email protected] was validated on 2026-04-10 irt-nfy: [email protected] notify: [email protected] mnt-by: MAINT-CLOUDFLARE-AP last-modified: 2026-05-09T01:29:07Z source: APNIC role: ABUSE CLOUDFLAREAP country: ZZ address: Cloudflare, Inc. address: 101 Townsend Street, San Francisco CA 94107 phone: +000000000 e-mail: [email protected] admin-c: CTC15-AP tech-c: CTC15-AP nic-hdl: AC1914-AP remarks: Generated from irt object IRT-CLOUDFLARE-AP remarks: [email protected] was validated on 2026-03-25 remarks: [email protected] was validated on 2026-04-10 abuse-mailbox: [email protected] mnt-by: APNIC-ABUSE last-modified: 2026-04-10T14:53:29Z source: APNIC role: Cloudflare Technical Contact address: 101 Townsend Street, San Francisco CA 94107 country: US phone: +1-650-319-8930 e-mail: [email protected] admin-c: CTC17-AP tech-c: CTC17-AP nic-hdl: CTC17-AP notify: [email protected] mnt-by: MAINT-CLOUDFLARE-AP last-modified: 2017-09-07T21:57:11Z source: APNIC % Information related to '2400:cb00:2049::/48AS13335' route6: 2400:cb00:2049::/48 origin: AS13335 descr: Cloudflare, Inc. 101 Townsend Street mnt-by: MAINT-CLOUDFLARE-AP last-modified: 2020-06-10T02:07:30Z source: APNIC % This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-US2)