Extract IP Addresses From Text and Logs

Every one of the four dotted groups must fall in the 0 to 255 range. That means a candidate like 999.1.1.1 or 256.0.0.1 is matched by the pattern but then discarded, so only genuine dotted-quad addresses reach the results.

Full eight-group addresses and the compressed double-colon forms, whether the :: sits at the start, the middle, or the end. That includes the loopback ::1 and the all-zeros :: address, plus mixed hex groups like 2001:db8::8a2e:370:7334.

Yes. Each unique address is listed once. Comparison is case-insensitive, so fe80::1 and FE80::1 count as the same address, and the first spelling that appears in your text is the one kept.

No. A plain colon-separated clock time has only three groups and no double colon, so it does not match the full eight-group form or any compressed form. The IPv6 pattern deliberately requires either eight groups or a :: shorthand.

No. The IPv4 matcher is anchored so a dotted-quad has to stand on its own, not sit inside a longer run of digits or dots. This keeps it from carving a fake address out of something like a build number.

No. The tool returns the bare address only. A trailing :8080 port, a /24 CIDR suffix, or an %eth0 zone identifier is treated as surrounding text and left out of the extracted address.

Within each list, addresses appear in the order they were first seen in your text. The Copy all button concatenates the IPv4 list first and then the IPv6 list, joined by newlines.

There is no fixed cap. The scan runs in your browser, so the practical ceiling is your device's memory. Even multi-megabyte log dumps are processed in a single pass without a round trip to a server.

Yes. Everything runs locally in your browser and nothing is uploaded, which matters when the logs you are scanning contain internal hostnames or customer traffic.