ARIN Lookup
About arin lookup.
This test will query the American Registry for Internet Numbers (ARIN) database and tell you who an IP address is registered to. Generally speaking, you will input an IP address and find out what ISP or hosting provider uses that block for its customers. Very large end customers may have there own ARIN allocations. Normally, this is used for finding abuse contacts to report bad behavior.
WHOIS / WHOIS History
Provide current and historical ownership information on domains / IPs. Identify all connections between domains, registrants, registrars, and DNS servers.
DNS / DNS History
Look into all current and historical DNS / IP connections between domains and A, MX, NS, and other records. Monitor suspicious changes to DNS records .
IP Geolocation / IP Netblocks
Get detailed context on an IP address, including its user’s geolocation, time zone, connected domains, connection type, IP range, ASN, and other network ownership details.
Domain Research Suite (DRS)
Access our web-based solution to dig into and monitor all domain events of interest.
Domain/WHOIS
Intelligence
Get access to a web-based enterprise-grade solution to search and monitor domain registrations and ownership details for branded terms, fuzzy matches, registrants of interest, and more.
White-Label
Predictive Threat Intelligence
Detect and block access to and from dangerous domain names before malicious actors can weaponize them. Contact us today for more information.
Internet Infrastructure
Unlock integrated intelligence on Internet properties and their ownership, infrastructure, and other attributes.
Enterprise API Packages
Our complete set of domain, IP, and DNS intelligence available via API calls as an annual subscription with predictable pricing.
Security Intelligence (SI) Suite
Offers complete access to WHOIS, IP, DNS, and subdomain data for product enrichment, threat hunting and more.
Premium API Services
Enjoy priority data access with our premium API services topped with extra perks including dedicated team support, enterprise-grade infrastructure, and SLAs for full scalability and high performance.
Multi-Level API User Administration Now Available - Manage individual API keys for team members in your organization.
- Internet Surface Intelligence
- Cyber Threat Intelligence Enrichment Solutions
- Digital Risk Protection Intelligence
- Know Who You’re Talking To (KWYTT) Intelligence
- Law Enforcement Intelligence
- Market and Competitive Intelligence
- Security Operations and Platform Intelligence
- Research Center
- Partnerships
- Domain Activity Reports
- Threat Reports
- Product Sheets
- White Papers
- Data Contribution and Exchange Program
- Integrations
- Research and Media Collaborations
- Resellers and Affiliates
- Knowledge Base
- Our Mission
- Press Release
- Success Stories
- WhoisXML API in Figures
IP Netblocks Lookup: Check Who Owns an IP Range Now
Uncover the ownership information of an IP address, including its IP netblock borders, organization’s or ISP’s name and address, contact details, and more. Test IP Netblocks lookup now. Download our product sheet to learn more.
What Are IP Netblocks?
IP netblocks refer to series or ranges of successive IP addresses that are part of the same block, such as 8.8.8.0–8.8.8.255. RIRs assign IP netblocks to netblock owners, typically ISPs and large enterprises that require a sizable number of IP addresses.
Why Use IP Netblocks Owner Lookup ?
IP Netblocks Owner Lookup retrieves data from one of today’s most comprehensive IP Netblocks WHOIS Database that contains information on more than 10.4 million netblocks and tens of thousands of unique ASNs and ranges refreshed daily.
Outputs from our IP netblocks lookup tool are formatted for intuitive data reporting with the most relevant ownership details readily available. The lookup reports can be easily shared with colleagues and relevant stakeholders via permanent URLs.
Practical usage
Bring Context to Your Cybersecurity Efforts
- Learn more about the range of an IP address identified as malicious . With IP Netblocks Owner Lookup, you can immediately find out who is in charge of a given IP range and report abuse to relevant entities.
- Correlate IP netblocks data with other sources of threat intelligence to build thorough attacker profiles and understand your network’s attack surface to thwart distributed denial-of-service (DDoS) and other attacks before these can halt business operations.
Make Informed Online Business Decisions
- Study your netblock allocation to reduce concentration risks and dependencies on certain ISPs and hosting providers.
- Correlate your web server logs with IP netblocks data to find out which networks your website traffic is coming from.
- If you’re thinking about expanding your Web portfolio or preparing for a merger or an acquisition, you can easily find neighboring netblocks that might be available for purchase with IP Netblocks Owner Lookup.
Protect Your Business and Reputation
- You can use the ownership and location information available in IP netblocks to implement and enforce digital rights management (DRM) and URL filtering strategies.
- Know if you are sharing your IP netblock with bad actors, which can cause your website to land on blacklists.
- Find out if anyone is abusing any address in your dedicated IP range .
Find out more about the largest IP Netblocks WHOIS Database
All of our IP netblocks data is also accessible in our extensive database, available in JSON or CSV with consistent and unified ranges.
Get 1,000 free API credits. No credit card required.
“WhoisXML API builds out data sets that help users correlate attack infrastructure with related IP and WHOIS information.”
Have questions?
We are here to listen. For a quick response, please select your request type. By submitting a request, you agree to our Terms of Service and Privacy Policy .
Or shoot us an email to
- Settings Profile and security information
Search ARIN Site or Whois
ARIN WHOIS IP Address Database Search
Find out what oganization an IP address is assigned to
ARIN's WHOIS service gives contact and registration information for IP addresses, autonomous system numbers (ASN), organizations or customers that are associated with these resources, and related Points of Contact (POC). It doesn't include information on domain names or military networks.
Instructions
Enter an IP addresses, autonomous system number (ASN), organization or customer name
To obtain a more specific response, you may conduct a search by using certain flags. Many of these flags can be combined to tailor the desired output. Flags must be separated from each other and from the search term by a space. Your results will vary depending on the refinements you apply in your search. Listed below are the flags currently available; you may only use one flag from each flag-type in a query, i.e. one record type, one attribute, etc.
Query-by-record-type
To limit your query to a specific record type, include one of the following flags:
Query-by-attributes
To limit your query to a specific record attribute, include one of the following flags:
Searches that retrieve a single record will display the full record. Searches that retrieve more than one record will be displayed in list output.
Display flags
To modify the way that the query results display, include one of the following flags:
The + flag cannot be used with the sub-query featured described below.
Record hierarchy
Records in the ARIN WHOIS database have hierarchical relationship with other records. To display those related records, use the following flags:
Wild card queries
WHOIS supports wild card queries. This feature is only supported as a trailing character option. To take advantage of this append the query with an asterisk * . This can also be used in combination with any flags defined above.
Other helpful hints
To guarantee matching only a single record, look it up by its handle using a handle-only search. In the record summary line, the handle is shown in parenthesis after the name.
When using a handle to conduct a search for POC information, be sure to add the -ARIN extension.
Queries that return more than 256 results will stop displaying data after the 256th result. You may want to narrow your search criteria or add flags to your query to limit the results.
To search on an individual's name, you may enter the last name, or to further restrict results, use the last name and first name, separated by a comma. For example: Smith, John .
What it's good for
- WHOIS search feature for IP addresses
- Procura de informação sobre IPs
- Find domain name owner from IP Address
- Search origin of IPs. kind of a reverse lookup
- ARIN search
- Strumento per trovare la provenienza geografica di un indirizzo IP e che possiede essa
- Find out who is behind that IP address
- Does a reverse IP check
- Look up IP address owner
- IP address search
- Whois IP address lookup
- Research IP addresses
- Shows ISP network blocks too
- Whois for IP addresses
- IP address tracer
- Search IP address owner
- para realizar un whois a la base de datos de ripe para saber a qué rango pertenece una IP
- IP address reverse lookup
- Good resource for tracking who owns an IP address
- Ferramenta para obter informações do host
- IP address location
- Find out who owns an IP address
Wayback Machine
See how ARIN WHOIS IP Address Database Search looked in the past.
By clicking "Accept" or continuing to use our site, you agree to our Website's Privacy Policy Accept
Free IP WHOIS Lookup
Enter an IP address to check who owns it and retrieve associated information such as registration date, location, and network details.
Use any IPV4 / IPV6 Address or your own IP
IP WHOIS - Check IP Address Registration and Ownership Details
Whether you are a tech expert, a network administrator, or someone interested in learning more — our tool is here to assist you. It is designed to uncover important information about “any IP address” or “ your own IP address ” in real time.
With our IP WHOIS Lookup Tool — you can easily find details like where an IP address comes from, who owns it, and essential network information. It's a valuable tool for troubleshooting network issues, analyzing cybersecurity threats, or satisfying your curiosity.
From discovering in-depth details about IP ranges , network types, registration dates, and update to checking associate autonomous system numbers — it helps you at every step. Use it to determine which organizations manage respective IP addresses, explore how different networks are connected, and understand their relationships.
It also provides a direct means to access abusive contact details related to IP ranges. This way, you can easily take strict action against online abuse or security issues.
How to Perform IP WHOIS Lookup?
It is as easy as you think. Simply enter the IP Address into the search bar and click “Lookup”. Our IP lookup WHOIS tool will take a second to display all the associated information on your screen.
IP WHOIS Result
Here are some key terms you need to know to understand the results obtained from IP WHOIS Lookup:
NetRange/CIDR : This entry covers the range of IP addresses and their CIDR notation.
NetName: The name associated with the IP range.
NetHandle : A unique identifier for this network block.
Parent: The parent network block that contains the respective IP range.
NetType: Describes the type of network registration.
OriginAS: The Autonomous System (AS) associated with the respective IP range, if applicable.
Organization: The organization or entity that manages the respective IP range.
RegDate: The registration date for the respective IP range (domain name).
Updated: The last update date for the respective IP range.
Ref : A link to the registry for further information about the respective IP range.
ResourceLink: Links to external resources for querying additional information.
OrgName: The name of the organization responsible for the respective IP range.
OrgId: A unique identifier for the organization.
Address: The organization's address details, including country or city.
OrgTechHandle: The technical contact handle for the organization.
OrgTechName: The name of the technical contact for the organization.
OrgTechPhone: The phone number of the technical contact.
OrgTechEmail: The email address of the technical contact.
OrgTechRef: A link to the registry for more information about the technical contact.
OrgAbuseHandle: The abuse contact handle for the organization.
OrgAbuseName: The name of the abuse contact for the organization.
OrgAbusePhone: The phone number of the abuse contact.
OrgAbuseEmail: The email address of the abuse contact.
OrgAbuseRef: A link to the registry for more information about the abuse contact.
Found a referral: Indicates if there is a referral to another WHOIS database.
Database query service: Information about the specific WHOIS database query service.
Abuse contact: Specifies the contact information for reporting abuse or security issues related to the respective IP range.
Route : Specific routing information for the respective IP range.
It is important to note that you will get the IP address owner's contact information from the IP WHOIS results. The owner can be the Internet Service Provider (ISP) information to whom the IP address is assigned.
Why Use Our WHOIS IP Lookup Tool?
IP WHOIS Lookup tool has been built to deliver an exceptional user experience, facilitating you with a reliable and lightning-fast way to check every detail that matters about an IP address owner. It is user-friendly, efficient, and secure — just as you need. Here are some reasons for which you can use it to your advantage:
Accurate Geolocation
Our IP WHOIS Lookup Tool provides estimated geolocation information for any IP address. It retrieves and displays the country, city, and even mailing address associated with the IP. This helps identify the origin of suspicious activities, analyze traffic patterns, and ensure absolute compliance with regional regulations. You can get IP's location from several geolocation databases to strengthen your results.
Detailed Network Information
You can use it to obtain details about the organization that holds the IP address, including their name, contact information, and administrative or technical personnel responsible for the network. This data enables efficient communication and collaboration with relevant professionals during network troubleshooting.
Registrar and Registration Details
It provides essential information about the registrar responsible for the IP address registration. You can access the registrar's name, website, and contact information. It also reveals the registration and expiration dates of the IP, allowing network administrators to track the status of their resources and plan accordingly.
Autonomous System (AS) Information
If you need Autonomous System information associated with an IP address, our advanced tool will cover it. It will display data, such as AS number, organization name, and routing policies. Understanding the AS infrastructure will help you to gain insights into the network's overall structure and detect routing issues .
Abuse Contact Details
In cases where suspicious or malicious activities are identified, our tool helps you to access abusive contact details—this way, it allows you to report any abuse or security incidents associated with the IP address range. You can leverage it to maintain network integrity and ensure timely actions against potential threats.
Get the Inside Scoop About IP WHOIS!
Here’s every key detail you’d need to know about IP WHOIS.
What is a WHOIS database?
The WHOIS database is a publicly accessible repository containing information about IP addresses, domain names, and registered owners. It provides details such as the organization or individual associated with the IP address, contact information, registration dates, and administrative details.
What is IP Address ownership?
IP address ownership refers to the legal and administrative control over an internet protocol address. It signifies that a particular individual, organization, or entity has the rights and responsibilities associated with using and managing a specific IP address or range of IP addresses. It is typically determined by the allocation and registration process by the Internet Assigned Numbers Authority (IANA) and the regional Internet registries (RIRs) they oversee.
How are IP addresses allocated and managed?
Someone somewhere owns an IP address that is in use on the internet. An Internet Assigned Numbers Authority (IANA) is responsible worldwide for managing the allocation of IP addresses. The organization is responsible for reporting the information, for example, IP address, root zone management in DNS, ASNs allocation, and other Internet numbers and Internet Protocol-related symbols.
The Internet Assigned Numbers Authority further assigns Internet number resources (IP addresses and AS numbers) to regional Internet registries (RIRs). These registries are responsible for allocating and registering Internet number resources within a specific region of the globe.
Each RIR has its regional rules and policies and follows those to assign the IP addresses and AS numbers to their customers, including ISPs and end-user organizations. Every IP address that floats on the global public internet is administrated by one of the five RIRs, each working within a specific region of the globe. The RIRs and their regulatory areas are as follows.
- African Network Information Centre (AfriNIC) Manages IP addresses for the African continent.
- American Registry for Internet Numbers (ARIN) Manages IP addresses for the United States, Canada, and many Caribbean and North Atlantic islands.
- Asia-Pacific Network Information Centre (APNIC) Manages IP addresses for Asia, Australia, and surrounding Countries.
- Latin America and Caribbean Network Information Centre (LACNIC) Manages IP addresses for Latin America and the Caribbean.
- Réseaux IP Européens Network Coordination Centre (RIPE NCC) Manages IP addresses for Europe, the Middle East, and the former USSR.
Suppose an RIR assigns a block of IP addresses to one of its ISP in the United States . The same ISP further assigns a sub-block of those IP addresses to one of their customer in Canada. The IP address's location still is reported as being in the United States.
Is IP WHOIS the same as WHOIS Domain?
No. IP WHOIS and WHOIS Domain lookup are not the same. IP WHOIS is used to obtain information about an IP address's ownership and registration details. In contrast, domain WHOIS provides information about a domain name's ownership and registration details. While both processes involve querying a WHOIS database, they retrieve information about different Internet resources.
What are the objectives (purposes) of an IP WHOIS lookup?
IP WHOIS Lookup helps you fulfill multiple objectives that include:
- Identifying the owner of an IP address
- Identifying the country/region associated with IP
- Investigating network suspicious activities
- Helping network administrators troubleshoot network issues.
Can I perform an IP WHOIS lookup for both IPv4 and IPv6 addresses?
Yes, our IP WHOIS lookup supports both IPv4 and IPv6 addresses. Using our IP WHOIS lookup tool, you can obtain WHOIS information for both IP addresses.
Does IP WHOIS lookup provide information about an IP address from the private network?
The IP WHOIS lookup tool and WHOIS databases do not provide any information about the IP addresses that belong to private (secured by proxy servers or VPNs) networks.
Can I see the WHOIS details of the end user?
The WHOIS IP address results provide the organization or individual's name against which the IP is registered in the IP WHOIS Database. Typically, the owner is none other than the internet service provider (ISP). It’s possible to get the end-user information only if the ISP allows it, which usually doesn’t happen.
Is IP WHOIS lookup legal?
Yes. Performing an IP WHOIS lookup is legal. This is because the information obtained through it is publicly available, and anyone can access it. However, it's essential to respect privacy regulations and use the obtained information responsibly and within the boundaries of the law.
DNS Check Tools
- DNS Checker
- Complete DNS Health Report
- Reverse IP Lookup
Productivity
- Binary Translator
- Reverse Image Search
- Credit Card Generator
- Notepad Online
- Morse Code Translator
- Image to Text
- Social Media Name Checker
DNS Server Database
- Global DNS Providers
- Australian DNS Servers
- United Kingdom DNS Servers
- United States DNS Servers
Developer Tools
- Password Generator
- Check HTTP Headers
- Check Website OS
- Page rank Checker
Network Tools
- Port Checker
- MAC Address Lookup
- ASN WHOIS Lookup
Email Tools
- Trace Email
- SPF Checker
- What is my IP
- IP Location Lookup
- IP Blacklist Check
- IP WHOIS Lookup
Apps And Add-ons
Copyright © DNSChecker.org, All Rights Reserved.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Lookup any IP address for FREE!
Use the IP lookup tool to see the geographical information about any IP address and also details on the type of connection and service provider. This tool will also display the geolocation of the IP address on a map.
The information below is provided with each search:
- Internet Service Provider (ISP)
- Organization
- Connection type
- Region, state, or province
- Latitude and Longitude
- Map of IP location
So how accurate is IP geolocation data?
IP Geolocation data is collected from ISPs and the accuracy is good across North America and Western Europe (see data below). Geolocation data from other parts of the world is less accurate and approaches 55% for accurate "city". A city is considered accurate if the IP is geolocated within 40km of the physical location.
Why is IP geolocation data not 100% accurate?
IP geolocation data comes from different database and each database may report the location of an IP address differently. IP blocks are assigned to different regional registries who then assign IP addresses to companies. Determining where these companies use each IP address is the challenging part.
In cases where the geolocation of the IP address is not known then the companies corporate office may be listed in the IP database. For example, Microsoft IPs often show as Redmond, WA, even when the user is elsewhere. Other reasons for IPs not being precise is the use of a VPN or proxy to hide the real IP and location of the user.
We still believe IP geolocation data is useful and mostly accurate. The accuracy is especially good for larger regions such as country. We caution users to use the results ini a responsible manner and understand the results are not 100% accurate.
How do I get someone's IP Address?
There are a number of ways to get someone's IP address but in general this person would either need to access a website or service that you administer or send you an email. The IP address can be found in the website logs or the headers of emails.
You should only attempt to obtain someone's IP address if you have a legitimate reason to do so. This typically means you offer an online service or need to report abuse.
What do the results of a lookup mean?
Each IP lookup will return ten fields and a warning message if the IP has abuse reported against it. The ten fields returned during each lookup are as follows:
- ISP: The internet service provider (ISP) associated with the IP address
- Organization: The organization or company who uses the IP address
- Connection type: The type of connection, such as Dialup, Cable/DSL, Cellular, or Corporate
- Continent: The continent where the IP address has been geolocated
- Country: The country where the IP address has been geolocated
- Region: The State, Provence, or Region where the IP address has been geolocated
- City: The city where the IP address has been geolocated
- Zip: The zip code where the IP address has been geolocated
- Longitude: The longitude where the IP address has been geolocated
- Latitude: The latitude where the IP address has been geolocated
How do I report IP abuse?
If you are experiencing harassment or other harmful activity from an IP address then you should report it and when appropriate partner with law enforcement. It is important to remember that sometimes IP addresses are being used to conduct harmful activity without the owners knowledge.
- Retrieve the IP address from the logs / headers
- Use the IP WHOIS Lookup tool to retrieve the WHOIS data for the IP
- Report the behavior of the IP to the "OrgAbuseEmail" or "OrgAbusePhone"
How can I check the reputation of an IP address?
Once you lookup an IP address on this page you will be informed if the IP address has negative reports against it. The message will appear above the IP address and the geolocation map. If no reports exists then no message will be displayed.
If you would like to make an inquiry directly against an IP reputation database then you can do so on ipsearch.io by visiting our IP reputation lookup tool
- Total reports
- Distinct users reporting
- Last reported date
- Abuse confidence score
- and more...
Who manages IP addresses across the globe?
You might wonder who is the global master of IP addresses and well we kind of have an answer. IANA (Internet Assigned Numbers Authority) is responsible for managing IP addresses and is managed by ICANN (Internet Corporation for Assigned Names and Numbers).
IANA sends IP blocks to five RIRs (Regional Internet Registries) who distribute IP addresses within their region. The five RIRs are as follows:
- ARIN (American Registry for Internet Numbers)
- RIPE NCC (Réseaux IP Européens Network Coordination Centre)
- APNIC (Asia-Pacific Network Information Centre)
- LACNIC (Latin America and Caribbean Network Information Centre)
- AFRINIC (African Network Information Centre)
You can read more in our article on IP Address Governance and Allocation.
Why did you start IPSearch.io?
Let's face it, we were not the first to provide IP lookup services on the internet. Our story begins with our founder starting a now large message board in 2011. Go Canes!
Andrew quickly noticed that the moderator features of the message board software could be improved upon and wrote and released a free Xenforo 2 add-ons called [Andrew] Moderator Panel. This add-on remains one of the top rated add-ons on Xenforo.
One of the features of this add-on was displaying IP geolocation data within Xenforo, opposed to having to click a link. After implementing this feature, Andrew realized that IP lookups could be improved upon and set out to create a modern IP lookup site. In January of 2024 IPSearch.io was launched.
Who is Rowdy Solutions LLC?
That is the name of the name Andrew gave to the company that owns this website. Rowdy is his eleven year old dog that Andrew adopted with his wife when they got back from their honeymoon. Rowdy is a good boy and his favorite food is tacos.
Recent articles
- May 25, 2024
- IPSearch.io News
What is the top reason you use a VPN?
Safeguard my ip address, access geo-restricted streaming content, conceal online activity from government surveillance, engage in online p2p fire sharing, bypass government censorship, access a work network, share this page.
Lookup the AS (autonomous system) name, number and netblocks associated with an IP address or ASN, and generate blocklists by ASN.
You can jump directly to the data with: https://asntool.com/<ip|asn>
Netblocks can be added or removed from autonomous systems at any time.
Something like this (use at your own risk): iptables-save | grep -v "ASNTool" | iptables-restore
I would tell you my source (which I came across by pure luck), but I'm afraid the more people who know about it, the more likely it is to dry up. I do not know why AS data is such a closely guarded secret. I hate how it only seems to be accessible through middlemen (at a price). That's why I created this.
That's because I combine adjacent netblocks where possible.
I'm not sure how long I can offer it before the bandwidth is cost prohibitive, but here it is: data.tsv.gz .
Format is: subnet low address (as an integer), subnet high address (as an integer), netblock string, ASN, AS name.
To find the ASN given a source IP, convert the IP to an integer, and find the rightmost (largest) low address (i.e. the first column) less than or equal to the source IP. Then ensure the source IP is between (inclusive) of the low/high address. The Python bisect module and find_le function is useful for this.
I won't stop you from making automated HTTP requests (if you keep it to a reasonable level). Put your email address in the HTTP user agent so I can contact you.
1 request per second. Exceeding the limit is undefined behavior.
I generated it from an attack on my own website in December of 2022. If you know of a better source, email me.
I'm holding out for IPv7.
I don't. It is provided to you out of the goodness of my heart.
I'll allow it. rumpelstiltskin at this domain.
IP Location and Operator Lookup
Ultrafast internet address lookup api.
IP to Geolocation and Risk Score Analysis REST API with field filtering flexibility in JSON, XML, TAB, CSV, or TXT format, designed for consumption with minimal client code.
The API can be of use in changing website content based on Operator's Location or to implement Access Restrictions based on Operator's Location and Risk score, such as TOR Exit node, Private Proxy, Open VPN or other untrusted routes and threatening behaviors.
What is IP Address Allocation?
Internet Protocol (IP) addresses are allocated to each device connected to the Internet (public address) or to a local network (private address) and are used to identify the device's network and the particular device when they communicate with other devices.
- Internet IP addresses are administered by a Number Resource Organization - there is a Registry Organization for each continent - e.g., ARIN for North America.
- Registry Organizations assign blocks of IP addresses to a Provider Organization such as an Internet Service Provider (ISP).
- ISPs provide individuals and organizations access to the Internet and allocate them IP addresses from the blocks they manage.
- An IPv4 Internet address is a unique 32-bit value expressed as a group of four numbers separated by a period - for example 34.130.46.78 - each number ranges from 0 to 255.
- An IPv6 Internet address is a unique 128-bit value expressed as a group of eight Hex strings separated by a colon character - for example 2602:306:e881:1000:abc:1089:0:ff - where each string is in the range from 0 to ffff.
What is an IP address Risk Score?
The IP address Risk Score alerts users to the possibility of an IP address being linked to malicious activity by a real person (human) or a machine (bot/server).
- An IP address assigned to a residential or cell phone customer by an ISP receives a low score if it is not recorded in any source as having been involved in any malicious activity in the recent past.
- When an IP address is identified as being used by a private VPN, residential proxy, or TOR connection, a medium-to-high score is given.
- IP addresses that were recently used for malicious activity such as security threats and cyber crimes are given the highest score, e.g., 100.
Understanding IP Address Assignment: A Complete Guide
Introduction
In today's interconnected world, where almost every aspect of our lives relies on the internet, understanding IP address assignment is crucial for ensuring online security and efficient network management. An IP address serves as a unique identifier for devices connected to a network, allowing them to communicate with each other and access the vast resources available on the internet. Whether you're a technical professional, a network administrator, or simply an internet user, having a solid grasp of how IP addresses are assigned within the same network can greatly enhance your ability to troubleshoot connectivity issues and protect your data.
The Basics of IP Addresses
Before delving into the intricacies of IP address assignment in the same network, it's important to have a basic understanding of what an IP address is. In simple terms, an IP address is a numerical label assigned to each device connected to a computer network that uses the Internet Protocol for communication. It consists of four sets of numbers separated by periods (e.g., 192.168.0.1) and can be either IPv4 or IPv6 format.
IP Address Allocation Methods
There are several methods used for allocating IP addresses within a network. One commonly used method is Dynamic Host Configuration Protocol (DHCP). DHCP allows devices to obtain an IP address automatically from a central server, simplifying the process of managing large networks. Another method is static IP address assignment, where an administrator manually assigns specific addresses to devices within the network. This method provides more control but requires careful planning and documentation.
Considerations for Efficient IP Address Allocation
Efficient allocation of IP addresses is essential for optimizing network performance and avoiding conflicts. When assigning IP addresses, administrators need to consider factors such as subnetting, addressing schemes, and future scalability requirements. By carefully planning the allocation process and implementing best practices such as using private IP ranges and avoiding overlapping subnets, administrators can ensure smooth operation of their networks without running out of available addresses.
IP Address Assignment in the Same Network
When two routers are connected within the same network, they need to obtain unique IP addresses to communicate effectively. This can be achieved through various methods, such as using different subnets or configuring one router as a DHCP server and the other as a client. Understanding how IP address assignment works in this scenario is crucial for maintaining proper network functionality and avoiding conflicts.
Basics of IP Addresses
IP addresses are a fundamental aspect of computer networking that allows devices to communicate with each other over the internet. An IP address, short for Internet Protocol address, is a unique numerical label assigned to each device connected to a network. It serves as an identifier for both the source and destination of data packets transmitted across the network.
The structure of an IP address consists of four sets of numbers separated by periods (e.g., 192.168.0.1). Each set can range from 0 to 255, resulting in a total of approximately 4.3 billion possible unique combinations for IPv4 addresses. However, with the increasing number of devices connected to the internet, IPv6 addresses were introduced to provide a significantly larger pool of available addresses.
IPv4 addresses are still predominantly used today and are divided into different classes based on their range and purpose. Class A addresses have the first octet reserved for network identification, allowing for a large number of hosts within each network. Class B addresses reserve the first two octets for network identification and provide a balance between network size and number of hosts per network. Class C addresses allocate the first three octets for network identification and are commonly used in small networks.
With the depletion of available IPv4 addresses, IPv6 was developed to overcome this limitation by utilizing 128-bit addressing scheme, providing an enormous pool of potential IP addresses - approximately 3.4 x 10^38 unique combinations.
IPv6 addresses are represented in hexadecimal format separated by colons (e.g., 2001:0db8:85a3:0000:0000:8a2e:0370:7334). The longer length allows for more efficient routing and eliminates the need for Network Address Translation (NAT) due to its vast address space.
Understanding these basics is essential when it comes to assigning IP addresses in a network. Network administrators must consider various factors such as the number of devices, network topology, and security requirements when deciding on the IP address allocation method.
In the next section, we will explore different methods of IP address assignment, including Dynamic Host Configuration Protocol (DHCP) and static IP address assignment. These methods play a crucial role in efficiently managing IP addresses within a network and ensuring seamless communication between devices.
Methods of IP Address Assignment
IP address assignment is a crucial aspect of network management and plays a vital role in ensuring seamless connectivity and efficient data transfer. There are primarily two methods of assigning IP addresses in a network: dynamic IP address assignment using the Dynamic Host Configuration Protocol (DHCP) and static IP address assignment.
Dynamic IP Address Assignment using DHCP
Dynamic IP address assignment is the most commonly used method in modern networks. It involves the use of DHCP servers, which dynamically allocate IP addresses to devices on the network. When a device connects to the network, it sends a DHCP request to the DHCP server, which responds by assigning an available IP address from its pool.
One of the key benefits of dynamic IP address assignment is its simplicity and scalability. With dynamic allocation, network administrators don't have to manually configure each device's IP address. Instead, they can rely on the DHCP server to handle this task automatically. This significantly reduces administrative overhead and makes it easier to manage large networks with numerous devices.
Another advantage of dynamic allocation is that it allows for efficient utilization of available IP addresses. Since addresses are assigned on-demand, there is no wastage of unused addresses. This is particularly beneficial in scenarios where devices frequently connect and disconnect from the network, such as in public Wi-Fi hotspots or corporate environments with a high turnover rate.
However, dynamic allocation does have some drawbacks as well. One potential issue is that devices may receive different IP addresses each time they connect to the network. While this might not be an issue for most users, it can cause problems for certain applications or services that rely on consistent addressing.
Additionally, dynamic allocation introduces a dependency on the DHCP server. If the server goes down or becomes unreachable, devices will not be able to obtain an IP address and will be unable to connect to the network. To mitigate this risk, redundant DHCP servers can be deployed for high availability.
Static IP Address Assignment
Static IP address assignment involves manually configuring each device's IP address within the network. Unlike dynamic allocation, where addresses are assigned on-demand, static assignment requires administrators to assign a specific IP address to each device.
One of the main advantages of static IP address assignment is stability. Since devices have fixed addresses, there is no risk of them receiving different addresses each time they connect to the network. This can be beneficial for applications or services that require consistent addressing, such as servers hosting websites or databases.
Static assignment also provides greater control over network resources. Administrators can allocate specific IP addresses to devices based on their requirements or security considerations. For example, critical servers or network infrastructure devices can be assigned static addresses to ensure their availability and ease of management.
However, static IP address assignment has its limitations as well. It can be time-consuming and error-prone, especially in large networks with numerous devices. Any changes to the network topology or addition/removal of devices may require manual reconfiguration of IP addresses, which can be a tedious task.
Furthermore, static allocation can lead to inefficient utilization of available IP addresses. Each device is assigned a fixed address regardless of whether it is actively using the network or not. This can result in wastage of unused addresses and may pose challenges in scenarios where addressing space is limited.
In order to efficiently allocate IP addresses within a network, there are several important considerations that need to be taken into account. By carefully planning and managing the allocation process, network administrators can optimize their IP address usage and ensure smooth operation of their network.
One of the key factors to consider when assigning IP addresses is the size of the network. The number of devices that will be connected to the network determines the range of IP addresses that will be required. It is essential to accurately estimate the number of devices that will need an IP address in order to avoid running out of available addresses or wasting them unnecessarily.
Another consideration is the type of devices that will be connected to the network. Different devices have different requirements in terms of IP address assignment. For example, servers and other critical infrastructure typically require static IP addresses for stability and ease of access. On the other hand, client devices such as laptops and smartphones can often use dynamic IP addresses assigned by a DHCP server.
The physical layout of the network is also an important factor to consider. In larger networks with multiple subnets or VLANs, it may be necessary to segment IP address ranges accordingly. This allows for better organization and management of IP addresses, making it easier to troubleshoot issues and implement security measures.
Security is another crucial consideration when allocating IP addresses. Network administrators should implement measures such as firewalls and intrusion detection systems to protect against unauthorized access or malicious activities. Additionally, assigning unique IP addresses to each device enables better tracking and monitoring, facilitating quick identification and response in case of any security incidents.
Efficient utilization of IP address ranges can also be achieved through proper documentation and record-keeping. Maintaining an up-to-date inventory of all assigned IP addresses helps prevent conflicts or duplicate assignments. It also aids in identifying unused or underutilized portions of the address space, allowing for more efficient allocation in the future.
Furthermore, considering future growth and scalability is essential when allocating IP addresses. Network administrators should plan for potential expansion and allocate IP address ranges accordingly. This foresight ensures that there will be sufficient addresses available to accommodate new devices or additional network segments without disrupting the existing infrastructure.
In any network, the assignment of IP addresses is a crucial aspect that allows devices to communicate with each other effectively. When it comes to IP address assignment in the same network, there are specific considerations and methods to ensure efficient allocation. In this section, we will delve into how two routers in the same network obtain IP addresses and discuss subnetting and IP address range distribution.
To understand how two routers in the same network obtain IP addresses, it's essential to grasp the concept of subnetting. Subnetting involves dividing a larger network into smaller subnetworks or subnets. Each subnet has its own unique range of IP addresses that can be assigned to devices within that particular subnet. This division helps manage and organize large networks efficiently.
When it comes to assigning IP addresses within a subnet, there are various methods available. One common method is manual or static IP address assignment. In this approach, network administrators manually assign a specific IP address to each device within the network. Static IP addresses are typically used for devices that require consistent connectivity and need to be easily identifiable on the network.
Another widely used method for IP address assignment is Dynamic Host Configuration Protocol (DHCP). DHCP is a networking protocol that enables automatic allocation of IP addresses within a network. With DHCP, a server is responsible for assigning IP addresses dynamically as devices connect to the network. This dynamic allocation ensures efficient utilization of available IP addresses by temporarily assigning them to connected devices when needed.
When considering efficient allocation of IP addresses in the same network, several factors come into play. One important consideration is proper planning and design of subnets based on anticipated device count and future growth projections. By carefully analyzing these factors, administrators can allocate appropriate ranges of IP addresses for each subnet, minimizing wastage and ensuring scalability.
Additionally, implementing proper security measures is crucial when assigning IP addresses in the same network. Network administrators should consider implementing firewalls, access control lists (ACLs), and other security mechanisms to protect against unauthorized access and potential IP address conflicts.
Furthermore, monitoring and managing IP address usage is essential for efficient allocation. Regular audits can help identify any unused or underutilized IP addresses that can be reclaimed and allocated to devices as needed. This proactive approach ensures that IP addresses are utilized optimally within the network.
The proper assignment of IP addresses is crucial for maintaining network security and efficiency. Throughout this guide, we have covered the basics of IP addresses, explored different methods of IP address assignment, and discussed considerations for efficient allocation.
In conclusion, understanding IP address assignment in the same network is essential for network administrators and technical professionals. By following proper allocation methods such as DHCP or static IP assignment, organizations can ensure that each device on their network has a unique identifier. This not only enables effective communication and data transfer but also enhances network security by preventing unauthorized access.
Moreover, considering factors like subnetting, scalability, and future growth can help optimize IP address allocation within a network. Network administrators should carefully plan and allocate IP addresses to avoid conflicts or wastage of resources.
Overall, a well-managed IP address assignment process is vital for the smooth functioning of any network. It allows devices to connect seamlessly while ensuring security measures are in place. By adhering to best practices and staying updated with advancements in networking technology, organizations can effectively manage their IP address assignments.
In conclusion, this guide has provided a comprehensive overview of IP address assignment in the same network. We hope it has equipped you with the knowledge needed to make informed decisions regarding your network's IP address allocation. Remember that proper IP address assignment is not only important for connectivity but also plays a significant role in maintaining online security and optimizing network performance.
Enhance Online Security: The Ultimate Guide to Conceal Your IP Address
Alternative Methods to Conceal Your IP Address Without a VPN
Maintain Privacy: Learn How to Alter Your IP Address
The Significance of IP Address for Online Security and Privacy
Comprehensive Handbook on VPNs, IP Addresses, and Proxy Servers
| | Additional DNS record type to lookup for domains | | Preserve duplicates | | | | Domain and IP bulk lookup tool allows to lookup domain, location, ISP and ASN for multiple hosts (IPs or domains) at once. It also supports lookup of MX or NS DNS records for multiple domains. This tool is commonly used for investigating IPs found in server logs. The limit is 100 IPs/domains per request. IP Subnet CalculatorThis calculator returns a variety of information regarding Internet Protocol version 4 (IPv4) and IPv6 subnets including possible network addresses, usable host ranges, subnet mask, and IP class, among others. IPv4 Subnet Calculator Network Class | Any A B C | Subnet | | IP Address | | | IPv6 Subnet Calculator Prefix Length: | | IP Address: | | | Related Bandwidth Calculator | Binary Calculator A subnet is a division of an IP network (internet protocol suite), where an IP network is a set of communications protocols used on the Internet and other similar networks. It is commonly known as TCP/IP (Transmission Control Protocol/Internet Protocol). The act of dividing a network into at least two separate networks is called subnetting, and routers are devices that allow traffic exchange between subnetworks, serving as a physical boundary. IPv4 is the most common network addressing architecture used, though the use of IPv6 has been growing since 2006. An IP address is comprised of a network number (routing prefix) and a rest field (host identifier). A rest field is an identifier that is specific to a given host or network interface. A routing prefix is often expressed using Classless Inter-Domain Routing (CIDR) notation for both IPv4 and IPv6. CIDR is a method used to create unique identifiers for networks, as well as individual devices. For IPv4, networks can also be characterized using a subnet mask, which is sometimes expressed in dot-decimal notation, as shown in the "Subnet" field in the calculator. All hosts on a subnetwork have the same network prefix, unlike the host identifier, which is a unique local identification. In IPv4, these subnet masks are used to differentiate the network number and host identifier. In IPv6, the network prefix performs a similar function as the subnet mask in IPv4, with the prefix length representing the number of bits in the address. Prior to the introduction of CIDR, IPv4 network prefixes could be directly obtained from the IP address based on the class (A, B, or C, which vary based on the range of IP addresses they include) of the address and the network mask. Since the introduction of CIDRs, however, assigning an IP address to a network interface requires both an address and its network mask. Below is a table providing typical subnets for IPv4. Prefix size | Network mask | Usable hosts per subnet | /1 | 128.0.0.0 | 2,147,483,646 | /2 | 192.0.0.0 | 1,073,741,822 | /3 | 224.0.0.0 | 536,870,910 | /4 | 240.0.0.0 | 268,435,454 | /5 | 248.0.0.0 | 134,217,726 | /6 | 252.0.0.0 | 67,108,862 | /7 | 254.0.0.0 | 33,554,430 | | /8 | 255.0.0.0 | 16,777,214 | /9 | 255.128.0.0 | 8,388,606 | /10 | 255.192.0.0 | 4,194,302 | /11 | 255.224.0.0 | 2,097,150 | /12 | 255.240.0.0 | 1,048,574 | /13 | 255.248.0.0 | 524,286 | /14 | 255.252.0.0 | 262,142 | /15 | 255.254.0.0 | 131,070 | | /16 | 255.255.0.0 | 65,534 | /17 | 255.255.128.0 | 32,766 | /18 | 255.255.192.0 | 16,382 | /19 | 255.255.224.0 | 8,190 | /20 | 255.255.240.0 | 4,094 | /21 | 255.255.248.0 | 2,046 | /22 | 255.255.252.0 | 1,022 | /23 | 255.255.254.0 | 510 | | /24 | 255.255.255.0 | 254 | /25 | 255.255.255.128 | 126 | /26 | 255.255.255.192 | 62 | /27 | 255.255.255.224 | 30 | /28 | 255.255.255.240 | 14 | /29 | 255.255.255.248 | 6 | /30 | 255.255.255.252 | 2 | /31 | 255.255.255.254 | 0 | /32 | 255.255.255.255 | 0 | - Settings Profile and security information
ARIN is a nonprofit, member-based organization that administers IP addresses & ASNs in support of the operation and growth of the Internet.Your IP address is - New to ARIN
- Request IP Addresses & ASNs
- Get Involved
AnnouncementsDeadline approaching — make sure your organization is eligible to vote in arin’s upcoming elections. Meetings/Events ARIN 54 Registration Now OpenCongratulations to the 2024 arin community grant recipients. ACSP/Surveys NOW CLOSED – Consultation on API Key Handling Congratulations to the arin 54 selected fellows, consultation on arin online change notifications. Education. Policy. Discussion. ARIN Meetings and Events are an important part of our open, transparent, bottom-up processes. Upcoming ARIN Events Event | Location | Date | | Ottawa, Canada | 24 September 2024 | | Toronto, Ontario, Canada | 24–25 October 2024 | | Charlotte, North Carolina | 27–30 April 2025 | | Arlington, Texas | 30–31 October 2025 | » | Recent Blog PostsVisit ARIN’s blog homepage for more. Announcing the 2024 ARIN Community Grant RecipientsWe would like to congratulate the organizations receiving funding from the ARIN Community Grant Program this year! Project Manager Amanda Gauldin shares details about their projects. Are Differences in RIR RPKI Implementations Hindering RPKI Adoption?In part three of the NRO RPKI Program blog series, network operators are invited to share details of their Resource Public Key Infrastructure adoption journey and what barriers they have faced. Journeying from Novice to Contributor: My Path into ARIN Policy DevelopmentAn ARIN 52 Fellow shares his experience in and after the program and the aspirations of participation and impact within the community it has fostered. What is My IP Location? | GeolocationLooking to query more than 1 IP? Try our Bulk IP Lookup IP Address DetailsIP Location: Moscow, Moskva (RU) [Details] ISP: LLC Internet Tehnologii Proxy: Not detected. Platform: Windows 7 Browser: Firefox 107.0 [User Agent] Screen Size: Javascript: Enabled Would you like to help us improve ip-to-location data by providing your feedback? Random FactsSecurity tools. Best VPN ProvidersI want to hide my IP address, browse anonymously, and protect my identity. Best Proxy ProvidersI want to prevent tracking my activities, and circumvent internet censorship. Person SearchSearch public records, and find anyone online by name, email or phone number. Latest Blog PostsThe Essentials of Hard SEO: Strengthening Your Online Presence Through Advanced Techniques- Alex Syrotenko
- Sep 08, 2024
In the ever-evolving world of search engine optimization (SEO), Hard SEO refers to the application of advanced, often technical strategies designed to enhance a website's... Easy Steps: How to Import MBOX Files in Gmail?- Anjali Aggarwal
- Sep 07, 2024
In this blog post, we'll go over how to import MBOX files in Google Workspace. Users important email data is now stored in MBOX formats,... How to Access iCloud Emails in MS Outlook SafelyIn today's fast-paced digital world, staying connected and organized is critical. With the integration of several platforms and devices, syncing or backing up your emails,... Top 10 Bulk SMS Service Providers: A Comprehensive GuideIn the rapidly evolving digital landscape, effective communication has become a cornerstone of business success. As companies strive to reach their target audience quickly and... SMM Reseller Panel: Your Gateway to Social Media SuccessLooking for the best SMM panel to boost your social media presence? An SMM reseller panel can be the perfect solution for individuals and businesses... Is PicLumen Truly Free for Unlimited Image Generation?During a time where visual quality written substance is the final deciding factor, making superior grade, proficient pictures is a higher priority than any time... How to Teach Your Parents About Tech: A Guide to Safeguarding the Older Generation OnlineIn today's rapidly advancing digital world, access to the internet and technology is not just a luxury; it’s a necessity. The need and intrigue of... The Advantages of Using Magento for E-commerceOnce you've identified your niche and target audience, the next crucial steps are selecting an e-commerce platform and building your website. AI in Web Analytics: A Game-Changer for Digital StrategyWeb analytics has always formed the backbone of monitoring and improving website performance. Conventional analytics has, until recently, focused on the tracking of active users,... How to Download a Folder from AWS S3 BucketTo download a folder from an AWS S3 bucket, one might have a perception that it is a difficult task especially if they have no... Why do you need geolocation?There are several ways to find the geolocation of a user: HTML5 API, Cell Signal, and IP Address to name a few. The pairing of an IP address to a geographical location is the method we used to provide geolocation data. There are times when you need to identify where your web visitors are coming from. You might have an ecommerce website, and would like to know where your potential customers are, pre-populate country codes on forms, display different languages and reduce credit card fraud based on geographic location. Or, you might want to fight against illegal spammers and hackers and would like to locate the sources of a problem. Although it would be nice to be able to find the precise location of a visitor, it is almost impossible to find the exact location of a host given its IP address . However, there are tools available to help identify the approximate location of the host. ARIN Whois database provides a mechanism for finding contact and registration information for IP resources registered with ARIN. You may also use 3rd party websites such as Geobytes or Dnsstuff to look up the IP address. The whois lookup will reveal the name of the ISP who owns that IP address, and the country where it originated from. If you're lucky, you might also find the city of origin. You may also use products developed by 3rd-party companies like Ip2location and MaxMind. You may also use reverse DNS to find out the hostname of the IP address, which might give you some clues. Many ISPs, Corporations, and Academic institutions use location as a qualified hostname, although this is not always true. A couple of things to note here: (1) Reverse DNS translation do not always work. It depends on the correct configuration of the ISP's DNS server. (2) The US domain names such as .com, .net and .org does not always imply that the host is located in the United States. You may use ' traceroute ' command to find clues to the location of the IP address. The names of the routers through which packets flow from your host to the destination host might hint at the geographical path of the final location. IP-based Geolocation FAQ1. what is ip-based geolocation. IP-based Geolocation is the mapping of an IP address or MAC address to the real-world geographic location of an Internet-connected computing or a mobile device. Geolocation involves mapping IP addresses to the country, region (city), latitude/longitude, ISP, and domain name among other useful things. 2. Where can I get an IP-based Geolocation database?There are several commercially available geolocation databases, and their pricing and accuracy may vary. Ip2location, MaxMind, Tamo Soft, DB-IP, Ipinfo, and IPligence offer fee-based databases that can be easily integrated into a web application. Most geolocation database vendors offer APIs and example codes (in ASP, PHP, .NET, and Java programming languages) that can be used to retrieve geolocation data from the database. We use several commercial databases to offer free geolocation data on our website. There are also freely available geolocation databases. Vendors offering commercial geolocation databases also offer a Lite or Community edition that provides IP-to-Country mappings. Ip2Country.net and Webhosting.info (Directi) offer free IP-to-Country databases that can be also integrated into your web application. There are companies also offering free web services that can be used to show the geolocation of an IP address on your website. 3. How accurate is IP-based Geolocation?The accuracy of the geolocation database varies depending on which database you use. For IP-to-country databases, some vendors claim to offer 98% to 99% accuracy although typical Ip2Country database accuracy is more like 95%. For IP-to-Region (or City), accuracy range anywhere from 50% to 75% if neighboring cities are treated as correct. Considering that there is no official source of IP-to-Region information, 50+% accuracy is pretty good. 4. How does IP-based geolocation work?ARIN Whois database provides a mechanism for finding contact and registration information for IP resources registered with ARIN. The IP whois information is available for free, and determining the country from this database is relatively easy. When an organization requires a block of IP addresses, a request is submitted, and allocated IP addresses are assigned to a requested ISP. Common Network Questions• Do you want to find an IP address of your network printer? Please read How to find an IP of a printer to find ways to obtain an IP number of your network printer. • Do you want to find IP Addresses of private network? Please read How to find IP addresses of computing devices on the private network? AdvertisementPopular tools. IP Address ArticlesMarch 1, 2016 How to hide my IP address?There are several ways to hide your IP address, and your geolocation. Hiding your IP address is concealing your "true" IP address with a different one. You may use a VPN, Proxy or Anonymous Browser to hide your IP address. April 14, 2016 How to change your IP address?Would you like to change the IP address of your computer, smartphone or tablet? You're getting your IP address from your Internet Service Provider, and you have the right to obtain a new IP address whenever you desire. Let us show you how you can change an IP address of your device. February 15, 2012 What is the difference between public and private IP address?A public IP address is an IP address that can be accessed over the Internet, and a private IP address is an IP address that is local to your private network. A public IP is a globally unique IP, while a private IP address can be reused in different networks. October 7, 2012 What is the difference between a static and dynamic IP address?An IP address is an address assigned to a device on the Internet. A static IP address is a fixed IP address that never changes, and a dynamic IP address is an IP that is assigned by the DHCP server which may change over time. Blog Categories- Artificial Intelligence (78)
- Automotive (16)
- Business (152)
- Ecommerce (64)
- Intellectual Property (8)
- Productivity (10)
- Cloud Services (74)
- Computing (58)
- Crypto & Blockchain (29)
- Cybersecurity (242)
- Distributed Denial of Service (10)
- Password (19)
- Safety (19)
- Data & Database (17)
- Digital Marketing (103)
- Education (33)
- Entertainment (8)
- Fashion (1)
- Finance (58)
- Healthcare (19)
- Internet of Things (22)
- IP Address (59)
- Geolocation (41)
- Network (88)
- Online Resources (8)
- Online Tools (50)
- Privacy (116)
- Virtual Private Network (82)
- Real Estate (4)
- Scams & Frauds (16)
- Smartphone (42)
- Social Media (59)
- Social Media Marketing (36)
- Software (133)
- Software Development (122)
- Software Testing (4)
- Mobile App Development (1)
- Technology (46)
- Information Technology (8)
- Travel (16)
- World Wide Web (147)
- Search Engine Optimization (52)
- Web Hosting (21)
- Web Design (9)
Do not sell or share my personal information.At IPLocation.net, we prioritize the privacy and security of our visitors. We want you to feel confident and comfortable when browsing our website. That's why we want to assure you that we do not sell or share any personal information collected from our website. Your trust is important to us. Whether you're browsing our site for information, or engaging with our content, rest assured that any data you provide remains strictly confidential. We adhere to stringent privacy policies and comply with all relevant regulations to safeguard your information. Your privacy matters, and we are committed to maintaining the highest standards of data protection. If you have any questions or concerns regarding our privacy practices, please don't hesitate to reach out to us. © 2006 - 2024, Brand Media, Inc. All rights reserved. IPv4 Multicast Address Space RegistryRegistries included below Local Network Control Block (224.0.0.0 - 224.0.0.255 (224.0.0/24))Internetwork control block (224.0.1.0 - 224.0.1.255 (224.0.1/24)), ad-hoc block i (224.0.2.0 - 224.0.255.255), reserved (224.1.0.0-224.1.255.255 (224.1/16)), sdp/sap block (224.2.0.0-224.2.255.255 (224.2/16)), ad-hoc block ii (224.3.0.0-224.4.255.255 (224.3/16, 224.4/16)), reserved (224.5.0.0-224.251.255.255 (251 /16s)), dis transient groups 224.252.0.0-224.255.255.255 (224.252/14)), reserved (225.0.0.0-231.255.255.255 (7 /8s)), source-specific multicast block (232.0.0.0-232.255.255.255 (232/8)), ad-hoc block iii (233.252.0.0-233.255.255.255 (233.252/14)), unicast-prefix-based ipv4 multicast addresses, scoped multicast ranges, relative addresses used with scoped multicast addresses. Address(es) | Description | References | Change Controller | Date Registered | Last Reviewed | 224.0.0.0 | Base Address (Reserved) | [ ][ ] | | | | 224.0.0.1 | All Systems on this Subnet | [ ][ ] | | | | 224.0.0.2 | All Routers on this Subnet | [ ] | | | | 224.0.0.3 | Unassigned | | | | | 224.0.0.4 | DVMRP Routers | [ ][ ] | | | | 224.0.0.5 | OSPFIGP OSPFIGP All Routers | [ ][ ] | | | | 224.0.0.6 | OSPFIGP OSPFIGP Designated Routers | [ ][ ] | | | | 224.0.0.7 | ST Routers | [ ][ ] | | | | 224.0.0.8 | ST Hosts | [ ][ ] | | | | 224.0.0.9 | RIP2 Routers | [ ][ ] | | | | 224.0.0.10 | EIGRP Routers | [ ] | | 1996-03-01 | | 224.0.0.11 | Mobile-Agents | [[Bill Simpson]] | | | | 224.0.0.12 | DHCP Server / Relay Agent | [[Unknown]] | | | | 224.0.0.13 | All PIM Routers | [ ] | | 1996-03-01 | | 224.0.0.14 | RSVP-ENCAPSULATION | [ ] | | 1996-04-01 | | 224.0.0.15 | all-cbt-routers | [ ][ ] | | 1997-02-01 | | 224.0.0.16 | designated-sbm | [ ] | | 1997-06-01 | | 224.0.0.17 | all-sbms | [ ] | | 1997-06-01 | | 224.0.0.18 | VRRP | [ ][ ] | | | | 224.0.0.19 | IPAllL1ISs | [ ] | | 1999-10-01 | | 224.0.0.20 | IPAllL2ISs | [ ] | | 1999-10-01 | | 224.0.0.21 | IPAllIntermediate Systems | [ ] | | 1999-10-01 | | 224.0.0.22 | IGMP | [ ] | | 1999-10-01 | | 224.0.0.23 | GLOBECAST-ID | [ ] | | 2000-03-01 | | 224.0.0.24 | OSPFIGP-TE | [ ] | | | | 224.0.0.25 | router-to-switch | [ ] | | 2000-03-01 | | 224.0.0.26 | Unassigned | | | | | 224.0.0.27 | Al MPP Hello | [ ] | | 2000-03-01 | | 224.0.0.28 | ETC Control | [ ] | | 2000-03-01 | | 224.0.0.29 | GE-FANUC | [ ] | | 2000-05-01 | | 224.0.0.30 | indigo-vhdp | [ ] | | 2000-05-01 | | 224.0.0.31 | shinbroadband | [ ] | | 2000-05-01 | | 224.0.0.32 | digistar | [ ] | | 2000-05-01 | | 224.0.0.33 | ff-system-management | [ ] | | 2003-03-01 | | 224.0.0.34 | pt2-discover | [ ] | | 2000-06-01 | | 224.0.0.35 | DXCLUSTER | [ ] | | 2000-07-01 | | 224.0.0.36 | DTCP Announcement | [ ] | | 2001-01-01 | | 224.0.0.37-224.0.0.68 | zeroconfaddr (renew 12/02) | [ ] | | 2001-12-01 | | 224.0.0.69-224.0.0.100 | Unassigned | | | | | 224.0.0.101 | cisco-nhap | [ ] | | 2001-12-01 | | 224.0.0.102 | HSRP | [ ] | | 2001-12-01 | | 224.0.0.103 | MDAP | [ ] | | 2002-02-01 | | 224.0.0.104 | Nokia MC CH | [ ] | | 2002-10-01 | | 224.0.0.105 | ff-lr-address | [ ] | | 2003-03-01 | | 224.0.0.106 | All-Snoopers | [ ] | | | | 224.0.0.107 | PTP-pdelay | [ ][ ] | | 2007-02-02 | | 224.0.0.108 | Saratoga | [ ] | | 2007-08-30 | 2011-03-17 | 224.0.0.109 | LL-MANET-Routers | [ ] | | | 2011-02-23 | 224.0.0.110 | IGRS | [ ] | | 2009-01-20 | | 224.0.0.111 | Babel | [ ] | | | | 224.0.0.112 | MMA Device Discovery | [ ] | | 2011-11-02 | | 224.0.0.113 | AllJoyn | [ ] | | 2011-11-18 | | 224.0.0.114 | Inter RFID Reader Protocol | [ ] | | 2012-06-12 | | 224.0.0.115 | JSDP | [ ] | | 2014-07-01 | | 224.0.0.116 | Device discovery/config | [ ] | | 2016-10-20 | | 224.0.0.117 | DLEP Discovery | [ ] | | 2017-04-03 | | 224.0.0.118 | MAAS | [ ] | | 2017-05-19 | | 224.0.0.119 | ALL_GRASP_NEIGHBORS | [ ] | | 2017-07-20 | | 224.0.0.120 | 3GPP MBMS SACH | [ ] | [ ] | 2022-11-02 | | 224.0.0.121 | ALL_V4_RIFT_ROUTERS | [ ] | | 2023-02-17 | | 224.0.0.122 | Network Virtualization Overlay (NVO) BUM Traffic | [ ] | | 2024-02-02 | | 224.0.0.123-224.0.0.149 | Unassigned | | | | | 224.0.0.150 | Ramp AltitudeCDN MulticastPlus | [ ] | [ ] | 2019-03-13 | | 224.0.0.151 | Unassigned | | | | | 224.0.0.152 | WiseHome | [ ] | [ ] | 2023-08-09 | | 224.0.0.153-224.0.0.250 | Unassigned | | | | | 224.0.0.251 | mDNS | [ ] | | 2000-04-01 | | 224.0.0.252 | Link-local Multicast Name Resolution | [ ] | | | 2011-03-17 | 224.0.0.253 | Teredo | [ ] | | | 2010-02-14 | 224.0.0.254 | RFC3692-style Experiment (*) | [ ] | | | | 224.0.0.255 | Unassigned | | | | | Address(es) | Description | References | Change Controller | Date Registered | Last Reviewed | 224.0.1.0 | VMTP Managers Group | [ ][ ] | | | | 224.0.1.1 | NTP Network Time Protocol | [ ][ ][ ] | | | | 224.0.1.2 | SGI-Dogfight | [ ] | | | | 224.0.1.3 | Rwhod | [ ] | | | | 224.0.1.4 | VNP | [ ] | | | | 224.0.1.5 | Artificial Horizons - Aviator | [ ] | | | | 224.0.1.6 | NSS - Name Service Server | [ ] | | | | 224.0.1.7 | AUDIONEWS - Audio News Multicast | [ ] | | | | 224.0.1.8 | SUN NIS+ Information Service | [ ] | | | | 224.0.1.9 | MTP Multicast Transport Protocol | [ ] | | | | 224.0.1.10 | IETF-1-LOW-AUDIO | [ ] | | | | 224.0.1.11 | IETF-1-AUDIO | [ ] | | | | 224.0.1.12 | IETF-1-VIDEO | [ ] | | | | 224.0.1.13 | IETF-2-LOW-AUDIO | [ ] | | | | 224.0.1.14 | IETF-2-AUDIO | [ ] | | | | 224.0.1.15 | IETF-2-VIDEO | [ ] | | | | 224.0.1.16 | MUSIC-SERVICE | | | | | 224.0.1.17 | SEANET-TELEMETRY | | | | | 224.0.1.18 | SEANET-IMAGE | | | | | 224.0.1.19 | MLOADD | [ ] | | 1996-04-01 | | 224.0.1.20 | any private experiment | [ ] | | | | 224.0.1.21 | DVMRP on MOSPF | [[John Moy]] | | | | 224.0.1.22 | SVRLOC | [ ] | | 1995-05-01 | | 224.0.1.23 | XINGTV | [ ] | | | | 224.0.1.24 | microsoft-ds | [<arnoldmµsoft.com>] | | | | 224.0.1.25 | nbc-pro | [<bloomer&birch.crd.ge.com>] | | | | 224.0.1.26 | nbc-pfn | [<bloomer&birch.crd.ge.com>] | | | | 224.0.1.27 | lmsc-calren-1 | [ ] | | 1994-11-01 | | 224.0.1.28 | lmsc-calren-2 | [ ] | | 1994-11-01 | | 224.0.1.29 | lmsc-calren-3 | [ ] | | 1994-11-01 | | 224.0.1.30 | lmsc-calren-4 | [ ] | | 1994-11-01 | | 224.0.1.31 | ampr-info | [ ] | | 1995-01-01 | | 224.0.1.32 | mtrace | [ ] | | 1995-01-01 | | 224.0.1.33 | RSVP-encap-1 | [ ] | | 1996-04-01 | | 224.0.1.34 | RSVP-encap-2 | [ ] | | 1996-04-01 | | 224.0.1.35 | SVRLOC-DA | [ ] | | 1995-05-01 | | 224.0.1.36 | rln-server | [ ] | | 1995-08-01 | | 224.0.1.37 | proshare-mc | [ ] | | 1995-10-01 | | 224.0.1.38 | Unassigned | | | | | 224.0.1.39 | cisco-rp-announce | [ ] | | 1996-03-01 | | 224.0.1.40 | cisco-rp-discovery | [ ] | | 1996-03-01 | | 224.0.1.41 | gatekeeper | [ ] | | 1996-05-01 | | 224.0.1.42 | iberiagames | [ ] | | 1996-07-01 | | 224.0.1.43 | nwn-discovery | [ ] | | 1996-11-01 | | 224.0.1.44 | nwn-adaptor | [ ] | | 1996-11-01 | | 224.0.1.45 | isma-1 | [ ] | | 1997-01-01 | | 224.0.1.46 | isma-2 | [ ] | | 1997-01-01 | | 224.0.1.47 | telerate | [ ] | | 1997-01-01 | | 224.0.1.48 | ciena | [ ] | | 1997-01-01 | | 224.0.1.49 | dcap-servers | [ ] | | | | 224.0.1.50 | dcap-clients | [ ] | | | | 224.0.1.51 | mcntp-directory | [ ] | | 1997-01-01 | | 224.0.1.52 | mbone-vcr-directory | [ ] | | 1997-01-01 | | 224.0.1.53 | heartbeat | [ ] | | 1997-03-01 | | 224.0.1.54 | sun-mc-grp | [ ] | | 1997-04-01 | | 224.0.1.55 | extended-sys | [ ] | | 1997-04-01 | | 224.0.1.56 | pdrncs | [ ] | | 1997-06-01 | | 224.0.1.57 | tns-adv-multi | [ ] | | 1997-06-01 | | 224.0.1.58 | vcals-dmu | [ ] | | 1997-08-01 | | 224.0.1.59 | zuba | [ ] | | 1997-09-01 | | 224.0.1.60 | hp-device-disc | [ ] | | 1997-07-01 | | 224.0.1.61 | tms-production | [ ] | | 1997-07-01 | | 224.0.1.62 | sunscalar | [ ] | | 1997-08-01 | | 224.0.1.63 | mmtp-poll | [ ] | | 1997-09-01 | | 224.0.1.64 | compaq-peer | [ ] | | 1997-10-01 | | 224.0.1.65 | iapp | [ ] | | 1997-12-01 | | 224.0.1.66 | multihasc-com | [ ] | | 1997-12-01 | | 224.0.1.67 | serv-discovery | [ ] | | 1997-12-01 | | 224.0.1.68 | mdhcpdisover | [ ] | | | | 224.0.1.69 | MMP-bundle-discovery1 | [ ] | | 1998-02-01 | | 224.0.1.70 | MMP-bundle-discovery2 | [ ] | | 1998-02-01 | | 224.0.1.71 | XYPOINT DGPS Data Feed | [ ] | | 1998-02-01 | | 224.0.1.72 | GilatSkySurfer | [ ] | | 1998-02-01 | | 224.0.1.73 | SharesLive | [ ] | | 1997-03-01 | | 224.0.1.74 | NorthernData | [[Sheers]] | | | | 224.0.1.75 | SIP | [[Schulzrinne]] | | | | 224.0.1.76 | IAPP | [ ] | | 1998-03 | | 224.0.1.77 | AGENTVIEW | [ ] | | 1998-03-01 | | 224.0.1.78 | Tibco Multicast1 | [ ] | | 1998-04-01 | | 224.0.1.79 | Tibco Multicast2 | [ ] | | 1998-04-01 | | 224.0.1.80 | MSP | [ ] | | 1998-06-01 | | 224.0.1.81 | OTT (One-way Trip Time) | [ ] | | 1998-06-01 | | 224.0.1.82 | TRACKTICKER | [ ] | | 1998-08-01 | | 224.0.1.83 | dtn-mc | [ ] | | 1998-08-01 | | 224.0.1.84 | jini-announcement | [ ] | | 1998-08-01 | | 224.0.1.85 | jini-request | [ ] | | 1998-08-01 | | 224.0.1.86 | sde-discovery | [ ] | | 1998-08-01 | | 224.0.1.87 | DirecPC-SI | [ ] | | 1998-08-01 | | 224.0.1.88 | B1RMonitor | [ ] | | 1998-09-01 | | 224.0.1.89 | 3Com-AMP3 dRMON | [ ] | | 1998-09-01 | | 224.0.1.90 | imFtmSvc | [ ] | | 1998-09-01 | | 224.0.1.91 | NQDS4 | [ ] | [ ] | 1998-09-01 | | 224.0.1.92 | NQDS5 | [ ] | [ ] | 1998-09-01 | | 224.0.1.93 | NQDS6 | [ ] | [ ] | 1998-09-01 | | 224.0.1.94 | NLVL12 | [ ] | [ ] | 1998-09-01 | | 224.0.1.95 | NTDS1 | [ ] | [ ] | 1998-09-01 | | 224.0.1.96 | NTDS2 | [ ] | [ ] | 1998-09-01 | | 224.0.1.97 | NODSA | [ ] | [ ] | 1998-09-01 | | 224.0.1.98 | NODSB | [ ] | [ ] | 1998-09-01 | | 224.0.1.99 | NODSC | [ ] | [ ] | 1998-09-01 | | 224.0.1.100 | NODSD | [ ] | [ ] | 1998-09-01 | | 224.0.1.101 | NQDS4R | [ ] | [ ] | 1998-09-01 | | 224.0.1.102 | NQDS5R | [ ] | [ ] | 1998-09-01 | | 224.0.1.103 | NQDS6R | [ ] | [ ] | 1998-09-01 | | 224.0.1.104 | NLVL12R | [ ] | [ ] | 1998-09-01 | | 224.0.1.105 | NTDS1R | [ ] | [ ] | 1998-09-01 | | 224.0.1.106 | NTDS2R | [ ] | [ ] | 1998-09-01 | | 224.0.1.107 | NODSAR | [ ] | [ ] | 1998-09-01 | | 224.0.1.108 | NODSBR | [ ] | [ ] | 1998-09-01 | | 224.0.1.109 | NODSCR | [ ] | [ ] | 1998-09-01 | | 224.0.1.110 | NODSDR | [ ] | [ ] | 1998-09-01 | | 224.0.1.111 | MRM | [ ] | | 1998-10-01 | | 224.0.1.112 | TVE-FILE | [ ] | | 1998-11-01 | | 224.0.1.113 | TVE-ANNOUNCE | [ ] | | 1998-11-01 | | 224.0.1.114 | Mac Srv Loc | [ ] | | 1998-11-01 | | 224.0.1.115 | Simple Multicast | [ ] | | 1998-11-01 | | 224.0.1.116 | SpectraLinkGW | [ ] | | 1998-11-01 | | 224.0.1.117 | dieboldmcast | [ ] | | 1998-11-01 | | 224.0.1.118 | Tivoli Systems | [ ] | | 1998-12-01 | | 224.0.1.119 | pq-lic-mcast | [ ] | | 1998-12-01 | | 224.0.1.120 | Pico | [ ] | [ ] | 2007-03-01 | | 224.0.1.121 | Pipesplatform | [ ] | | 1998-12-01 | | 224.0.1.122 | LiebDevMgmg-DM | [ ] | | 1999-01-01 | | 224.0.1.123 | TRIBALVOICE | [ ] | | 1999-01-01 | | 224.0.1.124 | Unassigned (Retracted 1/29/01) | | | | | 224.0.1.125 | PolyCom Relay1 | [[Coutiere]] | | | | 224.0.1.126 | Infront Multi1 | [ ] | | 1999-03-01 | | 224.0.1.127 | XRX DEVICE DISC | [ ] | | 1999-03-01 | | 224.0.1.128 | CNN | [ ] | | 1999-04-01 | | 224.0.1.129 | PTP-primary | [ ][ ] | | 2007-02-02 | | 224.0.1.130 | PTP-alternate1 | [ ][ ] | | 2007-02-02 | | 224.0.1.131 | PTP-alternate2 | [ ][ ] | | 2007-02-02 | | 224.0.1.132 | PTP-alternate3 | [ ][ ] | | 2007-02-02 | | 224.0.1.133 | ProCast | [ ] | | 1999-04-01 | | 224.0.1.134 | 3Com Discp | [ ] | | 1999-04-01 | | 224.0.1.135 | CS-Multicasting | [ ] | | 1999-05-01 | | 224.0.1.136 | TS-MC-1 | [ ] | | 1999-06-01 | | 224.0.1.137 | Make Source | [ ] | | 1999-06-01 | | 224.0.1.138 | Teleborsa | [ ] | | 1999-06-01 | | 224.0.1.139 | SUMAConfig | [ ] | | 1999-07-01 | | 224.0.1.140 | capwap-ac | [ ] | | | | 224.0.1.141 | DHCP-SERVERS | [ ] | | 1999-10-01 | | 224.0.1.142 | CN Router-LL | [ ] | | 1999-08-01 | | 224.0.1.143 | EMWIN | [ ] | | 2008-02-04 | | 224.0.1.144 | Alchemy Cluster | [ ][ ] | | 1999-08-01 | | 224.0.1.145 | Satcast One | [ ] | | 1999-08-01 | | 224.0.1.146 | Satcast Two | [ ] | | 1999-08-01 | | 224.0.1.147 | Satcast Three | [ ] | | 1999-08-01 | | 224.0.1.148 | Intline | [ ] | | 2000-02-01 | | 224.0.1.149 | 8x8 Multicast | [ ] | | 1999-09-01 | | 224.0.1.150 | Ramp AltitudeCDN MulticastPlus | [ ] | [ ] | 2019-03-13 | | 224.0.1.151 | Intline-1 | [ ] | | 2000-02-01 | | 224.0.1.152 | Intline-2 | [ ] | | 2000-02-01 | | 224.0.1.153 | Intline-3 | [ ] | | 2000-02-01 | | 224.0.1.154 | Intline-4 | [ ] | | 2000-02-01 | | 224.0.1.155 | Intline-5 | [ ] | | 2000-02-01 | | 224.0.1.156 | Intline-6 | [ ] | | 2000-02-01 | | 224.0.1.157 | Intline-7 | [ ] | | 2000-02-01 | | 224.0.1.158 | Intline-8 | [ ] | | 2000-02-01 | | 224.0.1.159 | Intline-9 | [ ] | | 2000-02-01 | | 224.0.1.160 | Intline-10 | [ ] | | 2000-02-01 | | 224.0.1.161 | Intline-11 | [ ] | | 2000-02-01 | | 224.0.1.162 | Intline-12 | [ ] | | 2000-02-01 | | 224.0.1.163 | Intline-13 | [ ] | | 2000-02-01 | | 224.0.1.164 | Intline-14 | [ ] | | 2000-02-01 | | 224.0.1.165 | Intline-15 | [ ] | | 2000-02-01 | | 224.0.1.166 | marratech-cc | [ ] | | 2000-02-01 | | 224.0.1.167 | EMS-InterDev | [ ] | | 2000-02-01 | | 224.0.1.168 | itb301 | [ ] | | 2000-03-01 | | 224.0.1.169 | rtv-audio | [ ] | | 2000-07-01 | | 224.0.1.170 | rtv-video | [ ] | | 2000-07-01 | | 224.0.1.171 | HAVI-Sim | [ ] | | 2000-07-01 | | 224.0.1.172 | Nokia Cluster | [ ][ ] | | 1999-08-01 | | 224.0.1.173 | host-request | [ ] | | 2001-06-01 | | 224.0.1.174 | host-announce | [ ] | | 2001-06-01 | | 224.0.1.175 | ptk-cluster | [ ] | | 2001-12-01 | | 224.0.1.176 | Proxim Protocol | [ ] | | 2002-02-01 | | 224.0.1.177 | Gemtek Systems | [ ] | | 2002-10-01 | | 224.0.1.178 | IEEE IAPP | [ ] | | 2003-01-01 | | 224.0.1.179 | 1451_Dot5_802_Discovery | [ ] | | 2006-04-11 | | 224.0.1.180 | 1451_Dot5_802_Group_1 | [ ] | | 2006-04-11 | | 224.0.1.181 | 1451_Dot5_802_Group_2 | [ ] | | 2006-04-11 | | 224.0.1.182 | 1451_Dot5_802_Group_3 | [ ] | | 2006-04-11 | | 224.0.1.183 | 1451_Dot5_802_Group_4 | [ ] | | 2006-04-11 | | 224.0.1.184 | VFSDP | [ ] | | 2007-03-06 | | 224.0.1.185 | ASAP | [ ] | | | | 224.0.1.186 | SL-MANET-ROUTERS | [ ] | | | | 224.0.1.187 | All CoAP Nodes | [ ] | | 2013-07-25 | | 224.0.1.188 | BRSDP | [ ] | [ ] | 2019-02-20 | | 224.0.1.189 | Amateur radio DMR | [ ][ ] | [ ] | 2021-02-08 | | 224.0.1.190 | All CoRE Resource Directories | [ ] | | 2021-03-16 | | 224.0.1.191-224.0.1.255 | Unassigned | | | | | Address(es) | Description | References | Change Controller | Date Registered | Last Reviewed | 224.0.2.0 | Unassigned | | | | | 224.0.2.1 | "rwho" Group (BSD) (unofficial) | [ ] | | | | 224.0.2.2 | SUN RPC PMAPPROC_CALLIT | [ ] | | | | 224.0.2.3 | EPSON-disc-set | [ ] | | 2005-01-01 | | 224.0.2.4 | All C1222 Nodes | [ ] | | 2009-08-28 | | 224.0.2.5 | Monitoring Discovery Protocol | [ ] | | 2012-04-17 | | 224.0.2.6 | BitSend MediaStreams | [ ] | | 2012-04-25 | | 224.0.2.7-224.0.2.8 | rxWARN | [ ] | | 2012-11-19 | | 224.0.2.9 | DATV streams | [ ] | | 2016-10-04 | | 224.0.2.10 | swapapp_multicast | [ ] | | 2017-05-19 | | 224.0.2.11 | LDA Discovery Service | [ ] | [ ] | 2018-10-17 | | 224.0.2.12 | CNP-HD-PLC | [ ] | [ ] | 2018-11-15 | | 224.0.2.13 | BSE | [ ] | [ ] | 2019-01-17 | | 224.0.2.14 | OPC Discovery | [ ] | [ ] | 2019-08-19 | | 224.0.2.15 | Unassigned | | | | | 224.0.2.16-224.0.2.17 | unidns | [ ] | [ ] | 2023-01-18 | | 224.0.2.18 | vivoh-directory-1 | [ ] | [ ] | 2023-10-13 | | 224.0.2.19 | vivoh-directory-2 | [ ] | [ ] | 2023-10-13 | | 224.0.2.20-224.0.2.63 | Unassigned | | | | | 224.0.2.64-224.0.2.95 | Intercontinental Exchange, Inc. | [ ] | [ ] | 1996-04 | 2007-07 | 224.0.2.96-224.0.2.127 | BallisterNet | [ ] | [ ] | 1997-07-01 | 2021-06-11 | 224.0.2.128-224.0.2.191 | WOZ-Garage | [ ] | | 1997-02-01 | | 224.0.2.192-224.0.2.255 | Intercontinental Exchange, Inc. | [ ] | [ ] | 1997-02-01 | | 224.0.3.0-224.0.3.255 | RFE Generic Service | [ ] | | | | 224.0.4.0-224.0.4.255 | RFE Individual Conferences | [ ] | | | | 224.0.5.0-224.0.5.127 | CDPD Groups | [[Bob Brenner]] | | | | 224.0.5.128-224.0.5.191 | Intercontinental Exchange, Inc. | [ ] | [ ] | 1998-10-01 | | 224.0.5.192-224.0.5.255 | Intercontinental Exchange, Inc. | [ ] | [ ] | 2001-08-01 | | 224.0.6.0-224.0.6.127 | Cornell ISIS Project | [[Tim Clark]] | | | | 224.0.6.128-224.0.6.143 | MoeSingh | [ ] | | 2009-09-24 | | 224.0.6.144 | QDNE | [ ] | | 2018-01-03 | | 224.0.6.145-224.0.6.150 | Unassigned | | | | | 224.0.6.151 | Canon-Device-control | [ ] | | 2014-08-01 | | 224.0.6.152-224.0.6.191 | Unassigned | | | | | 224.0.6.192-224.0.6.255 | OneChicago multicast | [ ] | | 2014-09-19 | | 224.0.7.0-224.0.7.255 | Where-Are-You | [ ] | | 1994-11-01 | | 224.0.8.0 | Cell Broadcast Encapsulation | [ ][ ] | [ ] [ ] | 2017-10-13 | | 224.0.8.1-224.0.8.255 | Civic Telemetry | [ ][ ] | [ ] [ ] | 2020-10-07 | | 224.0.9.0-224.0.9.255 | The Thing System | [ ] | | 1998-04-01 | | 224.0.10.0-224.0.10.255 | DLSw Groups | [ ] | | 1996-04-01 | | 224.0.11.0-224.0.11.255 | NCC.NET Audio | [ ] | | 1996-08-01 | | 224.0.12.0-224.0.12.63 | Microsoft and MSNBC | [ ] | | 1996-11-01 | | 224.0.12.64-224.0.12.231 | AsiaNext | [ ] | [ ] | 2023-03-03 | | 224.0.12.136-224.0.12.255 | Unassigned | | | | | 224.0.13.0-224.0.13.255 | WorldCom Broadcast Services | [ ] | | 1997-01-01 | | 224.0.14.0-224.0.14.255 | NLANR | [ ] | | 1997-02-01 | | 224.0.15.0-224.0.15.255 | Agilent Technologies | [ ] | | 1997-02-01 | | 224.0.16.0-224.0.16.255 | XingNet | [ ] | | 1997-04-01 | | 224.0.17.0-224.0.17.31 | Mercantile & Commodity Exchange | [ ] | | 1997-07-01 | | 224.0.17.32-224.0.17.63 | NDQMD1 | [ ] | [ ] | 1999-03-01 | | 224.0.17.64-224.0.17.127 | ODN-DTV | [ ] | | 1999-03-01 | | 224.0.17.128-224.0.17.255 | Unassigned | | | | | 224.0.18.0-224.0.18.255 | Dow Jones | [ ] | | 1997-01-01 | | 224.0.19.0-224.0.19.63 | Walt Disney Company | [ ] | | 1997-08-01 | | 224.0.19.64-224.0.19.95 | Cal Multicast | [ ] | | 1997-10-01 | | 224.0.19.96-224.0.19.127 | Intercontinental Exchange, Inc. | [ ] | [ ] | 1997-10 | 2007-07 | 224.0.19.128-224.0.19.191 | IIG Multicast | [ ] | | 1997-12-01 | | 224.0.19.192-224.0.19.207 | Metropol | [ ] | | 1998-05-01 | | 224.0.19.208-224.0.19.239 | Xenoscience, Inc. | [ ] | | 1998-07-01 | | 224.0.19.240-224.0.19.255 | MJDPM | [ ] | | 2007-03-01 | | 224.0.20.0-224.0.20.63 | MS-IP/TV | [ ] | | 1998-07-01 | | 224.0.20.64-224.0.20.127 | Reliable Network Solutions | [ ] | | 1998-08-01 | | 224.0.20.128-224.0.20.143 | TRACKTICKER Group | [ ] | | 1998-08-01 | | 224.0.20.144-224.0.20.207 | CNR Rebroadcast MCA | [ ] | | 1999-08-01 | | 224.0.20.208-224.0.20.255 | Unassigned | | | | | 224.0.21.0-224.0.21.127 | Talarian MCAST | [ ] | | 1999-01-01 | | 224.0.21.128-224.0.21.255 | Unassigned | | | | | 224.0.22.0-224.0.22.239 | WORLD MCAST | [ ] | | 1999-06-01 | | 224.0.22.240-224.0.22.255 | Jones International | [ ] | | 2007-10-31 | | 224.0.23.0 | ECHONET | [ ] | | 2003-02-01 | | 224.0.23.1 | Ricoh-device-ctrl | [ ] | | 2003-02-01 | | 224.0.23.2 | Ricoh-device-ctrl | [ ] | | 2003-02-01 | | 224.0.23.3-224.0.23.10 | Telefeed | [ ] | | 2003-04-01 | | 224.0.23.11 | SpectraTalk | [ ] | | 2003-05-01 | | 224.0.23.12 | KNXnet/IP | [ ] | [ ] | 2003-07-01 | 2023-08-23 | 224.0.23.13 | TVE-ANNOUNCE2 | [ ] | | 2003-10-01 | | 224.0.23.14 | DvbServDisc | [ ] | | 2004-01-01 | | 224.0.23.15-224.0.23.31 | MJDPM | [ ] | | 2007-03-01 | | 224.0.23.32 | Norman MCMP | [ ] | | 2004-02-01 | | 224.0.23.33 | RRDP | [ ] | | 2004-06-01 | | 224.0.23.34 | AF_NA | [ ] | | 2005-10-28 | | 224.0.23.35 | AF_OPRA_NBBO | [ ] | | 2005-10-28 | | 224.0.23.36 | AF_OPRA_FULL | [ ] | | 2005-10-28 | | 224.0.23.37 | AF_NEWS | [ ] | | 2005-10-28 | | 224.0.23.38 | AF_NA_CHI | [ ] | | 2005-10-28 | | 224.0.23.39 | AF_OPRA_NBBO_CHI | [ ] | | 2005-10-28 | | 224.0.23.40 | AF_OPRA_FULL_CHI | [ ] | | 2005-10-28 | | 224.0.23.41 | AF_NEWS_CHI | [ ] | | 2005-10-28 | | 224.0.23.42 | Control for IP Video | [ ] | | 2005-02-01 | | 224.0.23.43 | acp-discovery | [ ] | | 2005-02-01 | | 224.0.23.44 | acp-management | [ ] | | 2005-02-01 | | 224.0.23.45 | acp-data | [ ] | | 2005-02-01 | | 224.0.23.46 | dof-multicast | [ ] | | 2006-06-16 | 2015-04-23 | 224.0.23.47 | AF_DOB_CHI | [ ] | | 2005-10-28 | | 224.0.23.48 | AF_OPRA_FULL2_CHI | [ ] | | 2005-10-28 | | 224.0.23.49 | AF_DOB | [ ] | | 2005-10-28 | | 224.0.23.50 | AF_OPRA_FULL2 | [ ] | | 2005-10-28 | | 224.0.23.51 | Fairview | [ ] | | 2006-08-07 | | 224.0.23.52 | Intercontinental Exchange, Inc. | [ ] | [ ] | 2006-08-11 | | 224.0.23.53 | MCP | [ ] | | 2006-11-30 | | 224.0.23.54 | ServDiscovery | [ ] | | 2007-01-17 | | 224.0.23.55 | noaaport1 | [ ] | | 2008-02-04 | | 224.0.23.56 | noaaport2 | [ ] | | 2008-02-04 | | 224.0.23.57 | noaaport3 | [ ] | | 2008-02-04 | | 224.0.23.58 | noaaport4 | [ ] | | 2008-02-04 | | 224.0.23.59 | DigacIP7 | [ ] | | 2008-02-22 | | 224.0.23.60 | AtscSvcSig | [ ] | | 2008-12-19 | | 224.0.23.61 | SafetyNET p (potentially IGMPv1) | [ ] | | 2009-03-13 | | 224.0.23.62 | BluemoonGamesMC | [ ] | | 2009-05-12 | | 224.0.23.63 | iADT Discovery | [ ] | | 2009-05-12 | | 224.0.23.64-224.0.23.80 | Moneyline | [ ] | | 2004-01-01 | | 224.0.23.81-224.0.23.127 | Reserved (Moneyline) | | | | | 224.0.23.128-224.0.23.157 | PHLX | [ ] | [ ] | 2004-01-01 | | 224.0.23.158 | VSCP | [ ] | | 2005-09-01 | | 224.0.23.159 | LXI-EVENT | [ ] | | 2005-11-04 | | 224.0.23.160 | solera_lmca | [ ] | | 2006-02-09 | | 224.0.23.161 | VBooster | [ ] | | 2006-03-17 | | 224.0.23.162 | cajo discovery | [ ] | | 2006-03-17 | | 224.0.23.163 | INTELLIDEN | [ ] | | 2006-03-31 | | 224.0.23.164 | IceEDCP | [ ] | | 2006-07-11 | | 224.0.23.165 | omasg | [ ] | | 2006-07-11 | | 224.0.23.166 | MEDIASTREAM | [ ] | | 2006-08-15 | | 224.0.23.167 | Systech Mcast | [ ] | | 2006-08-21 | | 224.0.23.168 | tricon-system-management | [ ] | | 2007-07-06 | | 224.0.23.169 | MNET discovery | [ ] | | 2008-01-14 | | 224.0.23.170 | CCNx (not for global routing) | [ ] | | 2009-09-24 | | 224.0.23.171 | LLAFP | [ ] | | 2009-11-11 | | 224.0.23.172 | UFMP | [ ] | [ ] | 2010-02-04 | | 224.0.23.173 | PHILIPS-HEALTH | [ ] | [ ] | 2010-02-26 | | 224.0.23.174 | PHILIPS-HEALTH | [ ] | [ ] | 2010-02-26 | | 224.0.23.175 | QDP | [ ] | | 2010-03-12 | | 224.0.23.176 | CalAmp WCP | [ ] | | 2011-06-06 | | 224.0.23.177 | AES discovery | [ ] | | 2012-08-28 | | 224.0.23.178 | JDP Java Discovery Protocol | [ ] | | 2013-02-08 | | 224.0.23.179 | PixelPusher | [ ] | | 2014-06-04 | | 224.0.23.180 | network metronome | [ ] | | 2014-12-17 | | 224.0.23.181 | polaris-video-transport | [ ] | | 2016-04-19 | | 224.0.23.182-224.0.23.191 | Unassigned | | | | | 224.0.23.192-224.0.23.255 | PINKOTC | [ ] | | 2008-08-12 | | 224.0.24.0-224.0.24.127 | AGSC UK VVs | [ ] | | 2006-06-09 | | 224.0.24.128-224.0.24.255 | EM-MULTI | [ ] | | 2006-08-07 | | 224.0.25.0-224.0.28.255 | CME Market Data | [ ] | [ ] | 2007-03-22 | | 224.0.29.0-224.0.30.255 | Deutsche Boerse | [ ] | | 2007-03-22 | | 224.0.31.0-224.0.34.255 | CME Market Data | [ ] | [ ] | 2007-07-17 | | 224.0.35.0-224.0.35.255 | M2S | [ ] | | 2007-08-31 | | 224.0.36.0-224.0.36.255 | DigiPlay | [ ] | | 2016-09-29 | | 224.0.37.0-224.0.38.255 | London Metal Exchange | [ ] | [ ] | 2017-03-24 | | 224.0.39.0-224.0.40.255 | CDAS | [ ] | | 2007-09-12 | | 224.0.41.0-224.0.41.255 | Intercontinental Exchange, Inc. | [ ] | [ ] | 2007-11-28 | 2011-02-15 | 224.0.42.0-224.0.45.255 | Media Systems | [ ] | [ ] | 2008-01-15 | | 224.0.46.0-224.0.50.255 | Deutsche Boerse | [ ] | | 2008-01-25 | | 224.0.51.0-224.0.51.255 | ALCOM-IPTV | [ ] | [ ] | 2008-04-09 | 2018-02-20 | 224.0.52.0-224.0.53.255 | Euronext | [ ] | [ ] | 2008-07-23 | 2014-11-24 | 224.0.54.0-224.0.57.255 | Telia Norway mcast | [ ] | [ ] | 2008-08-20 | | 224.0.58.0-224.0.61.255 | Intercontinental Exchange, Inc. | [ ] | [ ] | 2008-08-27 | | 224.0.62.0-224.0.62.255 | BATS | [ ] | [ ] | 2008-12-24 | | 224.0.63.0-224.0.63.255 | BATS Trading | [ ] | [ ] | 2009-03-13 | | 224.0.64.0-224.0.67.255 | Euronext | [ ] | [ ] | 2009-03-13 | 2014-11-24 | 224.0.68.0-224.0.69.255 | Nasdaq Inc. | [ ] | [ ] | 2009-05-12 | | 224.0.70.0-224.0.71.255 | Intercontinental Exchange, Inc. | [ ] | [ ] | 2009-06-16 | 2011-03-01 | 224.0.72.0-224.0.72.255 | TMX | [ ] | [ ] | 2009-08-28 | | 224.0.73.0-224.0.74.255 | Direct Edge | [ ] | [ ] | 2009-08-28 | | 224.0.75.0-224.0.75.255 | Nasdaq Inc. | [ ] | [ ] | 2010-01-22 | | 224.0.76.0-224.0.76.255 | Intercontinental Exchange, Inc. | [ ] | [ ] | 2010-02-26 | 2011-03-01 | 224.0.77.0-224.0.77.255 | Intercontinental Exchange, Inc. | [ ] | [ ] | 2010-02-26 | | 224.0.78.0-224.0.78.255 | ALCOM-IPTV | [ ] | [ ] | 2010-03-12 | 2018-02-20 | 224.0.79.0-224.0.81.255 | Nasdaq Inc. | [ ] | [ ] | 2010-08-24 | | 224.0.82.0-224.0.85.255 | BATS Trading | [ ] | [ ] | 2011-01-31 | | 224.0.86.0-224.0.101.255 | Intercontinental Exchange, Inc. | [ ] | [ ] | 2011-02-10 | | 224.0.102.0-224.0.102.127 | Intercontinental Exchange, Inc. | [ ] | [ ] | 2011-04-13 | | 224.0.102.128-224.0.102.255 | MVS-IPTV-2 | [ ] | [ ] | 2014-06-12 | | 224.0.103.0-224.0.104.255 | MVS-IPTV | [ ][ ] | [ ] | 2011-04-20 | | 224.0.105.0-224.0.105.127 | MIAX Multicast | [ ] | [ ] | 2011-06-06 | | 224.0.105.128-224.0.105.255 | MVS-IPTV3 | [ ] | [ ] | 2017-12-04 | | 224.0.106.0-224.0.106.255 | TMX | [ ] | [ ] | 2011-06-16 | | 224.0.107.0-224.0.108.255 | TSX Inc. | [ ] | [ ] | 2011-07-13 | | 224.0.109.0-224.0.110.255 | TSX Inc. | [ ] | [ ] | 2011-10-25 | | 224.0.111.0-224.0.111.255 | VoleraDataFeed | [ ] | [ ] | 2011-10-25 | | 224.0.112.0-224.0.112.255 | JHB-STOCK-EXCH | [ ] | | 2011-12-07 | | 224.0.113.0-224.0.114.255 | Deutsche Boerse | [ ] | | 2011-12-19 | | 224.0.115.0-224.0.115.255 | TMX | [ ] | [ ] | 2012-06-12 | | 224.0.116.0-224.0.116.255 | Intercontinental Exchange, Inc | [ ] | [ ] | 2012-06-19 | | 224.0.117.0-224.0.119.255 | Nasdaq Inc. | [ ] | [ ] | 2012-07-12 | | 224.0.120.0-224.0.120.255 | czechbone iptv | [ ] | [ ] | 2013-01-15 | | 224.0.121.0-224.0.121.255 | AQUIS-EXCHANGE | [ ] | [ ] | 2013-05-13 | | 224.0.122.0-224.0.123.255 | DNS:NET TV | [ ] | | 2013-05-25 | | 224.0.124.0-224.0.124.255 | Boston Options Exchange | [ ][ ] | | 2013-05-30 | | 224.0.125.0-224.0.125.255 | Hanweck Associates | [ ] | [ ] | 2013-09-05 | | 224.0.126.0-224.0.129.255 | Intercontinental Exchange, Inc. | [ ] | [ ] | 2013-10-31 | | 224.0.130.0-224.0.131.255 | BATS Trading | [ ] | [ ] | 2014-03-05 | | 224.0.132.0-224.0.135.255 | Net By Net Holding IPTV | [ ] | | 2014-04-12 | | 224.0.136.0-224.0.139.255 | Aequitas Innovations Inc. | [ ] | [ ] | 2014-05-16 | | 224.0.140.0-224.0.140.255 | Instinet | [ ] | [ ] | 2014-09-04 | | 224.0.141.0-224.0.141.255 | MIAX-2 | [ ] | [ ] | 2015-06-30 | | 224.0.142.0-224.0.142.255 | MIAX M3 | [ ] | [ ] | 2017-05-19 | | 224.0.143.0-224.0.143.255 | A2X-EXCHANGE | [ ] | | 2017-06-02 | | 224.0.144.0-224.0.151.255 | VZ-Multicast-Public | [ ] | | 2015-03-23 | | 224.0.152.0-224.0.152.255 | cse-md | [ ] | | 2016-04-19 | | 224.0.153.0-224.0.156.255 | Telia Norway mcast | [ ] | [ ] | 2016-05-24 | | 224.0.157.0-224.0.157.255 | London Metal Exchange | [ ] | [ ] | 2017-01-23 | | 224.0.158.0-224.0.159.255 | TriAct Canada Marketplace LP | [ ] | | 2017-01-23 | | 224.0.160.0-224.0.165.255 | Deutsche Boerse | [ ] | | 2016-07-07 | | 224.0.166.0-224.0.167.255 | Virgin Connect IPTV | [ ] | | 2017-02-17 | | 224.0.168.0-224.0.169.255 | Deutsche Boerse | [ ] | | 2017-12-05 | | 224.0.170.0-224.0.170.255 | MVS-IPTV4 | [ ] | [ ] | 2018-06-07 | | 224.0.171.0-224.0.171.255 | COINBASE-MARKETS | [ ] | [ ] | 2019-01-25 | | 224.0.172.0-224.0.175.255 | Deutsche Boerse | [ ] | | 2018-06-19 | | 224.0.176.0-224.0.179.255 | MIAX-EX-3-4-5 | [ ] | [ ] | 2018-07-31 | | 224.0.180.0-224.0.181.255 | CBOE Europe | [ ] | [ ] | 2019-02-13 | | 224.0.182.0-224.0.183.255 | ALCOM-TV | [ ] | [ ] | 2019-02-28 | | 224.0.184.0-224.0.184.255 | AQUIS-EXCHANGE | [ ] | [ ] | 2019-08-28 | | 224.0.185.0-224.0.185.255 | Hanweck Associates | [ ] | [ ] | 2019-09-12 | | 224.0.186.0-224.0.186.255 | BOX Options Market | [ ] | [ ] | 2019-10-02 | | 224.0.187.0-224.0.188.255 | MVS-IPTV5 | [ ] | [ ] | 2019-11-13 | | 224.0.189.0-224.0.189.255 | Ido Rosen | [ ] | [ ] | 2021-03-23 | | 224.0.190.0-224.0.191.255 | RTP Media | [ ] | [ ] | 2020-10-01 | | 224.0.192.0-224.0.207.255 | Intercontinental Exchange, Inc. | [ ] | [ ] | 2021-04-01 | | 224.0.208.0-224.0.213.255 | Euronext | [ ] | [ ] | 2021-04-13 | | 224.0.214.0-224.0.214.255 | OSK B2B mVPN distribution | [ ] | [ ] | 2021-06-11 | | 224.0.215.0-224.0.215.255 | Tradeweb CLOB | [ ] | [ ] | 2022-01-06 | | 224.0.216.0-224.0.219.255 | RTP Media | [ ] | [ ] | 2021-07-30 | | 224.0.220.0-224.0.223.255 | Japan Exchange Group | [ ] | [ ] | 2021-09-07 | | 224.0.224.0-224.0.224.255 | AQUIS-EXCHANGE | [ ] | [ ] | 2021-12-21 | | 224.0.225.0-224.0.225.255 | Kalejdo TV | [ ] | [ ] | 2022-08-26 | | 224.0.226.0-224.0.227.255 | MVS-IPTV6 | [ ] | [ ] | 2022-06-09 | | 224.0.228.0-224.0.231.255 | London Metal Exchange | [ ] | [ ] | 2022-02-01 | | 224.0.232.0-224.0.239.255 | Lucera Financial Infra | [ ] | [ ] | 2022-02-17 | | 224.0.240.0-224.0.243.255 | London Metal Exchange | [ ] | [ ] | 2022-05-26 | | 224.0.244.0-224.0.244.255 | Clearpool AMS | [ ] | [ ] | 2023-05-19 | | 224.0.245.0-224.0.245.255 | OneChronos | [ ] | [ ] | 2023-08-29 | | 224.0.246.0-224.0.246.255 | MEMX Memoir | [ ] | [ ] | 2024-01-22 | | 224.0.247.0-224.0.247.255 | BOX Options Market | [ ] | [ ] | 2024-02-27 | | 224.0.248.0-224.0.249.255 | Unassigned | | | | | 224.0.250.0-224.0.251.255 | KPN Broadcast Services | [ ][ ] | | 2009-09-01 | | 224.0.252.0-224.0.252.255 | KPN Broadcast Services | [ ][ ] | | 2005-08-01 | | 224.0.253.0-224.0.253.255 | KPN Broadcast Services | [ ][ ] | | 2005-08-01 | | 224.0.254.0-224.0.254.255 | Intelsat IPTV | [ ] | | 2006-03-31 | 2011-02-22 | 224.0.255.0-224.0.255.255 | Intelsat IPTV | [ ] | | 2006-03-31 | 2011-02-22 | Address(es) | Description | References | Change Controller | Date Registered | Last Reviewed | 224.1.0.0-224.1.0.37 | Reserved | [ ] | | | | 224.1.0.38 | dantz | [ ] | | 2004-05-01 | | 224.1.0.39-224.1.1.255 | Reserved | [ ] | | | | 224.1.2.0-224.1.2.255 | Intercontinental Exchange, Inc. | [ ] | [ ] | 2006-02-17 | | 224.1.3.0-224.1.4.255 | NOB Cross media facilities | [ ] | | 2006-05-22 | | 224.1.5.0-224.1.255.255 | Reserved | [ ] | | | | Address(es) | Description | References | Change Controller | Date Registered | Last Reviewed | 224.2.0.0-224.2.127.253 | Multimedia Conference Calls | [ ] | | | | 224.2.127.254 | SAPv1 Announcements | [ ] | | | | 224.2.127.255 | SAPv0 Announcements (deprecated) | [ ] | | | | 224.2.128.0-224.2.255.255 | SAP Dynamic Assignments | [ ] | | | | Address(es) | Description | References | Change Controller | Date Registered | Last Reviewed | 224.3.0.0-224.3.0.63 | Nasdaqmdfeeds (re-new/March 2003) | [ ] | [ ] | 1999-03-01 | | 224.3.0.64-224.3.255.255 | Unassigned | | | | | 224.4.0.0-224.4.0.255 | London Stock Exchange Group | [ ] | [ ] | 2006-03-31 | | 224.4.1.0-224.4.1.255 | London Stock Exchange Group | [ ] | [ ] | 2008-02-25 | | 224.4.2.0-224.4.2.255 | London Stock Exchange Group | [ ] | [ ] | 2008-02-29 | | 224.4.3.0-224.4.4.255 | London Stock Exchange Group | [ ] | [ ] | 2008-12-24 | | 224.4.5.0-224.4.6.255 | London Stock Exchange Group | [ ] | [ ] | 2009-05-12 | | 224.4.7.0-224.4.7.255 | CBOE Holdings | [ ] | [ ] | 2012-04-10 | | 224.4.8.0-224.4.9.255 | Nasdaq Inc. | [ ] | [ ] | 2012-04-11 | | 224.4.10.0-224.4.13.255 | London Stock Exchange Group | [ ] | [ ] | 2012-04-11 | | 224.4.14.0-224.4.17.255 | London Stock Exchange Group | [ ] | [ ] | 2018-01-04 | | 224.4.18.0-224.4.21.255 | London Stock Exchange Group | [ ] | [ ] | 2021-02-04 | | 224.4.22.0-224.4.23.255 | London Stock Exchange Group | [ ] | [ ] | 2021-09-21 | | 224.4.24.0-224.4.31.255 | Fenics Market Data | [ ] | [ ] | 2023-01-18 | | 224.4.32.0-224.4.33.255 | Global Futures & Options Ltd | [ ] | [ ] | 2023-03-15 | | 224.4.34.0-224.4.39.255 | MIAX-3 | [ ] | [ ] | 2023-05-24 | | 224.4.40.0-224.4.43.255 | Japan Exchange Group | [ ] | [ ] | 2024-06-25 | | 224.4.44.0-224.4.47.255 | CME Group | [ ] | [ ] | 2024-08-02 | | 224.4.48.0-224.4.63.255 | Intercontinental Exchange, Inc. | [ ] | [ ] | 2023-04-10 | | 224.4.64.0-224.4.71.255 | CME Group | [ ] | [ ] | 2024-08-06 | | 224.4.72.0-224.4.255.255 | Unassigned | | | | | Address(es) | Description | References | Change Controller | Date Registered | Last Reviewed | 224.5.0.0-224.251.255.255 | Reserved | [ ] | | | | Address(es) | Description | References | Change Controller | Date Registered | Last Reviewed | 224.252.0.0-224.255.255.255 | DIS Transient Groups | [ ][ ] | | | | Address(es) | Description | References | Change Controller | Date Registered | Last Reviewed | 225.0.0.0-231.255.255.255 | Reserved | [ ] | | | | Relative | Description | References | Change Controller | Date Registered | Last Reviewed | 232.0.0.0 | Reserved | [ ] | | | | 232.0.0.1-232.0.0.255 | Reserved for IANA allocation | [ ] | | | | 232.0.1.0-232.255.255.255 | Reserved for local host allocation | [ ] | | | | Address(es) | Description | References | Change Controller | Date Registered | Last Reviewed | 233.0.0.0-233.251.255.255 | GLOP Block | [ ] | | | | Address(es) | Description | References | Change Controller | Date Registered | Last Reviewed | 233.252.0.0-233.252.0.255 | MCAST-TEST-NET | [ ][ ][ ] | | 2010-01-20 | 2010-01-20 | 233.252.1.0-233.252.1.255 | Pico | [ ] | [ ] | 2010-08-12 | | 233.252.2.0-233.252.7.255 | Tradition | [ ] | | 2010-08-12 | | 233.252.8.0-233.252.11.255 | BVMF_MKT_DATA | [ ] | | 2010-08-12 | | 233.252.12.0-233.252.13.255 | blizznet-tv-services | [ ] | | 2010-09-14 | | 233.252.14.0-233.252.17.255 | BVMF_MKT_DATA_2 | [ ] | | 2016-09-27 | | 233.252.18.0-233.252.18.255 | Pico | [ ] | [ ] | 2021-12-17 | | 233.252.19.0-233.255.255.255 | Unassigned | | | | | Address(es) | Description | References | Change Controller | Date Registered | Last Reviewed | 234.0.0.0-234.255.255.255 | Unicast-Prefix-based IPv4 Multicast Addresses | [ ] | | 2010-08-11 | | Address(es) | Description | References | Change Controller | Date Registered | Last Reviewed | 235.0.0.0-238.255.255.255 | Reserved | [ ] | | | | 239.0.0.0-239.255.255.255 | Organization-Local Scope | [ ][ ] | | 1997-01-01 | | Address(es) | Description | References | Change Controller | Date Registered | Last Reviewed | 0 | SAP Session Announcement Protocol | [ ] | | 1998-12-01 | | 1 | MADCAP Protocol | [ ] | | | | 2 | SLPv2 Discovery | [ ] | | 2001-12-01 | | 3 | MZAP | [ ] | | 2000-06-01 | | 4 | Multicast Discovery of DNS Services | [ ] | | 1999-08-01 | | 5 | SSDP | [ ] | | 2006-06-27 | | 6 | DHCP v4 | [ ] | | 1999-10-01 | | 7 | AAP | [ ] | | 2000-07-01 | | 8 | MBUS | [ ] | | | | 9 | UPnP | [ ] | | 2006-06-27 | | 10 | MCAST-TEST-NET-2 | [ ] | | | | 11-252 | Unassigned | | | | | 253 | Reserved | | | | | 254 | RFC3692-style Experiment (*) | [ ] | | | | 255 | Unassigned | | | | | Contact Information ID | Name | Organization | Contact URI | Last Updated | | | 3GPP | | | | Ad C. Spelt | | | 2009-09-01 | | Adam DeMinter | | | 2011-04-20 | | Adam Yellen | | | 2009-08-12 | | Akihiro Nishida | | | 2003-02-01 | | Alan Novick | | | 1998-08-01 | | Alan Robertson | | | 2012-04-17 | | | Ålands Telekommunikation Ab | | 2019-02-28 | | Alex Lee | | | 2002-10-01 | | Alexander Pevzner | | | 2006-03-17 | | Alexandre Gomes | | | 2024-02-27 | | Andrew Cherenson | | | | | Andrew Rowley | | | 2006-06-09 | | Andy Belk | | | 2005-02-01 | | Andy Crick | | | 2008-01-14 | | Anthony Daga | | | 1999-06-01 | | Anthony Lopresti | CME Group | | 2024-08-06 | | Antonio Querubin | | | 2008-02-04 | | | Applykane Technologies Private Limited | | 2017-05-19 | | | Aquis Exchange PLC | | 2021-12-21 | | Architecture Team | | | 2018-01-31 | | Arnoud Zwemmer | | | 1996-11-01 | | Asad Gilani | | | 1997-07-01 | | Asia Digital Exchange | | | 2024-04-05 | | Attila Miklóš | | | 2021-06-11 | | Bernd Uphoff | | | 2018-06-19 | | Bert van Willigen | | | 2004-01-01 | | Beverly Schwartz | | | 1998-06-01 | | Bill Manning | | | 1999-08-01 | | Bill Schilit | | | | | Bill Simpson | | | 1994-11-01 | | Bill Woodcock | | | 1998-11-01 | | Bob Braden | | | 1996-04-01 | | Bob Brzezinski | | | 2005-10-28 | | Bob Gaddie | | | 1998-08-01 | | Bob Meier | | | 1997-12-01 | | Bob Scheifler | | | 1998-08-01 | | Bob Sledge | | | 1998-12-01 | | Bodo Rueskamp | | | 2000-03-01 | | | BOX TECHNOLOGY CANADA INC. | | 2024-02-27 | | Brendan Eic | | | | | Brian Kean | | | 1995-08-01 | | Brian Kerkan | | | 2000-05-01 | | Brian Martinicky | | | 2000-03-01 | | Brian Trudeau | | | 2014-09-19 | | Bruce Factor | | | | | Bryan Costales | | | 1997-09-01 | | Bryant Eastham | | | 2015-04-23 | | | Beirut Stock Exchange | | 2019-01-17 | | Caleb Bell | | | 2012-11-19 | | Carl-Johan Sjöberg | | | 2012-04-25 | | Carl Malamud | | | 2014-01-03 | | | Cantor Fitzgerald | | 2023-01-18 | | | Cboe Bats, LLC | | 2024-08-30 | | Cboe POC | Cboe Bats, LLC | | 2024-08-30 | | Charles Gomes | | | 2023-06-05 | | Charles Lo | | | 2022-11-02 | | Charles Tewiah | | | 2005-09-01 | | Chas Honton | | | 1997-12-01 | | Choon Lee | | | 1996-04-01 | | Chris Adams | | | 2000-07-01 | | Christopher Mettin | | | 2009-05-12 | | Chuck McManis | | | | | | Clearpool | | 2023-06-05 | | Clem Verwey | | | 2011-12-07 | | | CME Group | | 2024-08-06 | | Colin Caughie | | | 2000-05-01 | | | Coinbase | | 2019-01-28 | | | COMTECH Kft. | | 2016-10-20 | | Craig Dowell | | | 2011-11-18 | | Dan Jackson | | | 1997-09-01 | | Dan Jakubiec | | | 2006-09-21 | | Daniel Dissett | | | 1998-12-01 | | Daniel Steinber | | | | | Darcy Brockbank | | | 1997-12-01 | | Darrell Sveistrup | | | 1999-06-01 | | Dave Cheriton | | | | | Dave Glanzer | | | 2003-03-01 | | Dave Thaler | | | 2000-06-01 | | David Beattie | Global Futures and Options Limited | | 2023-03-15 | | David Brett | | | 2016-04-19 | | David Meyer | | | 1997-01-01 | | David Mills | | | | | David Poole | | | 1997-04-01 | | David Rubin | | | 1996-08-01 | | David Wilson | | | 2013-05-30 | | Dean Blackketter | | | 1998-11-01 | | Dino Farinacci | | | 1996-03-01 | | Dirk Koopman | | | 2000-07-01 | | Doug Dillon | | | 1998-08-01 | | Douglas Marquardt | | | 1997-02-01 | | Duane Wessels | | | 1997-02-01 | | Ed Moran | | | 1997-10-01 | | Ed Purkiss | | | 1998-09-01 | | Eric Hall | | | 1999-10-01 | | Erick MacDonald Filzek | | | 2023-08-09 | | Erik Guttman | | | 2001-12-01 | | Ernst EDER | | | 2018-11-19 | | Euronext Admin | | | 2014-11-24 | | Evan Caves | | | 1998-06-01 | | Florian Weimer | | | 2013-02-08 | | Fred Baker | | | 1997-06-01 | | Gajendra Shukla | | | 2002-02-01 | | Gamini Karunaratne | | | 2023-05-24 | | Gary S. Malkin | | | | | Gary Scott Malkin | | | 1998-02-01 | | Gavin McKee | | | 2019-01-25 | | Gene Marsh | | | 1998-11-01 | | Geoff Golder | | | 2016-04-19 | | Geoff Mendal | | | 1999-01-01 | | George Neville-Neil | | | 2014-12-17 | | Giovanni Marzot | | | 2019-03-13 | | Giovanni Marzot | | | 2023-10-13 | | | Global Futures and Options Limited | | 2023-03-15 | | Grant Taylor | | | 2016-10-04 | | Guido Petronio | | | 2004-01-01 | | Guilherme Longanezi | | | 2016-09-27 | | Hatice Unal | | | 2019-01-25 | | Heiko Rupp | | | 1997-01-01 | | Henri Moelard | | | 1998-03 | | Henrik Lans | | | 2019-09-27 | | Hiroshi Okubo | | | 2014-08-01 | | Howard Gordon | | | | | | IANA | | | | Ian Armitage | | | 1999-08-01 | | Ian Stewart | | | 1999-06-01 | | Ian Wacey | | | 2000-05-01 | | Ian Wilson | | | 2001-12-01 | | Ido Rosen | | | 2021-03-23 | | | Instinet | | 2019-08-29 | | | Intercontinental Exchange, Inc. | | 2023-04-10 | | | IOT COMPANY SOLUCOES TECNOLOGICAS LTDA | | 2023-08-09 | | IP Admin | | | 2015-10-12 | | IPadmin - Orange Slovensko a.s. | | | 2021-06-11 | | Ishan Wu | | | 2000-03-01 | | Itamar Gilad | | | 2007-08-31 | | J. Ryan Stinnett | | | 2014-07-01 | | James Crawford | | | 1998-05-01 | | Jan Drwal | | | 2011-12-19 | | | Japan Exchange Group | | 2021-09-07 | | | Japan Exchange Group/Osaka Exchange, Inc. | | 2024-06-25 | | Jasmine Strong | | | 2014-06-04 | | Javier Torres | Members Exchange (MEMX) | | 2024-01-22 | | Jean-Marc MAGNIER | | | 2021-02-03 | | Jeff Schenk | | | 2006-03-31 | | Jerome Albin | | | 1997-06-01 | | Jerry Whitaker | | | 2008-12-19 | | Jim Ginsburg | | | 2007-10-31 | | Jim Lyle | | | 2006-08-07 | | Jim Toga | | | 1996-05-01 | | Joel Lynch | | | 1999-04-01 | | Johan Deleu | | | 2002-02-01 | | John Catherino | | | 2006-03-31 | | John Gabler | | | 2007-07-06 | | John Veizades | | | 1995-05-01 | | Johnathan Ryder | London Stock Exchange Group | | 2021-09-21 | | Jon Crowcroft | | | 1998-11-01 | | Jon Gabriel | | | 1998-12-01 | | Jon Postel | | | | | Jonathan Niedfeldt | | | 2008-02-22 | | Joost Demarest | KNX Association | | 2023-08-23 | | Jose Luis Marocho | | | 1996-07-01 | | Juan Ayas | | | 2018-10-17 | | Julian Nevell | | | 1999-08-01 | | Justin Beaman | | | 2022-06-09 | | | Kalejdo TV | | 2022-08-31 | | Kang Lee | | | 2007-02-02 | | Karel Vesely | Nej.cz s.r.o. | | 2024-01-23 | | Karen Seo | | | | | Karl Elad | | | 2006-03-31 | | Keith Thompson | | | 2001-06-01 | | Kelly Littlepage | | | 2023-08-29 | | Kevin Gross | | | 2010-03-12 | | Kevin Gross | | | 2012-08-28 | | Kevin McNicholas | | | 2022-02-17 | | | KNX Association | | 2023-08-23 | | KPN IP Office | | | 2011-04-18 | | Kristian A. Bognaes | | | 2014-01-08 | | Lau Wei Lun | | | 2023-03-03 | | LDA Audio Tech | | | 2018-10-19 | | Lev V. Cherednikov | | | 2014-04-12 | | Liming Wei | | | 1998-10-01 | | | LIRNEasia | | 2020-10-07 | | Lloyd Wood | | | 2011-03-17 | | LME Networks | London Metal Exchange | | 2023-04-27 | | | London Metal Exchange | | 2023-04-27 | | | London Stock Exchange Group | | 2021-09-21 | | | LonMark International | | 2018-11-19 | | Louis Mamakos | | | 1997-03-01 | | | Lucera Financial Infrastructures | | 2022-02-17 | | Madhav Karhade | | | 2003-05-01 | | Mark Armstrong | | | 2006-02-09 | | Mark Bakke | | | 2001-12-01 | | Mark Hamilton | | | 1998-11-01 | | Mark Handley | | | 1998-12-01 | | Mark Lewis | | | 1995-10-01 | | Mark Lipford | | | 2006-07-11 | | Marlon Berlin | | | 2013-05-25 | | Martin Forssen | | | | | Mary Timm | | | 1998-07-01 | | Masato Shindoh | | | 1997-08-01 | | Matthew Straight | | | 2007-03-01 | | Maurice Robberson | | | 2006-09-15 | | | Media Systems OOO | | 2021-10-22 | | | Mellanox Technologies, Inc. | | 2019-07-01 | | | Members Exchange (MEMX) | | 2024-01-22 | | | Meridian Labs LTD. | | 2020-10-07 | | | Miami International Security Exchange | | 2023-05-24 | | Michael Caravetta | | | 2013-06-03 | | Michael DeMoney | | | 1997-04-01 | | Michael Dolan | | | 2003-10-01 | | Michael Lyle | | | 2009-11-11 | | Michael Rosenberg | Nasdaq Inc. | | 2024-02-01 | | Michael Wang | | | 1999-03-01 | | | Midwest Video Solutions | | 2019-11-13 | | Mika Uusitalo | | | 1997-04-01 | | Mike King | | | 2019-02-07 | | Mike Pontillo | | | 2017-05-19 | | Mike Rodbell | | | 1997-01-01 | | Mike Roper | | | 1999-09-01 | | Mike Velten | | | 1999-01-01 | | Moe Singh | | | 2009-09-24 | | Morten Lindeman | | | 1999-03-01 | | Morteza Kalhour | | | 2002-10-01 | | Nadine Guillaume | | | 2005-02-01 | | | Nasdaq Inc. | | 2024-02-01 | | Neal Lawrence | | | 2017-06-02 | | Nedelcho Stanev | | | 1999-05-01 | | | Nej.cz s.r.o. | | 2024-01-23 | | NE-TEAM_at_telecomsys.com | | | 2014-11-07 | | Nick Barendt | | | 2005-11-01 | | Nigel Thompson | | | 1999-01-01 | | | OCX Group Inc | | 2023-08-29 | | Oliver Lewis | | | 2006-07-11 | | | OPC Foundation | | 2019-08-19 | | OSPF WG Chairs | | | | | Oyvind H. Olsen | | | 2007-09-12 | | Paolo Strazzera | | | 1999-06-01 | | Patrick Cipiere | | | 2001-01-01 | | Paul Langille | | | 2007-01-17 | | Paul Roberts | | | 2021-12-21 | | Paul Suhler | | | 2009-05-12 | | Paul Wallner | | | 2010-09-14 | | Paul Wissenbach | | | 1997-06-01 | | Peter Aronson | | | 1998-08-01 | | Peter Parnes | | | 2000-02-01 | | Peter White | | | 1999-04-01 | | | Philips Healthcare | | 2019-02-07 | | | Pico | | 2020-07-22 | | Pico Sales | | | 2020-07-22 | | Pierre Oliver | | | 2011-06-06 | | Piers Scannell | | | 2000-03-01 | | | Pilz GmbH and Co. KG | | 2009-03-17 | | Prakash Banthia | | | 1998-09-01 | | Ralph Kammerlander | | | 2000-06-01 | | Ram Iyer | | | 1998-03-01 | | Rami Chalhoub | | | 2019-01-17 | | | Ramp Holdings | | 2019-03-28 | | Raymond Shum | | | 1998-04-01 | | Richard Hodges | | | 1999-03-01 | | Richard Zulch | | | 2004-05-01 | | RIR Admin | | | 2023-04-10 | | Rob Janssen | | | 1995-01-01 | | Robert Hodgson | | | 2001-12-01 | | Robert Sautter | | | 1999-08-01 | | Robert Sliwinski | | | 2000-02-01 | | Robert Taylor | | | 2016-09-29 | | Roberto Costa Simoes | | | 2010-08-18 | | | RTP Media | | 2021-07-30 | | Ruben Hernandez | | | 2022-01-06 | | Ryon Coleman | | | 2006-04-11 | | | SEIKO EPSON Corp | | 2005-01-01 | | Sakon Kittivatcharapong | | | 2000-05-01 | | Scott Watson | | | 1997-08-01 | | | Semtech Corporation | | 2019-02-22 | | Sergey Shulgin | | | 2008-08-12 | | Shachar Dor | | | 2019-07-01 | | Shai Revzen | | | 1999-04-01 | | Shane Rowatt | | | 1997-03-01 | | Shivaun Albright | | | 1997-07-01 | | Simon Barber | | | 2009-09-24 | | Soren Martin Sorensen | | | 2006-08-07 | | Stacey O'Rourke | | | 1999-08-01 | | Stacey O'Rourke | | | 2001-01-01 | | Stephan Wasserroth | | | 2000-07-01 | | Stephen Dunne | | | 1997-01-01 | | Stephen Hanna | | | 2000-07-01 | | Stephen Ray Middleton | | | 2015-03-23 | | Stephen T. Lyda | | | 2000-02-01 | | Steve Casner | | | | | Steve Casner | | | 1995-01-01 | | Steve Deering | | | 1999-10-01 | | Steve Deering | | | | | Steve Loizou | | | 2023-01-18 | | Steve Polishinski | | | 2000-03-01 | | Stuart Kerry | | | 2003-01-01 | | Susie Armstrong | | | | | Takeshi Saito | | | 2003-02-01 | | Technicolor NL NOC | | | 2009-12-23 | | Telia-Norway-Get-NOC | | | 2019-08-28 | | Terry Gibson | | | 1997-08-01 | | Tetsuo Hoshi | | | 2004-06-01 | | Thomas Sörlin | | | 2022-08-31 | | Tim DeBaillie | | | 2006-11-30 | | TMX | | | 2023-04-14 | | TMX Network Engineering | | | 2023-04-14 | | Tom Ballister | | | 2021-06-11 | | Tom Blank | | | 1996-11-01 | | Tom White | | | 2011-11-02 | | Tony Ballardie | | | 1997-02-01 | | Tony Barber | | | 1997-01-01 | | Tony Przygienda | | | 1999-10-01 | | Tony Wong | | | 1998-07-01 | | Tradeweb Markets Inc | | | 2022-01-19 | | Tradition Network Operations and Command Center | | | 2010-09-22 | | TV System Administrators | Ålands Telekommunikation Ab | | 2019-02-28 | | | UPnP Forum | | 2006-06-27 | | Vadim B. Kantor | | | 2021-07-30 | | Vanya Levy | | | 2019-02-20 | | Victor Volpe | | | 1997-10-01 | | | Vivoh | | 2023-10-16 | | Vladimir Shishkov | | | 2017-02-17 | | Wally Beddoe | | | 2003-04-01 | | Walter Wallach | | | 1999-07-01 | | Wayne Carr | | | 1997-12-01 | | Wayne Wenyu Liu | | | 2012-06-12 | | Wenjie Peng | | | 1997-01-01 | | Werner Vogels | | | 1998-08-01 | | Wieland Holdfelder | | | 1997-01-01 | | Xiaoyu Zhou | | | 2009-01-20 | | Xie Shao | | | 2023-01-18 | | Yea Uang | | | 1994-11-01 | | Yossi Gal | | | 1998-02-01 | | Zia Bhatti | | | 1998-09-01 | | |
COMMENTS
IP Lookup Tool - Check IP Block info at ARIN
IP Netblocks Owner Lookup | WhoisXML API
ARIN Whois/RDAP - American Registry for Internet Numbers
Search ARIN Site or Whois - American Registry for Internet ...
If requesting a block larger than the minimum assignment, provide documentation justifying the need for additional subnets based on the number of sites in the organization's network within 12 months. Your initial assignment size will be determined by the number of justified sites your network has, for example: 2 - 12 sites: /44; 13 - 192 ...
The allocation of Internet Protocol version 4 (IPv4) address space to various registries is listed here. Originally, all the IPv4 address spaces was managed directly by the IANA. Later parts of the address space were allocated to various other registries to manage for particular purposes or regional areas of the world.
IP address. e.g.: 69.63.181.11. ARIN's WHOIS service gives contact and registration information for IP addresses, autonomous system numbers (ASN), organizations or customers that are associated with these resources, and related Points of Contact (POC). It doesn't include information on domain names or military networks. Internet. IP. ipaddress.
IP WHOIS Lookup - Instantly Fetch the WHOIS Info of an IP
Number Resources
List of assigned /8 IPv4 address blocks
IP blocks are assigned to different regional registries who then assign IP addresses to companies. Determining where these companies use each IP address is the challenging part. ... Each IP lookup will return ten fields and a warning message if the IP has abuse reported against it. The ten fields returned during each lookup are as follows ...
ARIN (or its predecessor registries) have performed allocation and assignment of IPv4 address blocks from specific address blocks assigned by IANA. The list of IPv4 address blocks is available here on the IANA website. ARIN's free pool of IPv4 address space was depleted on 24 September 2015. As a result, we are no longer fulfilling requests ...
Using Whois - American Registry for Internet Numbers
Enter IPs (v4) or ASNs (one per line), and/or choose from the list of common DDoS hosts. Use blocklists to reduce the harm caused by script-kiddie/for-hire DDoS attacks (that is, most of them). It is important to refresh the blocklist periodically (or remove it entirely when the DDoS has subsided). Blocking an entire autonomous system can block ...
ISPs provide individuals and organizations access to the Internet and allocate them IP addresses from the blocks they manage. An IPv4 Internet address is a unique 32-bit value expressed as a group of four numbers separated by a period - for example 34.130.46.78 - each number ranges from 0 to 255. An IPv6 Internet address is a unique 128-bit ...
In simple terms, an IP address is a numerical label assigned to each device connected to a computer network that uses the Internet Protocol for communication. It consists of four sets of numbers separated by periods (e.g., 192.168..1) and can be either IPv4 or IPv6 format. IP Address Allocation Methods.
special purposes relating to protocol assignments. This registry. contains the current assignments made by the IETF from this address. block. Address prefixes listed in the Special-Purpose Address Registry are. not guaranteed routability in any particular local or global context. The IPv4 and IPv6 Special-Purpose Address Registries maintain the.
Domain and IP bulk lookup tool. Domain and IP bulk lookup tool allows to lookup domain, location, ISP and ASN for multiple hosts (IPs or domains) at once. It also supports lookup of MX or NS DNS records for multiple domains. This tool is commonly used for investigating IPs found in server logs. The limit is 100 IPs/domains per request.
IP Subnet Calculator
American Registry for Internet Numbers
IP Address Lookup | Geolocation
Instant IP Address Lookup
IPv4 Multicast Address Space Registry. Host Extensions for IP Multicasting [RFC1112] specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting. The multicast addresses are in the range 224.0.0.0 through 239.255.255.255. Address assignments are listed below.