# US 2005/0039017 A1 · Method and system for authenticating a message sender using domain keys

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2005/0039017 A1
- Document ID: US20050039017A1
- Status: Published application
- Kind: A1
- Application number: 10/671,319
- Filed: 2003-09-24
- Published: 2005-02-17
- Earliest claimed: 2003-08-26
- Assignees: Yahoo! Inc.
- Inventors: Mark Delany
- Web page: https://patentgrep.com/patent/US20050039017A1

## CPC

- H04L 63/126: {the source of the received data}
- H04L 9/083: {involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]}
- H04L 9/30: Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
- H04L 9/3247: {involving digital signatures}
- H04L 61/4511: using domain name system [DNS]
- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method and system is directed to providing authentication of a message, such as email, and the like, by combining Public Key encryption and the Internet Domain Name System (the “DNS”). A domain owner may validate that an email originates from an authorized sender within their domain by using a private key component to digitally sign email outbound from its domain. Employing a public key component, along with a selector, an email recipient may check the validity of the signature, and thus determine that the email originated from a sender authorized by the domain owner. In one embodiment, the public key component used to verify an email signature may be “advertised” or otherwise made available via a TXT record in the DNS.

## Claims

### Claim 1

A method for message authentication, comprising:
generating a key pair associated with a domain, wherein a public component of the key pair is accessible to a domain name server (DNS) that is associated with the domain;
if a message originates from a sender's address associated with the domain, employing a private component of the key pair to digitally sign the message and forwarding the digitally signed message towards a recipient of the message; and
if the public component stored with the DNS verifies that the digitally signed message originated from the domain associated with the sender's address, providing the verified digitally signed message to the recipient.

### Claim 2 (depends on 1)

The method of claim 1, further comprising a text record that is accessible to the DNS and which includes at least the public component of the key pair.

### Claim 3 (depends on 1)

The method of claim 1, further comprising generating a selector that is associated with the key pair, wherein the selector is employable to identify the key pair's public component for accessing by the DNS.

### Claim 4 (depends on 3)

The method of claim 3, further comprising forming a lookup query for the DNS by combining the selector with the sender's address.

### Claim 5 (depends on 1)

The method of claim 1, further comprising employing a mail server associated with the domain to forward the digitally signed message towards the recipient of the message.

### Claim 6 (depends on 1)

The method of claim 1, further comprising employing a mail server associated with the domain to employ the private component of the key pair to digitally sign the message.

### Claim 7 (depends on 1)

The method of claim 1, further comprising employing a mail server that is associated with a domain of the recipient to verify the domain of origination for the message with the public component of the key pair.

### Claim 8 (depends on 1)

The method of claim 1, further comprising employing a mail server that is associated with a domain of the recipient to provide the verified digitally signed message to the recipient.

### Claim 9 (depends on 1)

The method of claim 1, further comprising accessing the public component of the key pair by employing a text record in a look up table for the DNS.

### Claim 10 (depends on 1)

The method of claim 1, further comprising generating a plurality of key pairs associated with the domain, wherein at least two key pairs are associated with at least two different senders and wherein each public component of each key pair is accessible by the DNS associated with the domain.

### Claim 11 (depends on 10)

The method of claim 10, further comprising separately associating private components of the at least two key pairs with at least two mail servers, wherein the at least two mail servers are associated with the domain.

### Claim 12 (depends on 10)

The method of claim 10, wherein each private component of each key pair employs a mail server associated with the domain to forward the digitally signed message towards the recipient of the message.

### Claim 13 (depends on 1)

The method of claim 1, further comprising employing one of a plurality of mail servers associated with the domain to digitally sign the message with the private component of the key pair and forward the digitally signed message towards the recipient.

### Claim 14

A system for message authentication, comprising:
a client that is enabled to generate at least one message for a recipient, wherein the client is associated with a domain;
a mail server associated with the domain of the client, wherein the mail server performs actions, including:
enabling the generation of a key pair associated with the domain, wherein a public component of the key pair is accessible to a DNS that is associated with the domain; and
if a message from the client originates from the domain, enabling a private component of the key pair to digitally sign the message and forward the digitally signed message towards the recipient of the message; and
a mail server associated with a domain of the recipient, wherein the mail server performs actions including enabling the public component stored with the DNS to verify that the digitally signed message originated from the domain associated with the client, and enabling each verified digitally signed message to be provided to the recipient.

