About MobileValidate

MobileValidate is a phone and e-mail checks API. Its short promise is "Know before you send." One request tells you whether a phone number is registered on messaging apps, what line type and carrier it has, and whether an e-mail address has a mailbox or an account on a service. Every answer is yes, no or unknown, with the time we checked.

MobileValidate is a product of BroadNet Technologies LLC, 100 Matawan Road, Suite 325, Matawan, NJ 07747, United States, part of the BroadNet Group.

What do we build, and for whom?

We build checks for teams that send messages, verify users and handle leads: SMS and messaging platforms, sign-up and one-time-passcode flows, fraud and trust-and-safety teams, contact centers and lead-generation businesses. The product focuses on four jobs: deliverability, fraud prevention, sign-up and OTP protection, and lead verification.

We don't build tools for unsolicited bulk messaging, for finding out who uses a particular app, or for looking people up. Checks never return names, photos or profiles, and requests that look like sequential number ranges or generated e-mail lists are rejected.

How do we work?

• Honest answers. Unknown is reported as unknown, never guessed, and you're not charged for inconclusive results (unknown, unsupported country, timeout, invalid, duplicate).
• Privacy by default. Identifiers are encrypted when stored, masked when shown and kept only for short default periods. See the trust page.
• Developer first. A documented API, test mode, webhooks, an SDK, a CLI and an MCP server for AI agents. See the docs.

Editorial process

Our guides, glossary entries, research posts and comparisons are written and checked by the MobileValidate team. These are the rules each page follows:

• Primary sources first. Rules, fees, dates and statistics come from the body that publishes them: the regulator, the standards body, the platform's own documentation or the official dataset. If a site blocks automated access, we use its official API or an archived copy and say which one. Each source is listed at the end of the post with its publisher and date.
• Dated facts. Facts that change, such as prices, porting times, rules in progress and operator counts, carry an "as of" date. Our own check prices come from the live catalog, so they match pricing. Code examples are run against the public sandbox before they are published.
• A fact check before publishing. Before a scheduled post goes live, every factual claim is checked again against its source. Each claim is either confirmed, updated or removed. Claims we can't source are removed.
• No unverifiable claims. We don't publish accuracy percentages or "official" labels. Platform names describe which service a check refers to. We don't speak for any platform.
• Updates. The "Updated" date on a post changes only when its text changes. Tables generated from our catalog show their own "Catalog data as of" date instead, so a data refresh doesn't make a post look newer than its text.
• Corrections. If you find an error, e-mail support@mobilevalidate.com with the page URL and, if you can, the source. We check it against the source, fix the page and update its date.

Company details

For access, use the request access form. For questions about your data, use the opt-out form.