# US 2026/0100970 A1 · Determining and Enforcing Data Location of Internet Traffic Routing Using Transport Layer Security (TLS) Server Name Indication (SNI)

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

- Number: US 2026/0100970 A1
- Document ID: US20260100970A1
- Status: Published application
- Kind: A1
- Application number: 18/907,378
- Filed: 2024-10-04
- Published: 2026-04-09
- Earliest claimed: 2024-10-04
- Assignees: Cloudflare, Inc.
- Applicants: Cloudflare, Inc.
- Inventors: Thomas Graham Arnfeld; Nicholas Jones
- Web page: https://patentgrep.com/patent/US20260100970A1

## CPC

- H04L 63/166: {at the transport layer}
- H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A compute server receives a secure session request as part of a secure session handshake. The request includes a Server Name Indication (SNI) field. The compute server determines a hostname from the SNI field and determines that a policy is applicable for the determined hostname. The policy indicates a first location where decrypting and servicing traffic for the determined hostname is permitted. The compute server determines that its location does not satisfy the determined policy. The compute server proxies the secure session handshake between the client network application and a second server that satisfies the determined policy. The compute server proxies layer 4 traffic transmitted over the secure session between the client network application and the second server.

## Claims

### Claim 1

A method in a first server of a plurality of servers of a distributed cloud computing network, comprising:
receiving a secure session request as part of a secure session handshake, wherein the secure session request includes a Server Name Indication (SNI) field, and wherein the secure session request originates from a client network application;
determining a hostname from the SNI field;
determining that a policy is applicable for the determined hostname, wherein the determined policy indicates a first location where decrypting and servicing traffic for the determined hostname is permitted;
determining that a second location of the first server does not satisfy the determined policy;
proxying the secure session handshake between the client network application and a second server of the distributed cloud computing network that satisfies the determined policy, wherein a successful secure session handshake creates a secure session between the client network application and the second server; and
proxying layer 4 traffic transmitted over the secure session between the client network application and the second server.

### Claim 2 (depends on 1)

The method of claim 1, wherein the first location is a region.

### Claim 3 (depends on 1)

The method of claim 1, wherein the secure session request is a ClientHello message.

### Claim 4 (depends on 1)

The method of claim 1, wherein the secure session request is received at the first server of the plurality of servers of the distributed cloud computing network due to an anycast implementation.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
determining that a certificate for the determined hostname is a dedicated certificate that does not cover any other hostname.

### Claim 6 (depends on 1)

The method of claim 1, wherein proxying the secure session handshake between the client network application and the second server of the distributed cloud computing network includes:
transmitting the secure session request to the second server;
receiving a response to the secure session request from the second server; and
transmitting the response to the secure session request to the client network application.

### Claim 7 (depends on 6)

The method of claim 6, wherein transmitting the secure session request to the second server includes transmitting a client IP address, a client port, a server IP address, and a server port of the secure session request.

### Claim 8

A non-transitory machine-readable storage medium that provides instructions that, if executed by a processing system of a first server of a plurality of servers of a distributed cloud computing network, will cause said first server to perform operations comprising:
receiving a secure session request as part of a secure session handshake, wherein the secure session request includes a Server Name Indication (SNI) field, and wherein the secure session request originates from a client network application;
determining a hostname from the SNI field;
determining that a policy is applicable for the determined hostname, wherein the determined policy indicates a first location where decrypting and servicing traffic for the determined hostname is permitted;
determining that a second location of the first server does not satisfy the determined policy;
proxying the secure session handshake between the client network application and a second server of the distributed cloud computing network that satisfies the determined policy, wherein a successful secure session handshake creates a secure session between the client network application and the second server; and
proxying layer 4 traffic transmitted over the secure session between the client network application and the second server.

### Claim 9 (depends on 8)

The non-transitory machine-readable storage medium of claim 8, wherein the first location is a region.

### Claim 10 (depends on 8)

The non-transitory machine-readable storage medium of claim 8, wherein the secure session request is a ClientHello message.

### Claim 11 (depends on 8)

The non-transitory machine-readable storage medium of claim 8, wherein the secure session request is received at the first server of the plurality of servers of the distributed cloud computing network due to an anycast implementation.

### Claim 12 (depends on 8)

The non-transitory machine-readable storage medium of claim 8, wherein the operations further comprise:
determining that a certificate for the determined hostname is a dedicated certificate that does not cover any other hostname.

### Claim 13 (depends on 8)

The non-transitory machine-readable storage medium of claim 8, wherein proxying the secure session handshake between the client network application and the second server of the distributed cloud computing network includes:
transmitting the secure session request to the second server;
receiving a response to the secure session request from the second server; and
transmitting the response to the secure session request to the client network application.

### Claim 14 (depends on 13)

The non-transitory machine-readable storage medium of claim 13, wherein transmitting the secure session request to the second server includes transmitting a client IP address, a client port, a server IP address, and a server port of the secure session request.

### Claim 15

A first server of a plurality of servers of a distributed cloud computing network, the first server comprising:
a processing system; and
a non-transitory machine-readable storage medium that provides instructions that, if executed by the processing system, will cause said first server to perform operations including:
receiving a secure session request as part of a secure session handshake, wherein the secure session request includes a Server Name Indication (SNI) field, and wherein the secure session request originates from a client network application,
determining a hostname from the SNI field,
determining that a policy is applicable for the determined hostname, wherein the determined policy indicates a first location where decrypting and servicing traffic for the determined hostname is permitted,
determining that a second location of the first server does not satisfy the determined policy,
proxying the secure session handshake between the client network application and a second server of the distributed cloud computing network that satisfies the determined policy, wherein a successful secure session handshake creates a secure session between the client network application and the second server, and
proxying layer 4 traffic transmitted over the secure session between the client network application and the second server.

### Claim 16 (depends on 15)

The first server of claim 15, wherein the first location is a region.

### Claim 17 (depends on 15)

The first server of claim 15, wherein the secure session request is a ClientHello message.

### Claim 18 (depends on 15)

The first server of claim 15, wherein the secure session request is received at the first server of the plurality of servers of the distributed cloud computing network due to an anycast implementation.

### Claim 19 (depends on 15)

The first server of claim 15, wherein the operations further comprise:
determining that a certificate for the determined hostname is a dedicated certificate that does not cover any other hostname.

### Claim 20 (depends on 15)

The first server of claim 15, wherein proxying the secure session handshake between the client network application and the second server of the distributed cloud computing network includes:
transmitting the secure session request to the second server;
receiving a response to the secure session request from the second server; and
transmitting the response to the secure session request to the client network application.

### Claim 21 (depends on 20)

The first server of claim 20, wherein transmitting the secure session request to the second server includes transmitting a client IP address, a client port, a server IP address, and a server port of the secure session request.
