Two tools, opposite directions, and a gap each one leaves that the other fills.
Two opposite directions at the same problem
dnstwist starts from your brand and generates names: character swaps, homoglyphs, inserted hyphens, bit-flips, alternative TLDs. Then it tests which of those resolve. A zone search starts from what is registered and asks which of it matches your brand.
Generation is bounded by the generator's rules. Search is bounded by the zones covered. Those are different boundaries.
What a permutation engine cannot generate
Anything its rules did not anticipate. A squat spelled in a way no edit rule produces; a brand-plus-keyword domain such as a brand followed by -support, -login or a product name, which is not a typographic variant at all and so is not generated by a character edit engine. Those are exactly the domains a contains match finds.
What a zone search cannot see
Every country-code top-level domain. .io, .ai, .co, .me and the rest are outside ICANN's zone data service entirely, and a permutation engine can test a candidate there simply by resolving it. For brand protection this is the more serious of the two gaps.
Resolving and existing are different tests
dnstwist tells you a name answers. A zone file tells you a name is delegated. A domain can be delegated and serve nothing, which is why parked_for_sale exists as a triage field — and a name can resolve through infrastructure that a delegation record alone would not reveal.
What each one costs per result
A dnstwist-based detector in the Apify Store charges $0.03 per registered domain found, or about $30 per thousand. A zone sweep charges $0.004 per match, about $4 per thousand — roughly seven times cheaper per result, for the structural reason that a held dataset is cheap to query.
Using both, and what that closes
The zone sweep covers 1,075 gTLDs broadly and cheaply, including the spellings nobody would guess. The permutation engine covers the country-code namespaces and tests resolution. Run together, the remaining gap is small and describable; run alone, either leaves a hole that the report should name rather than imply.
