Guerrillamail.com

Custom domains add an access choice

Guerrilla Mail says visitors receive a random address without registration, while the About page also says users can choose an address. The homepage says users can use a domain they own with the service.

For a custom domain, arriving email can be accessible only to the domain owner or shared with everyone. That distinction matters when deciding whether an inbox is intended for one person or shared access.

The homepage describes the service as protection from spam.

The API keeps inboxes session-bound

Guerrilla Mail describes a public JSON API over HTTP, with results returned as JSON-encoded strings. Its documentation says each request must include function, end-user IP, and user-agent parameters.

Clients must retain and send the PHPSESSID cookie to maintain session state. The documentation limits fetching to email owned by the current session ID. Fetched message bodies have filtered HTML, including scripts, applets, and iframes.

The API documentation advises clients not to check email too frequently, to avoid overloading the server. Its `check_email` function returns a maximum list of 20 messages.

Custom-domain access costs annually

The homepage, About page, and terms page list the domain service price and payment methods, checked 2026-10-31.

• Homepage: domain option at $9.99 USD per year; Bitcoin and PayPal listed for payment (checked 2026-10-31).
• About page: custom-domain email service at $9.99 USD per year; Bitcoin and PayPal accepted (checked 2026-10-31).
• Terms page: custom-domain access at $9.99 USD per year; Bitcoin and PayPal listed for the domain service (checked 2026-10-31).

The provider’s About page lists custom-domain email service at $9.99 USD per year.

Confirm setup before depending on the API

Before building around the API, ask the provider what setup a client needs. General integration checks should establish which systems the service supports and what configuration each connection requires.

Ask whether a client must preserve any additional state beyond the documented session cookie. Confirm how the provider expects clients to handle returned message content, and what response behavior to plan for when requests are made too frequently.

These are questions to resolve with the provider before committing a workflow to the integration. The available documentation should be checked against the client’s own technical requirements.

Registration-free access covers core tasks

• The provider says registration is not required and a random address is supplied on arrival.
• Users can choose an address, and the homepage says a domain they own can be used.
• For custom-domain email, access can be limited to the owner or shared with everyone.
• The API returns JSON-encoded strings, and fetched email bodies have filtered HTML.

Expiry and access rules narrow use

The Terms page says service is provided as-is, without express or implied warranties. It also disclaims responsibility for third-party resources and message content, including attachments.

• Anyone who knows an inbox ID may access that inbox.
• The API documentation says a session can expire after about 18 minutes of inactivity.
• For terms breaches or service abuse, the Terms say the vendor may terminate a license and delete data without notice or a specific reason.

See “What we could not confirm” for details that remain unresolved.

Compare inbox lifetime and access models

When comparing temporary email services, check how long messages remain available and whether inbox access is private or shared. Also compare sending capability, API scope, and any paid options. Match those conditions to the workflow before choosing a service.

Short-lived receiving defines the fit

Guerrilla Mail describes itself as a disposable temporary email address service. The service does not require registration and provides a random address when visited.

It is a poor fit when messages must remain available beyond the deletion window or when inbox access must be private. The service says anyone who knows an inbox ID may access its inbox.

Before relying on it, check whether the message’s expected lifetime and access requirements match these conditions.

Answers on inbox expiry and API use

How long does an inbox last?

The provider says email delivered to an inbox is deleted after 1 hour. Its homepage states that temporary email addresses last 60 minutes. The API documentation also says addresses expire after 60 minutes. These statements describe the service’s temporary window, not message retention beyond it.

Who can access an inbox?

Anyone who knows an inbox ID may access that inbox, according to the About page. The API documentation says clients can fetch email owned by the current session ID. These are distinct access conditions: the first describes inbox access, while the second describes the API’s session boundary.

What does the API require?

The API documentation requires each request to include function, end-user IP, and user-agent parameters. The documentation also advises against checking email too frequently to avoid overloading the server.

What does the API return?

The API returns JSON-encoded strings, and fetched message bodies have filtered HTML. The `check_email` function returns a maximum list of 20 messages, according to the API documentation. The documentation says the API may be rate limited.

How can users contact support?

The About page asks users to contact the service through Facebook or Twitter in English, and says it cannot always reply. The API documentation provides a support email for developers who created a Guerrilla Mail app. These are the contact routes described in the provider’s materials.

What do the terms say about outgoing email headers?

The Terms page says outgoing email will include an X-Originating-IP header with the listed address. This statement concerns outgoing email headers; it does not describe other message handling. The Terms page also disclaims responsibility for email message content, including attachments.

Proceed only when temporary access fits

Fits if temporary receiving meets the workflow’s retention needs and custom-domain access suits its setup.

Probably not if messages need longer retention or the workflow requires a warranty; the Terms page provides the service as-is.

Main risk… inbox access is available to anyone who knows the inbox ID, and the Terms permit license termination and data deletion under stated conditions. Check the access model before relying on the service.

Sources

Sources of the facts above: public pages, each with the date it was checked.

• www.guerrillamail.com/aboutchecked 2026-10-31
• www.guerrillamail.comchecked 2026-10-31
• www.guerrillamail.com/GuerrillaMailAPI.htmlchecked 2026-10-31
• www.guerrillamail.com/toschecked 2026-10-31

How this page was prepared

Editorial team of Traffic Gazette. Everything here comes from the public sources above, checked on 2026-10-31; the text was written by Traffic Gazette. No hands-on trial of the service took place. When the sources are updated, so is this page.

Last updated: 2026-10-31

Right of reply

Speaking for Guerrillamail.com? If you believe the entry is inaccurate or stale, send us proof. A documented refutation leads to a correction or removal of the entry. Money does not remove or soften an entry here.

Our contact for replies

No data available

Response time

No data available

Contact · Affiliate disclosure

Other reviews in this category: Disposable email

• Crazymailing.com — Disposable email
• Tempr.email — Disposable email