getting started

Test addresses

Reserved test.isbusinessemail.com addresses return fixed results with no key and never count toward quotas. Use them in docs, CI and smoke tests.

View as Markdown

Every address below returns a fixed, predictable result. They need no API key and are never counted toward any quota, so they’re safe in CI, smoke tests, demos and documentation.

Address category recommendation (b2b) What’s special
[email protected] business allow A plain company address
[email protected] personal block Shared-domain provider, is_free_provider: true
[email protected] disposable block is_disposable: true
[email protected] relay block is_relay: true
[email protected] education allow is_business: true
[email protected] invalid block Can’t receive mail
[email protected] unknown review Too little evidence to decide
[email protected] business allow Microsoft 365 detected, auth: "federated" via Okta, with a placeholder tenant ID
[email protected] business allow Google Workspace detected
[email protected] any block is_blocked: true: blocked under every policy, whatever the category
[email protected] business review info@-style role account, is_role_account: true

Examples

# No key needed
curl -sG https://api.isbusinessemail.com/v1/check \
  --data-urlencode "[email protected]"
# Same thing with POST, as you'd call it in production
curl -s https://api.isbusinessemail.com/v1/check \
  -H "Content-Type: application/json" \
  -d '{"email":"[email protected]"}'

Test addresses also work when you send a key, so your production code path can be tested end to end without spending quota.

A CI smoke test

#!/usr/bin/env bash
set -euo pipefail
api=https://api.isbusinessemail.com/v1/check

expect() {
  local email=$1 want=$2
  got=$(curl -sf "$api" -H "Content-Type: application/json" \
        -d "{\"email\":\"$email\"}" | jq -r .recommendation)
  [[ "$got" == "$want" ]] || { echo "FAIL $email: got $got, want $want"; exit 1; }
  echo "ok   $email → $got"
}

expect [email protected]   allow
expect [email protected]   block
expect [email protected] block
expect [email protected]    review

Unit tests for your signup logic

Use the test addresses to cover every branch of your own code: allow, review, block, did_you_mean, Workspace vs Microsoft 365 connector pre-selection. For failure paths (timeouts, 429, 5xx), mock the HTTP client; test addresses always succeed.

Mailbox verification

/v1/verify has its own test addresses at the same domain. They never open an SMTP connection: deliverable@, undeliverable@, disabled@, catch-all@, full@, disposable@, unknown@ and [email protected] each return the status and reason in their name. The verify docs list them all.