Use Case Page
Public Email Detection for Business Signup Flows
Detect public email domains like Gmail and Yahoo so you can request work emails for demos, sales inquiries, and B2B onboarding.
Why this matters
Public inboxes are fine for many consumer products, but B2B workflows often need a company address to qualify leads, personalize onboarding, or map signups to an account owner. This page focuses on using public-domain detection without overcomplicating the form.
Recommended next step
Use the homepage checker for a quick manual test, then wire the API into your form or signup flow.
What EmailCheck helps you do
Route self-serve signups and demo requests based on whether the address is personal or business-owned.
Keep sales pipelines cleaner by separating real company leads from low-intent submissions.
Layer in MX, typo, and disposable checks so the fallback experience still feels helpful.
Signals returned by the API
Each field corresponds to a real detection capability you can use directly in your business logic.
public_domainTrue when the address belongs to a public mailbox provider such as Gmail, Yahoo, or Outlook.com.
domainThe parsed domain makes it easy to branch logic for routing, analytics, and enrichment.
did_you_meanLets you recover users who typed a public provider domain incorrectly.
Common workflows
- Demo request forms that require a business email for qualification.
- Partner or reseller forms where a personal inbox reduces trust.
- Enterprise trials that need to match a signup to a company domain.
How to implement it
- Verify the address in real time before the form submits.
- If `public_domain` is true, keep the form lightweight and ask whether the user can share a work email.
- Let qualified users continue if the workflow should stay low friction.
Frequently asked questions
Why detect public email domains?
Public-domain detection helps B2B teams understand whether a signup likely represents a company account or a personal inbox.
Should I block Gmail signups?
Usually no. Asking for a work email is often better than hard blocking, especially for top-of-funnel or self-serve experiences.
Does EmailCheck identify the domain separately?
Yes. The API returns the parsed domain along with the public-domain flag so you can route or score the lead downstream.
Related pages
Explore more email verification topics and best practices for different use cases.
Disposable Email Checker for Signup Forms
Detect disposable, temporary, and throwaway inboxes before fake users create accounts. Check temp mail domains in real time with the EmailCheck API.
MX Record Checker for Email Domain Validation
Verify whether an email domain has valid MX records and can receive mail. Use EmailCheck to validate domains, mail servers, and deliverability signals in real time.
Role Account Detection for Shared Inboxes
Flag role-based email addresses like hello@, sales@, and support@ during signup or lead capture. Use EmailCheck to identify shared inboxes in real time.
One API call covers all your verification needs
No need to integrate multiple services. EmailCheck provides a unified interface for everything from basic validation to advanced risk detection.