Abstract: A computer-based method includes receiving, by at least one first server managed by a first domain name registrar, a search string that identifies a desired domain name by a potential owner. The desired domain name is determined to be available for transfer. A firm domain name transfer request for the desired domain name is received from the potential owner and sent to at least one domain name aftermarket server operating an Aftermarket Platform. An approval notification is received that the firm domain name transfer request is approved by the current owner. An authorization code for authorizing an electronic transfer of the desired domain name is received and utilized to transfer the desired domain name from a second domain name registrar to an account of the potential owner with the first domain name registrar so that the potential owner becomes a new owner of the desired domain name.

Abstract: A computer-based method includes receiving, by at least one first server managed by a first domain name registrar, a search string that identifies a desired domain name by a potential owner. The desired domain name is determined to be available for transfer. A firm domain name transfer request for the desired domain name is received from the potential owner and sent to at least one domain name aftermarket server operating an Aftermarket Platform. An approval notification is received that the firm domain name transfer request is approved by the current owner. An authorization code for authorizing an electronic transfer of the desired domain name is received and utilized to transfer the desired domain name from a second domain name registrar to an account of the potential owner with the first domain name registrar so that the potential owner becomes a new owner of the desired domain name.

Abstract: A domain name hi-jack prevention service may be selected by a domain name registrant and enabled by a Registrar. In a first embodiment, the Registrar may send a confirmation request via a preferred contact method to the registrant and only move the domain name from a first account to a second account (both managed by the Registrar) when the registrant confirms the request. In a second embodiment, a third party platform that is independent from and/or not the Registrar confirms the identity of the registrant before the Registrar moves the domain name from the first account to the second account (again, both managed by the Registrar). In a third embodiment, a third party platform communicates an authorization code to a verified registrant so the registrant can enter the authorization code with a Gaining Registrar so the domain name may be transferred from a Losing Registrar to the Gaining Registrar.

Abstract: A domain name hi-jack prevention service may be selected by a domain name registrant and enabled by a Registrar. In a first embodiment, the Registrar may send a confirmation request via a preferred contact method to the registrant and only move the domain name from a first account to a second account (both managed by the Registrar) when the registrant confirms the request. In a second embodiment, a third party platform that is independent from and/or not the Registrar confirms the identity of the registrant before the Registrar moves the domain name from the first account to the second account (again, both managed by the Registrar). In a third embodiment, a third party platform communicates an authorization code to a verified registrant so the registrant can enter the authorization code with a Gaining Registrar so the domain name may be transferred from a Losing Registrar to the Gaining Registrar.

Abstract: A domain name hi-jack prevention service may be selected by a domain name registrant and enabled by a Registrar. In a first embodiment, the Registrar may send a confirmation request via a preferred contact method to the registrant and only move the domain name from a first account to a second account (both managed by the Registrar) when the registrant confirms the request. In a second embodiment, a third party platform that is independent from and/or not the Registrar confirms the identity of the registrant before the Registrar moves the domain name from the first account to the second account (again, both managed by the Registrar). In a third embodiment, a third party platform communicates an authorization code to a verified registrant so the registrant can enter the authorization code with a Gaining Registrar so the domain name may be transferred from a Losing Registrar to the Gaining Registrar.

Abstract: A domain name hi-jack prevention service may be selected by a domain name registrant and enabled by a Registrar. In a first embodiment, the Registrar may send a confirmation request via a preferred contact method to the registrant and only move the domain name from a first account to a second account (both managed by the Registrar) when the registrant confirms the request. In a second embodiment, a third party platform that is independent from and/or not the Registrar confirms the identity of the registrant before the Registrar moves the domain name from the first account to the second account (again, both managed by the Registrar). In a third embodiment, a third party platform communicates an authorization code to a verified registrant so the registrant can enter the authorization code with a Gaining Registrar so the domain name may be transferred from a Losing Registrar to the Gaining Registrar.

Abstract: A domain name hi-jack prevention service may be selected by a domain name registrant and enabled by a Registrar. In a first embodiment, the Registrar may send a confirmation request via a preferred contact method to the registrant and only move the domain name from a first account to a second account (both managed by the Registrar) when the registrant confirms the request. In a second embodiment, a third party platform that is independent from and/or not the Registrar confirms the identity of the registrant before the Registrar moves the domain name from the first account to the second account (again, both managed by the Registrar). In a third embodiment, a third party platform communicates an authorization code to a verified registrant so the registrant can enter the authorization code with a Gaining Registrar so the domain name may be transferred from a Losing Registrar to the Gaining Registrar.

Abstract: A Buyer may enter a domain name or a related search string in a search field on a website operated by a Gaining Registrar. The Gaining Registrar may determine the domain name is registered at a Losing Registrar (a different registrar) and ask if the Buyer would like to make an offer on the domain name. If the Buyer does want to make an offer, the Gaining Registrar may validate the Buyer, collect a reserve from the Buyer and communicate the domain name and the offer (and possibly a time the offer is good) to an Aftermarket Platform (or possibly directly to the Losing Registrar). The Aftermarket Platform may then communicate the domain name, offer and possibly the time the offer is good to the Losing Registrar. The Losing Registrar may present the offer to the Seller (registrant of the domain name). The Seller may accept, decline, present a counter-offer to the Buyer or let the time the offer is good to expire.

Abstract: A Buyer may enter a domain name or a related search string in a search field on a website operated by a Gaining Registrar. The Gaining Registrar may determine the domain name is registered at a Losing Registrar (a different registrar) and ask if the Buyer would like to make an offer on the domain name. If the Buyer does want to make an offer, the Gaining Registrar may validate the Buyer, collect a reserve from the Buyer and communicate the domain name and the offer (and possibly a time the offer is good) to an Aftermarket Platform (or possibly directly to the Losing Registrar). The Aftermarket Platform may then communicate the domain name, offer and possibly the time the offer is good to the Losing Registrar. The Losing Registrar may present the offer to the Seller (registrant of the domain name). The Seller may accept, decline, present a counter-offer to the Buyer or let the time the offer is good to expire.

Abstract: A domain name hi-jack prevention service may be selected by a domain name registrant and enabled by a Registrar. In a first embodiment, the Registrar may send a confirmation request via a preferred contact method to the registrant and only move the domain name from a first account to a second account (both managed by the Registrar) when the registrant confirms the request. In a second embodiment, a third party platform that is independent from and/or not the Registrar confirms the identity of the registrant before the Registrar moves the domain name from the first account to the second account (again, both managed by the Registrar). In a third embodiment, a third party platform communicates an authorization code to a verified registrant so the registrant can enter the authorization code with a Gaining Registrar so the domain name may be transferred from a Losing Registrar to the Gaining Registrar.