Understanding unknown Result from MillionVerifier API Responses

·

When i run the HTTP API for MillionVerifier in my Clay table i get 4 different results: "ok", "catch_all", "invalid", "unknown" The "unknown" result is not an option in MillionVerifier, so i'm wondering what does that mean and where does it come from? Anyone who knows why that is? And what it means?

7 comments

· Sorted by Oldest

Valentin
·
·
it is an option: https://developer.millionverifier.com/#operation/single-verification
Valentin
·
·
means millionverifier wasn't able to verify that email
Ivan D.
·
·
Pretty much somewhat similar to catchall right?
Ariful A.
·
·
Ivan D. "unknown" also comes from million verifier. That says it tried to verify but failed due to temporary error and didn't get a definite response if it's valid or not.
Ariful A.
·
·
In the sense that both mean you can’t get a definite valid or invalid, they’re similar but the reason for failure is different. Catch-all is when the server accepts all emails, even if the mailbox doesn’t exist, while unknown is when no reliable response was received at all.
Ivan D.
·
·
Got it, thanks!
Ariful A.
·
·
My pleasure!

Valentin
·
·
it is an option: https://developer.millionverifier.com/#operation/single-verification
Valentin
·
·
means millionverifier wasn't able to verify that email
Ivan D.
·
·
Pretty much somewhat similar to catchall right?
Ariful A.
·
·
Ivan D. "unknown" also comes from million verifier. That says it tried to verify but failed due to temporary error and didn't get a definite response if it's valid or not.
Ariful A.
·
·
In the sense that both mean you can’t get a definite valid or invalid, they’re similar but the reason for failure is different. Catch-all is when the server accepts all emails, even if the mailbox doesn’t exist, while unknown is when no reliable response was received at all.
Ivan D.
·
·
Got it, thanks!
Ariful A.
·
·
My pleasure!