US20060168020A1 - Private domain name registration - Google Patents

Private domain name registration Download PDF

Info

Publication number
US20060168020A1
US20060168020A1 US11/008,610 US861004A US2006168020A1 US 20060168020 A1 US20060168020 A1 US 20060168020A1 US 861004 A US861004 A US 861004A US 2006168020 A1 US2006168020 A1 US 2006168020A1
Authority
US
United States
Prior art keywords
registrant
name
contact information
domain name
applicant
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US11/008,610
Inventor
Charles Brennan
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Network Solutions LLC
Original Assignee
Network Solutions LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US11/008,610 priority Critical patent/US20060168020A1/en
Assigned to NETWORK SOLUTIONS, LLC reassignment NETWORK SOLUTIONS, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BRENNAN, CHARLES JOSEPH, III
Application filed by Network Solutions LLC filed Critical Network Solutions LLC
Assigned to CREDIT SUISSE, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT reassignment CREDIT SUISSE, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT GRANT OF PATENT SECURITY INTEREST Assignors: NETWORK SOLUTIONS, LLC
Publication of US20060168020A1 publication Critical patent/US20060168020A1/en
Assigned to NETWORK SOLUTIONS, LLC reassignment NETWORK SOLUTIONS, LLC RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: CREDIT SUISSE, CAYMAN ISLANDS BRANCH, AS ADMINISTRATIVE AGENT
Assigned to DEUTSCHE BANK TRUST COMPANY AMERICAS, AS COLLATERAL AGENT reassignment DEUTSCHE BANK TRUST COMPANY AMERICAS, AS COLLATERAL AGENT SECURITY AGREEMENT Assignors: NETWORK SOLUTIONS LLC
Assigned to NETWORK SOLUTIONS, LLC reassignment NETWORK SOLUTIONS, LLC RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: DEUTSCHE BANK TRUST COMPANY AMERICAS, AS COLLATERAL AGENT
Assigned to JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT reassignment JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT FIRST LIEN SECURITY INTEREST IN PATENT RIGHTS Assignors: NETWORK SOLUTIONS, LLC
Assigned to JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT reassignment JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT SECOND LIEN SECURITY INTEREST IN PATENT RIGHTS Assignors: NETWORK SOLUTIONS, LLC
Assigned to NETWORK SOLUTIONS, LLC reassignment NETWORK SOLUTIONS, LLC RELEASE OF GRANT OF SECOND LIEN SECURITY INTEREST IN PATENT RIGHTS PREVIOUSLY RECORDED AT REEL/FRAME (027608/0255) Assignors: JPMORGAN CHASE BANK, N.A.
Assigned to NETWORK SOLUTIONS, LLC reassignment NETWORK SOLUTIONS, LLC RELEASE OF GRANT OF FIRST LIEN SECURITY INTEREST IN PATENT RIGHTS PREVIOUSLY RECORDED AT REEL/FRAME (027608/0319) Assignors: JPMORGAN CHASE BANK, N.A.
Assigned to JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT reassignment JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: NETWORK SOLUTIONS, LLC
Assigned to NETWORK SOLUTIONS, LLC reassignment NETWORK SOLUTIONS, LLC RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (034060/0945) Assignors: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/55Detecting local intrusion or implementing counter-measures
    • G06F21/56Computer malware detection or handling, e.g. anti-virus arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 characterised by the data terminal
    • H04L29/12009Arrangements for addressing and naming in data networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 characterised by the data terminal
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12047Directories; name-to-address mapping
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages
    • H04L51/12Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages with filtering and selective blocking capabilities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages
    • H04L51/28Details regarding addressing issues
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/15Directories; Name-to-address mapping
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/30Arrangements for managing 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 or network protocols for addressing or naming
    • H04L61/30Arrangements for managing names, e.g. use of aliases or nicknames
    • H04L61/3015Name registration, generation or assignment
    • H04L61/302Administrative registration, e.g. for domain names at internet corporation for assigned names and numbers [ICANN]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/30Arrangements for managing names, e.g. use of aliases or nicknames
    • H04L61/303Name structure

Abstract

A service for protecting the privacy of domain name registrants while preserving the registrant's ability to directly change the registration information or transfer the registration. A whois record is created that reflects the registrant's actual identity but contains contact information that is entirely associated with a privacy service.

