Updated Jul 14, 2026

Discovery

Filter a URL list by HTTP response code

HTTP status codes for a URL list. Nothing else.

Go · MIT license

Agent

overview

What hakcheckurl does

hakcheckurl reads a file of URLs and reports the HTTP status each returns, one line per URL. Concurrency is -t (default 8). Output is flat enough to grep by code.

Use it after a crawler or wordlist pass when you only need live, redirecting, forbidden, or gone. It does not return titles or tech fingerprints.

Trickest exposes hakcheckurl as a managed Discovery node with a URLs file input and file/folder outputs. Hand survivors to httpx when you need titles and technology next.

source github.com/hakluke/hakcheckurl

use cases

Where hakcheckurl fits

Filter a URL list to live ones

Check a large set of URLs for their response codes so a downstream stage works only from the URLs that answer.

Find broken and forbidden links

Scan crawler or brute-force output for 404 and 403 responses to surface dead links and access-controlled paths worth a closer look.

Clear a long list with more threads

Raise the thread count with -t so a large URL list resolves in parallel instead of one request at a time.

Trim a list before a heavier prober

Run hakcheckurl after content discovery to cut the set down before httpx classifies titles and technology on what remains.

reference

hakcheckurl inputs and flags

2 inputs
NameTypeFlagDescription
urls-fileFILE·File of target URLs to check.
threadsSTRING-tNumber of threads to use (default 8).

Showing key inputs. hakcheckurl exposes 2 inputs in total.

example

Run hakcheckurl

hakcheckurl · command
# check a list of URLs and print each status code, 16 threads
cat urls.txt | hakcheckurl -t 16
sample output
200 https://example.com/
301 https://example.com/blog
302 https://example.com/login
403 https://example.com/admin
404 https://example.com/old-report
500 https://example.com/api/v1/export
200 https://example.com/docs
401 https://example.com/dashboard

guidance

Choosing hakcheckurl

Use for a minimal pass that returns only HTTP status codes for a URL list. When you need titles, tech detection, and richer probe signal, reach for httpx. hakcheckurl is the lighter, single-purpose option.

httpx

Full HTTP prober with status, title, tech, and more. hakcheckurl returns only response codes.

httprobe

Minimal liveness check for hosts. Close sibling for a quick alive-or-not pass.

404checker

Focuses on 404 and soft-404 responses. Overlaps hakcheckurl dead-link filtering.

faq

hakcheckurl questions

The HTTP response code for each URL in the input file, one line per URL. Status codes only; no page titles or technology data.

A file of target URLs. Hakluke's original reads URLs from stdin; the Trickest node maps that to a URLs file input and requests each one.

Set -t. A higher value clears a long URL list in parallel. Default is 8 threads.

hakcheckurl prints the status code next to each URL. Grep for 403 to collect forbidden paths or 404 to list dead links, then feed survivors to the next node.

When you need more than a status code. httpx adds titles, technology detection, and redirect chains. Pick hakcheckurl when the response code alone answers the question.

httprobe reports whether a host answers over HTTP or HTTPS. hakcheckurl takes full URLs and returns the exact status code each one returns.

Run hakcheckurl yourself

A URL list feeds hakcheckurl, which checks each one's HTTP status and writes the live URLs as a queryable output.

Facts on this page come from the live Trickest tool library.