WO2000057298A2 - Apparatus and method for providing a business card web page - Google Patents

Apparatus and method for providing a business card web page Download PDF

Info

Publication number
WO2000057298A2
WO2000057298A2 PCT/US2000/040073 US0040073W WO0057298A2 WO 2000057298 A2 WO2000057298 A2 WO 2000057298A2 US 0040073 W US0040073 W US 0040073W WO 0057298 A2 WO0057298 A2 WO 0057298A2
Authority
WO
WIPO (PCT)
Prior art keywords
web page
domain name
web
customer
link
Prior art date
Application number
PCT/US2000/040073
Other languages
French (fr)
Other versions
WO2000057298A3 (en
Inventor
Vincent M. Lee
Peter Toscano
Ben Turner
Original Assignee
Network Solutions, Inc
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, Inc filed Critical Network Solutions, Inc
Priority to AU47148/00A priority Critical patent/AU4714800A/en
Publication of WO2000057298A2 publication Critical patent/WO2000057298A2/en
Publication of WO2000057298A3 publication Critical patent/WO2000057298A3/en

Links

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
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/955Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • G06F16/9566URL specific, e.g. using aliases, detecting broken or misspelled links
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/957Browsing optimisation, e.g. caching or content distillation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/30Managing network names, e.g. use of aliases or nicknames
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/30Managing network names, e.g. use of aliases or nicknames
    • H04L61/3015Name registration, generation or assignment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/45Network directories; Name-to-address mapping
    • H04L61/4505Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols

Definitions

  • the present invention relates to the field of domain name registration. More particularly, the invention relates to an apparatus and method for providing a single page customizable web site. BACKGROUND OF THE INVENTION
  • the World Wide Web allows for the access of information on the Internet by permitting a user to navigate Internet resources without Internet Protocol (IP) addresses or other technical knowledge.
  • IP Internet Protocol
  • the Web does away with command-line utilities, which typically require a user to transmit sets of commands to communicate with an Internet server. Instead, the Web is made up of thousands of interconnected web sites.
  • a user In order to access a web site, a user utilizes a uniform resource locator (URL) or domain name associated with the site.
  • URL uniform resource locator
  • domain name associated with the site. Because there are so many web sites in existence today and the number of web sites is always increasing, a domain name must first be registered with a domain name registration service. In that manner, it can be ensured that two web sites owned by two different people will not have the same domain name.
  • a domain name registration service is responsible for accepting a request for a domain name from an individual or a corporation and determining whether or not the domain name is already in use by somebody else. If the domain name is already taken, then the requester must choose a different domain name. If the domain name is available, then the requester is allowed to exclusively use the name and have it registered and stored in a database that maintains all of the domain names currently registered with that domain name registration service. Domain name registration services are a great convenience in that they allow individuals and corporations to exclusively use domain names without having to create the web site behind the domain name or to have any web presence at all. On the other hand, the time and expense required to launch a web site may be large.
  • a method consistent with the present invention provides a web page in a network.
  • the method includes the steps of receiving a request for registering a domain name, determining whether the request associates a web page with the domain name, storing information indicating association of the web page with the domain name, and sending the stored information to a web server hosting the web page.
  • Another method consistent with the present invention provides a web page in a network.
  • the method includes the steps of: displaying a list of one or more domain names, each having an associated link for purchasing a web page or an associated link for managing the web page; storing information indicating that a web page is associated with a selected domain name based on a determination that a link is selected for purchasing the associated web page; and directing a customer to a web page for editing the associated web page based on a determination that a link is selected for managing the associated web page.
  • Another method consistent with the present invention provides a web page in a network.
  • the method includes the steps of: displaying a list of one or more domain names, each having an associated link for purchasing a web page or an associated link for managing the web page; and storing information indicating that a web page is associated with a selected domain name based on a determination that a link is selected for purchasing the associated web page.
  • Another method consistent with the present invention provides a web page in a network.
  • the method includes the steps of: displaying a list of one or more domain names, each having an associated link for purchasing a web page or an associated link for managing the web page; and directing a customer to a web page for editing a web page associated with the selected domain name based on a determination that a link is selected for managing the associated web page.
  • Another method consistent with the present invention provides a web site in a network.
  • the method includes the steps of receiving a request for registering a domain name, determining whether the request associates a web site with the domain name, storing information indicating association of the web site with the domain name, and sending the stored information to a web server hosting the web site.
  • Another method consistent with the present invention provides a web site in a network.
  • the method includes the steps of: displaying a list of one or more domain names, each having an associated link for purchasing a web site or an associated link for managing the web site; storing information indicating that a web site is associated with a selected domain name based on a determination that a link is selected for purchasing the associated web site; and directing a customer to a web page for editing the associated web site based on a determination that a link is selected for managing the associated web site.
  • Another method consistent with the present invention provides a web page in a network.
  • the method includes the steps of receiving a request for registering a domain name, determining whether the request associates a web page with the domain name, and storing information indicating association of the web page with the domain name.
  • An apparatus consistent with the present invention provides a web page in a network.
  • the apparatus includes: a memory having program instructions; and a processor responsive to the program instructions to receive a request for registering a domain name, determine whether the request associates a web page with the domain name, store information indicating association of the web page with the domain name, and send the stored information to a web server hosting the web page.
  • the apparatus includes a memory having program instructions and a processor responsive to the program instructions for: displaying a list of one or more domain names, each having an associated link for purchasing a web page or an associated link for managing the web page; storing information indicating that a web page is associated with a selected domain name based on a determination that a link is selected for purchasing the associated web page; and directing a customer to a web page for editing the associated web page based on a determination that a link is selected for managing the associated web page.
  • FIG. 1 is a diagram of an exemplary network environment in which a method and system consistent with the present invention may be implemented
  • FIG. 2 is a diagram of an another exemplary network environment in which a method and system consistent with the present invention may be implemented;
  • FIG. 3 is an exemplary flowchart of a process for acquiring a business card through the domain name purchase flow in a manner consistent with the present invention.
  • FIG. 4 is an exemplary flowchart of a process for acquiring or editing a business card through the account management flow in a manner consistent with the present invention.
  • the apparatus and method of the present invention provides customers whose domain names are hosted by a domain name registration service the option of selecting the appearance of the web sites associated with the domain names.
  • customers may choose to have the web site of their newly registered or previously existing domain names switched from a default "Under Construction" page to a customizable web page or vice versa.
  • customers may choose to have their domain names forwarded to a web site not associated with the customizable web page.
  • customers may have the web site of their newly registered or previously existing domain names switched to a customizable web site, which may include one or more web pages.
  • FIG. 1 is a diagram of an exemplary network environment 100 in which a method consistent with the present invention may be implemented.
  • a single domain name registration system 105 such as the one owned by Network Solutions, Inc., includes registration web server 106, customer server 108, firewall 116, customer database 110, zone file 111, billing server 112, billing database
  • Customer 102 may include, for example, a personal computer of an individual or corporation that may want to register a domain name with a domain name registration system. Customer 102 may access the domain name registration system 105 through the system's registration web server 106. Registration web server 106 hosts the system's web page and is utilized by customer 102 to purchase or manage the various options that are associated with a domain name registration system account. For example, using the various web pages available on registration web server 106, customer 102 may sign up for an account, reserve or register a domain name, buy the web forwarding option, configure the web forwarding option (e.g., determine where a given web address will forward), buy electronic mail (e-mail) service, buy a single page business card, contact a customer service representation, etc.
  • e-mail electronic mail
  • the web forwarding option for example, forwards a web address hosted by a domain name registration system to a pre-existing URL
  • the e-mail service for example, matches a customer's e-mail address with a given domain name so that e-mail can be sent and received using a desired name (e.g , a company name) instead of the name of, for example, an e-mail vendor
  • the single page business card for example, forwards a web address to a single page web site designed by customer 102
  • Registration web server 106 provides two ways to purchase the single page business card option The first is through a process for purchasing a new domain name The second is through a process for managing existing domain name accounts
  • the term "single page business card" herein broadly refers to a web page or a web site
  • Registration web server 106 may be implemented, for example, using a SunServer machine available from Sun Microsystems running web server software, such as Apache Stronghold The web server software communicates with an account manager program that is also resident on registration web server 106 using a protocol, such as Java servlet In one embodiment, more than one registration web server 106 may be utilized by domain name registration system 105
  • Registration web server 106 communicates with customer server 108 through firewall 116 Data transferred between registration web server 106 and customer server 108 may be transferred according to the Visibroker Common Object Broker Architecture (COBRA) protocol created by Visigenic Customer server 108 receives customer data from registration web server 106, processes this data, and stores this data in customer database 110, if need be For example, customer server 108 may receive data indicative of a customer purchasing the single page business card option
  • COBRA Visibroker Common Object Broker Architecture
  • customer server 108 receives and processes customer data corresponding to the initial registration of a domain name by a customer, as well as data corresponding to the other options available at registration web server 106
  • Customer server 108 may be implemented, for example, using a SunServer machine available from Sun Microsystems running Solaris 2.5.1 or 2.6. In one embodiment, more than one customer server 108 may be utilized by domain name registration system 105.
  • Customer database 110 stores customer data that corresponds to the accounts of each customer using domain name registration system 105. This data may be stored in the form of one or more zone files 111. Customer database 110 stores the zone file 111 which contains data describing a portion of the domain name space for each domain name that is hosted by domain name registration system 105. For example, for a given domain name, there may be a zone file 111 that contains records relevant to the single page business card option or other options available to customer 102. Zone files generally contain the information needed to resolve domain names in Internet Protocol (IP) numbers. Alternatively, zone files may be stored in a database other than customer database 110. In that case, customer data corresponding to accounts may be stored in both customer database 110 and the zone file database.
  • IP Internet Protocol
  • customer database 110 may be an Oracle database that uses Oracle 8.0 database management system. Oracle 8.0 may also be used as the communication protocol between customer server 108 and customer database 110.
  • customer server 108 and customer database 110 are shown to be separate machines. Alternatively, customer server 108 and customer database 110 may be implemented on the same machine.
  • Billing server 112 may implement a process that handles all customer payments for registering domain names and other available services or options such as the single page business card option.
  • Billing server 112 receives an indication as to what service or option is being purchased by customer 102 and causes the indication to be stored in billing database 114 along with a price for the service or option being purchased.
  • billing database 114 stores the indication and the price in a table associated with customer 102.
  • Business card web server 122 hosts tools that allow customers of domain name registration system 105, such as customer 102, to set up and maintain their electronic business cards. For example, business card web server 122 may allow customer 102 to create a new single page business card, edit an existing single page business card, preview a single page business card, and disable the single page business card. Registration web server 106 directs customers to business card web server 122, where the tools may be used to manage a single page business card. Business card web server 122 subsequently stores the business card in business card database 124, which stores all of the business cards corresponding to domain names hosted by domain name registration system 105. Alternatively, business card web server 122 and business card database 124 may be part of domain name registration system 105 instead of remotely located.
  • User 120 may be a web surfer who enters a web address (e.g., domain name) that is hosted by domain name registration system 105. If domain name registration system 105 determines that the web address has the business card option by checking a record associated with the web address, then user 120 is directed to business card web server 122. The web browser used by user 120 may then send a query to business card web server 122 based on the web address.
  • Business card web server 122 searches business card database 124 for a business card that corresponds to the web address based on the query. If a business card is enabled for the web address, the business card is displayed as the web page for that web address. If no business card is enabled for the web address, a default "Under Construction" page may be displayed.
  • a user 120 who enters a web address hosted by domain name registration system 105 may be directed to business card web server 122 without first checking a record associated with the web address.
  • business card web server 122 may search business card database 124 for a business card and display an appropriate web page as previously explained.
  • Rectification unit 118 ensures that data stored at business card database 124 properly reflects data relating to business cards stored at customer database 110 by periodically checking for discrepancies between the databases. For example, rectification unit 118 may nightly extract data indicative of the previous day's log of transactions involving business cards from customer database 110. Rectification unit 118 may then sort the data in a predetermined manner and forward the sorted data to business card web server 122, where a comparison is made between the log data and corresponding data stored at business card database 124. If a discrepancy is detected, rectification unit 118 or business card web server 122 causes a correction of the data stored at business card database 124.
  • FIG. 2 is a diagram of an exemplary network environment 200 in which a method consistent with the present invention may be implemented.
  • FIG. 2 is the same as FIG. 1 except there is no rectification unit 118 in network environment 200, which may include customer 202, Internet 204, domain name registration service 205, business card web server 218, business card database 220, and user 222.
  • Domain name registration service 205 may include registration web server 206, firewall 216, customer server 208, customer database 210, zone file 211, billing server 212, and billing database 220.
  • FIG. 3 shows an exemplary flowchart of a process for acquiring a business card through the domain name purchase flow in a manner consistent with the present invention.
  • customer 102 accesses a web page of domain name registration system 105. Access can be gained, for example, by using a web browser to access the page.
  • the web page is essentially a unified interface for many of the features available from the domain name registration system 105 and is resident on registration web server 106.
  • the web page enables customer 102 to do business with domain name registration system 105 by accessing from a single web page the various features of domain name registration system 105.
  • the unified interface could be presented to customer 102 in the form of more than one web page.
  • customer 102 accesses the web page, customer 102 is presented with several features provided by domain name registration system 105. Customer 102 must then choose one of the features, which may include, for example, a whois feature, a register web address feature, an account management feature, and an email feature
  • customer 102 enters the desired domain name in a box on the unified interface web page resident on registration web server 106 (step 302).
  • registration web server 106 Upon receiving the domain name, registration web server 106 initiates a query to check for domain availability
  • step 304 The query provides a search in customer database 110 or another database (e.g., a whois database) for an entry with the entered domain name. If such an entry is found, then the domain name is not available. If no such entry is found, then the domain name is available. If the query results in the determination that the desired domain name is not available, then registration web server 106 informs customer 102 that the domain name is not available and shows the customer some possible alternatives to the domain name initially selected. For example, if customer 102 desires to register a domain name ofmydomain.com," but the domain name is not available, the registration web server 106 makes a determination as to whether or not "mydomain.net" or "mydomain.org" are available.
  • registration web server 106 informs the customer of the available alternatives. Note that other top-level domains in addition to “.com,” “.net,” and “.org” may be searched for both initially and as alternatives.
  • the registration web server 106 may direct customer 102 to enter or select another domain name after showing customer 102 the alternatives.
  • registration web server 106 informs customer 102 that the domain name is available and may show customer 102 some possible alternatives in addition to the domain name initially selected. For example, if customer 102 desires to book a domain name ofmydomain.com," and the domain name is available, registration web server
  • 106 may also make a determination as to whether or not "mydomain.net” or “mydomain.org” are available.
  • customer 102 In the case that customer 102 is an existing customer, customer 102 enters a username and a password, resulting in the prepopulation of the form customer 102 must complete to register a domain name (step 306).
  • Information that may be prepopulated into the form may include, for example, account holder information, contact information, and account password information.
  • Account holder and contact information may both include information, such as name, street address, state, e-mail address, phone number, etc.
  • Account password information may include information, such as the customer's password and a question to the customer in case an incorrect password is entered.
  • customer 102 may enter the aforementioned information (step 306). After customer 102 fills in the form, or after domain name registration system 105 prepopulates the form, customer 102 may still have to complete a portion of the form (step 308). For example, domain name registration system 105 may make certain options available to a customer that chooses to have domain name registration system 105 host the customer's domain name. Customer 102 designates whether or not those options are desired. For example, domain name registration system 105 may ask customer 102 whether the display for a domain name should be a default "Under Construction" page or a single page business card.
  • customer 102 submits the completed form to registration web server 106 by clicking on a button on the form web page (step 310). Subsequently, registration web server 106 sends the completed form to customer server 108 through firewall 116.
  • Customer server 108 examines the completed form containing the registration and option information to determine whether or not the business card option has been selected for the domain name that is being registered (step 312). If the business card option has not been selected for the domain name that is being registered, domain name registration proceeds normally (step 314). For example, upon determining that registration should proceed normally, customer server 108 may invoke a process that stores the registration information of the completed form in customer database 110. This storage may occur after customer server 108 checks customer database 110 for existing entries in customer database 110 with the desired domain name.
  • Customer server 108 also sends billing server 112 an indication that a domain name is being purchased by customer 102.
  • Billing server 112 stores data indicative of the cost of the domain name in billing database 114. If customer server 108 determines that the business card option has been selected for the domain name that is being registered, a slightly different domain name registration may occur (step 316). For example, customer server 108 may invoke a process that stores the registration information of the completed form in customer database 110 after checking for existing entries in customer database 110 with the desired domain name. In addition to the registration information, customer server 108 causes an indication to be stored in customer database 110 that a business card is being purchased for the domain name.
  • the indication may be a record, such as a cname record in a zone file created for the domain name in customer database 110 and/or a separate zone file database.
  • This record may include location information for the single page business card, such as the web address of business card web server 122.
  • the indication may be a flag or other simple indicator stored in customer database 110 separate from a zone file.
  • Customer server 108 also sends billing server 112 an indication that a domain name and business card are being purchased by customer 102. Billing server 112 then stores data indicative of the cost of the domain name and business card in billing database 114.
  • customer server 108 may proceed to send business card web server 122 a notification that the domain name purchased by customer 102 may access the tools resident on business card web server 122 for setting up or editing business cards (step 318).
  • business card web server 122 creates an entry in business card database 124 that corresponds to the purchased domain name.
  • customer server 108 may not send a notification to business card web server 122. In that case, a customer's access to a web page resident on business card web server 122 through a link, such as an edit business card link, may serve as the notification.
  • Customer server 108 also indicates to registration web server 106 that domain name purchase and business card purchase have been successfully completed. Registration web server 106 then informs customer 102 that the purchase was successful and that the business card may be set up or edited through a link provided on the account management page A link to the account management page may also be provided to customer 102
  • FIG 4 is an exemplary flowchart of a process for acquiring or editing a business card through the account management flow in a manner consistent with the present invention
  • the account management flow begins when a customer, such as customer 102, accesses an account management login page (step 402) Customer 102 must then log into the system (e g , provide authentication) by entering an account number and password Account numbers and passwords may generally be provided to customers upon registration of domain names
  • An account manager program resident on registration web server 106 determines whether or not the authentication is successful If the authentication is not successful, then customer 102 is prompted that authentication is invalid and is given another chance to enter the relevant information If authentication is successful, then registration web server 106 directs customer 102 to a web page that displays the account information (step 404)
  • the account information page makes several choices available to customer 102 These choices may include purchasing an e-mail option so that a customer can receive email that may be relevant to the customer's account, contacting an administrator of the domain name registration system 105 via email, purchasing or configuring a web forward
  • the account information page also includes general information relevant to the customer presently accessing the page (e g , customer 102) This information may include, for example, customer name, street address, phone number, fax number, e- mail address, etc
  • registration web server 106 directs customer 102 to a web page that allows customer 102 to choose what is presented to a user when the user accesses a web site of customer 102
  • registration web server 106 may also direct customer 102 to the aforementioned web page when customer 102 opts to purchase or configure web forwarding
  • the web page may display a list of one or more domain names owned by customer 102 (step 406) Each domain name on the list may have a corresponding buy business card link or edit business card link, along with an indication as to whether web forwarding has been activated for the domain name
  • a buy business card link may be displayed with a domain name in cases where customer 102 has not yet purchased a business card for the domain name
  • An edit business card link may be displayed with a domain name
  • the indication as to whether web forwarding has been activated for a domain name may be associated with each domain name on the list
  • the indication may be a box that is clicked on or off
  • each domain name on the list may have an associated space, where a web forwarding address may be entered
  • the web page may display data associated with each domain name, informing customer 102 whether a default web page, single page business card, or a web forwarding web site is active
  • registration web server 106 determines whether or not customer 102 has selected (e g , clicked on) a buy business card link associated with a domain name (step 408) If customer 102 has clicked on a buy business card link, then registration web server 106 immediately causes customer server 106 to store an indication that a business card is being purchased for the domain name in customer database 110 and billing database 114 (step 410)
  • the indication may be a record, such as a cname record in a zone file created for the domain name in customer database 110 and/or a separate zone file database This record may include location information for the single page business card, such as the web address of business card web server 122 Alternatively, the indication may be a flag or other simple indicator stored in customer database 110 separate from a zone file After the indicator has been stored, registration web server 106 redisplays the web page with the list of domain names such that the domain name has an associated edit business card link
  • registration web server 106 determines whether customer 102 clicks on an edit business card link
  • step 412 If customer 102 clicks on an edit business card link, registration web server 106 directs customer 106 to a web page resident on business card web server 122 (step 414).
  • the edit business card link opens a Secure Socket Layer (SSL) connection from a web browser used by customer 102 to the web page resident on business card web server 122.
  • SSL Secure Socket Layer
  • Using a SSL connection reduces the possibility of impersonation or unauthorized access to data.
  • registration web server 106 establishes communication with business card web server 122 by utilizing a URL that includes the web address of the aforementioned web page resident on business card web server 122 and certain parameters that are sent to business card web server 122. These parameters may include the domain name, supplement information, signature value, and a return URL.
  • Supplement information may include any miscellaneous data that may be useful.
  • Signature value may be used to validate the data and the origins of the connection to business card web server 122 thereby making sure that the data comes from domain name registration system 105.
  • the signature value may be the hex output of an MD5 hash generated by applying the MD5 algorithm to a string of values.
  • Return URL is the URL that business card web server 122 uses to return customer 102 directly back to the appropriate web page at registration web server 106.
  • customer 102 may manage a business card for the selected domain name in a manner selected by customer 102.
  • This web page includes various tools that customer 102 may utilize to manage a business card.
  • the page may provide tools that allow customer 102 to create a new business card, edit an existing business card, preview a business card, publish a business card, and disable a business card.
  • Creating a new business card or editing an existing business card may involve selecting a business card template, selecting a background color for the business card, selecting font, selecting effects, etc.
  • Previewing a business card allows customer 102 to view the business card as displayed to a user when the user accesses the web address (e.g., domain name) associated with the business card.
  • a business card uploads the business card created by customer 102 making it available to the public at the domain name associated with the business card.
  • Disabling a business card allows customer 102 to turn off the business card associated with the domain name such that a default "Under Construction" page is displayed when a user accesses the domain name Disablement does not delete the business card from business card database 124 so that customer 102 may go back and enable the business card at a later date if desired
  • customer 102 may click on a link provided by the web page resident on business card web server 122 The link directs customer 102 back to the account information web page resident on registration web server 106 using the return URL provided by registration web server 106 so that customer 102 does not have to enter account login information again
  • business card web server 122 may send an indication as to whether a business card is enabled or disabled back to registration web server 106 so that the appropriate indicator may be displayed with the list of domain names
  • registration web server 106 determines that customer 102 has not clicked on a buy business card link or an edit business card link, a determination is made as to whether customer 102 chooses the web forwarding option for a domain name (step
  • Customer 102 may choose the web forwarding option for a domain name by, for example, clicking a web forwarding status box that is associated with the domain name
  • any conflicting business card is disabled (step 420)
  • a business card is conflicting when the business card is enabled for a domain name and the web forwarding option is subsequently chosen for the domain name without first disabling the business card
  • a business card may be disabled, for example, by sending business card web server 122 an indication that the business card for the domain name should be disabled
  • Web forwarding may be set up in a manner consistent with that described m U S Application No 09/500,639, entitled “Apparatus and Method for Web Forwarding," filed February 9, 2000, Attorney Docket No 06978- 0097-00000 After web forwarding has been set up, the web page that displays the list of domain names is refreshed to indicate the new status of the domain names While the present invention has been described in connection with a preferred embodiment, many modifications will be readily apparent to those skilled in the art, and this application is intended to cover any adaptations or variations thereof. For example, the present invention may be utilized for business cards that have multiple web pages as opposed to a single web page.

Abstract

An apparatus and method for providing a single page web site is presented. A list of one or more domain names is displayed. Each domain name has either an associated link for purchasing a web page or an associated link for managing the web page. Information is stored indicating that a web page is associated with a selected domain name based on a determination that a link is selected for purchasing the associated web page. If a link is selected for managing the associated web page, then a customer is directed to a web page or web site for editing the associated web page.

Description

DOT COM BUSINESS CARD RELATED APPLICATION
This application claims the benefit of U.S. Provisional Application No. 60/125,107, filed March 19, 1999, the disclosure of which is expressly incorporated herein by reference in its entirety.
FIELD OF THE INVENTION The present invention relates to the field of domain name registration. More particularly, the invention relates to an apparatus and method for providing a single page customizable web site. BACKGROUND OF THE INVENTION
The World Wide Web allows for the access of information on the Internet by permitting a user to navigate Internet resources without Internet Protocol (IP) addresses or other technical knowledge. The Web does away with command-line utilities, which typically require a user to transmit sets of commands to communicate with an Internet server. Instead, the Web is made up of thousands of interconnected web sites.
In order to access a web site, a user utilizes a uniform resource locator (URL) or domain name associated with the site. Because there are so many web sites in existence today and the number of web sites is always increasing, a domain name must first be registered with a domain name registration service. In that manner, it can be ensured that two web sites owned by two different people will not have the same domain name.
A domain name registration service is responsible for accepting a request for a domain name from an individual or a corporation and determining whether or not the domain name is already in use by somebody else. If the domain name is already taken, then the requester must choose a different domain name. If the domain name is available, then the requester is allowed to exclusively use the name and have it registered and stored in a database that maintains all of the domain names currently registered with that domain name registration service. Domain name registration services are a great convenience in that they allow individuals and corporations to exclusively use domain names without having to create the web site behind the domain name or to have any web presence at all. On the other hand, the time and expense required to launch a web site may be large. Because a domain name must be registered as soon as possible to ensure the use of that domain name, a gap in time often occurs when a customer has a registered domain name but does not yet have a web site associated with the domain name. In those situations, a user attempting to access a web site associated with the domain name may be presented with a generic web page, such as an "Under Construction" page, or may be informed that access has failed. With this result, the user learns nothing about the services, organizations, or individuals that may be associated with the domain name. Accordingly, there is presently a need for a system and method providing a customizable single page web site that gives a customer an instant online identity upon domain name registration.
SUMMARY OF THE INVENTION A method consistent with the present invention provides a web page in a network. The method includes the steps of receiving a request for registering a domain name, determining whether the request associates a web page with the domain name, storing information indicating association of the web page with the domain name, and sending the stored information to a web server hosting the web page.
Another method consistent with the present invention provides a web page in a network. The method includes the steps of: displaying a list of one or more domain names, each having an associated link for purchasing a web page or an associated link for managing the web page; storing information indicating that a web page is associated with a selected domain name based on a determination that a link is selected for purchasing the associated web page; and directing a customer to a web page for editing the associated web page based on a determination that a link is selected for managing the associated web page.
Another method consistent with the present invention provides a web page in a network. The method includes the steps of: displaying a list of one or more domain names, each having an associated link for purchasing a web page or an associated link for managing the web page; and storing information indicating that a web page is associated with a selected domain name based on a determination that a link is selected for purchasing the associated web page.
Another method consistent with the present invention provides a web page in a network. The method includes the steps of: displaying a list of one or more domain names, each having an associated link for purchasing a web page or an associated link for managing the web page; and directing a customer to a web page for editing a web page associated with the selected domain name based on a determination that a link is selected for managing the associated web page.
Another method consistent with the present invention provides a web site in a network. The method includes the steps of receiving a request for registering a domain name, determining whether the request associates a web site with the domain name, storing information indicating association of the web site with the domain name, and sending the stored information to a web server hosting the web site.
Another method consistent with the present invention provides a web site in a network. The method includes the steps of: displaying a list of one or more domain names, each having an associated link for purchasing a web site or an associated link for managing the web site; storing information indicating that a web site is associated with a selected domain name based on a determination that a link is selected for purchasing the associated web site; and directing a customer to a web page for editing the associated web site based on a determination that a link is selected for managing the associated web site.
Another method consistent with the present invention provides a web page in a network. The method includes the steps of receiving a request for registering a domain name, determining whether the request associates a web page with the domain name, and storing information indicating association of the web page with the domain name.
An apparatus consistent with the present invention provides a web page in a network. The apparatus includes: a memory having program instructions; and a processor responsive to the program instructions to receive a request for registering a domain name, determine whether the request associates a web page with the domain name, store information indicating association of the web page with the domain name, and send the stored information to a web server hosting the web page.
Another apparatus consistent with the present invention provides a web page in a network. The apparatus includes a memory having program instructions and a processor responsive to the program instructions for: displaying a list of one or more domain names, each having an associated link for purchasing a web page or an associated link for managing the web page; storing information indicating that a web page is associated with a selected domain name based on a determination that a link is selected for purchasing the associated web page; and directing a customer to a web page for editing the associated web page based on a determination that a link is selected for managing the associated web page.
BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings are incorporated in and constitute a part of this specification and, together with the description, explain the advantages and principles of the invention. In the drawings,
FIG. 1 is a diagram of an exemplary network environment in which a method and system consistent with the present invention may be implemented;
FIG. 2 is a diagram of an another exemplary network environment in which a method and system consistent with the present invention may be implemented; FIG. 3 is an exemplary flowchart of a process for acquiring a business card through the domain name purchase flow in a manner consistent with the present invention; and
FIG. 4 is an exemplary flowchart of a process for acquiring or editing a business card through the account management flow in a manner consistent with the present invention.
DETAILED DESCRIPTION The following detailed description of the invention refers to the accompanying drawings. While the description includes exemplary embodiments, other embodiments are possible, and changes may be made to the embodiments described without departing from the spirit and scope of the invention. The following detailed description does not limit the invention. Instead, the scope of the invention is defined by the appended claims and their equivalents.
Overview The apparatus and method of the present invention provides customers whose domain names are hosted by a domain name registration service the option of selecting the appearance of the web sites associated with the domain names. In accordance with an embodiment consistent with the present invention, customers may choose to have the web site of their newly registered or previously existing domain names switched from a default "Under Construction" page to a customizable web page or vice versa. Alternatively, customers may choose to have their domain names forwarded to a web site not associated with the customizable web page.
In another embodiment, customers may have the web site of their newly registered or previously existing domain names switched to a customizable web site, which may include one or more web pages. System Architecture
FIG. 1 is a diagram of an exemplary network environment 100 in which a method consistent with the present invention may be implemented. In the embodiment of FIG. 1, a single domain name registration system 105, such as the one owned by Network Solutions, Inc., includes registration web server 106, customer server 108, firewall 116, customer database 110, zone file 111, billing server 112, billing database
114, and rectification unit 118.
Customer 102 may include, for example, a personal computer of an individual or corporation that may want to register a domain name with a domain name registration system. Customer 102 may access the domain name registration system 105 through the system's registration web server 106. Registration web server 106 hosts the system's web page and is utilized by customer 102 to purchase or manage the various options that are associated with a domain name registration system account. For example, using the various web pages available on registration web server 106, customer 102 may sign up for an account, reserve or register a domain name, buy the web forwarding option, configure the web forwarding option (e.g., determine where a given web address will forward), buy electronic mail (e-mail) service, buy a single page business card, contact a customer service representation, etc
The web forwarding option, for example, forwards a web address hosted by a domain name registration system to a pre-existing URL The e-mail service, for example, matches a customer's e-mail address with a given domain name so that e-mail can be sent and received using a desired name (e.g , a company name) instead of the name of, for example, an e-mail vendor The single page business card, for example, forwards a web address to a single page web site designed by customer 102 Registration web server 106 provides two ways to purchase the single page business card option The first is through a process for purchasing a new domain name The second is through a process for managing existing domain name accounts The term "single page business card" herein broadly refers to a web page or a web site
Registration web server 106 may be implemented, for example, using a SunServer machine available from Sun Microsystems running web server software, such as Apache Stronghold The web server software communicates with an account manager program that is also resident on registration web server 106 using a protocol, such as Java servlet In one embodiment, more than one registration web server 106 may be utilized by domain name registration system 105
Registration web server 106 communicates with customer server 108 through firewall 116 Data transferred between registration web server 106 and customer server 108 may be transferred according to the Visibroker Common Object Broker Architecture (COBRA) protocol created by Visigenic Customer server 108 receives customer data from registration web server 106, processes this data, and stores this data in customer database 110, if need be For example, customer server 108 may receive data indicative of a customer purchasing the single page business card option
Assuming that no errors occur in the processing of the data, the data can then be stored in customer database 110 In addition to data relevant to the single page business card option, customer server 108 receives and processes customer data corresponding to the initial registration of a domain name by a customer, as well as data corresponding to the other options available at registration web server 106
Customer server 108 may be implemented, for example, using a SunServer machine available from Sun Microsystems running Solaris 2.5.1 or 2.6. In one embodiment, more than one customer server 108 may be utilized by domain name registration system 105.
Customer database 110 stores customer data that corresponds to the accounts of each customer using domain name registration system 105. This data may be stored in the form of one or more zone files 111. Customer database 110 stores the zone file 111 which contains data describing a portion of the domain name space for each domain name that is hosted by domain name registration system 105. For example, for a given domain name, there may be a zone file 111 that contains records relevant to the single page business card option or other options available to customer 102. Zone files generally contain the information needed to resolve domain names in Internet Protocol (IP) numbers. Alternatively, zone files may be stored in a database other than customer database 110. In that case, customer data corresponding to accounts may be stored in both customer database 110 and the zone file database. In one embodiment, customer database 110 may be an Oracle database that uses Oracle 8.0 database management system. Oracle 8.0 may also be used as the communication protocol between customer server 108 and customer database 110. In the embodiment shown in FIG. 1, customer server 108 and customer database 110 are shown to be separate machines. Alternatively, customer server 108 and customer database 110 may be implemented on the same machine.
Billing server 112 may implement a process that handles all customer payments for registering domain names and other available services or options such as the single page business card option. Billing server 112 receives an indication as to what service or option is being purchased by customer 102 and causes the indication to be stored in billing database 114 along with a price for the service or option being purchased. In one embodiment, billing database 114 stores the indication and the price in a table associated with customer 102.
Business card web server 122 hosts tools that allow customers of domain name registration system 105, such as customer 102, to set up and maintain their electronic business cards. For example, business card web server 122 may allow customer 102 to create a new single page business card, edit an existing single page business card, preview a single page business card, and disable the single page business card. Registration web server 106 directs customers to business card web server 122, where the tools may be used to manage a single page business card. Business card web server 122 subsequently stores the business card in business card database 124, which stores all of the business cards corresponding to domain names hosted by domain name registration system 105. Alternatively, business card web server 122 and business card database 124 may be part of domain name registration system 105 instead of remotely located.
User 120 may be a web surfer who enters a web address (e.g., domain name) that is hosted by domain name registration system 105. If domain name registration system 105 determines that the web address has the business card option by checking a record associated with the web address, then user 120 is directed to business card web server 122. The web browser used by user 120 may then send a query to business card web server 122 based on the web address. Business card web server 122 searches business card database 124 for a business card that corresponds to the web address based on the query. If a business card is enabled for the web address, the business card is displayed as the web page for that web address. If no business card is enabled for the web address, a default "Under Construction" page may be displayed.
Alternatively, a user 120 who enters a web address hosted by domain name registration system 105 may be directed to business card web server 122 without first checking a record associated with the web address. In that case, business card web server 122 may search business card database 124 for a business card and display an appropriate web page as previously explained.
Rectification unit 118 ensures that data stored at business card database 124 properly reflects data relating to business cards stored at customer database 110 by periodically checking for discrepancies between the databases. For example, rectification unit 118 may nightly extract data indicative of the previous day's log of transactions involving business cards from customer database 110. Rectification unit 118 may then sort the data in a predetermined manner and forward the sorted data to business card web server 122, where a comparison is made between the log data and corresponding data stored at business card database 124. If a discrepancy is detected, rectification unit 118 or business card web server 122 causes a correction of the data stored at business card database 124. In one embodiment, the periodic dumps of log data sent by rectification unit 118 to business card web server 122 may be encrypted using the standard UNIX crypt command. Alternatively, network environment 100 may be implemented without a rectification unit 118. FIG. 2 is a diagram of an exemplary network environment 200 in which a method consistent with the present invention may be implemented. FIG. 2 is the same as FIG. 1 except there is no rectification unit 118 in network environment 200, which may include customer 202, Internet 204, domain name registration service 205, business card web server 218, business card database 220, and user 222. Domain name registration service 205 may include registration web server 206, firewall 216, customer server 208, customer database 210, zone file 211, billing server 212, and billing database 220.
Business Card Purchase Flow As was previously mentioned with respect to FIG. 1, a customer (e.g., customer 102) who desires to choose the single page business card option of the present invention for domain names owned by the customer can do so by selecting the option during the initial purchase of a domain name. FIG. 3 shows an exemplary flowchart of a process for acquiring a business card through the domain name purchase flow in a manner consistent with the present invention.
Initially, customer 102 accesses a web page of domain name registration system 105. Access can be gained, for example, by using a web browser to access the page. The web page is essentially a unified interface for many of the features available from the domain name registration system 105 and is resident on registration web server 106. The web page enables customer 102 to do business with domain name registration system 105 by accessing from a single web page the various features of domain name registration system 105. Alternatively, the unified interface could be presented to customer 102 in the form of more than one web page.
Once customer 102 accesses the web page, customer 102 is presented with several features provided by domain name registration system 105. Customer 102 must then choose one of the features, which may include, for example, a whois feature, a register web address feature, an account management feature, and an email feature To initiate the register web address process (e.g., purchase domain name flow), customer 102 enters the desired domain name in a box on the unified interface web page resident on registration web server 106 (step 302). Upon receiving the domain name, registration web server 106 initiates a query to check for domain availability
(step 304). The query provides a search in customer database 110 or another database (e.g., a whois database) for an entry with the entered domain name. If such an entry is found, then the domain name is not available. If no such entry is found, then the domain name is available. If the query results in the determination that the desired domain name is not available, then registration web server 106 informs customer 102 that the domain name is not available and shows the customer some possible alternatives to the domain name initially selected. For example, if customer 102 desires to register a domain name ofmydomain.com," but the domain name is not available, the registration web server 106 makes a determination as to whether or not "mydomain.net" or "mydomain.org" are available. If either one of these domain names is available, then registration web server 106 informs the customer of the available alternatives. Note that other top-level domains in addition to ".com," ".net," and ".org" may be searched for both initially and as alternatives. The registration web server 106 may direct customer 102 to enter or select another domain name after showing customer 102 the alternatives.
If the query results in the determination that the desired domain name is available, then registration web server 106 informs customer 102 that the domain name is available and may show customer 102 some possible alternatives in addition to the domain name initially selected. For example, if customer 102 desires to book a domain name ofmydomain.com," and the domain name is available, registration web server
106 may also make a determination as to whether or not "mydomain.net" or "mydomain.org" are available.
In the case that customer 102 is an existing customer, customer 102 enters a username and a password, resulting in the prepopulation of the form customer 102 must complete to register a domain name (step 306). Information that may be prepopulated into the form may include, for example, account holder information, contact information, and account password information. Account holder and contact information may both include information, such as name, street address, state, e-mail address, phone number, etc. Account password information may include information, such as the customer's password and a question to the customer in case an incorrect password is entered.
If customer 102 is not an existing customer, customer 102 may enter the aforementioned information (step 306). After customer 102 fills in the form, or after domain name registration system 105 prepopulates the form, customer 102 may still have to complete a portion of the form (step 308). For example, domain name registration system 105 may make certain options available to a customer that chooses to have domain name registration system 105 host the customer's domain name. Customer 102 designates whether or not those options are desired. For example, domain name registration system 105 may ask customer 102 whether the display for a domain name should be a default "Under Construction" page or a single page business card.
After the form is completed, customer 102 submits the completed form to registration web server 106 by clicking on a button on the form web page (step 310). Subsequently, registration web server 106 sends the completed form to customer server 108 through firewall 116. Customer server 108 examines the completed form containing the registration and option information to determine whether or not the business card option has been selected for the domain name that is being registered (step 312). If the business card option has not been selected for the domain name that is being registered, domain name registration proceeds normally (step 314). For example, upon determining that registration should proceed normally, customer server 108 may invoke a process that stores the registration information of the completed form in customer database 110. This storage may occur after customer server 108 checks customer database 110 for existing entries in customer database 110 with the desired domain name. Customer server 108 also sends billing server 112 an indication that a domain name is being purchased by customer 102. Billing server 112 stores data indicative of the cost of the domain name in billing database 114. If customer server 108 determines that the business card option has been selected for the domain name that is being registered, a slightly different domain name registration may occur (step 316). For example, customer server 108 may invoke a process that stores the registration information of the completed form in customer database 110 after checking for existing entries in customer database 110 with the desired domain name. In addition to the registration information, customer server 108 causes an indication to be stored in customer database 110 that a business card is being purchased for the domain name. In one embodiment, the indication may be a record, such as a cname record in a zone file created for the domain name in customer database 110 and/or a separate zone file database. This record may include location information for the single page business card, such as the web address of business card web server 122. Alternatively, the indication may be a flag or other simple indicator stored in customer database 110 separate from a zone file. Customer server 108 also sends billing server 112 an indication that a domain name and business card are being purchased by customer 102. Billing server 112 then stores data indicative of the cost of the domain name and business card in billing database 114.
After the information has been successfully stored in customer database 110 and billing database 114, customer server 108 may proceed to send business card web server 122 a notification that the domain name purchased by customer 102 may access the tools resident on business card web server 122 for setting up or editing business cards (step 318). In response, business card web server 122 creates an entry in business card database 124 that corresponds to the purchased domain name. Alternatively, customer server 108 may not send a notification to business card web server 122. In that case, a customer's access to a web page resident on business card web server 122 through a link, such as an edit business card link, may serve as the notification.
Customer server 108 also indicates to registration web server 106 that domain name purchase and business card purchase have been successfully completed. Registration web server 106 then informs customer 102 that the purchase was successful and that the business card may be set up or edited through a link provided on the account management page A link to the account management page may also be provided to customer 102
Business Card Account Management Flow FIG 4 is an exemplary flowchart of a process for acquiring or editing a business card through the account management flow in a manner consistent with the present invention The account management flow begins when a customer, such as customer 102, accesses an account management login page (step 402) Customer 102 must then log into the system (e g , provide authentication) by entering an account number and password Account numbers and passwords may generally be provided to customers upon registration of domain names An account manager program resident on registration web server 106 then determines whether or not the authentication is successful If the authentication is not successful, then customer 102 is prompted that authentication is invalid and is given another chance to enter the relevant information If authentication is successful, then registration web server 106 directs customer 102 to a web page that displays the account information (step 404) The account information page makes several choices available to customer 102 These choices may include purchasing an e-mail option so that a customer can receive email that may be relevant to the customer's account, contacting an administrator of the domain name registration system 105 via email, purchasing or configuring a web forwarding option, and purchasing or managing a single page business card option
The account information page also includes general information relevant to the customer presently accessing the page (e g , customer 102) This information may include, for example, customer name, street address, phone number, fax number, e- mail address, etc If customer 102 opts to purchase or manage a single page business card, registration web server 106 directs customer 102 to a web page that allows customer 102 to choose what is presented to a user when the user accesses a web site of customer 102 Note that registration web server 106 may also direct customer 102 to the aforementioned web page when customer 102 opts to purchase or configure web forwarding The web page may display a list of one or more domain names owned by customer 102 (step 406) Each domain name on the list may have a corresponding buy business card link or edit business card link, along with an indication as to whether web forwarding has been activated for the domain name A buy business card link may be displayed with a domain name in cases where customer 102 has not yet purchased a business card for the domain name An edit business card link may be displayed with a domain name in cases where customer 102 has already purchased a business card for the domain name Buy business card links and edit business card links are mutually exclusive such that only one or the other may be displayed with a domain name.
The indication as to whether web forwarding has been activated for a domain name may be associated with each domain name on the list For example, the indication may be a box that is clicked on or off In addition, each domain name on the list may have an associated space, where a web forwarding address may be entered In an alternative embodiment, in addition to the business card links and web forwarding indication, the web page may display data associated with each domain name, informing customer 102 whether a default web page, single page business card, or a web forwarding web site is active
Next, registration web server 106 determines whether or not customer 102 has selected (e g , clicked on) a buy business card link associated with a domain name (step 408) If customer 102 has clicked on a buy business card link, then registration web server 106 immediately causes customer server 106 to store an indication that a business card is being purchased for the domain name in customer database 110 and billing database 114 (step 410) In one embodiment, the indication may be a record, such as a cname record in a zone file created for the domain name in customer database 110 and/or a separate zone file database This record may include location information for the single page business card, such as the web address of business card web server 122 Alternatively, the indication may be a flag or other simple indicator stored in customer database 110 separate from a zone file After the indicator has been stored, registration web server 106 redisplays the web page with the list of domain names such that the domain name has an associated edit business card link
If customer 102 has not clicked on a buy business card link, then registration web server 106 determines whether customer 102 clicks on an edit business card link
(step 412) If customer 102 clicks on an edit business card link, registration web server 106 directs customer 106 to a web page resident on business card web server 122 (step 414). Essentially, the edit business card link opens a Secure Socket Layer (SSL) connection from a web browser used by customer 102 to the web page resident on business card web server 122. Using a SSL connection reduces the possibility of impersonation or unauthorized access to data. When the edit business card link is initially clicked, registration web server 106 establishes communication with business card web server 122 by utilizing a URL that includes the web address of the aforementioned web page resident on business card web server 122 and certain parameters that are sent to business card web server 122. These parameters may include the domain name, supplement information, signature value, and a return URL.
Supplement information may include any miscellaneous data that may be useful. Signature value may be used to validate the data and the origins of the connection to business card web server 122 thereby making sure that the data comes from domain name registration system 105. In one embodiment, the signature value may be the hex output of an MD5 hash generated by applying the MD5 algorithm to a string of values.
Return URL is the URL that business card web server 122 uses to return customer 102 directly back to the appropriate web page at registration web server 106.
Once directed to the web page resident at business card web server 122, customer 102 may manage a business card for the selected domain name in a manner selected by customer 102. This web page includes various tools that customer 102 may utilize to manage a business card. For example, the page may provide tools that allow customer 102 to create a new business card, edit an existing business card, preview a business card, publish a business card, and disable a business card. Creating a new business card or editing an existing business card may involve selecting a business card template, selecting a background color for the business card, selecting font, selecting effects, etc. Previewing a business card allows customer 102 to view the business card as displayed to a user when the user accesses the web address (e.g., domain name) associated with the business card. Publishing a business card uploads the business card created by customer 102 making it available to the public at the domain name associated with the business card. Disabling a business card allows customer 102 to turn off the business card associated with the domain name such that a default "Under Construction" page is displayed when a user accesses the domain name Disablement does not delete the business card from business card database 124 so that customer 102 may go back and enable the business card at a later date if desired When customer 102 finishes managing the business card, customer 102 may click on a link provided by the web page resident on business card web server 122 The link directs customer 102 back to the account information web page resident on registration web server 106 using the return URL provided by registration web server 106 so that customer 102 does not have to enter account login information again In an alternative embodiment, business card web server 122 may send an indication as to whether a business card is enabled or disabled back to registration web server 106 so that the appropriate indicator may be displayed with the list of domain names
If registration web server 106 determines that customer 102 has not clicked on a buy business card link or an edit business card link, a determination is made as to whether customer 102 chooses the web forwarding option for a domain name (step
418) Customer 102 may choose the web forwarding option for a domain name by, for example, clicking a web forwarding status box that is associated with the domain name After customer 102 selects web forwarding for a domain name, any conflicting business card is disabled (step 420) A business card is conflicting when the business card is enabled for a domain name and the web forwarding option is subsequently chosen for the domain name without first disabling the business card A business card may be disabled, for example, by sending business card web server 122 an indication that the business card for the domain name should be disabled
Once customer 102 enters a forwarding web address, web forwarding is set up for the domain name (step 422) Web forwarding may be set up in a manner consistent with that described m U S Application No 09/500,639, entitled "Apparatus and Method for Web Forwarding," filed February 9, 2000, Attorney Docket No 06978- 0097-00000 After web forwarding has been set up, the web page that displays the list of domain names is refreshed to indicate the new status of the domain names While the present invention has been described in connection with a preferred embodiment, many modifications will be readily apparent to those skilled in the art, and this application is intended to cover any adaptations or variations thereof. For example, the present invention may be utilized for business cards that have multiple web pages as opposed to a single web page. One skilled in the art will appreciate that all or part of the systems and methods consistent with the present invention may be stored on or read from computer-readable media, such as secondary storage devices, like hard disks, floppy disks, and CD-ROM; a carrier wave received from a network such as the Internet; or other forms of ROM or RAM. This invention should be limited only by the claims and equivalents thereof.

Claims

WHAT IS CLAIMED IS
1 A method for providing a web page in a network, said method comprising the steps of receiving a request for registering a domain name, determining whether the request associates a web page with the domain name, storing information indicating association of the web page with the domain name, and sending the stored information to a web server hosting the web page
2 The method of claim 1, further comprising the step of registering the domain name
3 The method of claim 1, wherein the stored information is a record in a zone file
4 The method of claim 1, wherein the web page is a single page web site 5 A method for providing a web page in a network, said method comprising the steps of displaying a list of one or more domain names, each having an associated link for purchasing a web page or an associated link for managing the web page, storing information indicating that a web page is associated with a selected domain name based on a determination that a link is selected for purchasing the associated web page, and directing a customer to a web page for editing the associated web page based on a determination that a link is selected for managing the associated web page
6 The method of claim 5, said displaying step further comprising providing an indication as to whether web forwarding is active for each domain name on the list
7 The method of claim 5, said displaying step further comprising providing an indication as to whether a web page is active for each domain name on the list 8 The method of claim 5, wherein the stored information is a record in a zone file
9. The method of claim 5, further comprising the step of: sending the stored information to the web site for editing the web page.
10. The method of claim 5, wherein the associated web page is a single page web site.
11. The method of claim 5, said directing step further comprising: sending a return uniform resource locator (URL) to a web site that includes the web page for editing the associated web page such that the customer is redirected back without reentering login information.
12. The method of claim 7, further comprising the step of: disabling an active web page associated with the selected domain name based on a determination that web forwarding is selected for the selected domain name.
13. A computer-readable medium containing instructions for performing a method for providing a web page in a network, said method comprising the steps of: receiving a request for registering a domain name; determining whether the request associates a web page with the domain name; storing information indicating association of the web page with the domain name; and sending the stored information to a web server hosting the web page.
14. A computer-readable medium containing instructions for performing a method for providing a web page in a network, said method comprising the steps of: displaying a list of one or more domain names, each having an associated link for purchasing a web page or an associated link for managing the web page; storing information indicating that a web page is associated with a selected domain name based on a determination that a link is selected for purchasing the associated web page; and directing a customer to a web page for editing the associated web page based on a determination that a link is selected for managing the associated web page.
15. An apparatus for providing a web page in a network, comprising: a memory having program instructions; and a processor responsive to the program instructions to receive a request for registering a domain name, determine whether the request associates a web page with the domain name, store information indicating association of the web page with the domain name, and send the stored information to a web server hosting the web page.
16. An apparatus for providing a web page in a network, comprising: a memory having program instructions; and a processor responsive to the program instructions to: display a list of one or more domain names, each having an associated link for purchasing a web page or an associated link for managing the web page; store information indicating that a web page is associated with a selected domain name based on a determination that a link is selected for purchasing the associated web page; and direct a customer to a web page for editing the associated web page based on a determination that a link is selected for managing the associated web page.
17. A method for providing a web page in a network, said method comprising the steps of: displaying a list of one or more domain names, each having an associated link for purchasing a web page or an associated link for managing the web page; and storing information indicating that a web page is associated with a selected domain name based on a determination that a link is selected for purchasing the associated web page.
18. A method for providing a web page in a network, said method comprising the steps of: displaying a list of one or more domain names, each having an associated link for purchasing a web page or an associated link for managing the web page; and directing a customer to a web page for editing a web page associated with the selected domain name based on a determination that a link is selected for managing the associated web page.
19. A method for providing a web site in a network, said method comprising the steps of: receiving a request for registering a domain name; determining whether the request associates a web site with the domain name; storing information indicating association of the web site with the domain name; and sending the stored information to a web server hosting the web site.
20. A method for providing a web site in a network, said method comprising the steps of: displaying a list of one or more domain names, each having an associated link for purchasing a web site or an associated link for managing the web site; storing information indicating that a web site is associated with a selected domain name based on a determination that a link is selected for purchasing the associated web site; and directing a customer to a web page for editing the associated web site based on a determination that a link is selected for managing the associated web site.
21. A method for providing a web page in a network, said method comprising the steps of: receiving a request for registering a domain name; determining whether the request associates a web page with the domain name; and storing information indicating association of the web page with the domain name.
PCT/US2000/040073 1999-03-19 2000-03-17 Apparatus and method for providing a business card web page WO2000057298A2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU47148/00A AU4714800A (en) 1999-03-19 2000-03-17 Dot com business card

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US12510799P 1999-03-19 1999-03-19
US60/125,107 1999-03-19

Publications (2)

Publication Number Publication Date
WO2000057298A2 true WO2000057298A2 (en) 2000-09-28
WO2000057298A3 WO2000057298A3 (en) 2000-12-28

Family

ID=22418213

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/040073 WO2000057298A2 (en) 1999-03-19 2000-03-17 Apparatus and method for providing a business card web page

Country Status (3)

Country Link
US (3) US7461334B1 (en)
AU (1) AU4714800A (en)
WO (1) WO2000057298A2 (en)

Families Citing this family (73)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6502135B1 (en) 1998-10-30 2002-12-31 Science Applications International Corporation Agile network protocol for secure communications with assured system availability
US10511573B2 (en) 1998-10-30 2019-12-17 Virnetx, Inc. Agile network protocol for secure communications using secure domain names
US7010604B1 (en) 1998-10-30 2006-03-07 Science Applications International Corporation Agile network protocol for secure communications with assured system availability
US7418504B2 (en) 1998-10-30 2008-08-26 Virnetx, Inc. Agile network protocol for secure communications using secure domain names
US6826616B2 (en) 1998-10-30 2004-11-30 Science Applications International Corp. Method for establishing secure communication link between computers of virtual private network
US7200863B2 (en) * 2000-05-16 2007-04-03 Hoshiko Llc System and method for serving content over a wide area network
US7287068B1 (en) * 2002-12-13 2007-10-23 Bmc Software, Inc. System and method for updating devices that execute an operating system or application program directly from nonvolatile storage
US20080022013A1 (en) * 2004-10-29 2008-01-24 The Go Daddy Group, Inc. Publishing domain name related reputation in whois records
US20060095459A1 (en) * 2004-10-29 2006-05-04 Warren Adelman Publishing domain name related reputation in whois records
US8904040B2 (en) * 2004-10-29 2014-12-02 Go Daddy Operating Company, LLC Digital identity validation
US9015263B2 (en) 2004-10-29 2015-04-21 Go Daddy Operating Company, LLC Domain name searching with reputation rating
US20080028443A1 (en) * 2004-10-29 2008-01-31 The Go Daddy Group, Inc. Domain name related reputation and secure certificates
US20080028100A1 (en) * 2004-10-29 2008-01-31 The Go Daddy Group, Inc. Tracking domain name related reputation
US8117339B2 (en) * 2004-10-29 2012-02-14 Go Daddy Operating Company, LLC Tracking domain name related reputation
US20060200487A1 (en) * 2004-10-29 2006-09-07 The Go Daddy Group, Inc. Domain name related reputation and secure certificates
US20060095404A1 (en) * 2004-10-29 2006-05-04 The Go Daddy Group, Inc Presenting search engine results based on domain name related reputation
US20070208940A1 (en) * 2004-10-29 2007-09-06 The Go Daddy Group, Inc. Digital identity related reputation tracking and publishing
US7797413B2 (en) * 2004-10-29 2010-09-14 The Go Daddy Group, Inc. Digital identity registration
US20080201338A1 (en) * 2007-02-16 2008-08-21 Microsoft Corporation Rest for entities
US20090248623A1 (en) * 2007-05-09 2009-10-01 The Go Daddy Group, Inc. Accessing digital identity related reputation data
US20090210400A1 (en) * 2008-02-15 2009-08-20 Microsoft Corporation Translating Identifier in Request into Data Structure
US8560519B2 (en) * 2010-03-19 2013-10-15 Microsoft Corporation Indexing and searching employing virtual documents
US8719223B2 (en) 2010-05-06 2014-05-06 Go Daddy Operating Company, LLC Cloud storage solution for reading and writing files
US8825745B2 (en) 2010-07-11 2014-09-02 Microsoft Corporation URL-facilitated access to spreadsheet elements
US8972604B1 (en) * 2012-08-17 2015-03-03 Amazon Technologies, Inc. Network address retention and assignment
US9516089B1 (en) 2012-09-06 2016-12-06 Locu, Inc. Identifying and processing a number of features identified in a document to determine a type of the document
US9483740B1 (en) 2012-09-06 2016-11-01 Go Daddy Operating Company, LLC Automated data classification
US9576065B2 (en) 2013-07-17 2017-02-21 Go Daddy Operating Company, LLC Method for maintaining common data across multiple platforms
US9160809B2 (en) 2012-11-26 2015-10-13 Go Daddy Operating Company, LLC DNS overriding-based methods of accelerating content delivery
US9141669B2 (en) 2013-01-22 2015-09-22 Go Daddy Operating Company, LLC Configuring an origin server content delivery using a pulled data list
US9384208B2 (en) 2013-01-22 2016-07-05 Go Daddy Operating Company, LLC Configuring a cached website file removal using a pulled data list
US9280523B2 (en) * 2013-01-23 2016-03-08 Go Daddy Operating Company, LLC System for conversion of website content
US9438493B2 (en) 2013-01-31 2016-09-06 Go Daddy Operating Company, LLC Monitoring network entities via a central monitoring system
US9378100B2 (en) 2013-05-17 2016-06-28 Go Daddy Operating Company, LLC Tools for storing, accessing and restoring website content via a website repository
US9537732B2 (en) 2013-07-30 2017-01-03 Go Daddy Operating Company, LLC Methods and systems for improving website performance
US9633128B2 (en) 2014-03-13 2017-04-25 Go Daddy Operating Company, LLC Lightweight web page generation
US9660933B2 (en) 2014-04-17 2017-05-23 Go Daddy Operating Company, LLC Allocating and accessing hosting server resources via continuous resource availability updates
US9501211B2 (en) 2014-04-17 2016-11-22 GoDaddy Operating Company, LLC User input processing for allocation of hosting server resources
US9130832B1 (en) 2014-10-09 2015-09-08 Splunk, Inc. Creating entity definition from a file
US10209956B2 (en) * 2014-10-09 2019-02-19 Splunk Inc. Automatic event group actions
US11671312B2 (en) 2014-10-09 2023-06-06 Splunk Inc. Service detail monitoring console
US9491059B2 (en) 2014-10-09 2016-11-08 Splunk Inc. Topology navigator for IT services
US10505825B1 (en) * 2014-10-09 2019-12-10 Splunk Inc. Automatic creation of related event groups for IT service monitoring
US10235638B2 (en) 2014-10-09 2019-03-19 Splunk Inc. Adaptive key performance indicator thresholds
US10474680B2 (en) 2014-10-09 2019-11-12 Splunk Inc. Automatic entity definitions
US10536353B2 (en) 2014-10-09 2020-01-14 Splunk Inc. Control interface for dynamic substitution of service monitoring dashboard source data
US11455590B2 (en) 2014-10-09 2022-09-27 Splunk Inc. Service monitoring adaptation for maintenance downtime
US9584374B2 (en) 2014-10-09 2017-02-28 Splunk Inc. Monitoring overall service-level performance using an aggregate key performance indicator derived from machine data
US10417225B2 (en) 2015-09-18 2019-09-17 Splunk Inc. Entity detail monitoring console
US11755559B1 (en) 2014-10-09 2023-09-12 Splunk Inc. Automatic entity control in a machine data driven service monitoring system
US9146962B1 (en) 2014-10-09 2015-09-29 Splunk, Inc. Identifying events using informational fields
US10193775B2 (en) * 2014-10-09 2019-01-29 Splunk Inc. Automatic event group action interface
US11501238B2 (en) 2014-10-09 2022-11-15 Splunk Inc. Per-entity breakdown of key performance indicators
US11200130B2 (en) 2015-09-18 2021-12-14 Splunk Inc. Automatic entity control in a machine data driven service monitoring system
US9760240B2 (en) 2014-10-09 2017-09-12 Splunk Inc. Graphical user interface for static and adaptive thresholds
US11087263B2 (en) 2014-10-09 2021-08-10 Splunk Inc. System monitoring with key performance indicators from shared base search of machine data
US9146954B1 (en) 2014-10-09 2015-09-29 Splunk, Inc. Creating entity definition from a search result set
US10305758B1 (en) 2014-10-09 2019-05-28 Splunk Inc. Service monitoring interface reflecting by-service mode
US9158811B1 (en) 2014-10-09 2015-10-13 Splunk, Inc. Incident review interface
US10417108B2 (en) 2015-09-18 2019-09-17 Splunk Inc. Portable control modules in a machine data driven service monitoring system
US9210056B1 (en) * 2014-10-09 2015-12-08 Splunk Inc. Service monitoring interface
US9967351B2 (en) 2015-01-31 2018-05-08 Splunk Inc. Automated service discovery in I.T. environments
US10198155B2 (en) * 2015-01-31 2019-02-05 Splunk Inc. Interface for automated service discovery in I.T. environments
CA2998585C (en) * 2015-09-28 2020-08-18 Arris Enterprises Llc Domain name system response spoofing at customer premise equipment device
US10942946B2 (en) 2016-09-26 2021-03-09 Splunk, Inc. Automatic triage model execution in machine data driven monitoring automation apparatus
US10942960B2 (en) 2016-09-26 2021-03-09 Splunk Inc. Automatic triage model execution in machine data driven monitoring automation apparatus with visualization
US10924467B2 (en) * 2016-11-04 2021-02-16 Microsoft Technology Licensing, Llc Delegated authorization for isolated collections
US10514854B2 (en) 2016-11-04 2019-12-24 Microsoft Technology Licensing, Llc Conditional authorization for isolated collections
US11372945B2 (en) * 2017-09-22 2022-06-28 International Business Machines Corporation Restructuring pages having similar content
US11093518B1 (en) 2017-09-23 2021-08-17 Splunk Inc. Information technology networked entity monitoring with dynamic metric and threshold selection
US11106442B1 (en) 2017-09-23 2021-08-31 Splunk Inc. Information technology networked entity monitoring with metric selection prior to deployment
US11159397B2 (en) 2017-09-25 2021-10-26 Splunk Inc. Lower-tier application deployment for higher-tier system data monitoring
US11676072B1 (en) 2021-01-29 2023-06-13 Splunk Inc. Interface for incorporating user feedback into training of clustering model

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5717863A (en) * 1995-09-27 1998-02-10 Intel Corporation Method and apparatus for managing pc conference connection addresses
WO1998012643A1 (en) * 1996-09-17 1998-03-26 National Systems Corporation Method and apparatus for creating and using dynamic universal resource locators
WO1998021672A2 (en) * 1996-11-15 1998-05-22 Inergy Online, Inc. Remote communication, information management, and home page authoring system

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5640193A (en) * 1994-08-15 1997-06-17 Lucent Technologies Inc. Multimedia service access by reading marks on an object
US5812769A (en) 1995-09-20 1998-09-22 Infonautics Corporation Method and apparatus for redirecting a user to a new location on the world wide web using relative universal resource locators
US5572643A (en) * 1995-10-19 1996-11-05 Judson; David H. Web browser with dynamic display of information objects during linking
US5751956A (en) * 1996-02-21 1998-05-12 Infoseek Corporation Method and apparatus for redirection of server external hyper-link references
US5995099A (en) * 1996-06-10 1999-11-30 Horstmann; Jens U. Method for creating and maintaining page links
US5933827A (en) * 1996-09-25 1999-08-03 International Business Machines Corporation System for identifying new web pages of interest to a user
US6052736A (en) * 1997-03-31 2000-04-18 International Business Machines Corp. Adaptive message routing in a multiple network environment with a master router
EP0889418A3 (en) 1997-06-30 1999-08-18 Sun Microsystems, Inc. Abstract URL resolution via relocation service
US5909686A (en) * 1997-06-30 1999-06-01 Sun Microsystems, Inc. Hardware-assisted central processing unit access to a forwarding database
WO1999008429A1 (en) * 1997-08-06 1999-02-18 Tachyon, Inc. A distributed system and method for prefetching objects
US6128279A (en) * 1997-10-06 2000-10-03 Web Balance, Inc. System for balancing loads among network servers
US6041360A (en) * 1997-11-21 2000-03-21 International Business Machines Corporation Web browser support for dynamic update of bookmarks
US6321242B1 (en) * 1998-02-06 2001-11-20 Sun Microsystems, Inc. Re-linking technology for a moving web site
US7765179B2 (en) * 1998-12-01 2010-07-27 Alcatel-Lucent Usa Inc. Method and apparatus for resolving domain names of persistent web resources

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5717863A (en) * 1995-09-27 1998-02-10 Intel Corporation Method and apparatus for managing pc conference connection addresses
WO1998012643A1 (en) * 1996-09-17 1998-03-26 National Systems Corporation Method and apparatus for creating and using dynamic universal resource locators
WO1998021672A2 (en) * 1996-11-15 1998-05-22 Inergy Online, Inc. Remote communication, information management, and home page authoring system

Also Published As

Publication number Publication date
US20130198413A1 (en) 2013-08-01
US7461334B1 (en) 2008-12-02
AU4714800A (en) 2000-10-09
US20090094379A1 (en) 2009-04-09
US9455951B2 (en) 2016-09-27
US8413043B2 (en) 2013-04-02
WO2000057298A3 (en) 2000-12-28

Similar Documents

Publication Publication Date Title
WO2000057298A2 (en) Apparatus and method for providing a business card web page
US7167904B1 (en) Unified web-based interface-to multiple registrar systems
US7447685B2 (en) Method and apparatus for providing geographically authenticated electronic documents
US7996468B2 (en) Method and system for controlled distribution of information profiles over a network in response to user requests
US6496855B1 (en) Web site registration proxy system
US7089325B1 (en) Method and apparatus for URL forwarding
US6175823B1 (en) Electronic gift certificate system
US7003546B1 (en) Method and system for controlled distribution of contact information over a network
US20070277235A1 (en) System and method for providing user authentication and identity management
US20020174363A1 (en) Method and apparatus for providing an anonymous identity for a user
JP2003526835A (en) Shared registration system for domain name related application registration
JP2001273309A (en) Access method for electronic business card for managing location information
EP1346273A2 (en) Method and system for account management
JP2001516094A (en) How Internet Domain Names Are Disabled
JP2001306472A (en) Electronic business card access method by hyper link
US20040006597A1 (en) Method for domain name sharing
US20020019800A1 (en) Method and apparatus for transacting divisible property
US7802291B2 (en) Systems and methods for providing zip code linked web sites
WO2000057611A2 (en) Apparatus and method for web forwarding
WO2006031615A2 (en) Apparatus and method for building conjoined computer systems
US20050138435A1 (en) Method and system for providing a login and arbitrary user verification function to applications
JP2004102760A (en) Web page access control system
EP1061462A1 (en) Storing and retrieving name card information
JP4603644B2 (en) Information processing apparatus and storage medium
CN103238144B (en) Information processor

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
AK Designated states

Kind code of ref document: A3

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase