Temp Mail in 60 Languages

What changed

TempMailGrab has had a translated interface for a while: buttons, labels, navigation. What it did not have was translated content. Open the German page for a service and you would find German navigation wrapped around English prose explaining what a disposable inbox is and when to use one.

That is now fixed. All 60 languages have their own service pages, their own guide, and their own A–Z directory — written in the language, not machine-passed through it.

Why a half-translated privacy tool is worse than it sounds

For most software, English fallback is a mild annoyance. For a tool whose entire purpose is helping you decide what to share and what not to, it is a functional problem.

The content that matters most on this site is not the button that generates an address. It is the part that tells you when not to use one: do not use a disposable inbox for your bank, for government services, for healthcare, or for any account you will need to recover. That is the advice that prevents someone locking themselves out of something important.

Advice you cannot read is advice that does not work. A visitor who understands "generate" but not the three paragraphs explaining the trade-off gets the tool without the judgement it requires. The interface is the easy half to translate and the less important one.

The second reason: search

There is a practical reason too, and it is worth being open about it.

Search engines treat near-identical pages under different URLs as duplicates and pick one to index, discarding the rest. Publishing 60 language versions of the same English text is not 60 pages — it is one page and 59 rejected copies. That is precisely what happened here: Google rejected several hundred URLs on this site as "Duplicate, Google chose different canonical than user".

The first response was to stop publishing the untranslated versions and redirect them to English. That fixed the duplication by removing the feature, which is a reasonable emergency measure and a bad permanent state — someone searching in Finnish or Tamil got an English page or nothing.

Writing real content in each language fixes it properly. A page that is genuinely different is not a duplicate.

What "properly translated" means here

A few specifics, because "we translated the site" can mean very little:

• URLs are localised, not just the text. The Spanish page for a service lives at /es/mail-for/correo-temporal-netflix, not at the English slug with Spanish text bolted on. Someone sharing that link shares something legible.
• Right-to-left languages actually render right-to-left. Arabic, Hebrew, Persian and Urdu get proper dir="rtl" layout rather than left-to-right text that happens to be in Arabic script.
• Scripts that would produce unreadable URLs use transliteration. A percent-encoded Thai or Urdu path is a wall of escape sequences the moment anyone pastes it into a chat window.
• Nothing falls back mid-page. There is now a build-time check that refuses to generate a page from an incomplete translation, because a page that is 80% translated is the exact failure mode this work existed to remove — and it is invisible until a search console tells you weeks later.

What is still English

Being straightforward about the gaps: the developer API documentation and this blog are English only, and the long-form use-case guides exist in six languages rather than all 60. Those are hand-written pieces, some of them very long, and translating them properly is a different kind of work than the generated pages.

Where a page does not exist in your language, the site links you to what does exist in your language rather than sending you to an English page you did not ask for.

Picking your language

Use the language selector in the header, or go straight to the prefix — /es/, /ja/, /ar/, /hi/ and so on. The tool itself works identically in every language: open the page, get an address, receive mail. Only the explanation of when to use it changes.