IP Library Granted Patent US 10,812,441
Granted Patent B2
US 10,812,441 · App. 16/149,928 · Granted Oct 20, 2020

System and method for suppressing DNS requests

Inventors: Eugene Lapidous (Saratoga, CA); Maxim Molchanov (Mountain View, CA)
Assignee: PANGO INC.
H04L61/1511H04L61/10H04L61/2007H04L61/6013H04L61/6068H04L63/00H04L63/0281H04L61/2038H04L61/6009H04L63/0272
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,812,441
App. No.
16/149,928
Granted
Oct 20, 2020
Kind
B2
Abstract

A virtual private router (VPR) intercepts DNS requests and returns a pseudo IP address to the requesting application and the pseudo IP address is mapped to a domain name in the request. Requests for content including the pseudo IP address are modified to include the corresponding domain name and transmitted to an intermediary server, which resolves the domain name to a real IP address and forwards the content request. The content is received by the intermediary server, which returns it to the requesting application, such as by way of the VPR. Real IP addresses may be returned by the intermediary server such that subsequent content requests to the domain name may bypass the intermediary server. Content requests may be sent to the intermediary server, which may instruct the VPR to bypass the server when bypass is needed.

Claims (39)

1. A method comprising:

receiving, by a first server, a plurality of requests, each request of the plurality of requests including a domain name and being received from a source; and

for each request of the plurality of requests:

obtaining, by a module on the first server, a selected option for processing the each request from a group of options by evaluating whether the domain name is associated with increased at least one of security and privacy risk according to a reputation score associated with the domain name in a threat database; and

when the reputation score associated with the domain name is below a predefined threshold and is not associated with a low probability of false alarm, selecting as the selected option (a) retrieving content referenced by the each request by the first server by:

resolving, by the first server, the domain name of the each request to a first routable internet protocol (IP) address;

retrieving, by the first server, the content referenced by the each request from a second server corresponding to the first routable IP address;

returning, by the first server to the source of the each request, the content referenced by the each request to a source of the each request;

when the reputation score associated with the domain name is above the predefined threshold, selecting as the selected option (b) retrieving the content referenced by the each request in bypass of the first server by:

resolving, by the first server, the domain name of the each request to the first routable IP address;

returning, by the first server to the source of the each request, a bypass response indicating that the source of the each request should send a second content request to the first routable IP address in bypass of the first server to retrieve the content referenced by the each request; and

when the reputation score associated with the domain name is below the predefined threshold and is associated with the low probability of the false alarm, selecting as the selected option (c) blocking the each request instead of retrieving the content referenced by the each request.

2. The method of claim 1 , further comprising, when the selected option is (b), in response to receiving the bypass response from the first server:

obtaining, by a module executing on the source of the each request, a second routable internet protocol (IP) address associated with the domain name,

sending, by the module executing on the source of the each request, a second request for the content referenced by the each request to a server corresponding to the second IP address, the second request being sent in bypass of the first server; and

receiving, by the module executing on the source of the each request, the content referenced by the each request in bypass of the first server.

3. The method of claim 2 , wherein obtaining the second IP address comprises issuing a domain name service (DNS) request including the domain name to a DNS server over a computer network, the DNS request being issued from the source of the each request after receiving the bypass response.

4. The method of claim 1 , further comprising requesting, by a module executing on the source of the each request, the content referenced by the each request from the first routable IP address.

5. The method of claim 1 , further comprising:

intercepting, from an application executing on the source of the each request by a module executing on the source of the each request, a request to resolve the domain name;

returning, by the module executing on the source of the each request, a first pseudo IP address without issuing a domain resolution request over a computer network;

intercepting, from the application executing on the source of the each request by a module executing on the source of the each request, an original content request including the first pseudo IP address;

generating, by the module executing on the source of the each request, the each request including the first domain name; and

and sending the each request to the first server.

6. The method of claim 1 , where the first server is at least one of a proxy server and a virtual private network (VPN) server.

7. A system comprising one or more processing devices and one or more memory devices operably couple to the one or more processing devices, the one or more memory devices storing executable code effective to cause the one or more processing devices to:

receive a content request including a domain name and received from a source;

obtain, by a module, a selected option for processing the content request from a group of options according to a reputation score associated with the domain name in a threat database, the module programmed to:

select option (a) as the selected option when the reputation score associated with the domain name is below a predefined threshold and is not associated with a low probability of false alarm;

select option (b) as the selected option when the reputation score associated with the domain name is above the predefined threshold; and

select option (c) as the selected option when the reputation score associated with the domain name is below the predefined threshold and is associated with the low probability of the false alarm;

when the selected option is option (a) retrieving content referenced by the content request by the system:

resolve the domain name of the content request to a first routable internet protocol (IP) address;

retrieve the content referenced by the content request from a second server corresponding to the first routable IP address; and

return, to the source of the content request, the content referenced by the content request;

when the selected option is option (b) retrieving the content referenced by the content request in bypass of the system:

resolve the domain name of the content request to the first routable IP address;

return to the source of the content request, a bypass response indicating that the source of the content request should send a second content request to the first routable IP address in bypass of the system to retrieve the content referenced by the content request; and

when the selected option is option (c) block the content request instead of retrieving the content referenced by the content request.

Assignments (10)
RELEASE OF SECURITY INTEREST Recorded Dec 17, 2024
From: JPMORGAN CHASE BANK, N.A.
To: AURA SUB, LLC; INTERSECTIONS, LLC; TWINGATE INC.
Reel/Frame 069616/0097 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 15, 2023
From: PANGO INC.
To: TWINGATE HOLDINGS INC.
Reel/Frame 062984/0748 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 15, 2023
From: TWINGATE HOLDINGS INC.
To: TWINGATE INC.
Reel/Frame 062984/0827 →
RELEASE OF SECURITY INTEREST Recorded Dec 8, 2021
From: JPMORGAN CHASE BANK, N.A.
To: PANGO, INC.; INTERSECTIONS INC.
Reel/Frame 058330/0983 →
SECURITY INTEREST Recorded Dec 7, 2021
From: INTERSECTIONS INC.; PANGO INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 058328/0941 →
SECURITY INTEREST Recorded Jul 2, 2020
From: PANGO, INC.; INTERSECTIONS INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 053105/0591 →
RELEASE OF SECURITY INTEREST Recorded Jul 1, 2020
From: PACIFIC WESTERN BANK
To: PANGO INC. (FORMERLY KNOWN AS ANCHORFREE INC.)
Reel/Frame 053116/0489 →
SECURITY INTEREST Recorded Jun 25, 2020
From: PANGO INC.
To: PACIFIC WESTERN BANK
Reel/Frame 053039/0417 →
CHANGE OF NAME Recorded Jan 10, 2020
From: ANCHORFREE INC.
To: PANGO INC.
Reel/Frame 051566/0680 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 2, 2018
From: LAPIDOUS, EUGENE; MOLCHANOV, MAXIM
To: ANCHORFREE INC.
Reel/Frame 047041/0081 →