Email Verification via Embedded Message Identifiers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increasing complexity and legitimacy of phishing emails makes it difficult for recipients to identify authentic emails from fraudulent ones, posing a significant security risk for organizations that rely heavily on email communication.

Innovation Solution

A computing platform that receives an electronic message, identifies its content, generates message-specific identifiers, embeds them into the message, and stores this information for later verification. When a verification request is received, the platform prompts the user to provide authentication information, which is compared to the stored message information to determine the email's validity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If phishing emails become more complex and look more legitimate, then the sophistication of fraudulent emails improves, but the ability of recipients to identify authentic emails from fraudulent ones deteriorates

Engineering Contradiction:
Improveemail authenticity identificationVSAvoidemail verification process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system embeds verification codes in emails during the sending process, so that verification mechanisms are already in place before the recipient needs to verify. This preliminary embedding of authentication data allows recipients to easily verify email authenticity without adding complex verification steps to the email reception process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary verification code embedded in the email that acts as a mediator between the sender and recipient. This code serves as a trusted indicator that recipients can check to determine email authenticity, resolving the contradiction by providing a simple verification mechanism that doesn't require complex analysis of email content.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If email verification systems rely on email provider technological standards, then integration with existing email infrastructure is improved, but the ability to operate independently of specific providers deteriorates

Engineering Contradiction:
Improveprovider-agnostic verificationVSAvoidverification system implementation
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The verification system is designed to be universal and provider-agnostic, working with emails from any email provider. The embedded verification codes and validation mechanisms are not tied to specific email infrastructure standards, allowing the system to function independently of any particular email provider while maintaining ease of implementation through standardized processes.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If users manually verify each email, then email security verification improves, but the time and effort required for verification deteriorates

Engineering Contradiction:
Improveemail verification accuracyVSAvoidverification time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The verification system enables users to easily verify email authenticity themselves through simple actions like checking embedded verification codes or using provided validation tools. This self-service approach allows users to verify emails accurately without requiring extensive time or external assistance, as the verification mechanisms are designed to be user-friendly and quickly accessible.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250069041A1Electronic Mail Verification
Publication Date: 2025.02.27 BANK OF AMERICA CORP
  • US20250069041A1 patent drawing
  • US20250069041A1 patent drawing
  • US20250069041A1 patent drawing

AI summary

Aspects of the disclosure relate to email verification. A computing platform may receive an electronic message and identify one or more portions of content in the message. Then, the computing platform may generate and embed one or more message-specific identifiers into the electronic message and store electronic message information associating the one or more portions of content with the one or more embedded message-specific identifiers. Thereafter, the computing platform may receive an electronic message verification request to verify authenticity of an identified electronic message received by a computing device. The computing platform may prompt a user of the computing device to provide authentication information associated with one or more portions of content of the identified electronic message. Based on comparing the authentication information provided by the user to the stored electronic message information, the computing platform may determine whether the identified electronic message is valid and send a notification accordingly.