Description

    BACKGROUND OF THE INVENTION
  • The Internet Corporation for Assigned Names and Numbers (“ICANN”) governs the registration of certain types of domain names on the Internet. It accredits registrars and promulgates policies on domain name registration. One of its policies mandates that each registrar maintain a publicly-accessible database (a “whois” database) that lists the name of, and contact information for, each of registrants for each domain name registered at that registrar. See ICANN Registrar Accreditation Agreement, Approved May 17, 2001, Section 3.3.
  • An example of a portion of a domain name registration record in a whois database is shown in FIG. 1. Registrant information 101 of domain name 102 includes the registrant name 103, postal mail address 104, telephone number 105. The administrative and technical information 106 includes the administrative contact name 107 and technical contact name 108, administrative contact e-mail address 109, technical contact e-mail address 110, administrative contact telephone number 111 and technical contact telephone number 112.
  • A registrant may wish to keep private certain of the information that is publicly available in the whois database, such as telephone numbers, e-mail addresses, mail addresses, etc. For example, publicly available e-mail addresses in the whois database are mined by SPAMmers. As a result, such e-mail addresses can receive substantial amounts of unsolicited commercial e-mail (“SPAM”). In response to the need to keep domain name registration information private, certain registrars offer services designed to shield such information.
  • One known domain name registration privacy service called SPAM Shield is offered by the registrar Dotster, Inc. The SPAM Shield service replaces a registrant's e-mail address in a whois record with a SPAM Shield e-mail address. E-mail received at the SPAM Shield address is filtered for SPAM before being forwarded to an e-mail address designated by the registrant. To further confound data miners, the SPAM Shield e-mail address in the whois record is changed every ten days.
  • Another known domain name registration privacy service is offered by Domains by Proxy, Inc. The registrant of a domain name subscribes to the Domain by Proxy service, which replaces all of the registrant's registrant, administrative and technical information in the whois entry for the domain name registration with Domain by Proxy information. FIG. 2 shows a comparison of publicly available whois information 201 and what is shown when the registrant subscribes to the Domains by Proxy service 202. Domains by Proxy is contractually bound to the subscriber to dispose of the domain name registration in accordance with the subscriber's instructions.
  • The Domains by Proxy service is described in International Patent Application numbers WO 2004/029821, “Proxy E-mail Method and System” and WO 2004/021203, “Method and System for Domain Name Registration and E-mail by Proxy.” The registrant essentially transfers the domain name registration to Domains by Proxy. The registrant thereby becomes a “subscriber” to the privacy service, which is contractually bound to act at the subscriber's behest as the registrant of the domain name.
  • When correspondence is addressed to the registrant of the domain name, the Domains by Proxy service offers to forward it to the subscriber. First class postal mail (other than legal notices), “junk” mail or other unsolicited communications (regardless of their mode of delivery) are discarded or returned to the sender by the privacy service.
  • Domains by Proxy creates an e-mail address that is accessible to the subscriber for each registered domain name (“DOMAIN_NAME”) of the format DOMAIN_NAME@domainsbyproxy.com (the “DBP account”). E-mails received at each such address are either forwarded to the subscriber as-is; filtered for SPAM and forwarded; or discarded, as elected in advance by the subscriber.
  • When Domains by Proxy receives certified or traceable courier mail or legal notices addressed to the subscriber's contact information found in his domain name registration, it sends an e-mail message to the subscriber's DBP account. The e-mail message identifies the sender of the correspondence, the date Domains by Proxy received it, and a brief description of its contents. The subscriber is given seventy-two hours to decide whether to reject the correspondence or have it forwarded via overnight courier, facsimile, or both, at the subscriber's expense. Should the subscriber not respond to the Domains by Proxy e-mail message, Domains by Proxy attempts to contact the subscriber via telephone. If the subscriber does not respond and is unreachable, Domains by Proxy reserves the right to immediately reveal the subscriber's identity and/or cancel the subscriber's private registration service. In that case, the subscriber once again becomes the registrant of the domain name, and the whois directory reverts to displaying the registrant's true registration name and contact information, including the registrant's identity, postal address, e-mail address and phone number.
  • In the Domains by Proxy scheme, making changes to the domain name registration can be cumbersome because Domains by Proxy is the registrant, albeit contractually bound to act in accordance with the subscriber's instructions with regard to the domain name registration. Thus, the subscriber cannot directly make any changes to the registration or registration information, e.g., using the registrar's account management utilities. Rather, the subscriber must instruct Domains by Proxy to make any change, which Domains by Proxy must then carry out.
  • For example, transferring a domain name registration from a first registrar (a “Losing Registrar”) to a second registrar (a “Gaining Registrar) must be done by the administrative contact or registered name as shown in the whois record for the domain name registration. All accredited domain name registrars must comply with the ICANN Policy on Transfer of Registrations between Registrars, dated 12 Jul. 2004 (“ICANN Transfer Policy.”) The Policy states, “The Administrative Contact and the Registered Name Holder, as listed in the Losing Registrar's or applicable Registry's (where available) publicly accessible WHOIS service are the only parties that have the authority to approve or deny a transfer request to the Gaining Registrar. In the event of a dispute, the Registered Name Holder's authority supersedes that of the Administrative Contact.” ICANN Transfer Policy, Section 1.1. Ordinarily, transferring a registration is done directly by the actual registrant of the domain name.
  • Thus, only Domains by Proxy can transfer a domain name registration from a Losing Registrar to a Gaining Registrar. A subscriber wishing to do so must instruct Domains by Proxy to make the transfer, and provide the necessary information and authorization to Domains by Proxy. Alternatively, the subscriber can cancel its Domains by Proxy service and become the registrant for the domain name, and then transfer the domain name registration himself. However, in so doing, his registration information will become publicly available in the whois record for the domain name registration.
  • A better domain name registration privacy system would protect the registrant's sensitive information while allowing him to manipulate the registration (e.g., transfer, change registration information, etc.) directly, without proceeding through a privacy service.
  • SUMMARY OF THE INVENTION
  • In accordance with an embodiment of the present invention, each and every of the postal mail address, telephone number and e-mail address of a registrant in a whois record can all be changed to an alternate postal mail address, telephone number and e-mail address, while the registrant name in the whois record remains the actual identity of the registrant. The alternate contact information can point to a privacy service, which can handle communications addressed to such alternate contacts on behalf of the registrant. This combination can maintain the privacy of the registrant contact information, while permitting the registrant to retain control over the domain name registration, because in this way, the actual registrant (rather than a proxy service) remains the legal registrant of the domain name registration. For example, the registrant can directly approve the transfer of the registration to a Gaining Registrar in accordance with the ICANN Policy on Transfer of Registrations between Registrars. A registrant can also make changes to the registrant information listed in the whois record directly through the domain registrar's account manager, without having to act through a privacy service.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 shows a prior art embodiment of a whois record.
  • FIG. 2 shows a prior art comparison of whois records using Domains by Proxy.
  • FIG. 3 shows a system in accordance with an embodiment of the present invention.
  • FIG. 4 shows a method in accordance with an embodiment of the present invention.
  • FIG. 5 shows a whois record in accordance with an embodiment of the present invention.
  • FIG. 6 is an apparatus in accordance with an embodiment of the present invention.
  • DETAILED DESCRIPTION
  • In accordance with an embodiment of the invention, the whois record for a domain name registration is configured such that the registrant name reflects the true identity of the registrant, while the registrant contact information is entirely replaced by alternate contact information. As used herein, “contact information” includes postal mail address(es), e-mail address(es) and telephone number that are displayed in a whois record. A “contact” is an individual address displayed in a whois record, and can include a postal address, e-mail address and/or a telephone number. “Correspondence” is any communication addressed to any contact information.
  • The registrant's actual e-mail address can be replaced by an alternate e-mail address that can be changed periodically to defeat data miners. E-mail received at the alternate address can be filtered for SPAM and/or malicious code (such as viruses, worms, etc.) and then forwarded to an e-mail address designated by the registrant.
  • The registrant's postal address can be replaced by an alternate address, such as a Post Office Box maintained by a registrar. Postal mail addressed to the alternate address can be handled in accordance with any suitable regime, e.g., depending on the identity of the sender, the mode of delivery, the content of the correspondence, etc. For example, United States Postal Service (“USPS”) Certified™ and Express Mail® can be opened by the privacy service and forwarded to the registrant by a variety of methods. For example, such opened mail can be scanned and forwarded to the registrant's e-mail account electronically. Such mail can also be forwarded to a postal address designated by the registrant. Third Class and Bulk mail can be destroyed upon receipt, unopened. All other mail can be returned to the sender, unopened.
  • A sender list can be maintained for each registrant. The sender list can include classes of senders with forwarding instructions. For example, for postal mail, the sender list can include a “scan and forward” class; a “forward in hard copy” class; etc. The privacy service can determine what action to take with regard to a piece of correspondence based upon the class to which the sender belongs. Examples of an entry in a sender class include the full name and address of a sender; the name only of a sender; the corporate affiliation only of a sender; a geographic origin indicator of the sender (e.g., a zip code, a state, a street name, etc.) For e-mail, the sender list can include a sender e-mail address (e.g., phillipz@acme.com); a sender domain (e.g., forward all e-mail from acme.com); etc. For telephone forwarding, the sender lists can include originating telephone numbers, which can be obtained using known caller-ID technology; originating area codes, etc. If sender information for a given received communication is not included in a sender list, then a default rule can be applied, e.g., block the attempted communication with the registrant. The sender list can be implemented automatically by storing it in a database that can be automatically queried upon receipt of an e-mail or telephone call.
  • Similarly, a registrant can designate a code (e.g., a number) that is correlated to a rule specifying the action to take with regard to the correspondence. Such a code can be included in the postal address (e.g., attn: 14535); in the subject line of an e-mail; entered through a telephone keypad at the prompting of an Interactive Voice Response (“IVR”) system; etc. The rule associated with a code can be “forward immediately”; “forward via first class mail”; “forward via overnight courier”; etc.
  • The alternate telephone number displayed in the whois entry can be answered by an answering service that instructs the caller how to contact the registrant. For example, the answering service can instruct the caller to contact the registrant via a given e-mail address; a postal address; etc. The provided e-mail and/or postal addresses can be alternate addresses, such as those displayed in the whois record. Alternatively, an incoming telephone number can be forwarded using call-forwarding technology, e.g., if the incoming call originates from a number that the registrant has instructed to be forwarded to a given number. The originating number can be detected by the privacy service using caller-ID technology.
  • The privacy service in accordance with the present invention can be offered by a domain name registrar directly, or by a privacy service provide in conjunction with a domain name registrar. A registrant can cancel the privacy service at any time, in which case the alternate contact information in the whois record will be changed to the registrant's contact information.
  • An embodiment of a system in accordance with the present invention is shown in FIG. 3. A registration server 301 is coupled to a privacy server 302 and a privacy database 303. The registration server 301 can receive from an applicant 304 a request to register a domain name using a privacy service in accordance with an embodiment of the present invention. The registration server 301 can collect the applicant's 304 name and contact information, and then can register the domain name (the applicant 304 thus becomes the registrant 304) with the registrant's name and alternate contact information. A record including the registrant's 304 domain name, name, contact information and privacy services preferences can be stored at privacy database 302. The registrant's 304 preferences can include a sender list, correspondence forwarding options, alternate registrant contact information (i.e., alternate addresses at which the registrant 304 can be contacted directly), an indication as to whether the registrant 304 has elected to have the domain name registration automatically renewed, payment information (such as a credit card number), etc.
  • The registration server 301, privacy server 302 and privacy database 303 can each be implemented in a different computer, can be implemented in two computers, or a single computer. The functions performed by each can be implemented in any way so as best to suit the needs and capabilities of the implementer.
  • Privacy server 302 can include a SMTP e-mail server 305 that serves as the destination address for e-mail messages sent to an alternate e-mail address maintained by the privacy service, as well as computer software for scanning e-mail messages and their attachments to determine if an e-mail message is likely to be SPAM or if it contains malicious code. When an e-mail message is received at the e-mail server 305, the privacy server can query the privacy database 303 to determine the forwarding instructions of the registrant. If the registrant has indicated that no e-mail messages are to be forwarded, then the received e-mail message can be deleted. If the registrant has provided a forwarding e-mail address, then the e-mail server 305 can scan the e-mail. If the e-mail server 305 determines that the message is not SPAM and does not include malicious code, then the received message can be forwarded to the registrant in accordance with the registrant's instructions. If SPAM or malicious code is detected, then the message can be deleted. A message with a summary of deleted e-mail messages directed to the alternate e-mail address of the registrant can be periodically sent to the registrant.
  • Privacy server 302 can also include a telephone server 306 adapted to receive telephone calls directed to the alternate telephone number for a domain name registration. The telephone server 306 can include an answering service that plays a pre-recorded message directing the caller to contact the registrant via other means. It can also include an Interactive Voice Response (“IVR”) system for collecting further information from a calling party and then directing the calling party to alternate contact means, such as postal mail or e-mail. The telephone server 306 can also include call forwarding hardware and software. Upon receiving an incoming call, the telephone server 306 can query the privacy database 303 and obtain a forwarding telephone number for incoming calls to a registrant's alternate telephone number. The telephone server 306 can forward a call to another number.
  • If the registrant wants to modify any domain name registration information, the registrant can change the registrant name, or selectively or entirely replace any and all alternate contact information by using an account management tool 307 at the registration server 301. Similarly, the registrant can transfer the domain name registration directly by using the account management tool 307 at the registration server 301.
  • A privacy server system 400 in accordance with an embodiment of the present invention is shown in FIG. 4. Processor 401 can be coupled to memory 402, which can store privacy instructions 403 that can be adapted to be executed by processor 401 to perform the method in accordance with an embodiment of the present invention. For example, privacy instructions 403 executing on processor 401 can receive a request for private registration for a domain name from a registration server. The request can include the registrant's name and contact information. The executing privacy instructions 403 can cause the domain name to be registered with the registrant's name and entirely with alternate contact information. Processor 401 can be coupled to port 404.
  • The privacy server system can include e-mail server instructions 405 that can implement SMTP and can include e-mail scanning software that can detect SPAM 406 and/or malicious code 407. This can be implemented using the same processor 401 and memory 402 as the privacy instructions 403, or can be implemented on a separate processor and memory in communication with a privacy server processor 401 and memory 402. The e-mail server 404 can include query and forwarding instructions 408 that can query the privacy database (not shown) to discover forwarding e-mail addresses and other forwarding instructions, and can forward or delete e-mail messages. If a message received at the e-mail server 404 is discovered to be SPAM or contain malicious code, it can be deleted and not forwarded to the registrant.
  • The privacy server system can include telephone server instructions 409 that can receive calls made to a registrant telephone number, and can include an automatic answering service instructions 401 that deliver a message to each calling party. Telephone server instructions 409 can also include query/call forward instructions 411 that can query the privacy database (not shown) to obtain consult call-forward rules and obtain call-forward information, and then forward a call received at an alternate telephone number to a registrant telephone number. Telephone server instructions 409 can also include IVR instructions 412 that can gather additional information from a calling party. Telephone server instructions 409 can be implemented using the same processor 401 and memory 402 as used by privacy instructions 403, or may be implemented by a separate processor and memory in communication with processor 401 and memory 402.
  • An example of a portion of a whois record in accordance with an embodiment of the present invention is shown in FIG. 5. The actual name of the registrant is shown 501, while the contact information shown in the whois record is entirely alternate contact information 502. As can be seen from FIG. 5, the same technique in accordance with an embodiment of the present invention can be implemented for the administrative contact. That is, the administrative contact name 503 can be the actual name of the administrative contact (rather than some alternate contact information), while the rest of the administrative contact information is alternate contact information 504. Likewise, the technical contact name 505 can be the actual contact name, while the rest of the technical contact information can be alternate contact information 506.
  • FIG. 6 shows an embodiment of an apparatus 600 storing a data structure in accordance with an embodiment of the present invention. The apparatus includes a processor 601 coupled to memory 602 storing a whois record 603 that includes a registrant name 604 that is the actual name of a registrant of a domain name, an alternate postal address 605, an alternate e-mail address 606 and an alternate telephone number 607.
  • The above description is meant to illustrate and not limit the scope of the present invention, which is fully defined by the scope of the claims. Those of skill in the art will recognize that the above description includes examples of how the present invention may be implemented, and will understand from the above description how to implement other embodiments that are within the scope of the claims

