A domain profile is what you can see about a name from the outside. It is a combination of small, durable facts: the TLD it lives on, the rough age at which it first appears in registries, the language it has predominantly carried, any subdomain that has been live, and how the name behaves under a fresh crawl today. None of those facts on their own decide anything. Together they decide whether the name is a comfortable fit for what you want to build on it.
This page is the companion to the domain history notes. History is the timeline view. Profile is the snapshot view. Most reuse decisions need both, in that order.
What a profile is, and what it is not
A profile is a piece of evidence, not a verdict. The temptation with profile data is to aggregate it into a single number and let the number make the call. The number rarely earns that level of trust. A name with a high score can carry hidden language drift; a name with a low score can be a clean small-site choice. The profile is most useful when it is read deliberately, with each component asked the same question: does this fit the next intended use?
TLD and country context
The top-level domain carries genuine information. A ccTLD carries a clear country signal in user perception even when search engines treat it carefully. A generic TLD sits more neutrally but interacts with prior use in important ways: a generic TLD that previously hosted a single-language regional site already has a country lean in practice, regardless of what the registry says.
The IANA root zone database is the practical source for TLD context. It is dry, but it is the right reference when you want to know whether a TLD is generic, country-coded, restricted, or under unusual policy.
Age and continuity
Age in isolation is a poor signal. Age combined with continuity is a useful one. A name that has resolved consistently for a long period under similar use is in a different position from a name that has aged through several reinventions, dormant periods, or registry transfers. The continuity story matters more than the headline number.
Language and topic continuity
Language and topic do most of the practical work in a profile read. A small site that plans to publish in a different language from the dominant historical language is fine, but it is doing a transition, not a continuation. A small site that plans to stay in roughly the same language and topic neighbourhood as prior use will pick up relevance signals more naturally.
Subdomain footprint
A profile read should always glance at the subdomain footprint. If a name carries one or two stable subdomains alongside www, that is normal. If a name once had a wide spread of subdomains running independent content, that is part of the context. The subdomain notes cover the trade-offs when planning new ones.
Indexability today
The simplest and most overlooked profile signal is what happens when you check a few representative URLs against a current crawler. A 404 is not bad news; it is just a fact. A 410 is sometimes a good signal, especially if the prior path was unsuitable for indexing. A 200 with stale content is the most common surprise. Profile reading treats these as facts to record, not problems to solve before the new build starts.
Worked examples
The notebook keeps two example profile pages walking through this exact pattern.
Where this fits next
Once a profile is read, the next decisions are concrete: hosting that fits the realistic traffic and cadence, favicon setup that loads on the first request, a subdomain plan that does not create work later, and a plain pre-launch checklist. None of these are glamorous. All of them quietly decide how the next six months feel.