A newly released command-line tool for checking domain name availability is generating buzz in the developer community, but users are already identifying significant technical limitations and suggesting substantial improvements. The tool, called tldx, promises to help developers quickly brainstorm and check available domain names across multiple top-level domains and variations.
Current tldx Features:
- Smart keyword-based domain permutations with prefixes, suffixes, and TLDs
- Concurrent WHOIS availability checks
- Real-time result streaming
- Optional domain length filtering
- Available on macOS via Homebrew, manual installation for Linux/Windows
Installation Problems Hit Early Adopters
Users attempting to install tldx through Homebrew are encountering immediate roadblocks. Multiple community members report 404 errors when trying to download the tool, with installation failing due to missing release files. The creator has acknowledged these issues and directed users to a GitHub issue tracker, but the problems highlight the challenges of distributing software across different platforms.
Technical Issues Identified:
- Homebrew installation failing with 404 errors
- WHOIS method unreliable and prone to blocking
- WHOIS protocol scheduled for retirement by IANA
- Results not sorted, making review difficult
- No timeout controls for long-running queries
WHOIS Method Faces Reliability Concerns
The technical approach behind tldx is drawing scrutiny from experienced developers. The tool currently relies on WHOIS queries to check domain availability, but community feedback suggests this method has serious flaws. Users point out that WHOIS services are unreliable and can quickly block repeated queries, making the tool less effective for bulk domain checking.
More concerning is the revelation that WHOIS itself is scheduled for retirement by IANA (Internet Corporation for Assigned Names and Numbers). This means the tool's core functionality may become obsolete in the future. Community members are recommending a shift to RDAP (Registration Data Access Protocol) as a more future-proof alternative.
Smart Optimization Strategies Emerge
The developer community is proposing clever solutions to improve the tool's efficiency. One particularly insightful suggestion involves using DNS checks before making WHOIS queries. By performing a quick SOA (Start of Authority) DNS request first, the tool could avoid unnecessary WHOIS queries when domains definitely exist, reducing the risk of being blocked by WHOIS servers.
You should consider adding DNS checks prior to WHOIS... doing a quick SOA DNS request can help reduce your WHOIS queries when the domain definitely exists
Community Suggested Improvements:
- Migrate from WHOIS to RDAP protocol
- Add DNS SOA checks before WHOIS queries
- Implement alphabetical sorting of results
- Separate available/taken domain lists
- Add timeout flags and result piping capabilities
- Consider terminal user interface (TUI) upgrade
User Experience Improvements Requested
Beyond technical fixes, users are asking for better ways to handle and view results. Current output streams results as they arrive from different servers, making it difficult to organize and review findings. Community suggestions include alphabetical sorting, separate lists for available and taken domains, timeout controls, and the ability to pipe results to files for further processing.
Some users are even suggesting a complete interface overhaul, moving from simple line-by-line output to a more sophisticated terminal user interface that could handle dynamic updates and better organization of results.
The community response reveals both enthusiasm for domain discovery tools and the high standards developers expect from command-line utilities. While tldx addresses a real need in an era where good domain names are increasingly scarce, its success will likely depend on addressing these early technical and usability concerns.
Reference: tldx