Claims (16)

1. A method for protecting the privacy of a registrant of a domain name, comprising configuring a whois record such that the registrant name displayed in the whois record is the actual registrant name and the contact information displayed in the whois record is entirely alternate contact information.
2. The method of claim 1, wherein correspondence received at an alternate contact is forwarded to a registrant contact in accordance with a predetermined rule.
3. The method of claim 2, wherein postal correspondence received at an alternate contact is scanned and forwarded to a registrant e-mail address.
4. The method of claim 1, wherein an e-mail message received at an alternate e-mail address is scanned and forwarded to a registrant e-mail address if it is determined not to be SPAM and if it is determined not to contain malicious code.
5. An apparatus for protecting the privacy of a registrant of a domain name, comprising:
a processor;
a memory coupled to said processor, said memory storing a whois record for a domain name registration wherein the registrant name of the whois record is the actual registrant name and the contact information of the whois record is entirely alternate contact information.
6. The apparatus of claim 5, wherein said instructions are further adapted to be executed by said processor to perform steps including:
receiving an e-mail message addressed to an alternate e-mail address listed in a whois record;
scanning the e-mail message for SPAM; and
forwarding the e-mail message to an e-mail address specified by the registrant if the message is determined not to be SPAM.
7. The apparatus of claim 5, wherein said instructions are further adapted to be executed by said processor to perform steps including:
receiving an e-mail message addressed to an alternate e-mail address listed in a whois record;
scanning the e-mail message to determine if the message contains malicious code; and
forwarding the e-mail message to an e-mail address specified by the registrant if the message is determined not to contain malicious code.
8. The apparatus of claim 5, wherein said instructions are further adapted to be executed by said processor to perform steps including:
answering a telephone call to an alternate telephone number; and
providing a prerecorded message to the calling party.
9. A method for managing a domain name registration, comprising:
receiving from an applicant a request to register a domain name;
storing the name of the applicant and applicant contact information correlated with alternate contact information for the domain name registration; and
causing the domain name to be registered with the applicant name as the registrant name and with contact information that is entirely alternate contact information.
10. A medium storing instructions adapted to be executed by a processor to perform steps including configuring a whois record such that the registrant name displayed in the whois record is the actual registrant name and the contact information displayed in the whois record is entirely alternate contact information.
11. The medium of claim 10, wherein said instructions are further adapted to be executed by said processor to forward correspondence received at an alternate contact to a registrant contact in accordance with a predetermined rule.
12. The medium of claim 10, wherein said instructions are further adapted to be executed by said processor to scan and forward to a registrant e-mail address postal correspondence received at an alternate contact.
13. A medium storing instructions adapted to be executed by a processor to perform steps including:
receiving from an applicant a request to register a domain name;
storing the name of the applicant and applicant contact information correlated with alternate contact information for the domain name registration; and
causing the domain name to be registered with the applicant name as the registrant name and with contact information that is entirely alternate contact information.
14. A system for protecting the privacy of a registrant of a domain name, comprising:
means for receiving from an applicant a request to register a domain name;
means for storing the name of the applicant and applicant contact information correlated with alternate contact information for the domain name registration; and
means for causing the domain name to be registered with the applicant name as the registrant name and with contact information that is entirely alternate contact information.
15. A method for protecting the privacy of a registrant of a domain name, including:
sending from an applicant a request to a register a domain name; and
causing the domain name to be registered with the applicant name as the registrant name and with contact information that is entirely alternate contact information.
16. A medium storing instructions adapted to be executed by a processor to perform steps including:
sending from an applicant a request to a register a domain name; and
causing the domain name to be registered with the applicant name as the registrant name and with contact information that is entirely alternate contact information.
US11/008,610 2004-12-10 2004-12-10 Private domain name registration Abandoned US20060168020A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/008,610 US20060168020A1 (en) 2004-12-10 2004-12-10 Private domain name registration

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US11/008,610 US20060168020A1 (en) 2004-12-10 2004-12-10 Private domain name registration
US13/480,750 US9817979B2 (en) 2004-12-10 2012-05-25 Private domain name registration
US15/784,599 US20180068123A1 (en) 2004-12-10 2017-10-16 Private domain name registration

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/480,750 Continuation US9817979B2 (en) 2004-12-10 2012-05-25 Private domain name registration

