US20140330674A1 - Certified offer service for domain names - Google Patents

Certified offer service for domain names Download PDF

Info

Publication number
US20140330674A1
US20140330674A1 US14/223,316 US201414223316A US2014330674A1 US 20140330674 A1 US20140330674 A1 US 20140330674A1 US 201414223316 A US201414223316 A US 201414223316A US 2014330674 A1 US2014330674 A1 US 2014330674A1
Authority
US
United States
Prior art keywords
user
domain name
offer
registrant
amount
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US14/223,316
Inventor
Scott Ableman
Suzanne Graham
Steve Miholovich
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Network Solutions LLC
Original Assignee
Network Solutions LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Network Solutions LLC filed Critical Network Solutions LLC
Priority to US14/223,316 priority Critical patent/US20140330674A1/en
Assigned to JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT reassignment JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: NETWORK SOLUTIONS, LLC
Publication of US20140330674A1 publication Critical patent/US20140330674A1/en
Assigned to NETWORK SOLUTIONS, LLC reassignment NETWORK SOLUTIONS, LLC RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (034060/0945) Assignors: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]
    • G06Q30/0609Buyer or seller confidence or verification
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/388Payment protocols; Details thereof using mutual authentication without cards, e.g. challenge-response
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions

Definitions

  • the field of the invention is Internet domain names, and in particular the sale of Internet domain name registrations through a service.
  • FIG. 1 shows a system in accordance with an embodiment of the present invention.
  • FIG. 2 shows an apparatus in accordance with an embodiment of the present invention.
  • FIGS. 3A-3C show the first part of a method in accordance with the present invention.
  • FIGS. 4A-4C show the second part of the method in accordance with an embodiment of the present invention.
  • FIG. 1 A system in accordance with an embodiment of the present invention is shown in FIG. 1 .
  • a user 101 and a registrant 102 are coupled to a third party service provider 103 through network 104 .
  • Third party service provider I 03 can be any entity that can effectuate the transfer a domain name, such as a domain name registrar, an entity with a contractual relationship with a domain name registrar, a registry, an independent entity offering the domain name transfer service in accordance with an embodiment of the present invention, etc.
  • Network 104 can be any suitable network, such as the Internet, a Virtual Private Network, a Local Area Network, a wireless network, etc., or any suitable combination thereof.
  • Third party service provider 103 can include an apparatus such as that shown in FIG. 2 .
  • the apparatus of FIG. 2 includes a processor 201 coupled to a memory 202 .
  • Processor 201 can be a general purpose microprocessor, such as the Pentitml IV processor made by the Intel Corporation of Santa Clara, Calif.
  • Processor 201 can be an Application Specific Integrated Circuit (ASIC) that embodies at least part of the method in accordance with an embodiment of the present invention in its hardware and/or firmware.
  • ASIC Application Specific Integrated Circuit
  • An example of an ASIC is a Digital Signal Processor.
  • Memory 202 can be any suitable device that can store electronic information, such as a hard disk, Compact Disc, Random Access Memory (RAM), Read Only Memory (ROM), flash memory, etc., or any suitable combination thereof.
  • Memory 202 stores certified offer instructions 203 that are adapted to be executed by processor 201 to perform the method in accordance with an embodiment of the present invention. All or part of the certified offer instructions can be stored on a medium, which can include fixed or portable memory 202 , or a telecommunications channel over which instructions 202 can be transmitted from a sender to a recipient.
  • the third party service provider is a domain name registrar.
  • a user visits the web site of the registrar to attempt to register a domain name.
  • the user submits the domain name 301 to a search engine at the registrar site to determine if the domain name is available 302 , or if it has already been registered by another. If the domain name is available, then the user can register it normally 303 .
  • the registrar site displays this result 304 to the user along with an option 305 for the user to make a certified offer 306 to purchase the domain name registration from its present registrant. If the user selects this option, the registrar can offer to the user an appraisal service 307 to assist the user in determining an appropriate amount to offer the registrant for the domain name.
  • the registrar site can appraise the value of the domain name by assessing the amount of traffic to the domain name, e.g., the number of times the name has been resolved by a name server operated by the registrar. Another measurement of “traffic” could be made by conducting a general search of the Internet and determining the number of links to a web page whose address includes the domain name. The more traffic to the name, the higher the appraised value could be.
  • domain name can be examined for the occurrence of any word or words in English and/or in any other language or languages. Domain names that are generic terms can be valued higher than domain names with fanciful terms that mean nothing in English or other languages. Similarly, domain names in English or Spanish could be valued more highly than domain names in languages spoken in countries with smaller economies.
  • the length of the domain name can also be considered in assessing its value. Shorter domain names can be assigned a higher value than longer domain names. Likewise, if the domain name links to an active web site, it can raise the appraised value compared to a domain name that does not link to an active site. Certain Top Level Domains (“TLD”, e.g., COM, NET, US, etc.) are generally more valuable than others. The value of a domain name with certain TLDs can be appraised to be higher than the same name except having another TLD.
  • TLD Top Level Domains
  • Any suitable metric and/or weighting scheme can be used to obtain an appraisal.
  • a present range of values can be established, e.g., running from the minimum cost of a registration (e.g., $100) to a large amount, such as $10,000. can be used the relevance of any word or words in the domain name, the length of the domain name, whether the domain name corresponds to a web site, and the top level domain of the domain name.
  • Each of the factors discussed above can be assigned a rating from 1 to 5, based upon an assessment of the factor in light of the domain name requested by the user.
  • the lowest traffic names can be assigned a traffic rating of “1”, with the highest receiving a rating of “5”
  • Rules can be implemented for deriving a word/language rating, e.g., if the domain name consists of a single real English or Spanish word, then it could be rated 5; a two or more such words, “4”; a single word in Laotian, “2”, etc.
  • the length of the domain name can be assigned a value equal to 7 minus the number of characters in the name, with a minimum score of 1.
  • the ratings can be weighted (or not) according to any suitable scheme.
  • TLD may be judged to be twice as important as language/word content, and so the TLD rating can be counted twice in calculating an overall score for the name.
  • the weighted factor ratings can be summed and then normalized to produce a number between 0 and 1. This number can be multiplied by the difference between the large amount (here, $10,000) and the minimum value (in this example, $100.) The resulting number can be added to the minimum to obtain an appraised dollar value for the domain name requested by the user.
  • the transaction can proceed by presenting a shopping cart screen 310 to the user.
  • the interface 310 can be used to gather user and user payment information.
  • the user's name, address, e-mail address and financial instrument information e.g., credit card number, debit card number, deposit account number, etc.
  • financial instrument information e.g., credit card number, debit card number, deposit account number, etc.
  • the user can also enter an offer amount for the domain name.
  • the offer amount can be the same as, or different than, the appraisal amount provided by the registrar.
  • the user can submit the offer by selecting a button on the interface, or by any other suitable means.
  • offer information can be stored as a record in an offer database 313 .
  • An offer information record can include an offer information identifier for distinguishing the record from other records of other offers, user name and contact information, the domain name that is the subject of the offer, the offer amount, etc.
  • the registrar can certify the offer by determining if the financial instrument identified by the user has sufficient funds or line of credit to pay at least the offer amount submitted by the user, i.e., the financial instrument can be “preauthorized” for at least the amount of the offer.
  • the financial instrument can be preauthorized for an amount greater that the offer amount, e.g., to verify that the user can pay the offer amount as well as a transaction fee and/or registration fee to the registrar. If the preauthorization is not successful, the offer can be declined by the registrar, and the transaction may be terminated. Alternatively, the user may be asked to provide another financial instrument.
  • a message 314 (via any suitable medium, e.g., pager message, instant message, SMS message, telephone call, etc.) acknowledging receipt of the offer can be sent to the user.
  • an offer message 315 in any suitable medium can be generated and sent to the registrant of the domain name.
  • Contact information for the registrant can be obtained from the whois information for the domain name.
  • the offer message can include a statement averring that the offer is “certified,” i.e., that a financial instrument of the offeror (whose identity can be kept secret by the registrar) has been preauthorized for the offer amount and a statement indicating that the offer is good for a certain period of time (e.g., 7 days, 24 hours, until the following Monday at 5 PM, etc.), after which it will expire.
  • An offer message to the registrant can include a link to a registrar interface designed to permit the registrant to respond to the offer, or else the interface can solicit a voice or keystroke response to indicate an action by the registrant in response to the offer.
  • the registrant can respond to the offer 401 by rejecting the offer and sending a message to the registrar indicating the rejection.
  • the user can be informed by the registrar that the offer has been rejected, and can abandon the transaction or make a new, higher offer.
  • the registrant can accept the offer 403 .
  • the registration can be “locked,” e.g., changes to the registration can be prevented until the offer transaction is either consummated.
  • the registrar can debit the user's financial instrument 404 and arrange to transfer the domain name from the registrant to the user.
  • the registrar can transfer the domain name to an account set up by the user, and add a year (or other period of time) to the expiration date of the registration. Until the registrant takes action with regard to the offer, the registrar can send periodic offer status updates 405 to the user.
  • the amount debited the user's financial instrument can be the sum of the offer amount, a transaction fee and a registration fee for the domain name, and can also include other fees.
  • the registrar can issue and mail to the registrant a check to the sum of the offer amount.
  • the registrar can transfer the offer amount electronically to an account of the registrant.
  • the amount transferred to the registrant can be less than the offer amount, e.g., can be the offer amount less a service charge retained by the registrar.
  • a record of the registrant's response can be added to the offer database.
  • the registrant can also respond to the offer with a counteroffer 406 .
  • the counteroffer can be submitted through a registrant counteroffer interface 407 provided by the registrar.
  • the counteroffer can include a counteroffer amount submitted by the registrant.
  • the counteroffer amount is the amount that the registrant will accept to transfer the domain name registration to the user.
  • the counteroffer can be sent in a message 408 (via any suitable medium, e.g., e-mail, SMS message, instant message, telephone call, etc.) to the user.
  • the counteroffer can be good indefinitely, or for a certain period of time before expiring 409 .
  • the registration can be locked when the registrar receives the message indicating that the registrant has submitted a counteroffer.
  • the user can reject the counteroffer 410 , in which case the transaction can be terminated 411 .
  • the user can accept the counteroffer 412 .
  • the user financial instrument can be debited 413 an amount equal to at least the amount of the counteroffer.
  • the user financial instrument can also be debited for registration and service fees.
  • the registrar can issue and mail a check to the registrant to the sum of the counteroffer amount, or to the sum of the counteroffer amount less a service fee. Alternatively, the registrar can electronically transfer the funds to a registrant account.
  • a record of the responses of the user and registrant, as well as financial details concerning the transaction, can be added to the offer database.
  • the registrar can contact the user to obtain the necessary information for transferring the domain name registration from the registrant to the user, e.g., information not gathered thus far in the transaction, such as a choice of name servers, a fax number for the user, etc. Alternatively, some or all of this information can be gathered at the beginning from the user, or at any convenient point during the transaction.
  • the third party providing the domain name offer and/or counteroffer service need not be a registrar, but may be any entity that can effectuate the transfer of a domain name.

