tldx
Bulk domain availability checking via RDAP, DNS, and WHOIS, with prefix/suffix permutations, regex patterns, MCP, and multiple output formats
Runssource: GitHubhomepageGoApache-2.0commit eb7468bae310
Go, Apache-2.0 licensed. The project labels itself: cli, developer tools, domain and golang.
tldx runs. An Argusic agent installed it in 6 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
tldx builds from source, its 294-test suite passes, and the binary answers version/help, performs real RDAP availability checks, and runs its MCP server over stdio without any third-party credentials
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Go toolchain not installed in container (no root to apt-install)3 minutes
- First attempt to download Go used wrong archive name .linux-x64 (404)1 minute
- Install time
- 6 minutes
- Cold machine to finish
- 32 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- go test ./... -count=1 exited 0 (294 tests passed, 0 failed); /tmp/tldx --version returned 'tldx version dev'; live lookups returned available=true for zznotrealzzz98765.com and available=false for google.com/google.io; MCP initialize and check_domains returned valid JSON-RPC responses
- Model tokens used
- 242,121
- Exact commit tested
- eb7468bae310
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- Install: downloaded Go 1.26.0 toolchain to user space (no root/system packages), `go build -o /tm… - Tests: `go test ./... -count=1` — 14/14 packages `ok`, 294 test cases passed, 0 failures. `go vet… - Real behavior: live RDAP lookups returned `available: true` for a made-up domain (`RDAP is not fo… No errors remained unfixed; only records are the initial gaps (missing Go toolchain) plus the `1644… tokens used 242,121 All verification complete. Final result: **Verification summary** - Install: downloaded Go 1.26.0 toolchain to user space (no root/system packages), `go build -o /tm… - Tests: `go test ./... -count=1` — 14/14 packages `ok`, 294 test cases passed, 0 failures. `go vet… - Real behavior: live RDAP lookups returned `available: true` for a made-up domain (`RDAP is not fo… No errors remained unfixed; only records are the initial gaps (missing Go toolchain) plus the `1644…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Took 6 minutes to install, slower than the median of the 59 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 60 cli projects Argusic has installed and timed, tldx was the 40th fastest to reach a running state, and 55 of 60 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 6 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tldx)Questions
- Does tldx run?
- Yes. tldx runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test tldx?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit eb7468bae310. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test tldx?
- The run that produced this verdict cost $0.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does tldx take to install?
- 6 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does tldx need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tldx?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does tldx compare with the alternatives?
- Of the 60 cli projects Argusic has installed and timed, tldx was the 40th fastest to reach a running state, and 55 of 60 reached one at all.
- Where is the evidence for tldx?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.