Abstract: Systems and methods of the present invention allow for tracking of domain name related reputation by a domain name Registering Entity (e.g. Registry, Registrar, etc.). In a preferred embodiment, the Registering Entity maintains a database with reputation data that can be accessed by the requesters. The Registering Entity may update reputation data based on a variety of events related to the domain name. The reputation data may be tracked on the domain name itself, URLs, domain name purchaser or registrant, or email addresses associated with the domain name. The reputation data may include various categories, such as email practices, website content, privacy policies and practices, fraudulent activities, domain name related complaints, overall reputation, etc. The registrant may opt for a reputation service while registering domain name. The requester may decide whether to allow email messages or to visit URLs based on the domain name related reputation.

Abstract: An example embodiment of a Community Web Site includes a Home Page, a Web Presence Tool Page, and a Product and Community Forum which is created and maintained by a Hosting Provider. The Home Page may be made accessible to Hosting Customers and Partners and is an ideal location for placement of ads since all members of the Web Hosting Community are funneled through this Web page. The Web Presence Tool Page may display information generated by a Partner regarding the Partner's application which may be viewed by the Hosting Customers. The Product and Community Forum may allow the Hosting Customers to share information regarding all the applications with other Hosting Customers.

Abstract: An example embodiment for using a Partner Web Site within a Web Hosting Community starts with a Hosting Provider creating the Partner Web Site, a Community Web Site, and operating one or more Hosting Servers. A Partner, from the Partner Web Site, may make an application available for purchase and use to a plurality of Hosting Customers. At least one of the Hosting Customers, from the Community Web Site, may purchase and utilize the application with their Hosted Web Site.

Abstract: An example of a certification process for an application to be made available to a plurality of Hosting Customers within a Web Hosting Community starts with a partner, from a Partner Web Site, submitting the application to a Hosting Provider. The Hosting Provider may perform a test on the application to verify the application conforms to a predetermined standard. The Hosting Provider may perform one or more manual or automated test and look for viruses, worms, Trojen horses, adware, malware, reliability/compatibility issues or other problems with the application that may adversely impact the Web Hosting Community. If the application passes the test, the Hosting Provider may make the application available to the plurality of Hosting Customers. In preferred embodiments, the Hosting Customer may purchase the application thereby triggering the Hosting Provider to automatically make the application available for use by the Hosting Customer's Hosted Web Site.

Abstract: An example embodiment of a Web Hosting Community includes at least three members, i.e. a Hosting Provider, a Hosting Customer and a Partner. The Hosting Provider may have one or more Hosting Servers, and create and maintain a Partner Web Site and a Community Web Site. The Partner Web Site and the Community Web Site may provide tools that are tailored for the needs of the Partner and the Hosting Customer, respectively, to participate in the Web Hosting Community. The Partner may provide an application, i.e. software program, to be integrated into the Web Hosting Community and the Hosting Customer may purchase and install the application onto its Hosted Web Site, which is stored on a Hosting Server.

Abstract: Systems and methods of the present invention allow for archiving files in an online community. An example system includes a Community Website hosted on at least one Hosting Server; a Forum accessible to a plurality of Members via said Community Website, said Forum capable of being written to and read by said plurality of Members; a File Archiving System having the ability to store a plurality of files generated by said Forum; and a Network communicatively coupling said Community Website, said at least one Hosting Server, said Forum, said plurality of Members, and said File Archiving system.

Abstract: Systems and methods of the present invention allow for providing and managing an online business community. An exemplary system may comprise at least one Hosting Server maintained by a Hosting Entity; a Community Website accessible to a plurality of Clients and hosted on said at least one Hosting Server; a Resource Database storing a plurality of Content, wherein at least some of said Resources are generated by a Member; a Directory Database storing a plurality of Member Information; and a Network communicatively coupling said Hosting Server, said Community Website, said plurality of Clients, said Resource Database, and said Directory Database.