Abstract

A method for purchasing a domain name registration. A user conducts a search to determine if a domain name is available. If it is already registered, the user can make an anonymous offer through a third party to the present registrant to purchase the domain name registration. The offer is certified by the third party by verifying that a financial instrument provided by the user has available funds that are at least sufficient to pay the offer amount for the domain name.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This application is a continuation of U.S. application Ser. No. 10/854,221, filed May 27, 2004, the disclosure of which is incorporated by reference in its entirety.
  • FIELD OF THE INVENTION
  • The field of the invention is Internet domain names, and in particular the sale of Internet domain name registrations through a service.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 shows a system in accordance with an embodiment of the present invention.
  • FIG. 2 shows an apparatus in accordance with an embodiment of the present invention.
  • FIGS. 3A-3C show the first part of a method in accordance with the present invention.
  • FIGS. 4A-4C show the second part of the method in accordance with an embodiment of the present invention.
  • DETAILED DESCRIPTION
  • A system in accordance with an embodiment of the present invention is shown in FIG. 1. A user 101 and a registrant 102 are coupled to a third party service provider 103 through network 104. Third party service provider I 03 can be any entity that can effectuate the transfer a domain name, such as a domain name registrar, an entity with a contractual relationship with a domain name registrar, a registry, an independent entity offering the domain name transfer service in accordance with an embodiment of the present invention, etc. Network 104 can be any suitable network, such as the Internet, a Virtual Private Network, a Local Area Network, a wireless network, etc., or any suitable combination thereof.
  • Third party service provider 103 can include an apparatus such as that shown in FIG. 2. The apparatus of FIG. 2 includes a processor 201 coupled to a memory 202. Processor 201 can be a general purpose microprocessor, such as the Pentitml IV processor made by the Intel Corporation of Santa Clara, Calif. Processor 201 can be an Application Specific Integrated Circuit (ASIC) that embodies at least part of the method in accordance with an embodiment of the present invention in its hardware and/or firmware. An example of an ASIC is a Digital Signal Processor.
  • Memory 202 can be any suitable device that can store electronic information, such as a hard disk, Compact Disc, Random Access Memory (RAM), Read Only Memory (ROM), flash memory, etc., or any suitable combination thereof. Memory 202 stores certified offer instructions 203 that are adapted to be executed by processor 201 to perform the method in accordance with an embodiment of the present invention. All or part of the certified offer instructions can be stored on a medium, which can include fixed or portable memory 202, or a telecommunications channel over which instructions 202 can be transmitted from a sender to a recipient.
  • The method in accordance with an embodiment of the present invention is shown in FIG. 3. In this embodiment, the third party service provider is a domain name registrar. A user visits the web site of the registrar to attempt to register a domain name. The user submits the domain name 301 to a search engine at the registrar site to determine if the domain name is available 302, or if it has already been registered by another. If the domain name is available, then the user can register it normally 303.
  • If the domain name is not available because it is registered to another, the registrar site displays this result 304 to the user along with an option 305 for the user to make a certified offer 306 to purchase the domain name registration from its present registrant. If the user selects this option, the registrar can offer to the user an appraisal service 307 to assist the user in determining an appropriate amount to offer the registrant for the domain name.
  • The registrar site can appraise the value of the domain name by assessing the amount of traffic to the domain name, e.g., the number of times the name has been resolved by a name server operated by the registrar. Another measurement of “traffic” could be made by conducting a general search of the Internet and determining the number of links to a web page whose address includes the domain name. The more traffic to the name, the higher the appraised value could be.
  • Similarly, the domain name can be examined for the occurrence of any word or words in English and/or in any other language or languages. Domain names that are generic terms can be valued higher than domain names with fanciful terms that mean nothing in English or other languages. Similarly, domain names in English or Spanish could be valued more highly than domain names in languages spoken in countries with smaller economies.
  • The length of the domain name can also be considered in assessing its value. Shorter domain names can be assigned a higher value than longer domain names. Likewise, if the domain name links to an active web site, it can raise the appraised value compared to a domain name that does not link to an active site. Certain Top Level Domains (“TLD”, e.g., COM, NET, US, etc.) are generally more valuable than others. The value of a domain name with certain TLDs can be appraised to be higher than the same name except having another TLD.
  • Any suitable metric and/or weighting scheme can be used to obtain an appraisal. In one embodiment, a present range of values can be established, e.g., running from the minimum cost of a registration (e.g., $100) to a large amount, such as $10,000. can be used the relevance of any word or words in the domain name, the length of the domain name, whether the domain name corresponds to a web site, and the top level domain of the domain name. Each of the factors discussed above can be assigned a rating from 1 to 5, based upon an assessment of the factor in light of the domain name requested by the user. For example, the lowest traffic names can be assigned a traffic rating of “1”, with the highest receiving a rating of “5” Rules can be implemented for deriving a word/language rating, e.g., if the domain name consists of a single real English or Spanish word, then it could be rated 5; a two or more such words, “4”; a single word in Laotian, “2”, etc. The length of the domain name can be assigned a value equal to 7 minus the number of characters in the name, with a minimum score of 1. TLDs can be assigned a rating in accordance with entries in a table (e.g., COM and NET=“5”, “ORG”=“3”, etc.)
  • The ratings can be weighted (or not) according to any suitable scheme. For example, TLD may be judged to be twice as important as language/word content, and so the TLD rating can be counted twice in calculating an overall score for the name. The weighted factor ratings can be summed and then normalized to produce a number between 0 and 1. This number can be multiplied by the difference between the large amount (here, $10,000) and the minimum value (in this example, $100.) The resulting number can be added to the minimum to obtain an appraised dollar value for the domain name requested by the user.
  • The transaction can proceed by presenting a shopping cart screen 310 to the user. The interface 310 can be used to gather user and user payment information. For example, the user's name, address, e-mail address and financial instrument information (e.g., credit card number, debit card number, deposit account number, etc.) can be submitted by the user through the interface (e.g., such as a shopping cart interface) and received by the registrar. The user can also enter an offer amount for the domain name. The offer amount can be the same as, or different than, the appraisal amount provided by the registrar. The user can submit the offer by selecting a button on the interface, or by any other suitable means.
  • When the offer is submitted by the user, the user can be presented with confirmation screens 311 and 312, offer information can be stored as a record in an offer database 313. An offer information record can include an offer information identifier for distinguishing the record from other records of other offers, user name and contact information, the domain name that is the subject of the offer, the offer amount, etc.
  • After the offer is submitted, the registrar can certify the offer by determining if the financial instrument identified by the user has sufficient funds or line of credit to pay at least the offer amount submitted by the user, i.e., the financial instrument can be “preauthorized” for at least the amount of the offer. The financial instrument can be preauthorized for an amount greater that the offer amount, e.g., to verify that the user can pay the offer amount as well as a transaction fee and/or registration fee to the registrar. If the preauthorization is not successful, the offer can be declined by the registrar, and the transaction may be terminated. Alternatively, the user may be asked to provide another financial instrument.
  • A message 314 (via any suitable medium, e.g., pager message, instant message, SMS message, telephone call, etc.) acknowledging receipt of the offer can be sent to the user. Similarly, an offer message 315 in any suitable medium can be generated and sent to the registrant of the domain name. Contact information for the registrant can be obtained from the whois information for the domain name. The offer message can include a statement averring that the offer is “certified,” i.e., that a financial instrument of the offeror (whose identity can be kept secret by the registrar) has been preauthorized for the offer amount and a statement indicating that the offer is good for a certain period of time (e.g., 7 days, 24 hours, until the following Monday at 5 PM, etc.), after which it will expire. An offer message to the registrant can include a link to a registrar interface designed to permit the registrant to respond to the offer, or else the interface can solicit a voice or keystroke response to indicate an action by the registrant in response to the offer.
  • As shown in FIG. 4, the registrant can respond to the offer 401 by rejecting the offer and sending a message to the registrar indicating the rejection. In this case, the user can be informed by the registrar that the offer has been rejected, and can abandon the transaction or make a new, higher offer. Alternatively, the registrant can accept the offer 403. When a message is received by the registrar indicating the registrant has accepted the offer and if the domain name registration is hosted by the registrar, then the registration can be “locked,” e.g., changes to the registration can be prevented until the offer transaction is either consummated. The registrar can debit the user's financial instrument 404 and arrange to transfer the domain name from the registrant to the user. For example, the registrar can transfer the domain name to an account set up by the user, and add a year (or other period of time) to the expiration date of the registration. Until the registrant takes action with regard to the offer, the registrar can send periodic offer status updates 405 to the user.
  • The amount debited the user's financial instrument can be the sum of the offer amount, a transaction fee and a registration fee for the domain name, and can also include other fees. The registrar can issue and mail to the registrant a check to the sum of the offer amount. Alternatively, the registrar can transfer the offer amount electronically to an account of the registrant. The amount transferred to the registrant can be less than the offer amount, e.g., can be the offer amount less a service charge retained by the registrar. A record of the registrant's response can be added to the offer database.
  • The registrant can also respond to the offer with a counteroffer 406. The counteroffer can be submitted through a registrant counteroffer interface 407 provided by the registrar. The counteroffer can include a counteroffer amount submitted by the registrant. The counteroffer amount is the amount that the registrant will accept to transfer the domain name registration to the user. The counteroffer can be sent in a message 408 (via any suitable medium, e.g., e-mail, SMS message, instant message, telephone call, etc.) to the user. The counteroffer can be good indefinitely, or for a certain period of time before expiring 409. The registration can be locked when the registrar receives the message indicating that the registrant has submitted a counteroffer. The user can reject the counteroffer 410, in which case the transaction can be terminated 411. The user can accept the counteroffer 412. If the counteroffer is accepted by the user, then the user financial instrument can be debited 413 an amount equal to at least the amount of the counteroffer. The user financial instrument can also be debited for registration and service fees. The registrar can issue and mail a check to the registrant to the sum of the counteroffer amount, or to the sum of the counteroffer amount less a service fee. Alternatively, the registrar can electronically transfer the funds to a registrant account.
  • A record of the responses of the user and registrant, as well as financial details concerning the transaction, can be added to the offer database.
  • After a successful offer (or counteroffer) transaction, the registrar can contact the user to obtain the necessary information for transferring the domain name registration from the registrant to the user, e.g., information not gathered thus far in the transaction, such as a choice of name servers, a fax number for the user, etc. Alternatively, some or all of this information can be gathered at the beginning from the user, or at any convenient point during the transaction.
  • The foregoing description is meant to illustrate, and not limit, the scope of the invention. One of skill in the art will understand that the invention encompasses other aspects that have not been explicitly described. For example, the third party providing the domain name offer and/or counteroffer service need not be a registrar, but may be any entity that can effectuate the transfer of a domain name.

