Extract IP Addresses
Pull IPv4 and IPv6 addresses out of text — log files, configs, traffic dumps. Browser-only.
0 ips found
About Extract IP Addresses
The IP extractor scans text for both IPv4 dotted-decimal and IPv6 colon-hex addresses. It validates IPv4 octets are 0–255 to avoid matching ordinary numbers, and accepts IPv6 in its various forms (full, compressed, with leading ::).
When to use it
- Pulling source/destination IPs out of a log slice
- Auditing a config file for hardcoded addresses
- Collecting unique client IPs from a request log
- Quick check of which IPs appear in a network capture summary
How it works
Two regexes run independently: one for IPv4 (with strict 0–255 octet validation) and one for IPv6 (covering full, compressed, and leading-:: forms). Matches from both are combined.
Examples
999.1.1.1 is rejected because 999 > 255
From 192.168.1.5 to ::1 via 2001:db8::a (not 999.1.1.1).
192.168.1.5 ::1 2001:db8::a
Frequently asked questions
- Are CIDR ranges matched?
- Only the IP portion. A CIDR like 192.168.0.0/24 produces just 192.168.0.0; the /24 is left in the source text.
- What about non-routable IPs?
- All syntactically valid IPv4/IPv6 addresses are matched — private (10.x, 192.168.x), loopback (127.0.0.1, ::1), and link-local. Filter the output if you only want public IPs.
- Does it handle IPv4-mapped IPv6 (::ffff:192.168.1.1)?
- Partially — the IPv6 portion matches and the embedded IPv4 octets also match separately. The result has both forms.