Domain subsidization makes it impossible to understand the true cost of ownership registrars offer these days. Domain comparison sites already exist, but they lack transparency, and are largely funded by affiliate earnings and sponsored placements - making the price comparisons clouded with sponsored placements rather than actual real multi-registrar price data. The existing sites aren't a source of truth I trust, so I built my own.
The goal of tld.wiki is to let you find a domain you love, understand the TRUE cost of ownership, and get it ranking at the top of Google.
It has full Agentic capabilities. You can plug it's MCP into your agent, and let it discover TLDs, check domains, and review back-link opportunities in for you.
I focused hard on the actual capabilities of each page. Wonder when a registrar increased their .com prices? We track history - and so much more.
Your domain research in one place - continuously improving from community (and potentially Agentic) submissions. That's my overall goal here.
I think that this project is really great and I am curious to hear what you think about open-sourcing the project if that's possible.
I think that open-sourcing can help foster the .wiki style community even more and I am very much interested in contributing and it will be much more helpful for me to contribute if it could be open source!
There are some issues I think but clicking cheapest renewal has issues where it shows: abudhabi at 0.00 but in reality it has 82$/yr costs.
The same goes for .ac.ae domains as well iirc
The website is also incredibly slow and takes multiple seconds for responses for what it's worth.
Anyways a really good project and I wish you luck and hoping that it can be open-sourced hopefully :-D
Fixed that issue, and added the requested filters. Thank you!
Application code is private for now. I might open source it in the future - it's closed source now as I want to avoid a cat-and-mouse situation with registrars, as most data is maintained somewhat programmatically.
Speed will continue to be improved with time.
It is hard to balance accuracy, speed, and scale with this project - as certain methods of availability ingestion return fast (but occasionally unreliable) data. Will try to make certain improvements over the following days.
3 comments
[ 1.8 ms ] story [ 22.9 ms ] threadThe goal of tld.wiki is to let you find a domain you love, understand the TRUE cost of ownership, and get it ranking at the top of Google.
It has full Agentic capabilities. You can plug it's MCP into your agent, and let it discover TLDs, check domains, and review back-link opportunities in for you.
I focused hard on the actual capabilities of each page. Wonder when a registrar increased their .com prices? We track history - and so much more.
Your domain research in one place - continuously improving from community (and potentially Agentic) submissions. That's my overall goal here.
Would love to hear what you guys think :)
I think that this project is really great and I am curious to hear what you think about open-sourcing the project if that's possible.
I think that open-sourcing can help foster the .wiki style community even more and I am very much interested in contributing and it will be much more helpful for me to contribute if it could be open source!
There are some issues I think but clicking cheapest renewal has issues where it shows: abudhabi at 0.00 but in reality it has 82$/yr costs.
The same goes for .ac.ae domains as well iirc
The website is also incredibly slow and takes multiple seconds for responses for what it's worth.
Anyways a really good project and I wish you luck and hoping that it can be open-sourced hopefully :-D
Application code is private for now. I might open source it in the future - it's closed source now as I want to avoid a cat-and-mouse situation with registrars, as most data is maintained somewhat programmatically.
We do have forms for public contribution requests however located at https://github.com/tld-wiki/community covering certain topics.
Speed will continue to be improved with time. It is hard to balance accuracy, speed, and scale with this project - as certain methods of availability ingestion return fast (but occasionally unreliable) data. Will try to make certain improvements over the following days.