Claims (16)

1. A computer-implemented method comprising:
receiving, from a user, an offer message indicating an offer amount for a domain name registered to a registrant different from the user;
certifying that the user has access to funds that are at least sufficient to pay the offer amount; and
responsive to the offer amount being successfully certified, sending to the registrant an offer to purchase the domain name registration from the registrant.
2. The method of claim 1, wherein the offer to purchase the domain name registration is sent to the registrant without revealing the identity of the user to the registrant.
3. The method of claim 1, further comprising:
receiving an acceptance of the offer from the registrant;
debiting a financial instrument of the user; and
arranging for the transfer of the domain name from the registrant to the user.
4. The method of claim 1. further comprising:
receiving a search request for a desired domain name;
identifying the domain name as a result of a search for the desired domain name;
providing a search result that indicates the domain name is a result for the search, and that the domain name is registered.
5. The method of claim 1, further comprising locking the registration of the domain name after receiving a message from the registrant indicating that the registrant has accepted the offer or after receiving a message from the user indicating that the user has accepted the counteroffer.
6. The method of claim 1, wherein the registrant is given a period of time within which to respond to the offer to purchase the domain name registration, after which the offer expires.
7. The method of claim 1, further comprising:
receiving from the registrant a counteroffer to sell the domain name registration, wherein the counteroffer includes a counteroffer amount: and
sending to the user an indication of the counteroffer, including the counteroffer amount.
8. The method of claim 7, further comprising:
receiving from the user an acceptance of the counteroffer; and
sending an indication of the acceptance of the counteroffer to the registrant.
9. The method of claim 8, further comprising:
debiting a financial instrument of the user; and
arranging for the transfer of the domain name from the registrant to the user.
10. The method of claim 1, further including receiving registration information from the user, wherein the registration information is used to register the domain name to the user.
11. The method of claim 1, wherein the offer sent to the registrant indicates that the offer is certified for the offer amount.
12. The method of claim 1, further comprising:
providing, by the computer system, an appraisal estimating a value of the domain name.
13. The method of claim 12, wherein the appraisal estimate is based on at least one selected from the group consisting of: a length of the domain name; a top level domain included in the domain name; an amount of traffic using the domain name; a relevance of at least one word in the domain name; and a determination of whether the domain name corresponds to an existing web site.
14. The method of claim 1, wherein certifying that the user has access to funds that are at least sufficient to pay the offer amount includes pre authorizing a credit card of the user for at least the amount of the offer.
15. The method of claim 1, wherein certifying that the user has access to funds that are at least sufficient to pay the offer amount includes checking the balance of an account of the user at a bank based upon a debit instrument of the user, wherein the debit instrument is issued by the bank.
16. The method of claim 1, wherein certifying that the user has access to funds that are at least sufficient to pay the offer amount includes checking the balance of a deposit account maintained by the user.
US14/223,316 2004-05-27 2014-03-24 Certified offer service for domain names Abandoned US20140330674A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/223,316 US20140330674A1 (en) 2004-05-27 2014-03-24 Certified offer service for domain names

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10/854,221 US8706585B2 (en) 2004-05-27 2004-05-27 Certified offer service for domain names
US14/223,316 US20140330674A1 (en) 2004-05-27 2014-03-24 Certified offer service for domain names

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/854,221 Continuation US8706585B2 (en) 2004-05-27 2004-05-27 Certified offer service for domain names

