The sort | uniq of the browser
Every sysadmin knows the pipeline: sort file | uniq, sort -n, sort -u. This page is that toolbox for text that isn't in a file yet, an IP list pasted from a firewall console, hostnames copied out of a wiki table, a block of log lines. Operations apply in place, so they chain naturally: trim, drop empties, dedupe, sort, click, click, click, copy.
Dedupe details that matter
Deduplication here keeps the first occurrence and preserves the original order of survivors, unlike sort -u, which necessarily reorders. If order doesn't matter, sort first and the result matches the shell exactly. Watch for the classic false-duplicates trap: web01 and web01␠ (trailing space) are different lines to any exact comparison, which is why the Trim button exists and why running it before Dedupe is the right habit. Invisible whitespace is responsible for a remarkable share of "why is this host in the list twice" confusion.
Numeric sort and shuffle
Alphabetic sort puts 10 before 2; numeric sort parses each line's leading number, matching sort -n, right for port lists, sizes and counts. (IP addresses are neither: for a strictly correct IP ordering, the shell's sort -t. -k1,1n -k2,2n -k3,3n -k4,4n remains the trick.) Shuffle uses the browser's cryptographic RNG with a Fisher–Yates pass, genuinely unbiased, useful for picking canary hosts or randomising a maintenance order without favouritism.