AiVikings domain guides combine live product pricing with sourced information about a top-level domain, such as .app, .ai, or .com. We separate those two kinds of information because they change at different speeds and require different evidence.
Where TLD facts come from
For TLD policy, registry, and technical facts, we prefer primary sources: the registry or official NIC website, IANA delegation records, and ICANN materials when they are the relevant primary record.
These sources can support facts such as TLD type, registry operator, technical backend, delegation date, HTTPS requirements, registration restrictions, RDAP or WHOIS endpoints, and other documented policy details. Every fact in a TLD facts table is linked to its source.
Where price information comes from
First-year registration, renewal, and transfer prices come from the current AiVikings catalogue at render time. We do not copy those volatile values into the editorial source of truth. For longer ownership views, the page calculates the three-, five-, and ten-year totals from the current first-year and renewal prices. These totals are estimates based on displayed prices, not promises of future pricing.
Registered-domain counts
When a page shows a registered-domain count, it is clearly labelled as a third-party aggregate observation. AiVikings uses DomainNameStat only for that TLD-level metric and cites it directly.
That number is useful context, but it is not an official registry total. We do not use DomainNameStat for registry policy, eligibility, lifecycle rules, pricing, auctions, inventory, or competitor-level data.
What we do not use as a fact source
We do not store competitor pages, competitor-derived claims, competitor prices, auctions, inventories, or marketplace information in the TLD content source of truth. Competitor pages may be useful for understanding page formats during private research, but they are not evidence for a published AiVikings fact.
If a detail cannot be verified from an appropriate source, it remains absent. We do not fill the gap with an estimate or generic copy.
How a TLD page is checked
Before a page is rendered, its content is checked against the current fact pack. The process rejects expired source references, unsupported numbers, unsupported FAQ claims, competitor language, and generic or repeated wording. Source-backed facts, pricing, and page metadata are then assembled into the published page.
If a registry changes a policy or a source becomes stale, the fact pack should be refreshed before that claim is published again.