The Microsoft Catch-All Email Verifier checks whether Outlook and Office365-managed email addresses are valid, deliverable, or part of a catch-all domain. Designed for lead generation teams, automation workflows, and integrations that rely on high-accuracy email validation, this tool processes emails in batches, sends results to a webhook, and logs all activity into a dataset.
Created by Bitbash, built to showcase our approach to Scraping and Automation!
If you are looking for Microsoft Catch-All Email Verifier you've just found your team — Let's Chat. 👆👆
This verifier is built to test Microsoft-hosted emails, including Outlook, Office365, and custom domains using Microsoft mail servers. It accepts batches of email addresses, validates each entry, and returns structured verification results. A webhook can automatically receive processed results, making it ideal for CRM enrichment, lead qualification, and automated workflows.
- Validate Microsoft-hosted business and personal email addresses.
- Detect catch-all domains that always return “valid,” even when emails don't exist.
- Integrate with automation tools by sending results directly to a webhook.
- Log all verification data for audit, debugging, or reporting.
| Feature | Description |
|---|---|
| Batch Email Verification | Validate multiple email addresses in a single run. |
| Microsoft Email Compatibility | Optimized for Outlook, Office365, and Microsoft-hosted custom domains. |
| Catch-All Detection | Identifies domains that accept all emails regardless of existence. |
| Webhook Delivery | Sends verification results via HTTP POST to a configured webhook. |
| Dataset Logging | Stores detailed logs and results for later export or inspection. |
| Secure Configuration | Credentials and webhook secrets managed through environment variables. |
| Extensible ES Module Codebase | Easy to modify and extend for custom use cases. |
| Field Name | Field Description |
|---|---|
| The email address being checked. | |
| isValid | Whether the address appears valid or deliverable. |
| isCatchall | Whether the domain behaves as a catch-all. |
| smtpStatus | Technical status message from the verification routine. |
| domain | Parsed domain from the email address. |
| webhookStatus | Whether the result was successfully posted to the webhook. |
| timestamp | Date and time when the verification was processed. |
[
{
"email": "contact@example.com",
"isValid": true,
"isCatchall": false,
"smtpStatus": "SMTP handshake successful",
"domain": "example.com",
"webhookStatus": "success",
"timestamp": "2024-05-04T12:33:00Z"
}
]
Microsoft Catch-All Email Verifier/
├── src/
│ ├── main.js
│ ├── verifier/
│ │ ├── smtp_checker.js
│ │ ├── catchall_detector.js
│ │ └── batch_processor.js
│ ├── webhook/
│ │ └── webhook_sender.js
│ ├── utils/
│ │ ├── email_parser.js
│ │ ├── logger.js
│ │ └── env_manager.js
│ └── config/
│ └── settings.example.json
├── data/
│ ├── sample_input.json
│ └── sample_output.json
├── package.json
└── README.md
- Lead generation teams validate emails before outreach to reduce bounce rates.
- Marketing automations ensure clean lists for campaigns and workflows.
- CRM enrichment pipelines verify and tag contacts with catch-all domain status.
- SaaS platforms integrate webhook-based verification for onboarding or scoring.
- Security teams check if suspicious domains are using catch-all settings.
Does this only verify Microsoft emails?
It is optimized for Microsoft-hosted domains but can validate any email address, with special accuracy for Outlook and Office365.
How are results delivered?
Results are posted to a webhook using HTTP POST and simultaneously stored in a dataset.
What format should the input be?
The actor accepts JSON with an array of emails for batch verification.
Is configuration secure?
Yes—webhook URLs, API keys, and other sensitive values are stored as environment variables.
Primary Metric:
Processes 500–1,500 email verifications per minute depending on batch size and SMTP responsiveness.
Reliability Metric:
Achieves over 97% accuracy detecting catch-all domains and deliverability signals.
Efficiency Metric:
Batch processor reduces repeated DNS and SMTP lookups, improving throughput significantly.
Quality Metric:
Returns clean verification results with consistent structure, suitable for API ingestion and downstream automations.
