The number of checks advertised matters less than what they really are: a genuine SMTP verification, and a clear answer when nothing allows a conclusion.
Scope of the checks
How many checks run on a submitted address, and which ones are named?
Test it yourself Submit a test address and count the sections returned in the response, without relying on the figure advertised on the home page.
At YesWeCheck 20 named checks, each with its own field in the response and its own cost. The list is published in full on this site, in the order the engine runs them.
Reality of the SMTP verification
Does the verdict come from a real dialogue with the receiving server, or from a statistical model?
Test it yourself Request SMTP verification on an address whose domain you control, then look for the incoming session in the logs of your own mail server.
At YesWeCheck A real dialogue with the receiving server, carried through to the mailbox check, without ever sending a message. Its verdict prevails over every other signal.
Undecidable cases
What does the service return when no conclusion is possible, and is that answer charged?
Test it yourself Submit an address on a domain that accepts everything, and an address on a domain that delays, then read the status returned and the credit balance.
At YesWeCheck An unknown status, clearly distinct from the other three, and never charged. You only pay for the answers that teach you something.
Domain health
Which public declarations of the domain are read, beyond the mail server?
Test it yourself Submit an address on a domain whose public records you know, and check that each declaration read appears in the response.
At YesWeCheck Six declarations: the mail server, the sending authorisation, the anti-spoofing policy, the brand logo, the age of the registration and the declared registrant.