Disposable email
Guerrillamail.com
Guerrilla Mail deletes inbox email after 1 hour, according to its About page. Its homepage says temporary addresses last 60 minutes, and the About page says anyone who knows an inbox ID may access that inbox. The disposable-address offer therefore comes with a short window and an access condition.
Editorial review based on public sources, without hands-on testing; facts checked on 2026-10-31.
This page contains no partner link to this service.
- Logo
Service logos remain the property of their owners; we use them for identification only.- Name
- Guerrillamail.com
- Category
- Disposable email
- Official site
- guerrillamail.com · No link provided
- Facts checked
Random addresses and inbox access
The homepage and About page describe the address options and access terms, checked 2026-10-31.
- Registration: not required, according to the homepage.
- Starting address: a random address is provided on arrival, according to the About page.
- Address choice: users can choose their own email address, according to the About page.
- Address duration: the homepage states 60 minutes.
- Inbox access: anyone who knows the inbox ID may access it, according to the About page.
Custom-domain access costs separately
Custom-domain email service is listed at $9.99 USD per year on the About page. The homepage and Terms also list the domain option at $9.99 USD per year. These are vendor-listed prices, not a comparison of available plans.
The provider lists Bitcoin and PayPal as payment methods for the domain service, according to its Terms. The homepage and About page also name those payment methods.
With a domain the user owns, incoming email can be accessible only to the domain owner or shared with everyone, according to the homepage. The About page describes the same two access choices for custom-domain email.
Disposable mail and the Go-Guerrilla project
Guerrilla Mail describes its service as disposable temporary email and says it provides protection from spam. The provider says its email is powered by the open-source Go-Guerrilla project.
The About page says the website uses a session cookie and may use preference and third-party cookies. It also states that the site is accessible only through HTTPS encryption. The homepage identifies Jamit Software Limited as copyright holder. The Terms identify the holder for 2006–2026.
API sessions, requests, and message limits
The API documentation describes a public JSON API over HTTP. Each request must include a function, end-user IP, and user-agent parameters, according to the documentation. Clients must retain and send the PHPSESSID cookie to maintain session state.
A client can fetch only emails owned by its current session ID, the documentation states. API results are returned as JSON-encoded strings. Fetched email bodies have HTML filtered, including scripts, applets, and iframes, according to the provider.
The check_email function returns a maximum list of 20 messages, according to the API documentation. This is a message-list cap, separate from the session and request requirements.
Extension and session timing in the API
The API’s extend function adds one hour to an email address, with a maximum extension of two hours, according to the documentation. Before relying on it, ask support how the extension behaves for an address already near expiry. This is a clarification request, not a different stated limit.
The API documentation says a session can expire after about 18 minutes of inactivity. It separately states that email addresses expire after 60 minutes. Ask support how clients should handle a session expiring before an address does, and what response to expect when the session is no longer active.
The provider says API requests may be rate limited. Ask support how to recognize a limit response during normal API use.
Retention, access, and use restrictions
The Terms give Guerrilla Mail discretion to terminate a license and delete data without notice or a specific reason in cases of terms breaches or service abuse. They also describe the license as non-transferable and subject to change or revocation.
The Terms prohibit repeatedly making many requests to over-use server resources. They also prohibit reverse engineering, circumvention, attacks intended to gain unauthorized privileges, spam, fraud, phishing, malicious software, and other listed misuse.
The service is provided as-is without express or implied warranties, including merchantability and fitness for a particular purpose, according to the Terms. The Terms also disclaim responsibility for third-party resources and email message content, including attachments.
The Terms state that outgoing email includes an X-Originating-IP header with the listed address. Several details are missing; they are listed under What we could not confirm.
Registration-free access and documented controls
The About page and API documentation describe access and handling features, checked 2026-10-31.
- The About page says visitors receive a random address without registration.
- Website access is restricted to HTTPS, according to the provider.
- The API documentation says fetched email bodies have HTML filtered, including scripts, applets, and iframes.
- The documented extend function adds one hour to an address, subject to a maximum extension of two hours.
- A public JSON API is documented for developers, according to the provider.
These points describe the entry method, transport, message handling, and developer access. They do not change the stated inbox access condition or retention period.
Short-lived receiving suits the stated scope
Guerrilla Mail describes its core service as disposable temporary email. The About page says inbox email is deleted after 1 hour, while the API documentation gives an address expiry of 60 minutes.
That short receiving window defines the service more clearly than the registration-free entry point. The owned-domain option offers a separate access choice: incoming mail can be limited to the owner or shared with everyone.
Decide based on the retention and access terms relevant to the intended use.
Compare inbox terms by retention and access
Compare disposable-email services by inbox lifetime, control over the address, and who can access received messages. Also check whether sending is supported, whether an API is documented, and what paid terms apply. These criteria distinguish temporary receiving from services with different access or retention models.
What we could not confirm
- Integrations and setup requirements
- Recovery options for deleted inbox messages
- Privacy and security details beyond inbox-ID access
- API rate-limit thresholds and enforcement details
- Available custom domains and owned-domain setup steps
- Outgoing-email support for ordinary users
- Per-user address or inbox allowances
Questions about inbox and API terms
Can an address be extended?
The documentation also says addresses expire after 60 minutes. Ask support how the extension behaves when an address is already close to expiry.
What happens when a session expires?
Address expiry is a separate condition: the documentation states that email addresses expire after 60 minutes. For a client relying on both, ask support how it should handle a session ending before the address does.
Which parameters must an API request include?
The API also requires clients to retain and send the PHPSESSID cookie to maintain session state. These requirements describe request parameters and session continuity, not the message-list limit.
How does the API limit requests?
The Terms also prohibit repeatedly making many requests to over-use server resources.
Where can users ask service questions?
The provider asks users to contact it through Facebook or Twitter in English and says it cannot always reply. This describes the general contact route and response qualification. Developers who created a Guerrilla Mail app are directed to a support email in the API documentation.
Can a custom domain’s incoming mail be shared?
The provider says incoming email at a user-owned domain can be accessible only to that user or shared with everyone. The two choices concern who can access arriving mail. Confirm which choice applies before relying on the domain option for a particular workflow.
Proceed after the terms are clear
Fits if temporary receiving matches the intended use and the inbox access condition is acceptable.
Probably not if the workflow requires messages to remain available beyond the stated retention window.
Main risk… relying on an address without accounting for its expiry or the inbox-ID access condition. Before proceeding, check retention, inbox access, and request rules in the relevant service documentation.
Sources
Every fact on this page traces back to a public page listed here, with the day it was read.
- www.guerrillamail.com/aboutchecked
- www.guerrillamail.comchecked
- www.guerrillamail.com/toschecked
- www.guerrillamail.com/GuerrillaMailAPI.htmlchecked
Notes on the making of this review
Editorial team of Payout Desk. This page rests on the public sources listed above, which Payout Desk checked on 2026-10-31. There was no hands-on testing. The page is updated when the sources change.
Last updated:
Right of reply
If you represent Guerrillamail.com and think this entry is inaccurate or out of date, write to us and attach evidence. After the refutation is documented, the entry is corrected or removed. No payment changes what we publish.
- Our contact for replies
- No data available
- Response time
- No data available