Publications (1)

Publication Number Publication Date
US20140330674A1 true US20140330674A1 (en) 2014-11-06

Family

ID=35463564

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/854,221 Active 2029-08-18 US8706585B2 (en) 2004-05-27 2004-05-27 Certified offer service for domain names
US14/223,316 Abandoned US20140330674A1 (en) 2004-05-27 2014-03-24 Certified offer service for domain names

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/854,221 Active 2029-08-18 US8706585B2 (en) 2004-05-27 2004-05-27 Certified offer service for domain names

Country Status (5)

Country Link
US (2) US8706585B2 (en)
EP (1) EP1782252A4 (en)
AU (2) AU2005250809A1 (en)
CA (1) CA2568172A1 (en)
WO (1) WO2005119501A2 (en)

Families Citing this family (39)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7877432B2 (en) * 2003-07-08 2011-01-25 The Go Daddy Group, Inc. Reseller program for registering domain names through resellers' web sites
US20060282795A1 (en) * 2004-09-13 2006-12-14 Network Solutions, Llc Domain bar
US20060095404A1 (en) * 2004-10-29 2006-05-04 The Go Daddy Group, Inc Presenting search engine results based on domain name related reputation
US7797413B2 (en) * 2004-10-29 2010-09-14 The Go Daddy Group, Inc. Digital identity registration
US8904040B2 (en) * 2004-10-29 2014-12-02 Go Daddy Operating Company, LLC Digital identity validation
US20080028443A1 (en) * 2004-10-29 2008-01-31 The Go Daddy Group, Inc. Domain name related reputation and secure certificates
US20080022013A1 (en) * 2004-10-29 2008-01-24 The Go Daddy Group, Inc. Publishing domain name related reputation in whois records
US8117339B2 (en) * 2004-10-29 2012-02-14 Go Daddy Operating Company, LLC Tracking domain name related reputation
US20070208940A1 (en) * 2004-10-29 2007-09-06 The Go Daddy Group, Inc. Digital identity related reputation tracking and publishing
US9015263B2 (en) 2004-10-29 2015-04-21 Go Daddy Operating Company, LLC Domain name searching with reputation rating
US20080028100A1 (en) * 2004-10-29 2008-01-31 The Go Daddy Group, Inc. Tracking domain name related reputation
US20060095459A1 (en) * 2004-10-29 2006-05-04 Warren Adelman Publishing domain name related reputation in whois records
US20060200487A1 (en) * 2004-10-29 2006-09-07 The Go Daddy Group, Inc. Domain name related reputation and secure certificates
US20050125451A1 (en) * 2005-02-10 2005-06-09 The Go Daddy Group, Inc. Search engine and domain name search integration
US8214272B2 (en) * 2006-09-05 2012-07-03 Rafael A. Sosa Web site valuation
US20090248623A1 (en) * 2007-05-09 2009-10-01 The Go Daddy Group, Inc. Accessing digital identity related reputation data
US20090119198A1 (en) * 2007-11-06 2009-05-07 Gregory Manriquez Method for Domain Trading
US7805379B1 (en) * 2007-12-18 2010-09-28 Amazon Technologies, Inc. Method and system for leasing or purchasing domain names
US9531581B1 (en) 2007-12-18 2016-12-27 Amazon Technologies, Inc. Method and system for identifying and automatically registering domain names
US8224923B2 (en) * 2009-06-22 2012-07-17 Verisign, Inc. Characterizing unregistered domain names
US20110208767A1 (en) * 2010-02-19 2011-08-25 The Go Daddy Group, Inc. Semantic domain name spinning
US8909558B1 (en) 2010-02-19 2014-12-09 Go Daddy Operating Company, LLC Appraising a domain name using keyword monetary value data
US8706728B2 (en) * 2010-02-19 2014-04-22 Go Daddy Operating Company, LLC Calculating reliability scores from word splitting
US9058393B1 (en) 2010-02-19 2015-06-16 Go Daddy Operating Company, LLC Tools for appraising a domain name using keyword monetary value data
US8515969B2 (en) * 2010-02-19 2013-08-20 Go Daddy Operating Company, LLC Splitting a character string into keyword strings
US20150095176A1 (en) * 2012-10-01 2015-04-02 Frank Taylor Schilling Domain Name Marketplace With Mobile Sales And Brokerage Platform
US20140188651A1 (en) * 2013-01-02 2014-07-03 Minds + Machines Domain name registration and resale
US9904944B2 (en) 2013-08-16 2018-02-27 Go Daddy Operating Company, Llc. System and method for domain name query metrics
US9715694B2 (en) 2013-10-10 2017-07-25 Go Daddy Operating Company, LLC System and method for website personalization from survey data
US9613374B2 (en) 2013-10-10 2017-04-04 Go Daddy Operating Company, LLC Presentation of candidate domain name bundles in a user interface
US9684918B2 (en) 2013-10-10 2017-06-20 Go Daddy Operating Company, LLC System and method for candidate domain name generation
US9866526B2 (en) 2013-10-10 2018-01-09 Go Daddy Operating Company, LLC Presentation of candidate domain name stacks in a user interface
US10140644B1 (en) 2013-10-10 2018-11-27 Go Daddy Operating Company, LLC System and method for grouping candidate domain names for display
US9953105B1 (en) 2014-10-01 2018-04-24 Go Daddy Operating Company, LLC System and method for creating subdomains or directories for a domain name
US9954818B2 (en) * 2014-10-23 2018-04-24 Go Daddy Operating Company, LLC Domain name hi-jack prevention
US9865011B2 (en) * 2015-01-07 2018-01-09 Go Daddy Operating Company, LLC Notifying registrants of domain name valuations
US10296506B2 (en) 2015-01-07 2019-05-21 Go Daddy Operating Company, LLC Notifying users of available searched domain names
US9972041B2 (en) 2015-02-18 2018-05-15 Go Daddy Operating Company, LLC Earmarking a short list of favorite domain names or searches
NO341393B1 (en) * 2015-05-28 2017-10-30 Innovar Eng As Apparatus and method for attaching a cable to a pipe body

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5794207A (en) * 1996-09-04 1998-08-11 Walker Asset Management Limited Partnership Method and apparatus for a cryptographically assisted commercial network system designed to facilitate buyer-driven conditional purchase offers
US5872850A (en) * 1996-02-02 1999-02-16 Microsoft Corporation System for enabling information marketplace
US6298342B1 (en) * 1998-03-16 2001-10-02 Microsoft Corporation Electronic database operations for perspective transformations on relational tables using pivot and unpivot columns
US20010047343A1 (en) * 2000-03-03 2001-11-29 Dun And Bradstreet, Inc. Facilitating a transaction in electronic commerce
US20020016769A1 (en) * 2000-07-11 2002-02-07 Ellen Barbara Method and system for on-line payments

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6338082B1 (en) * 1999-03-22 2002-01-08 Eric Schneider Method, product, and apparatus for requesting a network resource

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5872850A (en) * 1996-02-02 1999-02-16 Microsoft Corporation System for enabling information marketplace
US5794207A (en) * 1996-09-04 1998-08-11 Walker Asset Management Limited Partnership Method and apparatus for a cryptographically assisted commercial network system designed to facilitate buyer-driven conditional purchase offers
US6298342B1 (en) * 1998-03-16 2001-10-02 Microsoft Corporation Electronic database operations for perspective transformations on relational tables using pivot and unpivot columns
US20010047343A1 (en) * 2000-03-03 2001-11-29 Dun And Bradstreet, Inc. Facilitating a transaction in electronic commerce
US20020016769A1 (en) * 2000-07-11 2002-02-07 Ellen Barbara Method and system for on-line payments

