How do you handle catch-all domains? That is usually where verification APIs disagree most, so a separate risky status instead of valid or invalid would be useful.

Email verification is an important quality gate before a campaign goes out, and the mix of single-email checks, bulk lists, disposable detection, and catch-all handling is thoughtfully scoped. Clear reason codes would make the results even more actionable for teams.

The homepage says bulk uploads accept CSV, XLSX, and TXT, but the /v1/verify-mails/ API docs list only CSV and TXT. Is XLSX supported in the dashboard only, or can API clients upload it too? A clear distinction in the docs would help teams avoid failed bulk jobs.

Bounce rate and sender reputation are what hurt teams most. For bulk verification, do results come back with a reason code per address (disposable, catch-all, syntax, no mailbox) that I could use to segment a list instead of a simple valid/invalid flag?

Cleaning lists before sending is the step most teams skip, so a verification API fits well into the sending flow. Do you flag catch-all domains separately, since those are the hardest to call valid or invalid?

I feel that my new project needs it.

Credits that never expire are a good fit for small senders who only clean a list every few months. Does the free 1,000 credits cover the bulk upload with the deep SMTP and spam trap checks, or only single-address lookups?

Catch-all domain detection is the part most cheap verifiers get wrong. Would love to know if the bulk endpoint returns a confidence score for those risky addresses.