API archive entry · source-reported
Kickbox
Email verification API
Decision snapshot
Kickbox is catalogued as a Email API from Kickbox. The directory reports no auth authentication, HTTPS support, and CORS as yes.
- Category
- Authentication
- No auth
- HTTPS
- Reported
- CORS
- Yes
Evaluation pathway
- Define endpoints, fields, freshness, and expected request volume.
- Read the live source and confirm access, terms, limits, and version.
- Test representative inputs, errors, latency, pagination, and data quality.
- Plan monitoring, retries, caching, version pinning, and a fallback.
What still needs verification
Pricing and quotas
Confirm current plans, free-tier limits, overages, and request ceilings.
Endpoint coverage
Check that the operations and response fields match the intended workload.
Reliability
Look for uptime history, a status page, support routes, and service commitments.
Data and privacy
Review retention, licensing, regional processing, and compliance requirements.
Versioning
Confirm the active version, change policy, deprecation window, and migration guidance.
Developer experience
Validate SDKs, examples, error formats, pagination, and test environments.
Nearby Email options
AGPC Domain Check
Check a domain's SPF, DKIM, DMARC and MX with a graded shareable report
No auth · HTTPS reported · CORS Yes
Disify
Validate and detect disposable and temporary email addresses
No auth · HTTPS reported · CORS Yes
EVA
Validate email addresses
No auth · HTTPS reported · CORS Yes
Source reference
This page separates source-reported facts from questions that need live provider verification.