Also Published As

Publication number Publication date
AU2011202381A1 (en) 2011-06-09
AU2005250809A1 (en) 2005-12-15
WO2005119501A3 (en) 2007-12-06
CA2568172A1 (en) 2005-12-15
EP1782252A2 (en) 2007-05-09
EP1782252A4 (en) 2009-03-25
WO2005119501A2 (en) 2005-12-15
US20060004784A1 (en) 2006-01-05
US8706585B2 (en) 2014-04-22

Similar Documents

Publication Publication Date Title
US8706585B2 (en) Certified offer service for domain names
US11301855B2 (en) Data verification in transactions in distributed network
US7865428B2 (en) Computer-implemented method and system for managing accounting and billing of transactions over public media such as the internet
JP4871358B2 (en) Method and system for improving the security of financial transactions through a trusted third party
US20050222954A1 (en) Multi-factor algorithm for facilitating electronic payments to payees
WO2001007873A2 (en) A method for performing a transaction over a network
US8527474B2 (en) Acquirer device and method for support of merchant data processing
CA2426168A1 (en) Method and apparatus for evaluating fraud risk in an electronic commerce transaction
AU2005201681A1 (en) Method and apparatus for conducting commerce between individuals
KR20010034629A (en) A method for using a telephone calling card for business transactions
JP2003016295A (en) Method, system and program for online shopping
US11170378B2 (en) Methods for payment and merchant systems
US20040022380A1 (en) Method and system to validate payment method
US20100077464A1 (en) Merchant device and method for support of merchant data processing
WO2001031483A2 (en) A system and method for verifying on-line information presented by internet users
US7650304B1 (en) Solicitation to web marketing loop process
JP5001481B2 (en) Auction system and method using network
US20020087411A1 (en) Expected value methods ans systems for paying and qualifying
WO2001001299A1 (en) Method and system for providing financial services
US11797997B2 (en) Data verification in transactions in distributed network
AU2007202567B2 (en) Charitable giving
EP1234261A2 (en) Expected value methods and systems for paying and qualifying
KR20040032024A (en) Buying and Exchanging System and Method by An Exchanging Gift-ticket
AU5203100A (en) Method and system for providing financial services
JP2002222376A (en) System and method for settling small amount of online electronic credit, and program recording medium for the system

Legal Events

Date Code Title Description
AS Assignment

Owner name: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT

Free format text: SECURITY INTEREST;ASSIGNOR:NETWORK SOLUTIONS, LLC;REEL/FRAME:034060/0945

Effective date: 20140909

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: NETWORK SOLUTIONS, LLC, FLORIDA

Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (034060/0945);ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:047785/0618

Effective date: 20181011