IP & Network

IP-Whois-opzoeking

Eigenaar, ASN en allocatiedetails voor IPv4 of IPv6.

IP address IPv4 or IPv6
2606:4700:4700::1111
ARIN
Organization?
Cloudflare, Inc.
Country
Verenigde Staten US
IP Range?
2606:4700::/32
NetName?
CLOUDFLARENET
Registry?
ARIN
Network Details
NetRange? 2606:4700:: - 2606:4700:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF
Registered? 2011-11-01
Updated? 2024-09-04
Contact & Abuse
Abuse email? [email protected]
Abuse phone? +1-650-319-8930
Raw Whois
# # 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: 2606:4700:: - 2606:4700:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF CIDR: 2606:4700::/32 NetName: CLOUDFLARENET NetHandle: NET6-2606-4700-1 Parent: NET6-2600 (NET6-2600-1) NetType: Direct Allocation OriginAS: Organization: Cloudflare, Inc. (CLOUD14) RegDate: 2011-11-01 Updated: 2024-09-04 Comment: All Cloudflare abuse reporting can be done via https://www.cloudflare.com/abuse Comment: Geofeed: https://api.cloudflare.com/local-ip-ranges.csv Ref: https://rdap.arin.net/registry/ip/2606:4700:: OrgName: Cloudflare, Inc. OrgId: CLOUD14 Address: 101 Townsend Street City: San Francisco StateProv: CA PostalCode: 94107 Country: US RegDate: 2010-07-09 Updated: 2024-11-25 Ref: https://rdap.arin.net/registry/entity/CLOUD14 OrgNOCHandle: CLOUD146-ARIN OrgNOCName: Cloudflare-NOC OrgNOCPhone: +1-650-319-8930 OrgNOCEmail: [email protected] OrgNOCRef: https://rdap.arin.net/registry/entity/CLOUD146-ARIN OrgAbuseHandle: ABUSE2916-ARIN OrgAbuseName: Abuse OrgAbusePhone: +1-650-319-8930 OrgAbuseEmail: [email protected] OrgAbuseRef: https://rdap.arin.net/registry/entity/ABUSE2916-ARIN OrgTechHandle: ADMIN2521-ARIN OrgTechName: Admin OrgTechPhone: +1-650-319-8930 OrgTechEmail: [email protected] OrgTechRef: https://rdap.arin.net/registry/entity/ADMIN2521-ARIN OrgRoutingHandle: CLOUD146-ARIN OrgRoutingName: Cloudflare-NOC OrgRoutingPhone: +1-650-319-8930 OrgRoutingEmail: [email protected] OrgRoutingRef: https://rdap.arin.net/registry/entity/CLOUD146-ARIN RTechHandle: ADMIN2521-ARIN RTechName: Admin RTechPhone: +1-650-319-8930 RTechEmail: [email protected] RTechRef: https://rdap.arin.net/registry/entity/ADMIN2521-ARIN RNOCHandle: NOC11962-ARIN RNOCName: NOC RNOCPhone: +1-650-319-8930 RNOCEmail: [email protected] RNOCRef: https://rdap.arin.net/registry/entity/NOC11962-ARIN RAbuseHandle: ABUSE2916-ARIN RAbuseName: Abuse RAbusePhone: +1-650-319-8930 RAbuseEmail: [email protected] RAbuseRef: https://rdap.arin.net/registry/entity/ABUSE2916-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. #
What does each field mean?

Field reference

Organisatie

Naam van de organisatie die dit IP-blok bij het regionale register heeft geregistreerd. Dat kan een ISP zijn (KPN, Ziggo, Deutsche Telekom), een cloudprovider (Amazon Technologies, Google LLC), of een corporate AS van een onderneming.

ASN (Autonomous System)

BGP-routering-identifier (bijv. <code>AS15169</code> = Google). Elke publieke IP is bereikbaar via één of meer ASN's. De ASN vertelt u de netwerk-operator, ongeacht wie het onderliggende IP-blok bezit.

CIDR

Classless Inter-Domain Routing-notatie. <code>192.168.1.0/24</code> betekent dat de eerste 24 bits het netwerkprefix zijn — 256 adressen (.0 tot .255). Kleiner getal = groter blok: /16 = 65k, /8 = 16M.