Abstract: Systems and methods of the present invention allow for providing and managing sub-communities within an online business community. An exemplary system may comprise an Online Business Community having a Community Website hosted on at least one Hosting Server, said at least one Hosting Server communicatively coupled to a Network; a Homepage on said Community Website accessible to a plurality of Members via said Network; and a plurality of Groups accessible to said plurality of Members via said Homepage, wherein each of said Groups relates to a subject.

Abstract: Systems and methods of the present invention allow for designating membership in an online business community. An exemplary method may comprise the steps of: designating a plurality of Members as participants in an Online Business Community; and providing each of said plurality of Members with a Membership Designator.

Abstract: Disclosed systems and methods provide for tracking of domain name related reputation by a domain name Registering Entity (e.g. Registry, Registrar, Reseller, etc.). The Registering Entity maintains a database with reputation data that can be accessed by the requesters. A domain name may be registered through the Registering Entity or a third party. The reputation data may be tracked on the domain name itself, URLs, domain name purchaser or registrant, or email addresses associated with the domain name. The reputation data may include various categories, such as email practices, website content, privacy policies and practices, fraudulent activities, domain name related complaints, digital certificates associated with the domain name, overall reputation, etc. The reputation data may be digitally signed for authenticity. The requester may decide whether to allow email messages or to visit URLs based on the domain name related reputation.

Abstract: Disclosed systems and methods provide for issuing a secure certificate using improved methods in verifying a Subscriber. In a sample embodiment, a Registering Entity maintains a database with reputation data that can be accessed by a Certification Authority. The Registering Entity may update reputation data based on a variety of events related to the domain name. The reputation data may be tracked on the domain name, URLs, domain name purchaser or registrant, and/or email addresses associated with the domain name. The reputation data may include various categories, such as email practices, website content, privacy policies and practices, fraudulent activities, domain name related complaints, overall reputation, etc. The Certification Authority may decide whether to issue or deny a secure certificate based on the reputation associated with the Subscriber's domain name. The reputation data may be digitally signed for authenticity. The reputation data may be stored in a digital certificate.

Abstract: Disclosed methods provide for publishing domain name related reputation data in WHOIS records. Reputation data may be published in the WHOIS records of the domain name. Reputation data may include values, ratings, or scores, as well as links or references to the locations where such values, ratings, or scores may be found (e.g. URL link). The reputation data may be tracked on the domain name itself, URLs, domain name purchaser or registrant, or email addresses associated with the domain name. The reputation data may include various categories, such as email practices, website content, privacy policies and practices, fraudulent activities, domain name related complaints, overall reputation, etc. The requester may decide whether to allow email messages or visit URLs based on the domain name related reputation. The reputation data in WHOIS may be digitally signed for authenticity. WHOIS data may blacklist or whitelist a resource.

Abstract: Disclosed methods provide for presenting search engine results based on domain name related reputation data. The search engine may sort or order search engine results based on domain name related reputation data. In some cases links connected to low reputation domain names may be excluded from search engine results. Alternatively, the search engine may show reputation ratings next to the links in the search engine results. Thus, allowing the Internet user to determine whether to visit the link or not. The reputation data may be tracked on the domain name itself, URLs, domain name purchaser or registrant, or email addresses associated with the domain name. The reputation data may include various categories, such as email practices, website content, privacy policies and practices, fraudulent activities, domain name related complaints, overall reputation, etc. The reputation data may be digitally signed for authenticity. The reputation data may be stored in a digital certificate.

Abstract: Systems and processes of the present invention allow for digital identity validation. In an example embodiment, a digital identity is registered to a Registrant. During the registration process, one or more registration records are collected from the Registrant and stored in a Records Database. The registration records may include information regarding a digital identity, its Registrant, or another person or entity associated with the digital identity. They may also include name, address, phone number, email address, website, URL, or other information. The information is then verified, possibly by contacting a Registrant, administrative contact, technical contact, or another contact to confirm at least some information in the records. If the information is verified, the Digital Identity Provider may provide the Registrant with a Validation Marker indicating that the digital identity has been validated.

