# US 2021/0342438 A1 · Platform for generation of passwords and/or email addresses

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

- Number: US 2021/0342438 A1
- Document ID: US20210342438A1
- Status: Published application
- Kind: A1
- Application number: 17/344,389
- Filed: 2021-06-10
- Published: 2021-11-04
- Earliest claimed: 2015-04-30
- Assignees: Phantomkey Technology Limited
- Applicants: Phantomkey Technology Limited
- Inventors: Michael Hugh Thomas DYMOND
- Web page: https://patentgrep.com/patent/US20210342438A1

## CPC

- G06F 21/46: by designing passwords or checking the strength of passwords
- G06F 21/41: where a single sign-on provides access to a plurality of computers
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 9/0861: {Generation of secret information including derivation or calculation of cryptographic keys or passwords}
- H04L 9/0863: {involving passwords or one-time passwords (network architectures or network communication protocols for using one-time keys in a packet data network H04L63/067)}
- H04L 9/3228: {One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key}
- H04L 51/42: Mailbox-related aspects, e.g. synchronisation of mailboxes
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A password and/or email address management platform configured to regenerate a previously generated password for a given web domain or digital system without permanently storing the previously generated password. The platform can operate without maintaining a permanent store or list of other user-related information, e.g. a list of web domains or systems for which passwords have been generated. In an embodiment, the platform performs the steps of concatenating a plurality of password input data elements into a requested phantom password input data string, applying a hashing algorithm to the requested phantom password input data string to generate a phantom password hash, applying a hash-to-string function to convert the phantom password hash to a phantom password, and purging the password generation system of the phantom password after it is notified to a user.

## Claims

### Claim at position 1

1-27. (canceled)

### Claim 28

A method of handling emails sent to a phantom email address, the method comprising:
receiving an email addressed to a complete phantom email address at a processing domain;
generating an email address reference based on the complete phantom email address;
searching in a system database for a stored reference that matches the generated email address reference; and
if a match exists, determining subsequent handling of the email using the domain from which the email was sent.

### Claim 29 (depends on 28)

The method of claim 28, wherein generating the email address reference comprises:
concatenating a plurality of email address reference input elements into an email address reference input data string; and
applying a hashing algorithm to the email address reference input data string to generate a reference email address hash, and
wherein searching in a system database comprises matching the generated reference email address hash with a stored email address hash stored in the system database.

### Claim 30 (depends on 29)

The method of claim 29, wherein the plurality of email address reference input elements comprises:
the complete phantom email address, and
an internal salt selected from a list based on a characteristic of the complete phantom email address.

### Claim 31 (depends on 28)

The method of claim 28, wherein the system database stores email handling instructions in association with a respective domain, and wherein determining subsequent handling of the email includes searching for email handling instructions stored in association with the domain from which the email was sent.

### Claim 32 (depends on 29)

The method of claim 29, wherein:
the stored email address hash is related to a user,
the system database is arranged to store a randomizer for that user, and
the step of determining subsequent handling of the email includes:
concatenating a plurality of domain/key input elements into a domain/key input data string;
applying a hashing algorithm to the domain/key input data string to generate a reference domain/key hash, wherein the plurality of domain/key input elements comprises:
the complete phantom email address;
the domain from which the email was sent; and
an internal salt selected from a list based on a predetermined character of the user's randomizer; and
matching the generated reference domain/key hash to a stored domain/key hash stored on the system database,
wherein email handling instructions are associated with each stored domain/key hash on the system database.

### Claim 33 (depends on 31)

The method of claim 31, wherein the email handling instructions comprise any one of forwarding, holding and deleting the email.