### Claim 15 (depends on 14)

The system of claim 14, wherein the message is at least one of an email, instant message (IM), short message service (SMS).

### Claim 16 (depends on 14)

The system of claim 14, further comprises a text record that is accessible to the DNS and which includes at least the public component of the key pair.

### Claim 17 (depends on 14)

The system of claim 14, further comprises a selector that is associated with the key pair, wherein the selector is employable to identify the key pair's public component for accessing by the DNS.

### Claim 18 (depends on 14)

The system of claim 14, further comprising a plurality of key pairs that are associated with at least two different clients, wherein each public component of each key pair is accessible by the DNS associated with the domain.

### Claim 19

A carrier wave signal that enables actions for message authentication, comprising:
generating a key pair associated with a domain, wherein a public component of the key pair is accessible to a domain name server (DNS) that is associated with the domain;
if a message originates from a sender's address associated with the domain, employing a private component of the key pair to digitally sign the message and forwarding the digitally signed message towards a recipient of the message; and
if the public component stored with the DNS verifies that the digitally signed message originated from the domain associated with the sender's address, providing the verified digitally signed message to the recipient.

### Claim 20 (depends on 19)

The carrier wave signal of claim 19, further comprising generating a selector that is associated with the key pair, wherein the selector is employable to identify the key pair's public component for accessing by the DNS.

### Claim 21 (depends on 19)

The carrier wave signal of claim 19, further comprising generating a plurality of key pairs associated with the domain, wherein at least two key pairs are associated with at least two different senders and wherein each public component of each key pair is accessible by the DNS associated with the domain.

### Claim 22 (depends on 21)

The carrier wave signal of claim 21, further comprising separately associating private components of the at least two key pairs with at least two mail servers, wherein the at least two mail servers are associated with the domain.

### Claim 23 (depends on 21)

The carrier wave signal of claim 21, wherein each private component of each key pair employs a mail server associated with the domain to forward the digitally signed message towards the recipient of the message.

### Claim 24

A client that enables message authentication, comprising:
enabling the generation of a key pair associated with a domain, wherein a public component of the key pair is accessible to a domain name server (DNS) that is associated with the domain;
if a message originates from a sender's address associated with the domain, enabling a private component of the key pair to be employed to digitally sign the message and forwarding the digitally signed message towards a recipient of the message; and
if the public component stored with the DNS verifies that the digitally signed message originated from the domain associated with the sender's address, providing the verified digitally signed message to the recipient.

### Claim 25 (depends on 24)

The client of claim 24, further comprising enabling the generation of a plurality of key pairs associated with the domain, wherein at least two key pairs are associated with at least two different senders and wherein each public component of each key pair is accessible by the DNS associated with the domain.

### Claim 26 (depends on 25)

The client of claim 25, further comprising enabling the separate association of private components of the at least two key pairs with at least two mail servers, wherein the at least two mail servers are associated with the domain.

### Claim 27 (depends on 25)

The client of claim 25, further comprising enabling each private component of each key pair to employ a mail server associated with the domain to forward the digitally signed message towards the recipient of the message.

### Claim 28

A server that enables message authentication, comprising:
enabling the generation of a key pair associated with a domain, wherein a public component of the key pair is accessible to a domain name server (DNS) that is associated with the domain;
if a message originates from a sender's address associated with the domain, enabling a private component of the key pair to be employed to digitally sign the message and forwarding the digitally signed message towards a recipient of the message; and
if the public component stored with the DNS verifies that the digitally signed message originated from the domain associated with the sender's address, providing the verified digitally signed message to the recipient.

### Claim 29

A method for enabling message authentication, comprising:
means for enabling the generation of a key pair associated with a domain, wherein a public component of the key pair is accessible to a domain name server (DNS) that is associated with the domain;
if a message originates from a sender's address associated with the domain, means for enabling a private component of the key pair to be employed to digitally sign the message and forwarding the digitally signed message towards a recipient of the message; and
if the public component stored with the DNS verifies that the digitally signed message originated from the domain associated with the sender's address, means for providing the verified digitally signed message to the recipient.
