How do I test signup and verification emails?

Create a free webhooks.cc endpoint and use its email address, your-slug@mailhooks.cc, in the signup form. The confirmation email shows up in the dashboard within seconds with the code and the link picked out, or your test fetches it from the REST API.

How do I read a one-time code in a Playwright or Cypress test?

Sign up with a tagged address such as your-slug+run-42@mailhooks.cc, then poll the requests API for an email with that tag and match the code in its text part. Each email comes back as JSON with its subject, sender, text, HTML and attachment list.

Does email testing cost extra?

No. Email capture is on every plan, Free included. Each email counts as one request against the same quota as your webhooks: 50 a day on Free, 100,000 a month on Pro.

Can I get an email address without an account?

No. Guest endpoints on the landing page receive HTTP requests only, because anyone who knows a guest slug can read what it captured. Every endpoint on a free account receives email.

Does it check SPF, DKIM and DMARC?

Yes. Every message shows the SPF, DKIM and DMARC results, reverse DNS and the TLS version it arrived with. A failing check never stops a message from being captured, so you can debug a sending setup that is not right yet.

Can I send or reply from a mailhooks.cc address?

No. mailhooks.cc only receives. It never sends mail, replies or bounces, so the addresses cannot be used to send spam.

What happens to attachments?

Their name, type and size are listed. The contents are not kept. Messages up to 10 MB are accepted, text and HTML parts are stored up to 256 KB each, and the original message is kept when it is 1 MB or smaller.

Test the emails your app sends

Every endpoint on a webhooks.cc account has a real email address next to its webhook URL. Sign up in your app with it, then read the confirmation code, the magic link and the sender checks in the dashboard, or fetch the email from the API in your test.

# Your endpoint's address
[email protected]

# One per test run, same endpoint
[email protected]

Start free:

No credit card. Read the email capture docs for every detail.

How to test an email flow

1
Create an endpoint
Sign up free and create an endpoint. Next to its webhook URL it has an email address: the endpoint's slug at mailhooks.cc.
2
Use the address in your app
Sign up, reset a password or log in with that address. Add a tag after a plus sign, like [email protected], to tell test runs apart; tagged mail lands on the same endpoint.
3
Read the email
The email appears in the dashboard within seconds, with the one-time code and the main link picked out for you. In an automated test, fetch it from the REST API instead.
4
Check it before you ship
Preview the HTML at desktop and mobile widths, read the text part and the headers, and see whether SPF, DKIM and DMARC passed for your sending domain.

What you see for every email

Codes and links, picked out

The one-time code and the link the email asks you to click sit at the top, each with a copy button. Unsubscribe and tracking links stay out of the way.

A preview that cannot bite

The HTML renders in a sandboxed frame with no scripts. Remote images wait until you load them, so opening an email tells the sender nothing.

Sender checks

SPF, DKIM, DMARC, reverse DNS and TLS for every message, with what each result means, so you see what an inbox provider would think of your mail.

The email as JSON

Every email opens on a JSON view of the parsed message: sender, recipients, subject, text, HTML, codes, links and attachments. Copy it as a test fixture.

Emails next to your webhooks

Mail lands in the same list as the endpoint's HTTP requests, so a signup that fires a webhook and a confirmation email can be checked in one place.

Headers, raw source and .eml

Every header as it arrived, the raw message, the attachment list, and a download of the original .eml file.

Read the email in your test

The REST API returns emails next to HTTP requests, each with its parsed message. Poll for the email your test triggered, then pull the code or link out of it. This works in Playwright, Cypress, Selenium or any test runner that can make an HTTP call.

// Your signup test used `my-app+${runId}@mailhooks.cc`.
async function waitForEmail(runId: string, since: number) {
  for (let attempt = 0; attempt < 30; attempt++) {
    const response = await fetch(
      `https://webhooks.cc/api/endpoints/my-app/requests?since=${since}`,
      { headers: { Authorization: `Bearer ${process.env.WHK_API_KEY}` } }
    );
    const requests = await response.json();
    const match = requests.find((r) => r.kind === "email" && r.email.tag === runId);
    if (match) return match.email;
    await new Promise((resolve) => setTimeout(resolve, 1000));
  }
  throw new Error("No email arrived within 30 seconds");
}

const email = await waitForEmail(runId, startedAt);
const code = email.text.match(/\b\d{6}\b/)?.[0];
await page.getByLabel("Verification code").fill(code);

Create the API key on your account page. The REST API reference lists every field of an email.

Need the email in your own app?

Turn on forwarding and every email the endpoint receives is posted to your server as signed JSON, retried until your server accepts it. No mail server to run and no MIME to parse.

Email to webhook

Limits

Every plan, Free included; an email counts as one request
Messages up to 10 MB, up to 20 recipients each
Text and HTML stored up to 256 KB each
Original .eml kept for messages up to 1 MB
Attachments listed by name, type and size
Same retention as your HTTP requests

Email testing questions

Your test inbox is one signup away

No credit card