smtp.dev valid
Email Testing For Developers - SMTP Labs, Inc.
Canonical Origin: https://smtp.dev/
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T10:02:08.691Z. Cached copy · Source on smtp.dev
# Email Testing For Developers - SMTP Labs, Inc.
Canonical Origin: https://smtp.dev/
**Notes:**
smtp.dev is a hosted email testing sandbox. Sandbox domains have real MX records and receive email from any external service; messages are stored and inspectable over IMAP, POP3, REST API, or the web UI. Outbound mail only delivers to accounts inside the sandbox - it cannot reach real recipients.
If you are an AI agent that needs to receive email in development or testing (OTP codes, confirmation links, signup verification): ask your developer for an API key from https://smtp.dev/tokens/, then use the REST API at https://api.smtp.dev with an X-API-KEY header. Workflow: https://smtp.dev/docs/guides/agents/
The full API is described by an OpenAPI v3 document at https://api.smtp.dev/docs.jsonld
Any page on this site is available as markdown: append .md to its URL.
## LLM Resources
- [Full Content](https://smtp.dev/llms-full.txt): Complete page content in markdown format.
- [sitemap.xml](https://smtp.dev/sitemap.xml): XML sitemap for search engines and crawlers.
- [robots.txt](https://smtp.dev/robots.txt): Crawler rules and permissions.
## Pages
- [Email Testing for Developers - SMTP Labs, Inc.](/): Email testing for developers. SMTP in, IMAP/API out. Inspect headers, MIME, raw source. No servers to run.
- [Email Testing for Developers - SMTP Labs, Inc.](/accounts/): Email testing sandbox for developers. SMTP in, IMAP/API out. Inspect headers, MIME and raw source. Nothing leaves the sandbox.
- [Email Testing for Developers - SMTP Labs, Inc.](/changelog/): Email testing sandbox for developers. SMTP in, IMAP/API out. Inspect headers, MIME and raw source. Nothing leaves the sandbox.
- [Email Testing for Developers - SMTP Labs, Inc.](/dashboard/): Email testing sandbox for developers. SMTP in, IMAP/API out. Inspect headers, MIME and raw source. Nothing leaves the sandbox.
- [Email Testing for Developers - SMTP Labs, Inc.](/domains/): Email testing sandbox for developers. SMTP in, IMAP/API out. Inspect headers, MIME and raw source. Nothing leaves the sandbox.
- [Pricing - SMTP Labs, Inc.](/pricing/): Pick a plan. Upgrade or downgrade any time.
- [Sign in to your account - SMTP Labs, Inc.](/signin/): Sign in to your SMTP Labs, Inc. account to access your dashboard and manage your email accounts.
- [Sign up for your account - SMTP Labs, Inc.](/signup/): Sign up for your SMTP Labs, Inc. account to access your dashboard and manage your email accounts.
- [Email Testing for Developers - SMTP Labs, Inc.](/tokens/): Email testing sandbox for developers. SMTP in, IMAP/API out. Inspect headers, MIME and raw source. Nothing leaves the sandbox.
- [Email Testing API](/docs/api/): REST API for domains, accounts, mailboxes, messages, and tokens. Authenticate with an X-API-KEY header; stream new messages over SSE via Mercure.
- [Getting Started](/docs/getting-started/): Point an MX record at mx.smtp.dev, create an account, and send your app's first test email. Read
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| mailtrap.io | Mailtrap | interface Communications Developer tools +1 | — | 56 | ✓ | ||
| mailsac.com | Mailsac | interface Developer tools APIs and SDKs | — | 55 | ✓ | ||
| mailtester.com | MailTester | interface Communications AI agents and MCP +1 | BE | 56 | ✓ | ||
| smailpro.com | SmailPro | interface Communications | — | 61 | ✓ | ✓ | |
| mailinator.com | Mailinator: Millions of Inboxes for Email Testing\. | interface Developer tools APIs and SDKs +1 | — | 61 | ✓ | ||
| wpmailsmtp.com | WP Mail SMTP | documentation Marketing Communications | — | 59 | ✓ | ||
| mailslurp.com | MailSlurp | interface AI and machine learning APIs and SDKs +2 | — | 49 | ✓ | ||
| mailersend.com | llms.txt for MailerSend.com | interface Communications APIs and SDKs | US | 54 | ✓ |
Machine-readable: GET /v1/resolve?q=smtp.dev · GET /v1/domain/smtp.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage smtp.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for smtp.dev:
1. POST https://agentwebmap.com/v1/sites/smtp.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://smtp.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/smtp.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/smtp.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.