# US 2021/0344712 A1 · Systems and methods for electronic signing of electronic content requests

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

- Number: US 2021/0344712 A1
- Document ID: US20210344712A1
- Status: Published application
- Kind: A1
- Application number: 17/374,518
- Filed: 2021-07-13
- Published: 2021-11-04
- Earliest claimed: 2017-06-26
- Assignees: Verizon Media Inc.
- Applicants: Verizon Media Inc.
- Inventors: Lachlan A. MAXWELL; Andrew BRAKSATOR; George FLETCHER
- Web page: https://patentgrep.com/patent/US20210344712A1

## CPC

- H04L 63/1483: {service impersonation, e.g. phishing, pharming or web spoofing (detection of rogue wireless access points H04W12/12)}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 9/14: using a plurality of keys or algorithms
- 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 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/126: {the source of the received data}
- H04L 2209/60: Digital content management, e.g. content distribution
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods are disclosed for cryptographic signing of content requests. One method includes receiving, at a content network, a content request from a publisher website, the publisher website purporting to be associated with a publisher domain. At the content network, a public key may be received associated with the publisher domain. At the content network, at least one policy may be received associated with the publisher domain. It may be determined whether the content request comprises a cryptographic signature. If it is determined that the content request does not comprise a cryptographic signature, content may or may not be provided to the publisher website according to the policy from the publisher domain. If it is determined that the content request comprises a cryptographic signature, the cryptographic signature of the request may be validated using the public key. Upon successfully validating the cryptographic signature of the content request, content maybe provided to the publisher website according to the content request.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A method for validating the identity of publisher websites, the method including:
receiving a content request from a publisher website purporting to be associated with a publisher domain;
receiving or accessing at least one content policy associated with the publisher domain;
determining whether the received content request comprises a cryptographic signature;
determining whether or how to provide content to the publisher website according to the received or accessed content policy associated with the publisher domain; and
validating the cryptographic signature according to the content request.

### Claim 22 (depends on 21)

The method of claim 21, further comprising:
prompting the publisher domain to add cryptographic signatures to content requests.

### Claim 23 (depends on 21)

The method of claim 21, further comprising:
upon determining that the content request does not comprise a cryptographic signature, forwarding information associated with the content request to the publisher domain.

### Claim 24 (depends on 21)

The method of claim 21, further comprising:
upon determining that the content request does not comprise a cryptographic signature, forwarding the content request to the publisher domain with a request for a corresponding cryptographic signature.

### Claim 25 (depends on 21)

The method of claim 21, further comprising:
providing content to the publisher website for additional content requests from the publisher website without validation.

### Claim 26 (depends on 21)

The method of claim 21, further comprising:
receiving a plurality of content requests from the publisher domain; and
validating cryptographic signatures associated with the content requests in a batch.

### Claim 27 (depends on 21)

The method of claim 21, further comprising:
determining that the content policy associated with the publisher domain requires all content requests associated with the publisher domain to be cryptographically signed; and
upon determining that the content request does not comprise a cryptographic signature, denying the content request.

### Claim 28 (depends on 21)

The method of claim 21, wherein a publisher key is received from a Domain Name Server associated with the publisher domain.

### Claim 29

A system for validating the identity of publisher websites, the system including:
at least one data storage device storing instructions for validating the identity of publisher websites; and
at least one processor configured to execute the instructions to perform operations comprising:
receiving a content request from a publisher website purporting to be associated with a publisher domain;
receiving or accessing at least one content policy associated with the publisher domain;
determining whether the received content request comprises a cryptographic signature;
determining whether or how to provide content to the publisher website according to the received or accessed content policy associated with the publisher domain; and
validating the cryptographic signature according to the content request.

### Claim 30 (depends on 29)

The system of claim 29, further comprising:
prompting the publisher domain to add cryptographic signatures to content requests.

### Claim 31 (depends on 29)

The system of claim 29, the method further comprising:
upon determining that the content request does not comprise a cryptographic signature, forwarding information associated with the content request to the publisher domain.

### Claim 32 (depends on 29)

The system of claim 29, the method further comprising:
upon determining that the content request does not comprise a cryptographic signature, forwarding the content request to the publisher domain with a request for a corresponding cryptographic signature.

### Claim 33 (depends on 29)

The system of claim 29, the method further comprising:
providing content to the publisher website for additional content requests from the publisher website without validation.

### Claim 34 (depends on 29)

The system of claim 29, the method further comprising:
receiving a plurality of content requests from the publisher domain; and
validating cryptographic signatures associated with the content requests in a batch.

### Claim 35 (depends on 29)

The system of claim 29, the method further comprising:
determining that the content policy associated with the publisher domain requires all content requests associated with the publisher domain to be cryptographically signed; and
upon determining that the content request does not comprise a cryptographic signature, denying the content request.

### Claim 36 (depends on 29)

The system of claim 29, wherein a publisher key is received from a Domain Name Server associated with the publisher domain.

### Claim 37

A non-transitory computer-readable medium storing instructions that, when executed by a computer, cause the computer to perform operations validating the identity of publisher websites, the operations comprising:
receiving a content request from a publisher website purporting to be associated with a publisher domain;
receiving or accessing at least one content policy associated with the publisher domain;
determining whether the received content request comprises a cryptographic signature;
determining whether or how to provide content to the publisher website according to the received or accessed content policy associated with the publisher domain; and validating the cryptographic signature according to the content request.

### Claim 38 (depends on 37)

The computer-readable medium of claim 37, the operations further comprising:
upon determining that the content request does not comprise a cryptographic signature, forwarding the content request to the publisher domain with a request for a corresponding cryptographic signature.

### Claim 39 (depends on 37)

The computer-readable medium of claim 37, the operations further comprising:
providing content to the publisher website for additional content requests from the publisher website without validation.

### Claim 40 (depends on 37)

The computer-readable medium of claim 37, the operations further comprising:
receiving a plurality of content requests from the publisher domain; and
validating cryptographic signatures associated with the content requests in a batch.