Abstract: Systems and processes of the present invention allow for digital identity registration. In an example embodiment, a Registrant may access a website to enter a requested digital identity and registration information. The requested digital identity may comprise a piece of client software, a digital certificate, or a URL comprising any combination of characters—perhaps including a domain name that may be owned by the Registrant. A Digital Identity Database may then be searched to determine the availability of the requested digital identity. If the requested digital identity includes a domain name, WHOIS records may be searched to determine whether the Registrant owns and/or controls the domain name. The Registrant's registration information also may be validated. The requested digital identity may then be registered to the Registrant, possibly by adding the requested digital identity to the Digital Identity Database and/or adding the registration information to a Records database.

Abstract: Systems and processes of the present invention allow for tracking and publishing digital identity related reputation. In an example embodiment, a Digital Identity Provider maintains a database with reputation data that can be accessed by Requesters. The Digital Identity Provider may update reputation data based on a variety of events related to a digital identity. The reputation data may be tracked regarding the digital identity itself, digital identity purchaser or registrant, or an email address, domain name, URL, or website associated with the digital identity. The reputation data may include various categories, such as email practices, website content, privacy policies and practices, fraudulent activities, domain name related complaints, overall reputation, etc. The reputation data may be published in a publicly-available database, a private database, or via other methods. The Registrant may opt for a reputation service while registering a digital identity.

Abstract: A Registrar may receive and register a domain name for a Registrant. The Registrant may use the domain name to facilitate access to a website that promotes a business of the Registrant. The Registrar may determine, typically either by asking the Registrant or by searching on-line databases, operational area(s) of the Registrant's business and store the domain name and the operational area(s) in a database. The database may be the DNS with this additional information, the WHOIS database or a whole new database may be created. This process may be repeated so that a database is created or updated to have a plurality of domain names where at least some of the domain names are associated with one or more operational areas of a business. Once created, the database may be accessed via a global computer network by any application that desires information related to operational areas of businesses.

Abstract: A search engine website may receive a search term from a User, a relevant geographical location of the User and, from an on-line database such as a Domain Name System database, a WHOIS database or another database, a plurality of operational areas for a plurality of different businesses. Using the search term, the geographical location of the User and information regarding the operational areas of a plurality of businesses, combined with other information maintained by the search engine, a search result may be created and displayed for the User. In a preferred embodiment, descriptions and links to websites of businesses that have operational areas encompassing or proximate to the User's geographical location are displayed prominently in the search result.

Abstract: Systems and methods of the present invention allow for issuing a secure certificate using improved methods in verifying a Subscriber. In a sample embodiment, a Registering Entity maintains a database with reputation data that can be accessed by a Certification Authority. The Registering Entity may update reputation data based on a variety of events related to the domain name. The reputation data may be tracked on the domain name, URLs, domain name purchaser or registrant, and/or email addresses associated with the domain name. The reputation data may include various categories, such as email practices, website content, privacy policies and practices, fraudulent activities, domain name related complaints, overall reputation, etc. The Certification Authority may decide whether to issue or deny a secure certificate based on the reputation associated with the Subscriber's domain name.

Abstract: The present invention provides methods for covering a plurality of domain names with a single certificate. This may be accomplished even if two or more of the domain names have different top level domains (TLDs). In certain embodiments, a Subscriber may be subjected to a vetting process as a prerequisite to allowing the Subscriber to create an account. Once the Subscriber has an account, the Subscriber may request a certificate, possibly covering multiple domain names, from the account without further vetting. In other embodiments, one or more domain names may be subjected to a vetting process prior to receiving a certificate. The history and prior usage of the domain name(s) may be examined to determine if a certificate should be issued for the domain names. Subjecting the domain names to a vetting process may also be done in combination with subjecting the Subscriber to a vetting process.