Netnaam

Vrij label dat de registrant aan deze allocatie heeft toegekend — voorbeelden: <code>GOOGLE</code>, <code>AMAZON-AES</code>, <code>HETZNER-NBG1-DC1</code>. Handig om de klant-leverancier-grens binnen een groot netwerk te herkennen.

Netbereik

Expliciete range van de allocatie, bijv. <code>8.8.8.0 – 8.8.8.255</code>. Equivalent aan de CIDR-notatie, maar handiger als u wilt controleren of een specifieke IP binnen het bereik valt.

Register (RIR)

Het Regional Internet Registry dat deze adresruimte beheert: ARIN (Noord-Amerika), RIPE (Europa / Midden-Oosten), APNIC (Azië-Pacific), LACNIC (Latijns-Amerika), AFRINIC (Afrika). Bepaalt welke WHOIS-server gezaghebbend is.

Geregistreerd

Wanneer het regionale register dit blok voor het eerst toewees. Een heel recente datum op een "bekende" IP duidt meestal op recente transfer of sub-allocatie, niet op verse uitgifte vanuit IANA.

Bijgewerkt

Tijdstempel van de laatste WHOIS-wijziging — contacten, naam, status. Frequente updates kunnen duiden op reassignments, fusies of abuse-listing opschoning.

Abuse-e-mail

Verplicht kanaal voor abuse-meldingen volgens RFC 7485 / RIR-beleid. De operator moet binnen enkele werkdagen reageren. Meld scanning, brute-force, spam, DDoS — geen privé-geschillen.

Abuse-telefoon

Backup-kanaal voor tijdkritische abuse (live aanval, lopende DDoS). Wordt minder gebruikt dan e-mail; sommige kleinere operators publiceren er geen.

Over deze tool

A whois lookup reveals who owns an IP address and which organization operates the network it belongs to. Every IPv4 and IPv6 address on the public internet is allocated through one of five Regional Internet Registries — ARIN, RIPE, APNIC, LACNIC, and AFRINIC — and they maintain public databases of these allocations.

Our tool queries the correct registry automatically based on the address you enter, then parses the response into structured data: organization name, ASN (autonomous system number), CIDR range, country, abuse contact, and registration dates. The raw registry response is also available if you need the unprocessed output.

When to use this tool

  • Investigating suspicious traffic. Identify which organization owns an IP that appeared in your server logs.
  • Reporting abuse. Find the correct abuse contact to report spam, brute-force attempts, or DDoS traffic.
  • Geolocation verification. Cross-reference an IP's declared country with its registry allocation.
  • Network planning. Check ASN ownership when evaluating transit providers or peering relationships.

How whois data stays accurate

Registries require IP holders to keep contact details current, but enforcement varies. Smaller allocations under a corporate umbrella may show the parent organization rather than the actual operator. For the most accurate picture, combine whois data with rDNS lookups and ASN routing information — all three perspectives together tell a clearer story than any single one.

Veelgestelde vragen

Is whois lookup legal?

Yes. Whois data is published by the regional internet registries specifically to be publicly queryable. Looking up an IP address is equivalent to reading public DNS records — entirely legal and widely used by network engineers, security researchers, and journalists.

Can I see the personal owner of an IP?

Usually no. IP addresses are allocated to organizations (ISPs, hosting providers, corporations) rather than individuals. To trace an IP back to a specific user, you would need to contact the ISP with a formal legal request — information our tool cannot provide.

Why does my home IP show my ISP's name?

That is by design. ISPs receive blocks of IPs from registries and assign individual addresses to their customers dynamically. The whois record reflects the ISP because they are the registered owner of the block — your specific address is just a temporary lease within that block.

How often is whois data cached?

We cache whois responses for 12 hours to respect registry rate limits and give you instant answers. Registry data itself changes infrequently — typically once per allocation (months or years apart), so caching has no practical impact on accuracy.

Does this tool support IPv6?

Fully. Enter any IPv6 address in standard notation (for example 2606:4700:4700::1111) and we will query the appropriate registry. All response fields — ASN, CIDR, organization, abuse contacts — work identically for IPv6.