Keeping Track of the Addresses You Make

Stage: several addresses at once. In control: you.

1. A genuinely disposable address does not need remembering

If an address exists to catch one code and then disappear, there is nothing to keep track of. You read the message, you use what was in it, and the mailbox goes. The bookkeeping problem appears at one specific moment: when an address outlives the task it was created for.

That moment is the whole subject here. Everything that feels like clutter in a set of generated addresses is a symptom of addresses that were meant to last minutes and ended up lasting weeks.

2. The unit being counted is an address, and an address costs nothing to hold

A generated address is not an account. It has no password, no second factor, no recovery path, no settings and no inactivity counter watching it. There is nothing to maintain, nothing to review annually and nothing to secure, because there is nothing behind the string except a timer.

That changes the arithmetic completely. Advice about limiting how many mailboxes you run exists because each real mailbox costs attention. These cost none. The constraint that shapes a set of permanent accounts simply is not present here, so copying the same instinct across produces the wrong answer.

3. The right number is one address per task, not one per week

Generate a new address for each form rather than reusing a favourite for a few days. The reason is mechanical rather than moral. One address used on five sites means five senders arriving in one mailbox, which makes the box harder to read and gives you one shared point of failure: when that mailbox goes, all five things go with it at once.

Five separate addresses fail separately, which is the entire benefit. Each one carries one relationship, expires on its own schedule and takes nothing else with it. Since making another one is free and instant, there is no reason to economise on a resource that does not run out.

4. When something is worth writing down, three fields cover it

If an address needs recording, record the address, the service it was used on and the date. Nothing else has ever proved useful. A note about what the mailbox contained is worthless a day later, because the mailbox is gone.

Where to put those three fields is a solved problem: your password manager already stores one entry per service, and the address belongs in the username field of that entry, next to the credentials for the same site. A separate spreadsheet of disposable addresses becomes stale within a week and gets consulted never. Use the tool that is already open at the exact moment you need the answer.

5. As a guest there is nothing to track, because there is nothing to track with

Worth being blunt about the starting position. A guest holds exactly one mailbox, it is tied to a cookie in the browser you are sitting in, and generating a replacement deletes the previous one and its contents on the spot rather than parking it somewhere. There is no list, no history and no second tab holding a different address. The only ledger is the page in front of you.

That is why the bookkeeping question is really a question about scale. One address at a time needs no system. The moment a task wants two live addresses, the browser session stops being able to represent the situation at all, and whatever you write down is the only record that exists.

6. A free account is the built-in answer to this question

Ten mailboxes running at once, everything cleared a week after you last signed in, and no single message surviving past thirty days whatever else happens. That is the shape of the answer when one address per task starts producing more addresses than a browser session can hold.

The account also unlocks domains that are not listed publicly, attachments, and a mailbox that is not readable by anyone who happens to know the string. It costs nothing, there is no paid tier above it, and the service is funded by advertising rather than by upselling you. What it does not do is turn a disposable address into a permanent one: the timers are longer, not absent.

7. One symptom tells you a task has outgrown this kind of address

The signal is precise: you feel the need to write an address down so that you can come back to it next month. That impulse means the mailbox has to survive longer than the mailbox is built to survive, and no amount of note-keeping fixes a mailbox that will not be there.

At that point the task needs a real address, or it needs no account at all, which is more often available than people expect. What it does not need is a disposable address propped up with reminders. The other half of the same warning is what happens when the string is handed to somebody else.

8. A written-down address decays in a way a written-down account does not

Here is the trap in any list of disposable addresses that survives a few weeks. An entry in a password manager for a permanent account stays true until you change something. An entry naming a generated address stops being true on its own, and worse, it can become true about somebody else.

The mechanism is simple. Once a mailbox expires the string goes back into circulation, because the alternative is a permanent register of every name ever issued, which is exactly the sort of record this service exists not to keep. Nothing stops the same word pair and the same four digits being handed to the next visitor who presses the button. Your note still says that address belongs to that account; the mail it now attracts lands in a stranger's inbox instead. That is the whole argument of what happens when the same address comes back, and it is the reason a date column earns its place in the note: an entry older than a day is describing something that no longer exists.

Automation has the same problem in a different shape. An inbox created through the interface returns an identifier, and that identifier, not the address string, is the handle worth storing for the length of a test run. A key may hold a hundred live inboxes at once and each one expires a day after it was made, so anything that keeps a list of addresses without keeping their creation times is building a list that quietly turns into fiction.

9. An address you no longer need requires nothing from you

There is no closing procedure. You do not unsubscribe, delete, deregister or tidy. The mailbox expires twenty four hours after its last use, or immediately if you ask for a new address, and that is the end of it.

The absence of an exit step is a property of the tool rather than a missing feature. Every permanent account you open is a small debt you will service for years; a generated address is settled the moment you stop looking at it. Keeping that difference clear is most of what good address hygiene amounts to.

The handover

Your control over these addresses ends the moment you paste one into a form, and after that the copies multiply somewhere you cannot see: a single signup usually spreads your address across four or five systems, each with its own retention rules and its own idea of who you are. That is also why changing an address later is expensive on the far side, for reasons set out in why the address makes a poor user id. Your side of the arrangement stays simple, and the next address is waiting on the front page.