TLD Reference List
Reference list of top-level domains (TLDs) — generic, country-code, and sponsored TLDs with descriptions.
How it works
- 1Configure your options above
- 2Click "Generate" — processing happens in your browser
- 3Copy or download the result
What to do next
About TLD Reference List
TLD Reference List runs the developer utility job locally inside your browser. Reference list of top-level domains (TLDs) — generic, country-code, and sponsored TLDs with descriptions. The work happens on your machine, the result is generated on your machine, and the page exposes the controls you need to drive it without burying them in menus.
If you fit any of these descriptions, TLD Reference List should slot cleanly into your workflow: QA engineers writing repro cases; site reliability engineers triaging logs; students learning new languages. The tool keeps the controls focused on what matters for each of these use cases.
TLD Reference List is a static page plus a client-side engine. The browser does the work; there is no separate backend in the loop for the actual processing. That architecture is why the tool starts immediately, why it does not depend on the load on a remote service, and why running multiple jobs in a row does not slow it down.
Behind the controls you see, standard browser APIs is doing the actual developer utility. Formats are detected on load and the engine produces a deterministic output for any given input + options combination — useful when you need to re-run a job and expect identical results.
The right moment to reach for TLD Reference List is when you have a focused developer utility job that fits inside a browser tab. Open the page, drop in the file or paste your input, choose the options that matter, and the tool returns the result.
For multi-step jobs, TLD Reference List sits next to Port Number Reference, URL Parser, and DNS Zone File Generator. None of them depend on each other — you can use TLD Reference List on its own — but together they cover the common variations of the task this page exists to handle.
The output handed back by TLD Reference List is the output file. If you would prefer to keep the result in the browser instead of downloading it, you can copy it from the result panel and paste it directly into another tab — useful when the next tool in your workflow expects pasted text rather than a file.
A practical note on limits: TLD Reference List accepts inputs up to 0 MB per run, and the tool processes one input at a time to keep memory usage predictable. If you ever bump into the ceiling, the cause is the size of the input.
The transformation in TLD Reference List is deterministic — the same input plus the same options produces the same result every run. That predictability matters when the result has to match an upstream specification or be reproducible later.
A short note on how TLD Reference List came to look the way it does: every iteration started by watching how someone unfamiliar with the tool actually used it, then removing whatever got in their way. That is why the upload area dominates the screen, the run button is bigger than the secondary controls, and the result panel is unmissable when the job finishes.
Useful patterns when working with TLD Reference List: keep the input file open in another tab so you can compare against the result; give the output file a descriptive name when saving so you can find it later (the default name is sensible but generic); and treat each run as independent — the tool has no concept of "history", which means you cannot accidentally pollute one job with leftovers from another.
When something goes wrong, the cause is usually one of three things: a malformed input, a browser that is out of memory, or a corporate proxy that is interfering with the page's static assets. The first two are easy to diagnose; the third typically requires asking your IT team to allow standard browser APIs to load.
If you also use a command-line tool for tld reference list, TLD Reference List is a convenient alternative for the times you are on a different machine or helping someone who is not comfortable in a terminal. The output is a standard file in the format documented above.
Open the workspace above to start using TLD Reference List. The engine loads on the first interaction so the page itself stays light, and once the tool is warm it processes subsequent jobs quickly. The moment the page is interactive, the tool is ready to do real work on your file.
How it works
- 1Reach the TLD Reference List page in your browser to begin.
- 2Add your developer input by dropping it onto the page or browsing for it.
- 3Adjust the options to match what you need. Sensible defaults cover the most common case, so you can usually skip this step.
- 4Trigger processing. standard browser APIs reads your input, applies the transformation, and writes the result back into the page.
- 5Download the result. The file is generated in your browser and saved through your normal download flow.
- 6Run additional jobs as needed. The same controls and defaults apply on every run.
Common use cases
- Encode binary content for transport in a JSON body using TLD Reference List.
- Hash a string for a quick reproducibility check.
- Compare two API responses to spot a regression.
- Format a noisy log line into something a teammate can read.
- Decode a token to confirm its claims during a debugging session.
- Generate a quick fixture without leaving the browser.
- Pretty-print a minified blob during incident triage.
- Generate boilerplate from a single specification line.
FAQ
What is a TLD?
A top-level domain is the last part of a domain name (e.g. .com, .org, .uk). It sits at the highest level of the DNS hierarchy.
gTLD vs ccTLD?
gTLDs (generic) are open to anyone (.com, .org, .net). ccTLDs (country-code) represent countries (.uk, .de, .jp) — some have restrictions.
Which TLD should I choose?
.com is still the most recognized. Use .dev or .io for tech projects, ccTLDs for local markets, and new gTLDs for branding.
Are new TLDs good for SEO?
Google treats all TLDs equally for ranking. ccTLDs may help with local search in their respective countries.
HTTPS-only TLDs?
.dev and .app are HTTPS-only — browsers enforce HTTPS via preloaded HSTS, so HTTP will not work.
Private?
Yes — reference generated locally.
What input formats are supported by TLD Reference List?
The accepted formats are listed in the upload area on the tool itself. If your input is in a format that is not directly supported, convert it first using one of Favtoo's converter tools — every Favtoo converter outputs a file that is a clean input to the next tool in the chain.
What does the error message in TLD Reference List mean?
Failures usually fall into one of three buckets: the input is in an unsupported format, the input is over the size cap, or the input is structurally malformed (a truncated download, a partial export, or a stream the engine does not recognise). The first two are easy to confirm — check that your file is in a supported format and that it is below 0 MB. For the third, opening the file in its native viewer first is the fastest way to confirm the source is intact.
Are there any restrictions on using TLD Reference List at work?
TLD Reference List can be used for personal and commercial work alike — there is no separate "business" licence to purchase. The output you generate is yours to use however you want, including in client deliverables, internal documents, or commercial products. Favtoo's only ask is fair, individual use; the tool is not designed to be embedded as a backend service or wrapped behind an API for resale.
Does TLD Reference List support batch processing?
TLD Reference List processes one input at a time by design — it keeps memory usage predictable on lower-end devices and makes results easier to verify. To handle a folder, run the tool once per file; the page stays loaded between runs and remembers your last-used settings, so the second run is essentially instant.
Will TLD Reference List ask me to pay to download the result?
TLD Reference List is free to use. The processing runs in your browser, which keeps the per-user cost low enough that the tool can be offered openly. The download is the same file the engine produced — you can use it for as many runs as you need.
Is TLD Reference List lossless?
TLD Reference List is built to preserve quality wherever the underlying developer format allows it. Operations that are mathematically lossless (e.g. structural transformations, lossless re-encoding) round-trip with no perceptible change. Operations that involve a lossy codec inevitably introduce small artefacts at the byte level, but the defaults aim at the sweet spot where output looks or sounds the same to a normal viewer or listener while still being meaningfully smaller or faster than the input.
Do I need to install anything to use TLD Reference List?
No installation is needed. TLD Reference List runs as a normal web page, with no browser extension, no native helper, and no separate desktop client to download. That is partly a privacy choice — extensions can request broad permissions, while a regular page is sandboxed by default — and partly a convenience one: you can use TLD Reference List on any computer you have temporary access to without leaving anything installed on it.
How many times per day can I use TLD Reference List?
Inputs are capped at 0 MB per file, which keeps memory usage stable across phones, tablets and older laptops. You can run TLD Reference List as often as you need; every run produces a full-quality result.
Why use TLD Reference List instead of a paid online tool?
Desktop apps usually have more advanced features but require installation, maintenance and (often) a licence. Paid online tools are convenient but route your file through their servers and gate downloads behind accounts. TLD Reference List sits in between: free, instant, and private, but intentionally narrow in scope. For one-off jobs and the common developer utility operations, it is usually the lowest-friction choice; for highly specialised work, a dedicated app is still the right answer.