67mail

How 67mail works

One address, one password, one clock. Here is the full path a message takes, from the sender to the 24 hour delete.

Updated 18 November 20267 min read

1. Create a mailbox

Signup asks for one thing: how long the mailbox should live. The options are 10 minutes, 1, 3, 6, 12 or 24 hours, or permanent. There is no name, no email and no phone number.

The server generates a 10 character local part and a 20 character password in five groups. The full address is the local part plus 67mail.bond.

The password is hashed with scrypt and a random salt before it is stored. The plain password is shown once on the welcome page, held in memory for that session, then discarded. Save it. There is no reset by email, because there is no other address on the account.

A captcha runs before the account is created. Signups are also limited per IP address.

2. Receive the mail

One address per account goes to Cloudflare Email Routing. A catch all route passes every message to an Email Worker. The Worker posts the raw message to the app over HTTPS with a shared secret.

The app checks the secret, the size and the recipient. Messages over 512 KB are refused. So are messages that would push the mailbox over 2 MB. A refused message produces a bounce for the sender instead of a silent drop.

Accepted mail is parsed into sender, recipient, subject, text, HTML and attachments. The raw message and each attachment are written to disk. A database row points at them.

3. Read it safely

The inbox lists sender, subject, a short preview, the time and an unread marker. Open a message to see the body and any attachments.

HTML mail is cleaned with an allowlist before storage. Scripts, frames, forms and event handlers are removed. The result is served in a sandboxed iframe from a separate route.

Remote images are replaced with a transparent GIF before the page is built. The body policy only allows data images. A tracking pixel never gets a request, so it cannot record an open or an IP address.

Attachments are served with a download disposition. Nothing runs in the browser.

The inbox does not poll. Refresh the page to check for new mail.

4. Let it expire

Every message gets an expiry time 24 hours after delivery. A sweep removes the body, the raw file and the attachments. Reading a message does not extend it.

A temporary account has its own expiry, set at signup. When it passes, the account, its address, its password hash, its sessions and its mail are deleted. A permanent account has no expiry, but its mail still leaves after 24 hours.

You can delete a message, clear the inbox or delete the whole account at any time from the app. Deletion is immediate and there is no recovery.

Limits

ItemValueNote
Per message512 KBAttachments included
Per mailbox2 MBTotal stored mail
Addresses per account1Generated at signup
Lifetime10 min to permanentChosen once
Message retention24 hoursFrom delivery
SendingNoneReceive only
SignupCaptchaNo email confirmation

Security and operations

The app runs behind nginx on a single server. TLS terminates at nginx. The app binds to localhost and is not reachable directly.

The origin only accepts traffic from Cloudflare's edge ranges. Ports 80 and 443 are closed to everything else. Public DNS returns Cloudflare addresses, not the origin.

Sessions use an HttpOnly, Secure, SameSite cookie. There is a per IP limit on signup and login, and a captcha on both forms.

The app has no third party analytics and no ad scripts.

What 67mail is not

  • It is not a sending service.
  • It is not a backup. Every message has a fixed expiry.
  • It is not anonymous from the operator. Stored mail can be accessed for operations and abuse handling.
  • It is not a way around a site's rules. Some services block disposable domains, and that is their choice.

It is a small inbox with a short life. Use it that way.

See it in under a minute.

Create a mailbox, send it a message, and watch the clock. Mail deletes after 24 hours.