Publications (1)

Publication Number Publication Date
US20060168020A1 true US20060168020A1 (en) 2006-07-27

Family

ID=36698231

Family Applications (3)

Application Number Title Priority Date Filing Date
US11/008,610 Abandoned US20060168020A1 (en) 2004-12-10 2004-12-10 Private domain name registration
US13/480,750 Active US9817979B2 (en) 2004-12-10 2012-05-25 Private domain name registration
US15/784,599 Abandoned US20180068123A1 (en) 2004-12-10 2017-10-16 Private domain name registration

Family Applications After (2)

Application Number Title Priority Date Filing Date
US13/480,750 Active US9817979B2 (en) 2004-12-10 2012-05-25 Private domain name registration
US15/784,599 Abandoned US20180068123A1 (en) 2004-12-10 2017-10-16 Private domain name registration

Country Status (1)

Country Link
US (3) US20060168020A1 (en)

Cited By (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080059586A1 (en) * 2006-08-18 2008-03-06 Susann Marie Keohane Method and apparatus for eliminating unwanted e-mail
US20080215716A1 (en) * 2002-08-30 2008-09-04 The Go Daddy Group, Inc. Domain name hijack protection
US20100131558A1 (en) * 2008-11-19 2010-05-27 Logan James D System and method for managing copyright licensing
US20110145336A1 (en) * 2009-12-14 2011-06-16 Carroll Martin D Electronic mail server and method for automatically generating address lists
US20120254386A1 (en) * 2011-04-01 2012-10-04 Verisign, Inc. Transfer of DNSSEC Domains
US20150056965A1 (en) * 2012-05-08 2015-02-26 Tencent Technology (Shenzhen) Company Limited Method and Terminal For Processing Information
US20160119283A1 (en) * 2014-10-23 2016-04-28 Go Daddy Operating Company, LLC Domain name hi-jack prevention
US20160285836A1 (en) * 2012-10-25 2016-09-29 Verisign, Inc. Privacy Preserving Registry Browsing
US9613374B2 (en) 2013-10-10 2017-04-04 Go Daddy Operating Company, LLC Presentation of candidate domain name bundles in a user interface
US9684918B2 (en) 2013-10-10 2017-06-20 Go Daddy Operating Company, LLC System and method for candidate domain name generation
US9715694B2 (en) 2013-10-10 2017-07-25 Go Daddy Operating Company, LLC System and method for website personalization from survey data
EP3223497A1 (en) * 2016-03-25 2017-09-27 VeriSign, Inc. Systems and methods for preserving privacy of a registrant in a domain name system ("dns")
US9779125B2 (en) 2014-11-14 2017-10-03 Go Daddy Operating Company, LLC Ensuring accurate domain name contact information
US9785663B2 (en) 2014-11-14 2017-10-10 Go Daddy Operating Company, LLC Verifying a correspondence address for a registrant
US9866526B2 (en) 2013-10-10 2018-01-09 Go Daddy Operating Company, LLC Presentation of candidate domain name stacks in a user interface
US9904944B2 (en) 2013-08-16 2018-02-27 Go Daddy Operating Company, Llc. System and method for domain name query metrics
US9953105B1 (en) 2014-10-01 2018-04-24 Go Daddy Operating Company, LLC System and method for creating subdomains or directories for a domain name
US9972041B2 (en) 2015-02-18 2018-05-15 Go Daddy Operating Company, LLC Earmarking a short list of favorite domain names or searches
US10129196B2 (en) * 2015-06-23 2018-11-13 International Business Machines Corporation Handling various scenarios where an email recipient is not available
US10140644B1 (en) 2013-10-10 2018-11-27 Go Daddy Operating Company, LLC System and method for grouping candidate domain names for display
US10346627B2 (en) 2012-10-25 2019-07-09 Verisign, Inc. Privacy preserving data querying

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106302834A (en) * 2015-05-12 2017-01-04 阿里巴巴集团控股有限公司 Domain name transfer method and apparatus

Citations (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6044205A (en) * 1996-02-29 2000-03-28 Intermind Corporation Communications system for transferring information between memories according to processes transferred with the information
US20010012378A1 (en) * 1997-11-26 2001-08-09 Dimitri Kanevsky Internet assisted mail
US6286045B1 (en) * 1997-05-19 2001-09-04 Matchlogic, Inc. Information storage and delivery over a computer network using centralized intelligence to monitor and control the information being delivered
US6308203B1 (en) * 1997-10-14 2001-10-23 Sony Corporation Information processing apparatus, information processing method, and transmitting medium
US6311207B1 (en) * 1996-06-03 2001-10-30 Webtv Networks, Inc. Method of using electronic tickets containing privileges for improved security
US6314459B1 (en) * 1998-08-13 2001-11-06 U.S. Philips Corporation Home-network autoconfiguration
US6321267B1 (en) * 1999-11-23 2001-11-20 Escom Corporation Method and apparatus for filtering junk email
US6330605B1 (en) * 1998-11-19 2001-12-11 Volera, Inc. Proxy cache cluster
US6345294B1 (en) * 1999-04-19 2002-02-05 Cisco Technology, Inc. Methods and apparatus for remote configuration of an appliance on a network
US20020091827A1 (en) * 2000-11-01 2002-07-11 Raymond King Domain name acquisition and management system and method
US6434600B2 (en) * 1998-09-15 2002-08-13 Microsoft Corporation Methods and systems for securely delivering electronic mail to hosts having dynamic IP addresses
US6446133B1 (en) * 1999-02-26 2002-09-03 I-Dns.Net International Pte Ltd. Multi-language domain name service
US6477577B1 (en) * 1996-04-05 2002-11-05 Fujitsu Limited Network connection system and connection substitute correspondence client
US6480508B1 (en) * 1999-05-12 2002-11-12 Westell, Inc. Router-based domain name system proxy agent using address translation
US20020178381A1 (en) * 2001-05-22 2002-11-28 Trend Micro Incorporated System and method for identifying undesirable content in responses sent in reply to a user request for content
US6496855B1 (en) * 1999-03-02 2002-12-17 America Online, Inc. Web site registration proxy system
US6519589B2 (en) * 1999-09-22 2003-02-11 Raredomains.Com System and method for generating domain names and for facilitating registration and transfer of the same
US20030191969A1 (en) * 2000-02-08 2003-10-09 Katsikas Peter L. System for eliminating unauthorized electronic mail
US6675208B1 (en) * 1997-10-14 2004-01-06 Lucent Technologies Inc. Registration scheme for network
US6687746B1 (en) * 1999-08-30 2004-02-03 Ideaflood, Inc. System apparatus and method for hosting and assigning domain names on a wide area network
US20040064561A1 (en) * 2002-08-30 2004-04-01 Parsons Robert R. Method and system for domain name registration and email by proxy
US6745248B1 (en) * 2000-08-02 2004-06-01 Register.Com, Inc. Method and apparatus for analyzing domain name registrations
US20040111480A1 (en) * 2002-12-09 2004-06-10 Yue Jonathan Zhanjun Message screening system and method
US6880007B1 (en) * 1999-06-07 2005-04-12 Register Com, Inc. Domain manager and method of use
US20050289084A1 (en) * 2004-06-25 2005-12-29 The Go Daddy Group, Inc. Method for a Web site with a proxy domain name registration to receive a secure socket layer certificate
US20060015868A1 (en) * 2002-08-30 2006-01-19 Rechterman Barbara J Proxy email method and system
US7007093B2 (en) * 2000-03-01 2006-02-28 Spicer Corporation Network resource control system

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH10275119A (en) 1997-03-31 1998-10-13 Hitachi Software Eng Co Ltd Electronic mail system
WO1999006929A2 (en) 1997-08-03 1999-02-11 At & T Corp. An extensible proxy framework for e-mail agents
GB2347053A (en) 1999-02-17 2000-08-23 Argo Interactive Limited Proxy server filters unwanted email
JP2001167017A (en) 1999-12-10 2001-06-22 Kojima Co Ltd Internet registration contract system
WO2001084812A2 (en) * 2000-05-03 2001-11-08 Daniel Schoeffler Method of enabling transmission and reception of communication when current destination for recipient is unknown to sender
JP2002063116A (en) 2000-08-22 2002-02-28 Xaxon R & D Corp Electronic mail proxy server
JP2002091874A (en) 2000-09-13 2002-03-29 Yes:Kk Proxy electronic mail processor and program storage medium
JP2002297938A (en) 2001-03-29 2002-10-11 Mark-I Inc Registration acceptance and application proxy system for domain name
WO2004029821A1 (en) 2002-08-30 2004-04-08 Parsons Advanced Holdings, Inc. Proxy email method and system
WO2004021203A1 (en) 2002-08-30 2004-03-11 Parsons Advanced Holdings, Inc. Method and system for domain name registration and email by proxy
US20050080642A1 (en) * 2003-10-14 2005-04-14 Daniell W. Todd Consolidated email filtering user interface
US7529802B2 (en) * 2004-06-16 2009-05-05 International Business Machines Corporation Method for performing multiple hierarchically tests to verify identity of sender of an email message and assigning the highest confidence value
US20060036690A1 (en) * 2004-07-12 2006-02-16 O'neil Patrick J Network protection system

Patent Citations (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6044205A (en) * 1996-02-29 2000-03-28 Intermind Corporation Communications system for transferring information between memories according to processes transferred with the information
US6477577B1 (en) * 1996-04-05 2002-11-05 Fujitsu Limited Network connection system and connection substitute correspondence client
US6311207B1 (en) * 1996-06-03 2001-10-30 Webtv Networks, Inc. Method of using electronic tickets containing privileges for improved security
US6286045B1 (en) * 1997-05-19 2001-09-04 Matchlogic, Inc. Information storage and delivery over a computer network using centralized intelligence to monitor and control the information being delivered
US6675208B1 (en) * 1997-10-14 2004-01-06 Lucent Technologies Inc. Registration scheme for network
US6308203B1 (en) * 1997-10-14 2001-10-23 Sony Corporation Information processing apparatus, information processing method, and transmitting medium
US20010012378A1 (en) * 1997-11-26 2001-08-09 Dimitri Kanevsky Internet assisted mail
US6314459B1 (en) * 1998-08-13 2001-11-06 U.S. Philips Corporation Home-network autoconfiguration
US6434600B2 (en) * 1998-09-15 2002-08-13 Microsoft Corporation Methods and systems for securely delivering electronic mail to hosts having dynamic IP addresses
US6330605B1 (en) * 1998-11-19 2001-12-11 Volera, Inc. Proxy cache cluster
US6446133B1 (en) * 1999-02-26 2002-09-03 I-Dns.Net International Pte Ltd. Multi-language domain name service
US6496855B1 (en) * 1999-03-02 2002-12-17 America Online, Inc. Web site registration proxy system
US6345294B1 (en) * 1999-04-19 2002-02-05 Cisco Technology, Inc. Methods and apparatus for remote configuration of an appliance on a network
US6480508B1 (en) * 1999-05-12 2002-11-12 Westell, Inc. Router-based domain name system proxy agent using address translation
US6880007B1 (en) * 1999-06-07 2005-04-12 Register Com, Inc. Domain manager and method of use
US6687746B1 (en) * 1999-08-30 2004-02-03 Ideaflood, Inc. System apparatus and method for hosting and assigning domain names on a wide area network
US6519589B2 (en) * 1999-09-22 2003-02-11 Raredomains.Com System and method for generating domain names and for facilitating registration and transfer of the same
US6321267B1 (en) * 1999-11-23 2001-11-20 Escom Corporation Method and apparatus for filtering junk email
US20030191969A1 (en) * 2000-02-08 2003-10-09 Katsikas Peter L. System for eliminating unauthorized electronic mail
US7007093B2 (en) * 2000-03-01 2006-02-28 Spicer Corporation Network resource control system
US6745248B1 (en) * 2000-08-02 2004-06-01 Register.Com, Inc. Method and apparatus for analyzing domain name registrations
US20020091827A1 (en) * 2000-11-01 2002-07-11 Raymond King Domain name acquisition and management system and method
US20020178381A1 (en) * 2001-05-22 2002-11-28 Trend Micro Incorporated System and method for identifying undesirable content in responses sent in reply to a user request for content
US20060015868A1 (en) * 2002-08-30 2006-01-19 Rechterman Barbara J Proxy email method and system
US20040064561A1 (en) * 2002-08-30 2004-04-01 Parsons Robert R. Method and system for domain name registration and email by proxy
US7130878B2 (en) * 2002-08-30 2006-10-31 The Go Daddy Group, Inc. Systems and methods for domain name registration by proxy
US20040111480A1 (en) * 2002-12-09 2004-06-10 Yue Jonathan Zhanjun Message screening system and method
US20050289084A1 (en) * 2004-06-25 2005-12-29 The Go Daddy Group, Inc. Method for a Web site with a proxy domain name registration to receive a secure socket layer certificate

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Hidden Registration FAQ and Details", HiddenRegistration.com, October 17, 2002 *

Cited By (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8751685B2 (en) * 2002-08-30 2014-06-10 Go Daddy Operating Company, LLC Domain name hijack protection
US20080215716A1 (en) * 2002-08-30 2008-09-04 The Go Daddy Group, Inc. Domain name hijack protection
US20100175137A1 (en) * 2002-08-30 2010-07-08 The Go Daddy Group, Inc. Domain name hijack protection
US8775675B2 (en) * 2002-08-30 2014-07-08 Go Daddy Operating Company, LLC Domain name hijack protection
US9245136B2 (en) 2002-08-30 2016-01-26 Go Daddy Operating Company, LLC Domain name hijack protection
US20080059586A1 (en) * 2006-08-18 2008-03-06 Susann Marie Keohane Method and apparatus for eliminating unwanted e-mail
US20100131558A1 (en) * 2008-11-19 2010-05-27 Logan James D System and method for managing copyright licensing
US20110145336A1 (en) * 2009-12-14 2011-06-16 Carroll Martin D Electronic mail server and method for automatically generating address lists
US20120254386A1 (en) * 2011-04-01 2012-10-04 Verisign, Inc. Transfer of DNSSEC Domains
US20150056965A1 (en) * 2012-05-08 2015-02-26 Tencent Technology (Shenzhen) Company Limited Method and Terminal For Processing Information
US9866536B2 (en) * 2012-10-25 2018-01-09 Verisign, Inc. Privacy preserving registry browsing
US20160285836A1 (en) * 2012-10-25 2016-09-29 Verisign, Inc. Privacy Preserving Registry Browsing
US10346627B2 (en) 2012-10-25 2019-07-09 Verisign, Inc. Privacy preserving data querying
US9904944B2 (en) 2013-08-16 2018-02-27 Go Daddy Operating Company, Llc. System and method for domain name query metrics
US9684918B2 (en) 2013-10-10 2017-06-20 Go Daddy Operating Company, LLC System and method for candidate domain name generation
US9715694B2 (en) 2013-10-10 2017-07-25 Go Daddy Operating Company, LLC System and method for website personalization from survey data
US10140644B1 (en) 2013-10-10 2018-11-27 Go Daddy Operating Company, LLC System and method for grouping candidate domain names for display
US9866526B2 (en) 2013-10-10 2018-01-09 Go Daddy Operating Company, LLC Presentation of candidate domain name stacks in a user interface
US9613374B2 (en) 2013-10-10 2017-04-04 Go Daddy Operating Company, LLC Presentation of candidate domain name bundles in a user interface
US9953105B1 (en) 2014-10-01 2018-04-24 Go Daddy Operating Company, LLC System and method for creating subdomains or directories for a domain name
US10277556B2 (en) * 2014-10-23 2019-04-30 Go Daddy Operating Company, LLC Domain name hi-jack prevention
US20160119283A1 (en) * 2014-10-23 2016-04-28 Go Daddy Operating Company, LLC Domain name hi-jack prevention
US9954818B2 (en) * 2014-10-23 2018-04-24 Go Daddy Operating Company, LLC Domain name hi-jack prevention
US9785663B2 (en) 2014-11-14 2017-10-10 Go Daddy Operating Company, LLC Verifying a correspondence address for a registrant
US9779125B2 (en) 2014-11-14 2017-10-03 Go Daddy Operating Company, LLC Ensuring accurate domain name contact information
US9972041B2 (en) 2015-02-18 2018-05-15 Go Daddy Operating Company, LLC Earmarking a short list of favorite domain names or searches
US10129196B2 (en) * 2015-06-23 2018-11-13 International Business Machines Corporation Handling various scenarios where an email recipient is not available
US10142273B2 (en) 2015-06-23 2018-11-27 International Business Machines Corporation Handling various scenarios where an email recipient is not available
EP3445022A1 (en) * 2016-03-25 2019-02-20 Verisign, Inc. Systems and methods for preserving privacy of a registrant in a domain name system ("dns")
US20170279762A1 (en) * 2016-03-25 2017-09-28 Verisign, Inc. Systems and methods for preserving privacy of a registrant in a domain name system ("dns")
EP3223497A1 (en) * 2016-03-25 2017-09-27 VeriSign, Inc. Systems and methods for preserving privacy of a registrant in a domain name system ("dns")

Also Published As

Publication number Publication date
US9817979B2 (en) 2017-11-14
US20130104229A1 (en) 2013-04-25
US20180068123A1 (en) 2018-03-08

Similar Documents

Publication Publication Date Title
US7428576B2 (en) Addressee-defined mail addressing system and method
US9875466B2 (en) Probability based whitelist
EP2068516B1 (en) E-mail management services
US6957248B2 (en) System and method for forwarding electronic messages
US8085891B2 (en) System and method for management of mobile device communication
JP3919008B2 (en) Transparent implementation using value-added electronic messaging service, and the intermediate server
Gabber et al. Consistent, yet anonymous, Web access with LPWA
US6738462B1 (en) Unified communications automated personal name addressing
US7433923B2 (en) Authorized email control system
AU2004225050B2 (en) Control and management of electronic messaging
US5974449A (en) Apparatus and method for providing multimedia messaging between disparate messaging platforms
US7415504B2 (en) System and method for controlling distribution of network communications
US8209387B2 (en) Method and system for filtering unauthorized electronic mail messages
EP1488584B9 (en) System and method for supporting message delivery in a network
US8194564B2 (en) Message filtering method
US9742922B2 (en) Message routing
US6161129A (en) Unlisted address messaging system
US7647321B2 (en) System and method for filtering electronic messages using business heuristics
US20010003202A1 (en) Instant messaging
US6307931B1 (en) System and method for allowing communication between networks having incompatible addressing formats
US6557036B1 (en) Methods and apparatus for site wide monitoring of electronic mail systems
US20050071428A1 (en) Method and apparatus for delivering an electronic mail message with an indication of the presence of the sender
CA2364486C (en) Unified directory for caller id and electronic mail addresses
USRE40992E1 (en) Method and system for blocking unwanted communications
US20030009698A1 (en) Spam avenger

Legal Events

Date Code Title Description
AS Assignment

Owner name: NETWORK SOLUTIONS, LLC, VIRGINIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BRENNAN, CHARLES JOSEPH, III;REEL/FRAME:016077/0246

Effective date: 20041210

AS Assignment

Owner name: CREDIT SUISSE, CAYMAN ISLANDS BRANCH, AS COLLATERA

Free format text: GRANT OF PATENT SECURITY INTEREST;ASSIGNOR:NETWORK SOLUTIONS, LLC;REEL/FRAME:017024/0833

Effective date: 20060109

AS Assignment

Owner name: NETWORK SOLUTIONS, LLC, VIRGINIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE, CAYMAN ISLANDS BRANCH, AS ADMINISTRATIVE AGENT;REEL/FRAME:018990/0797

Effective date: 20070307

AS Assignment

Owner name: DEUTSCHE BANK TRUST COMPANY AMERICAS, AS COLLATERA

Free format text: SECURITY AGREEMENT;ASSIGNOR:NETWORK SOLUTIONS LLC;REEL/FRAME:019161/0051

Effective date: 20070307

AS Assignment

Owner name: NETWORK SOLUTIONS, LLC, VIRGINIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:DEUTSCHE BANK TRUST COMPANY AMERICAS, AS COLLATERAL AGENT;REEL/FRAME:027136/0379

Effective date: 20111027

AS Assignment

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

Free format text: SECOND LIEN SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:NETWORK SOLUTIONS, LLC;REEL/FRAME:027608/0255

Effective date: 20111027

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

Free format text: FIRST LIEN SECURITY INTEREST IN PATENT RIGHTS;ASSIGNOR:NETWORK SOLUTIONS, LLC;REEL/FRAME:027608/0319

Effective date: 20111027

STCB Information on status: application discontinuation

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

AS Assignment

Owner name: NETWORK SOLUTIONS, LLC, FLORIDA

Free format text: RELEASE OF GRANT OF SECOND LIEN SECURITY INTEREST IN PATENT RIGHTS PREVIOUSLY RECORDED AT REEL/FRAME (027608/0255);ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:034079/0941

Effective date: 20140909

Owner name: NETWORK SOLUTIONS, LLC, FLORIDA

Free format text: RELEASE OF GRANT OF FIRST LIEN SECURITY INTEREST IN PATENT RIGHTS PREVIOUSLY RECORDED AT REEL/FRAME (027608/0319);ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:034077/0659

Effective date: 20140909

AS Assignment

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

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

Effective date: 20140909

AS Assignment

Owner name: NETWORK SOLUTIONS, LLC, FLORIDA

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

Effective date: 20181011