# US 2023/0412625 A1 · System and Method for Determining If a Sender's Email is being Eavesdropped On

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

- Number: US 2023/0412625 A1
- Document ID: US20230412625A1
- Status: Published application
- Kind: A1
- Application number: 18/124,419
- Filed: 2023-03-21
- Published: 2023-12-21
- Earliest claimed: 2022-06-20
- Inventors: Zafar Khan
- Web page: https://patentgrep.com/patent/US20230412625A1

## CPC

- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04L 63/1475: {Passive attacks, e.g. eavesdropping or listening without modification of the traffic monitored}
- H04L 63/1483: {service impersonation, e.g. phishing, pharming or web spoofing (detection of rogue wireless access points H04W12/12)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system and method and analyzer for determining if HTTP requests generated by user interaction with an email is an activity of an intended recipient. At least one link is added into an email sent by a sender, wherein the link automatically extracts data associated with the link when the email is opened at a recipient. A server receives receive HTTP requests at an internet address when a received email is opened at the recipient. Opening the email at the recipient automatically activates the link that is configured to automatically extract data associated with the link. An analyzer makes a determination, as to whether the data returned associated with the HTTP request include indicators that the HTTP request was not initiated by the intended recipient.

## Claims

### Claim 1

A system for determining if HTTP requests generated by user interaction with an email is an activity of an intended recipient, wherein a link is embedded in the email and configured to automatically extract, said system comprising:
a link adding module configured to add at least one link into an email sent by a sender, wherein the link is configured to automatically extract data associated with the link when the email is opened at a recipient; and
a web server, including:
a processor programmed using hardware and/or software commands, wherein the processor is configured to receive HTTP requests at an internet address when a received email is opened at the recipient, said opening of the email automatically activating the link that is configured to automatically extract data associated with the link;
at least one database comprising parameters related to email opens, and
an analyzer configured to make a determination, based on said parameters, as to whether the data returned associated with the HTTP request include indicators that the HTTP request was not initiated by the intended recipient.

### Claim 2 (depends on 1)

The system of claim 1, wherein the analyzer is further configured to determine if there is an additional HTTP request record at a different location than a location that the sender of the email indicates is an expected location, and record the determination in a database associated with the analyzer.

### Claim 3 (depends on 2)

The system of claim 2, wherein the analyzer is further configured to determine if there is an additional HTTP request record at a different country location from the declared home country or determined home country of the initial recipient, and record the determination in a database associated with the analyzer.

### Claim 4 (depends on 2)

The system of claim 2, wherein the analyzer is further configured to determine if there is an additional HTTP request record at a different country location from the home country of the sender and records the determination in a database associated with the analyzer.

### Claim 5 (depends on 2)

The system of claim 2, wherein the analyzer is further configured to determine if there is an additional HTTP request record at a country location that is in a list of countries as a parameter at the analyzer and records the determination in a database associated with the analyzer.

### Claim 6 (depends on 2)

The system of claim 2, wherein the analyzer is further configured to determine if there is an additional HTTP request record at an ISP or VPN provider IP range that is in a list of ISP or VPN provider IP ranges as a parameter at the analyzer and records the determination in a database associated with the analyzer.

### Claim 7 (depends on 2)

The system of claim 2, wherein the analyzer is further configured to determine if there is an HTTP request record that includes device information that is in a list of device information parameters at the analyzer and records the determination in a database associated with the analyzer.

### Claim 8 (depends on 1)

The system of claim 1, wherein the result of the analyzer is retained in a report.

### Claim 9 (depends on 8)

The system of claim 8, wherein the report is returned to at least one of the sender and an administrator associated with the sender.

### Claim 10 (depends on 9)

The system of claim 9, wherein the report contains an aggregate of the records for an associated group of senders.

### Claim 11 (depends on 8)

The system of claim 8, wherein the report is rendered tamper-detectable.

### Claim 12 (depends on 8)

The system of claim 8, wherein the report contains a portion of the HTTP record.

### Claim 13 (depends on 1)

The system of claim 1, wherein the at least one database includes a database of IP address ranges for respective countries.

### Claim 14 (depends on 1)

The system of claim 1, where the at least one database includes a database of IP address ranges of high-risk Virtual Private Networks (VPNs) networks, mobile devices, and high-risk Content Delivery Networks (CDNs).

### Claim 15

A method for determining if HTTP requests generated by user interaction with links or with links configured to automatically extract in an email is an activity of an intended recipient of the email, said method comprising:
1) adding a tracking link to a sent email;
2) recording an opening of the email by one or more devices via a tracking link server;
3) extracting and parsing HTTP data associated with the opening(s) of the email;
4) populating a database with the HTTP data, including at least the internet protocol (IP) address of the connection with the one or more devices opening the email;
5) analyzing geolocation data associated with the intended recipient and the one or more devices opening the email; and
6) performing a comparative analysis assessing risk of email interception.

### Claim 16 (depends on 15)

The method of claim 15, further comprising:
7) populating said database with the IP address of the sender that is parsed from the HTTP open tracking data; wherein the comparative analysis further comprises the steps of:
8) comparing whether the recipient country differs from the sender country or the sender's declared home or safe geolocations, based on IP addresses or sender declarations;
9) comparing where there are two openings associated with the same recipient email, and whether the openings occurred in different countries from one another; and
10) generating and transmitting a report to the sender and/or sender administrator, wherein the report indicates a risk factor associated with each recipient of the email, and wherein the risk factor is computed based on geolocation.

### Claim 17 (depends on 16)

The method of claim 16, wherein the risk factor is further computed based on at least one of the following:
the type of device the email was opened on;
whether a VPN was used; and
whether the click was human-generated or bot-generated.

### Claim 18 (depends on 15)

The method of claim 15, wherein the HTTP open data captured IP address is compared to an IP address geolocation database.

### Claim 19 (depends on 15)

The method of claim 15, further comprising the step of transmitting alerts upon given criteria being met.

### Claim 20

An analyzer that is configured to:
receive an HTTP request that is associated with an email message ID of an email opened at one or more devices opening the email;
extract and parse received HTTP data associated with the HTTP request;
populate a first database with the HTTP data, including from the HTTP data the internet protocol (IP) address of the connection with the one or more devices opening the email as a first information;
access a second database or a subsection of the first database, that contains at least one of geolocation or network owner data associated with the internet protocol (IP) address or other information in the HTTP data in the first information, which is a second information;
access a third database or an additional subsection of the first database that contains at least one of IP addresses, IP address ranges, network owner, or device user agent data that is flagged with a risk level indicative of email interception by at least one unauthorized third party, which is a third information;
compare at least a portion of the first information with at least a portion of the third information, or compare at least a portion of the second information with the at least a portion of the third information to determine if at least a portion of the first or the second information matches the at least portion of the third information; and
if at least a portion of the first information or second information matches the at least portion of the third information, generate a report with a risk indication that indicates that the one or more devices opening the email were not intended devices.
