IP address extractor
Extract IPv4 and IPv6 addresses from text: IPv4 needs exactly four 0–255 octets and IPv6 understands :: compression, so version strings like 1.2.3 and clock times like 12:30:45 are never misread; optionally keep one family only, dedupe and sort.
Runs in your browserEvery computation happens in your browser — your data never leaves this device.
Extracted addresses
One item per line, ready to copy.
Paste text to extract IP addresses
Matches: 0 · Unique: 0 · IPv4: 0 · IPv6: 0
What this tool does
- Pull every client IP out of a log to see which host or region is hammering the service.
- Build a firewall allow-list: paste a messy thread of addresses and get a clean list back.
- Check an IPv6 migration by extracting both families at once and counting what is still IPv4.
Example
Input
Hosts 192.168.1.1 and 10.0.0.1, loopback ::1, IPv6 2001:db8::1; version 1.2.3 and time 12:30:45 are not addresses.
Output
192.168.1.1 10.0.0.1 ::1 2001:db8::1
1.2.3 has only three octets and 12:30:45 is not made of hex groups, so both are skipped; switch the family selector to keep only IPv4 or only IPv6.
Frequently asked questions
Will a version like 1.2.3.4 be treated as an IP?
Yes — it genuinely looks like four 0–255 octets. What is filtered out is the wrong number of octets (1.2.3) or an octet above 255 (999.1.1.1).
How accurate is :: compression in IPv6?
Fairly: with :: the non-empty groups must not exceed seven and each must be 1–4 hex digits; without :: there must be exactly eight groups, so times such as 12:30:45 never match.
Are ports stripped?
The result contains the address only, so 8080 in 1.2.3.4:8080 is not included. Digits glued to the address are matched greedily as the longest candidate.
Can I sort the results?
They are listed in order of appearance by default; tick “Sort the output” to sort by code point instead.
How much text can it handle?
Two million characters. Beyond that it reports an error instead of freezing the tab.
Keywords：IP提取IP地址提取ip extractorIPv4IPv6批量提取IP日志IP正则提取IP