THE WORLDSCONTACT GUIDE

From your first upload
to a useful result.

A practical guide to preparing a list, running a verification job, and understanding the report.

1. Prepare your list

Use a CSV, XLSX, or TXT file containing the email addresses you want to check. Upload it in your workspace and select the email column. The analysis identifies blank entries, duplicates, and addresses with invalid syntax.

2. Review the estimate

The upload estimate is one credit for each unique address with valid syntax. Review the analysis and your available credits before starting. Credits are reserved while the job runs, then settled when it completes.

3. Follow the verification job

WorldsContact resolves mail infrastructure and checks recipient responses. Your workspace shows job progress. Receiving servers may be temporarily unavailable or decline to provide a definitive answer; those conditions can produce an unknown result.

4. Read the results in context

• Deliverable: the server accepted the recipient during the check. This is not a guarantee of future delivery.
• Risky: available signals warrant a closer review.
• Undeliverable: the check found a permanent rejection or an invalid address or mail infrastructure.
• Unknown: the available evidence was inconclusive, for example after a timeout or temporary server response.

Look at the reason and evidence strength alongside the status. Not every check produces every type of evidence. Catch-all detection, in particular, is not available for every verification path.

5. Export and act

Download your completed CSV report from the job’s results page. It includes the email, classification, reason, evidence strength, and available verification details. Use these findings in your existing workflow; WorldsContact does not automatically update your CRM or send a campaign.

Working with APIs

Your account’s API key page is in the application. Customer account information is available through the existing account API. Bulk verification currently uses the upload workflow described above; this guide does not advertise a public bulk verification API. Infrastructure node endpoints are reserved for authorized verification workers.