Extract IP addresses from logs & text
Pull every valid IPv4 and IPv6 address. Filter by family and public vs private (10.x, 172.16-31.x, 192.168.x, 127.x).
10.0.0.1 192.168.1.5 2001:0db8:85a3:0000:0000:8a2e:0370:7334 8.8.8.8
How to extract IP addresses
IPv4 candidates are validated (each octet 0-255). IPv6 matching is permissive — drop colon-separated hex sequences.
- 01
Paste logs
Server logs, audit dumps, packet captures (as text).
Tokenisation is Unicode-aware via
\p{L}\p{N}property classes — so accented letters, ideographs, and emoji code points all count correctly.logsUTF-8Unicodecode pointsliveinput · textraw · UTF-8192.168.1.5 → /api
loaded · UTF-8UTF-8 · ready - 02
Filter family
IPv4 only, IPv6 only, or both.
Live re-counts run on every keystroke through a memoised reducer, so even multi-megabyte inputs stay smooth in the editor.
v4v6livememoisedoptionsfamily · optionsipv4 · live192.168.1.5
options applied · livelive - 03
Public or private
RFC 1918 ranges (10.x, 172.16-31.x, 192.168.x) plus loopback (127.x) count as private.
Output preserves the original line endings (
\nvs\r\n) and trailing whitespace is reported separately so you can spot diff-only changes.RFC 1918line endingswhitespacediff-cleanreproduciblescope · countedpublic · ready8.8.8.8
counted · livecounted - 04
Copy or download
Text or CSV (with header).
Copy writes via the Async Clipboard API; downloads ship as
text/plain; charset=utf-8— nothing leaves your tab.copyclipboardtext/plainblobclient-sideexport · copiedready · done✓ Copied
shipped · ready to shipsuccess
Text-processing fundamentals worth knowing
Tokenise with Unicode classes
Use \p{L}\p{N} with the u flag so accents, ideographs, and emoji count properly.
Normalise line endings
Convert \r\n to \n before diffing or hashing — Windows-vs-Unix endings produce phantom changes.
Mind invisible characters
Zero-width joiners, BOMs, and non-breaking spaces look identical to ASCII space. Strip them before comparison or storage.
Stream don’t slurp
For multi-megabyte text, iterate line-by-line rather than loading everything to memory — keeps the tab responsive.
Choose collation deliberately
Default JS sort is code-point order, not human alphabetical. Use Intl.Collator for locale-aware sorting.
Re-run after normalisation
NFC vs NFD changes byte length but not visible glyphs. String.prototype.normalize() before counts and comparisons.
When to extract IPs
Anywhere you need to inventory network addresses.
Log triage
Find unique IPs hitting an endpoint over a window. Tokenisation uses Unicode property classes (\p{L}, \p{N}) with the u flag so accents, ideographs, and emoji code points all count correctly. Surrogate-pair-aware counts mean 🚀 weighs 1, not 2.
Unicode-correctFirewall audit
Inventory public IPs in audit logs. Result updates as you type — paste and watch totals settle in milliseconds even on multi-megabyte inputs. Heavy work runs through a memoised reducer so the editor never janks.
diff-cleanDNS replay
Get all addresses returned by a dns lookup batch. Output normalises line endings to LF for clean diffs across platforms. Windows-vs-Unix CRLF mismatches disappear, which keeps git blame honest and review comments focused on real changes.
instant countsDDoS analysis
Identify top attacking IPs. Code-point counts are stable across NFC/NFD normalisation. Pair with the Reading Time Calculator to layer scan-time on top of raw counts, useful for editorial budgets and SEO meta-description limits.
platform-awareAllowlist building
Extract internal IPs for a firewall rule update. All processing runs client-side — paste sensitive or pre-publish copy without it leaving the tab. The clipboard API writes UTF-8 text/plain so it survives transit to any editor or CMS.
code-point-accurateCompliance
Find any IPs that leaked into application logs. Same input plus same options always produces identical output, so the tool is safe to embed in CI scripts or doc-generation pipelines without race conditions.
losslessFrequently asked questions
Something missing?
Tell us what you need. We ship the top requests every two weeks.