Questions deserve straight answers.

VXSentry checks email addresses before you send. It reviews format, domain and mail-routing data, mailbox responses when available, catch-all behavior, disposable providers, role addresses, patterns and applicable suppression information. It then places each address in one of six clear result categories.

VXSentry is not an email sending platform. Its standard verification probe uses SMTP envelope commands and stops before the DATA stage, so it does not send message content to the recipient. Receiving mail systems may still log the technical probe.

The receiving server accepted the mailbox and the domain did not behave like a catch-all. That is strong evidence that it is a reasonable candidate for sending, but it is not a promise that a future message will be delivered or reach the inbox.

A clear problem was found: invalid syntax, a domain that cannot receive mail, or a mailbox rejected by the receiving server. The recommended action is Suppress.

A catch-all domain appears to accept mail for almost any recipient name. That makes the domain reachable, but it prevents VXSentry from confirming that one specific mailbox exists. The recommended action is Verify manually.

The domain can receive mail, but the mailbox could not be confirmed. A provider may hide mailbox information, block the check, greylist it or not answer in time. VXSentry says Unknown rather than turning incomplete evidence into a positive result.

The address has a warning that deserves review, such as a role-based label or suspicious pattern. The recommended action is Send with caution.

A strong risk signal was found. In the current verifier, that means a match on an applicable account or platform suppression entry, or a known disposable-email provider. The recommended action is Do not send.

No. Inbox placement also depends on sender reputation, authentication, message content, recipient engagement and provider policy. Verification helps you understand the address before sending; it cannot guarantee delivery or inbox placement.

VXSentry may flag patterns and suppression matches that warrant caution, but it does not claim to identify every spam trap. No public result should be treated as a complete spam-trap guarantee.

Yes. Mailboxes close, providers change policy, servers fail and recipients can block a sender after a check. Verification is a point-in-time assessment, not a zero-bounce promise.

Yes. Each original row and its columns are kept in the result export. VXSentry appends seven result fields for the record ID, category, score, confidence, status, reason and recommended action.

It depends on list size and how quickly receiving mail systems respond. The job page shows live progress. Some server checks deliberately wait for a bounded response, so a larger list or slow providers can take longer.

No. VXSentry uses one-time verification credit packages. There is no mandatory monthly verification subscription.

A paid list job uses one credit for each processable email when processing starts. Rows that are not processable are skipped. Eligible failed or incomplete worker-outage checks are refunded by the job accounting rules.

Yes. You can return to Pricing or the billing area and buy another one-time package when you need it. Credits are added after Square confirms a completed payment.

Not at this time. Download the enriched CSV, choose the records you want to use, and import them into your sending platform yourself. VXSentry does not automatically remove or update contacts in outside systems.

No. Those controls authenticate mail from your domain and help receiving systems evaluate it. Address verification serves a different purpose: understanding the records in your list before you send.

VXSentry stores original rows with results so it can show and export your job. Verification jobs and row-level results have a default 30-day purge threshold, but purge is currently started by an administrator rather than guaranteed automatically on day 30. Some financial, audit, security and free-check records are kept separately. See the Privacy Policy for the full details.