FFree Domain MailFREE
Sign inCreate accountOpen app →
Open menu

Free reference

Safe Test Data

Reserved domains, IP ranges, fictional phone numbers and test email addresses you can paste into any form, fixture or screenshot.

Generate a test email that really receives mail

A reserved address like test@example.com never delivers anywhere. For a sign-up that sends a code, make a live public inbox instead.

Test address
ethanyoung8632@freedomainmail.info

Public inbox: anyone who knows the address can read it. Use it for tests only.

Safe test data is made of values that standards or regulators have set aside, so they can never reach a real person, server or phone. This page lists them with a copy button each, and lets you make a live public inbox when a test needs an email that really arrives.

Which domains are safe to use in test data?

Two standards set aside names that will never be sold or delegated, so nothing you test with can reach a stranger's website or inbox. Use these instead of a made-up domain, which someone may own.

ValueWhat it isUse it for
example.comReserved example domainSample email addresses and URLs in documentation and fixtures
example.netReserved example domainA second name when a test needs two different domains
example.orgReserved example domainA third name for multi-domain tests
mail.exampleName under the reserved .example top-level domainHostnames that can never resolve on the public internet
app.testName under the reserved .test top-level domainTest environments, CI jobs and mocked DNS
nobody.invalidName under .invalid, guaranteed never to existLookups and delivery that must fail on purpose
app.localhostLoopback name under .localhostYour own machine during development

Sources: RFC 2606 (reserved domain names) and RFC 6761 (special-use domain names).

Which IP addresses are reserved for examples?

These blocks are set aside for documentation and are never assigned to anyone, so an address from them cannot point at a real server or person.

RangeExample addressFamily and source
192.0.2.0/24192.0.2.1IPv4, TEST-NET-1 (RFC 5737)
198.51.100.0/24198.51.100.23IPv4, TEST-NET-2 (RFC 5737)
203.0.113.0/24203.0.113.42IPv4, TEST-NET-3 (RFC 5737)
2001:db8::/322001:db8::1IPv6 documentation prefix (RFC 3849)

Sources: RFC 5737 (IPv4 documentation blocks) and RFC 3849 (IPv6 documentation prefix).

Which phone numbers are safe to use in tests?

A random phone number is a stranger's phone. These ranges are reserved for fiction, or withdrawn, so a number from them cannot ring a real subscriber. They are the same ranges our random identity generator uses.

CountryReserved rangeExample
United States(any area code) 555-0100 to 555-0199(212) 555-0142
United Kingdom, mobile07700 900000 to 07700 90099907700 900123
United Kingdom, London020 7946 0000 to 020 7946 0999020 7946 0123
Australia, mobile0491 570 006 to 0491 570 1590491 570 042
Australia, landline(0X) 5550 xxxx(02) 5550 1234
VietnamNo official fiction range; the retired 0123 mobile prefix (withdrawn in 2018) no longer connects0123 456 7890

Sources: the North American fiction range 555-0100 to 555-0199, Ofcom's numbers for TV and radio drama, ACMA's fictitious numbers. Vietnam publishes no such range.

Which email addresses can I use for testing?

Addresses on reserved domains are safe because mail to them is never delivered to a person. That also means they prove nothing about delivery, so use them for format and storage tests, not for receiving.

AddressWhat happens to mailUse it for
test@example.comNot delivered to anyoneFixtures, screenshots, documentation
user@example.orgNot delivered to anyoneSecond user in a test
qa+signup1@example.netNot delivered to anyonePlus-tag handling in a form
jane@mail.exampleThe domain can never resolveHostname that must not exist
dev@app.testOnly exists inside your own test setupMocked mail in CI
bounce@nobody.invalidAlways fails to deliverBounce and error handling

Sources: RFC 2606 and RFC 6761 for the domains; the address names are ours. For an address that really receives mail, use the live inbox at the top of this page.

Why use reserved test values instead of made-up ones?

A made-up domain may belong to someone, a random phone number rings a stranger and a guessed IP address may be a real server. Reserved values remove that risk: the example domains and the .test and .invalid names are never sold, the documentation IP blocks are never assigned and the fictional phone ranges are never given to subscribers.

They also keep your data honest. Anyone reading a fixture, a bug report or a screenshot can see at once that the value is a placeholder, and a leaked test database exposes nobody.

You needUseBecause
A domainexample.com, example.net, example.orgReserved for examples, never sold
A hostname that must failanything.invalidGuaranteed never to exist
An IP address192.0.2.1, 198.51.100.23, 203.0.113.42, 2001:db8::1Documentation blocks, never assigned
A phone numberA number from the fictional range of its countryCannot reach a subscriber
An email that must arriveA live public inbox from this pageReserved domains deliver nowhere

Can I receive mail at example.com?

No. Mail sent to an example domain is not delivered to a person, which is exactly why it is safe, and why it cannot test anything about delivery. A sign-up flow that emails a confirmation code, a password reset or an invoice needs an address whose inbox you can read.

That is what the live inbox at the top of this page is for. It creates a real public address on one of our temp-mail domains, and messages sent to it appear on the page within seconds. Anyone who knows the address can read it, so use it for tests only. For a private address you can keep, a free account is the next step, and the email validator shows how a form is likely to judge an address before you try it.

What about payment and identity test values?

We deliberately do not list payment, banking or identity numbers here, not even as test data. For payment flows, use the test mode and the test values in your payment provider's own documentation. For names, addresses and phones as a set, the random identity generator builds a made-up person from the safe ranges above, and the password generator makes a strong password for the test account.

Frequently asked questions

Is this safe test data free?

Yes. The tables are free to copy and the live inbox needs no sign-up. Nothing you copy is sent to us.

Why not just use my own email address for testing?

Test mail can end up in real inboxes, mailing lists and logs. A reserved address cannot, and a live public inbox keeps test mail away from your personal one.

Is example.com a real website?

The name exists so it can appear in documentation, and a page does load there, but it is not for you to use. Mail addressed to it is not delivered to a person.

Why are the IP addresses 192.0.2.x and 203.0.113.x?

Those blocks are reserved for documentation and examples and are never assigned to a network, so a request to one cannot reach a real machine on the public internet.

Are these phone numbers real?

No. They come from ranges that telephone regulators set aside for fiction or have withdrawn. Vietnam has no official fiction range, so the example uses the retired 0123 prefix, which no longer connects.

Can I get a test email that really receives mail?

Yes, use the live inbox at the top of the page. It opens a public address, and a code or message sent there shows up on the page. See also temp mail for OTP codes.

Where can I find payment test values?

In your payment provider's own test mode documentation. We do not list any, on purpose.

Need a test address you can keep? A free account holds a private address and lets you send and reply from it.