Straight answers

This is the design center of the whole product. Three protections stack: (1) we confirm we can deliver to your server with a coded test email before you change DNS; (2) borderline mail is held for you to review — not guessed at, not silently deleted; (3) only mail that is overwhelmingly junk (or carries a virus) is refused outright, and even then the sender's server is told at delivery time, so a legitimate sender knows immediately rather than wondering.

New, unknown senders are briefly asked to "try again in a moment" — a standard technique called greylisting. Real mail servers retry automatically and the message arrives a few minutes later; most bulk spam software never retries. Senders you've received from before aren't delayed, and trusted one-time-code senders (like login codes) are exempted.

Open it in the site, click Release to inbox, and optionally tick "also allow this sender from now on." Release re-delivers the original message to the addressee. If you think the verdict itself was wrong, one more click opens a review with us.

No — and structurally we can't through the customer systems: message bodies are never stored in the website, never shown, never available to its API. Filtering decisions are made in-flight by software; what's kept is the metadata record (sender, subject, score, checks). The full data story is here.

Your mail waits — it doesn't vanish. Sending servers automatically queue and retry for days when a receiver is unreachable; that behavior is built into how email works. An outage on our side delays delivery rather than losing anything.

Both. You (the admin) see everything for your domain; you can invite colleagues, and each sees just their own mailbox. Invitations are verified the natural way — we deliver a code to that mailbox, and only its owner can complete the invite. You can promote a colleague to co-admin any time.

No — paste your exported list into the import box (one entry per line: allow,domain,supplier.com) and it's applied in seconds. Bad lines are skipped and reported, never fatal.

Free during the pilot, with no payment details collected. When billing arrives, pilot customers get generous notice and simple pricing — no surprise conversion.

The account page has a guided exit: repoint your MX first (we check it for you, so the hand-off can't drop mail), download your lists and history as a CSV, then close. No retention dark patterns, no phone call required.

webdfw.com — a small web-services shop in the Lake Cities, Texas area, running mail infrastructure for its own business customers for years. Pilot customers talk directly to the people who operate the filter: support@webdfw.com.