IP Address Extractor
Extract IPv4 and IPv6 addresses from text - free, no signup.
What this tool does
Paste a log file, config, or any text, and every IPv4 and IPv6 address in it is found and listed separately - useful for reviewing server logs, firewall rules, or network documentation without hunting through the text by eye.
Finds IPv4 addresses (like 192.168.1.1) using a pattern that validates each number is 0-255, so it doesn't match arbitrary dotted number sequences.
Finds IPv6 addresses in both full and common compressed (::) notation.
Lists the two address families separately, since they're used differently and mixing them into one list would obscure which is which.
Matches on address format only - it does not classify a result as private, public, loopback or reserved, so 192.168.1.1 and 8.8.8.8 are both simply listed as IPv4 addresses.
Range-checks each IPv4 octet against 0-255, so a malformed value like 999.999.999.999 is correctly excluded rather than matched as if it were four arbitrary dot-separated numbers.
How to use it
- Paste your log, config, or text.
- Review the IPv4 and IPv6 lists.
- Copy or download the results.
Why use this extractor
Logs, firewall reports and emails contain IP addresses mixed in with other numbers. A validating extractor finds real addresses and separates IPv4 from IPv6.
Why we built it
We built the IP address extractor to list IPv4 and IPv6 addresses separately because they are structurally different. Work with ranges using the IP subnet calculator and extract other items with the email extractor.
Related tools worth a look: the Hashtag & Mention Extractor and the Postal / ZIP Code Extractor.
Who this tool is for
- Network and security staff reading logs
- Developers cleaning data
- Students of networking
When to use it
- Reading IPs from server or firewall logs.
- Building a blocklist or allowlist.
- Auditing a document for addresses.
- Counting unique clients.
Why IPv4 and IPv6 are kept separate
They're different address systems, not two spellings of the same address.
IPv4 and IPv6 are structurally different addressing systems that happen to coexist on the modern internet - a device can have both an IPv4 and an IPv6 address at the same time, and they aren't interchangeable or convertible into each other. Merging them into one list would make it harder to tell, at a glance, which protocol a given log line or config entry is actually using, so this tool keeps them in two clearly labeled lists.
Why a valid format is not the same as a public address
A private address like 192.168.1.1 and a public one like 8.8.8.8 have exactly the same dotted-quad shape - four numbers from 0 to 255, separated by dots. Nothing in that shape says whether the address is routable on the public internet, reserved for a local network, or a loopback address pointing back at the same machine.
This tool matches format only. It does not look up or classify a result by range, so private, public, loopback and reserved addresses are all simply listed as IPv4 or IPv6 addresses found in the text.
| Address | Format | Range |
|---|---|---|
| 8.8.8.8 | IPv4 | Public |
| 192.168.1.1 | IPv4 | Private (RFC 1918) |
| 127.0.0.1 | IPv4 | Loopback |
| ::1 | IPv6 | Loopback |
If you need to separate private and public addresses, that requires checking each result against the reserved-range tables (RFC 1918 for private IPv4, and their IPv6 equivalents) - a step this tool does not perform.
What you give it, and what you get back
| Item | Details |
|---|---|
| Input | Any text. |
| Output | IPv4 and IPv6 addresses listed separately, de-duplicated. |
| Notes | Each IPv4 number is validated 0-255. |
Issues you may run into
| What you see | Why it happens | What to do |
|---|---|---|
| Version number is missed or matched | Dotted numbers can look similar. | Review the list. |
| IPv6 edge case missed | Only full and compressed forms are matched. | Check unusual notations. |
| Reachability expected | This only checks format. | Use network tools to test. |
Assumptions and limitations
- IPv6 matching covers full and common compressed (::) notation but not every exotic edge case of the IPv6 address specification.
- This finds addresses matching the correct format - it doesn't verify whether an address is actually reachable, public, or in use.
Frequently asked questions
How do I extract IP addresses from a log file online for free?
Paste your log or text and every IPv4 and IPv6 address found appears instantly in its own list.
Does this validate that each number in an IPv4 address is in range?
Yes - the pattern only matches numbers from 0 to 255 in each position, so it won't falsely match something like 999.999.999.999.
Does this handle compressed IPv6 addresses (with ::)?
Yes - both full and common :: compressed notation are recognized.
Can I tell which addresses are duplicates?
Yes - turn on 'Remove duplicates' to see each unique address only once, with a count of how many duplicates were merged.
Is my data uploaded anywhere?
No. Extraction happens entirely in your browser - nothing is sent to a server, which matters for something as sensitive as a server log.
Does this tell me which addresses are private (like 192.168.x.x) versus public?
No. A private address like 192.168.1.1 and a public one like 8.8.8.8 have exactly the same dotted-quad format, so format matching alone cannot tell them apart. This tool lists every address that matches the IPv4 or IPv6 shape; separating private from public ranges needs a lookup against the reserved-range tables (RFC 1918 and equivalents), which this tool does not do.
Does it flag loopback or reserved addresses like 127.0.0.1 or ::1?
No, for the same reason - loopback and reserved addresses are still valid-format addresses, so they appear in the results alongside every other match rather than being called out separately.