Random Fake Email Generator
Save on Google Your fake emails
Email settings
Alias style
Runs in your browser. Nothing is stored or sent. Addresses at reserved domains cannot receive mail, so do not use them to sign up for real services.
Related tools
| Tool | What it does |
|---|---|
| Random Word Generator | Generate random nouns, verbs and adjectives for games, writing prompts and brainstorming. |
| Random PIN Generator | Create unguessable 4-digit, 6-digit or custom PINs with weak-PIN filters. |
| Random Number Generator | Pick random numbers in any range, with sorting and unique-number options. |
| Random Team Generator | Split names into balanced, color-coded teams and share them with a link. |
| Random Country Generator | Pick a random country with its flag, capital, population and ISO codes. |
RFC Fictional Reserved Domain Reference
Click any highlighted item to copy it. Only the names reserved by RFC 2606 and RFC 6761 are guaranteed safe for fake email addresses.
Showing 70 of 70 entries
| Domain / Item | Type | RFC / Reference | Notes & Typical Use |
|---|---|---|---|
| Reserved second-level domain | RFC 2606 | For documentation and examples; it can never be registered by anyone | |
| Reserved second-level domain | RFC 2606 | For documentation and examples; mail cannot reach a real person | |
| Reserved second-level domain | RFC 2606 | For documentation and examples; also reserved by RFC 6761 | |
| Reserved top-level domain | RFC 2606, RFC 6761 | For testing DNS software and test environments; never resolves publicly | |
| Reserved top-level domain | RFC 2606, RFC 6761 | For examples in documentation, such as mail.example | |
| Reserved top-level domain | RFC 2606, RFC 6761 | For names that are obviously invalid, used as placeholders | |
| Reserved top-level domain | RFC 2606, RFC 6761 | Names under it resolve to the local machine | |
| Special-use name | RFC 6761 | Resolves to the loopback address, 127.0.0.1 or ::1 | |
| Special-use top-level domain | RFC 7686 | Tor hidden services; never resolved by normal DNS | |
| Special-use top-level domain | RFC 6762 | Multicast DNS on a local network | |
| Special-use domain | RFC 8375 | Names for devices on a home network | |
| Special-use top-level domain | RFC 9476 | Alternative, non-DNS naming systems | |
| Private-use top-level domain | ICANN, 2024 | Reserved by ICANN for private use; not delegated in the global DNS | |
| Infrastructure domain | RFC 1035 | Reverse DNS lookups for IPv4 addresses | |
| Infrastructure domain | RFC 3596 | Reverse DNS lookups for IPv6 addresses | |
| IPv4 documentation range | RFC 5737 | TEST-NET-1, for examples and documentation | |
| IPv4 documentation range | RFC 5737 | TEST-NET-2, for examples and documentation | |
| IPv4 documentation range | RFC 5737 | TEST-NET-3, for examples and documentation | |
| IPv6 documentation prefix | RFC 3849 | The classic IPv6 prefix for examples | |
| IPv6 documentation prefix | RFC 9637 | A larger IPv6 documentation block added in 2024 | |
| 16-bit AS numbers for documentation | RFC 5398 | Fictional autonomous system numbers for examples | |
| 32-bit AS numbers for documentation | RFC 5398 | Fictional 32-bit autonomous system numbers for examples | |
| MAC addresses for documentation | RFC 7042 | EUI-48 addresses reserved for examples | |
| Local part maximum | 64 octets | RFC 5321 | The part before the @ sign may not exceed 64 octets |
| Whole address maximum | 254 characters | RFC 5321, errata to RFC 3696 | The practical limit for an address in an SMTP path |
| Domain label maximum | 63 octets | RFC 1035 | Each dot-separated part of a domain name |
| Domain name maximum | 253 characters | RFC 1035, RFC 5321 | Length of a full domain name in text form |
| Allowed local-part characters | Letters, digits and ! # $ % & ' * + - / = ? ^ _ ` { | } ~ | RFC 5322 atext | This tool only uses lowercase letters, digits and . _ - + |
| Dot rules | No leading, trailing or double dots | RFC 5322 dot-atom | Unquoted local parts cannot start or end with a dot |
| Quoted local parts | "john doe"@example.com | RFC 5322 quoted-string | Valid in theory but rejected by many systems |
| Case sensitivity | Domain: no. Local part: yes in theory | RFC 5321 section 2.4 | Most providers ignore case in the local part |
| Subaddressing | user+tag@example.com | RFC 5233 and provider rules | The + separator is common but chosen by each mail provider |
| Display names | Name <address> | RFC 5322 name-addr | A friendly name followed by the address in angle brackets |
| International addresses | UTF-8 local parts | RFC 6531 (SMTPUTF8) | Needs support at every server that handles the message |
| Name: first.last | example.com | The most common test-user format | |
| Name: f.last | example.net | Initial plus last name | |
| Name: first.l | example.org | First name plus last initial | |
| Name: last.first | mail.test (.test) | Surname first, on a reserved TLD | |
| Name: underscore | example.com | Underscore separator | |
| Name: hyphen | example.net | Hyphen separator | |
| Name: no separator | example.org | Joined first and last name | |
| Handle | example.com | Adjective and noun | |
| Handle: hyphen | mail.example (.example) | Adjective and noun with a hyphen | |
| Random string | mail.invalid (.invalid) | 10 random characters, starting with a letter | |
| Random string | example.net | 12 random characters | |
| Plus alias | example.com | Base address plus a tag | |
| Plus alias with digits | example.org | Tag with random digits added | |
| Sequence | example.com | Numbered accounts for QA and load tests | |
| Sequence with prefix | example.net | Custom prefix before the number | |
| Sequence on localhost | localhost | Only works on your own machine | |
| First-name pool | 60 names | This tool | Used by Name and Plus alias styles |
| Last-name pool | 60 names | This tool | 60 x 60 = 3,600 name combinations |
| Handle pool | 40 adjectives x 40 nouns | This tool | 1,600 combinations before digits |
| Random string | Up to 16 characters | This tool | A letter first, then a-z and 0-9 |
| Plus alias tags | 10 tags | This tool | shop, news, signup, test, trial, promo, travel, forum, game, work |
| Uniqueness | Unique within a batch | This tool | Digits are added automatically if names run out |
| Batch size | 1 to 5,000 | This tool | The list shows the first 200; Copy All and downloads include every address |
| CSV columns | email, local_part, domain, display_name, first_name, last_name, style | RFC 4180 | Comma separated with quoted fields and CRLF line ends |
| Share link parameters | ?domain=example.com&count=10 | This tool | Also style, pattern, sep, len, prefix, digits and names |
| Randomness | crypto.getRandomValues() | Web Crypto API | Generated in your browser; nothing is sent to a server |
| Use reserved domains | Always for test data | RFC 2606 | Reserved names cannot belong to anyone, so test mail cannot reach a real person |
| Why not test.org or test.com | Not reserved | RFC 2606 | They are ordinary domains that other people have registered, so avoid them |
| Do not sign up with them | No inbox | Common sense | Reserved-domain addresses cannot receive confirmation emails |
| Need a real inbox? | Use your own | Best practice | Use plus addresses on a mailbox you own, or a testing mail service |
| Documentation and READMEs | example.com | RFC 2606 | The standard choice for tutorials, manuals and screenshots |
| Unit and CI tests | Reserved domains | Best practice | They prevent accidental real emails from test runs |
| Staging environments | Allow-list only | Best practice | Block outbound mail except to approved or reserved test domains |
| Demos and screenshots | Fake addresses | Privacy | Avoid exposing real customers' addresses |
| Validation testing | Valid and invalid cases | RFC 5322 | Test dots, plus signs, long local parts and domain limits |
| Bulk imports | CSV export | RFC 4180 | Load addresses into databases, CRMs and spreadsheets |
Frequently asked questions
| Question | Answer |
|---|---|
| What domains are safe for fake email addresses? | RFC 2606 reserves example.com, example.net and example.org, plus the top-level domains .test, .example, .invalid and .localhost. Nobody can register them, so addresses such as user@example.com can never reach a real person. |
| Is test.org a reserved domain? | No. RFC 2606 does not reserve test.org or test.com. They are ordinary domains that other people can own, so mail sent to them might reach someone. Use example.com, example.net, example.org, or a name under .test such as mail.test instead. |
| Can these fake emails receive mail? | No. Addresses at reserved domains cannot receive messages, so you cannot use them to confirm a sign-up. They are meant for documentation, demos, automated tests and sample data. |
| What are the alias styles? | Name creates realistic names like maria.santos, Handle creates readable pairs like swift.otter, Random creates strings like k7x2m9qa4p, Plus alias adds a tag such as maria+shop, and Sequence creates numbered accounts such as user0001 for QA and load tests. |
| How do I export many addresses at once? | Set how many emails you want, up to 5,000, then press Generate Emails and use Download CSV. The file includes the email, local part, domain, display name, first and last name and style. Copy All and Download TXT give you plain lists. |
| How do I share my settings with a link? | Copy the share link, which looks like ?domain=example.com&count=10. Anyone who opens it gets the generator with the same domain, count and style already chosen, and a fresh set of random addresses. |