DOMAINING DIY CHALLENGE: Your Own Domain Marketplace Part I



The challenge is to create our own domain marketplace, technically speaking.


What is a domain marketplace ?





For this series, let’s establish that a domain marketplace is:

  1. More than one domain is for sale.
  2. A proper checkout page, where the inquirer has the ability to buyNow ( with at least two choices of payment) ; Counter-offer or ask for support.
  3. Ability to monitor all domains from a single dashboard.
  4. Multiple languages.
  5. International Domain Names ( IDN ) support (Ex: RoséWine.com which translates to xn--roswine-dya.com).
  6. Ability to Auction ( DIY Your own auction platform ).
  7. Real Time Stats as well as Domain Statuses (exp.date (real exp. date not registry or registrar exp. date), is it up or down, which ip currently resolves to.
  8. Ability to automatically generate a landing page, with domaining bits.
  9. Ability to deploy royalty-free apps in one or more domains, as automated as possible. Website Builder would be a bonus.
  10. Reports that accurately tell us everything related to the leads interacting with the domain in question (Think something similar to HotJar, which is great but expensive). Also, the report of domains with landing pages will be different than domains with real apps in them. Both categories are part of the marketplace inventory.
  11. You Tell Me.

In essence, any given domain of the designated portfolio should resolve to a landing page -or an app- and somewhere there will be ( or not ) a link to our universal checkout page ( POS from now onwards ). The link can be a simple “Learn More” or a different pitch, coming from a real app. We will learn how to place free open source royalty-free apps in your marketplace, in a later part of this series.

Do you have any abilities that you wish to have in your marketplace but do not see listed above ? Please leave a comment and let me know.


Obviously we will need to tackle this challenge in many parts, so I have divided this series in the following, Road Map:

Part I: This Introduction, that will be updated to reflect requests and progress.

Part II: Creating a proper checkout page for your domains.

Part III: Creating a custom landing page that can be applied to multiple-domains.

UPDATE [November 15th,2017] Checkpoint: Creating an open source repository with open-sourced code deliverable(s), in a github repository for DIY Domaining Marketplace challenge from DomainOverflow.com  

Part IV: Creating a centralised dashboard or admin dashboard if you will, to monitor your marketplace activity. Including network status and fetching the proper expiration date(s).

Part V: Demystifying IDNs ( domains with funny characters, ex: trocaderò.com ) and translating the marketplace to Portuguese and Italian -or any other language.This will also include an open source tool to convert between unicode-punycodes-utf-8.

Part VI:Creating your own Auction platform and seamlessly link it to the recently created checkout page.

Part VII: Deploying a real open-source, royalty-free app within one or more domains in your marketplace.

Part VIII: It’s all about data: Reports & Real time stats.

Part IX: Enhancements to your new domain marketplace ( your wish list ).

Part X: Alternative to all previous steps: Dotboss.digital. In fact, this part is already published here, feel free to peek.

Reference 1: Building the ultimate domaining server. A step-by-step guide on setting up your hosting/server for the purpose of domain investing (domaining).

Reference 2: Choosing your hosting. Is the cloud for you ? A simple but efficient guide on finding the best home for your domains.

(HINT: Your -minimum- should be a VPN with root access; about CD$ 200 or less per year. Also make sure your VPN comes with a free license of cpanel; most hostings have this a default ). There will be a subsequent article here on how to place your domaining server up at the cloud (i.e.: Amazon’s AWS, Google Cloud and Microsoft Azure ).

Technical Requirements.

Although this is a technical blog, I will do my utmost to ensure clarity and road maps to non-technical audiences. Depending on the feedback, it would be feasible to create additional articles, to better explain the technology used throughout this series. ( “save the equations, learn math, use the equations” principle apply)

Various technologies will be used, in no particular order of appearance, and it includes the following but not necessarily limited to:

PHP,  HTML, Ruby, Asynchronous JavaScript , DNS Records, The difference between a RegistrAr and a Registry, sld.tld, API and REST APIs ( use and concept; we will be creating a REST API router for price update, in part III of this series ), Software Versioning ( git and bit bucket ), Persistence / Database ( MySQL or JSON, both examples will be covered ). cpanel/whm ( 90% of all hosting accounts use a control panel called cpanel;  we will also cover github’s free hosting ; if anyone needs plesk please let us know ).

Please don’t be discouraged, if you are not technical at all. I will always explain what is the purpose and how would you go about learning it, but I will also provide ready downloads of ready scripts that we develop through this series.

Ready ?

Questions ? Comments ? Feel free to leave them down below.

Whenever you are ready, head over to Part II: Creating a proper checkout page for your domains.


Thanks for reading and happy domaining,




Tags: , , , , , , , ,


Leave a Reply

Your email address will not be published. Required fields are marked *

%d bloggers like this: