Data sources
Every dataset published on this site, where the data came from, and which rows are verified vs. still sample data.
Pricing
Each registrar's pricing rows in pricing.csv use a single source_url per row. When that URL is the registrar's official pricing page and we have confirmed the published values against it, the registrar's verified flag in registrars.json is true.
| Registrar | Status | Source URL | Last checked | |
|---|---|---|---|---|
| Namecheap | Sample / preview | www.namecheap.com/domains/registration/results/?domain=example.com | 2026-05-12 | |
| Porkbun | Verified from registrar page | porkbun.com/products/domains | 2026-05-27 | |
| Cloudflare Registrar | Sample / preview | www.cloudflare.com/products/registrar/ | 2026-05-27 | |
| GoDaddy | Sample / preview | www.godaddy.com | 2026-05-12 | |
| Spaceship | Sample / preview | www.spaceship.com | 2026-05-12 | |
| Dynadot | Sample / preview | www.dynadot.com | 2026-05-12 | |
| Squarespace Domains | Sample / preview | www.squarespace.com/domains | 2026-05-12 |
Other datasets
- registrar-scores.json — illustrative scoring. All scores are sample until each registrar has been hands-on tested per the scoring methodology.
- country-recommendations.json — recommended-registrar picks per country are heuristic until each registrar's pricing and per-country availability are verified.
- methodology.json — scoring weights and update frequencies. These are policy (decided by us), not measurements; nothing to verify externally.
- country-registry-facts.json (rendered into /countries/) — registry operator, policy authority, nexus rules per country. Each entry cites its own source URL on the rendered page.
- lib/tlds.ts (rendered into /tlds/) — registry operator and IANA root reference per TLD.
How to interpret this
If a page's data is partly verified and partly sample (e.g., the pricing tracker), it will show the per-row indicators ( verified / sample) along with a legend. The site-wide Preview data banner stays until all registrars are verified.
Suggest a correction
See the corrections policy. Verified corrections are applied within 7 business days and noted in the changelog.