An example
When you send mail to sam@example.com, the MX records of example.com in DNS name the server that takes it, and your mail server delivers there. A domain with no MX record and no address record can't receive mail. A domain owner who publishes a null MX record (a single record pointing at ".") is saying in public that it never will.
Why it matters to an app with a free tier
A person who signs up with an address that can't receive mail never reads anything you send. The signup still costs you a confirmation email, which bounces, and an account in your app. From the MX records you also learn who handles a domain's mail, and a brand-new domain whose mail goes to a burner mail server is a burner domain whatever its name says.
What SignupBouncer does
We look up each domain's MX records on every plan. A domain that can't receive mail, because it has a null MX record or no MX record and no address record to fall back to, is refused as no_mx. A DNS failure or timeout doesn't count, so a slow resolver never refuses anyone.
A domain whose mail goes to a burner mail server is refused as burner_mx. That server handles mail for three or more disposable domains and, in our lookups, for no real mail provider on our list. We hand-review its network before listing it, unless a temp-mail site we collect domains from runs it. This is how we catch disposable domains that are too new for any list.