Why one bad hostname doesn't sink the whole batch

A typo'd domain, a host that genuinely doesn't have the requested record type, and a domain that doesn't exist at all are three different, completely normal outcomes when checking a list of hostnames someone else compiled — pulled from an inventory spreadsheet, a migration list, or a set of domains to audit. Failing the entire batch because one entry errors out would make the tool far less useful for exactly the case it's meant for: quickly checking a mixed list where some entries are expected to fail. Looking up each host independently and reporting a per-host result means one bad entry costs you one row of output, not the whole run.

Why the cap exists, and what to reach for beyond it

The 10-host cap isn't arbitrary — it matches the rate limit this site's DNS endpoint enforces (10 requests/minute) to keep the service responsive and available for every visitor, not just one person running a large batch. For genuinely large lists — hundreds or thousands of hostnames — a local script (`dig +short` in a shell loop, or PowerShell's `Resolve-DnsName`) will both be faster and have no such limit, since it resolves directly against your own configured DNS server rather than going through this site's rate-limited backend. This tool is aimed at the common case of checking a handful of hosts quickly from a browser with no local tooling handy, not bulk resolution at scale.