Chapter 1 of 6 · Six carrier domains
About BillionVerify
BillionVerify tells you whether an email address is real before you send to it: syntax, domain and MX, a live SMTP check, and separate flags for disposable, role and catch-all addresses.
Try the free Email CheckerAbout this video
File verification needs a paid account. BillionVerify is not affiliated with or endorsed by Docomo, au, SoftBank or Vodafone.
Video transcript
Six carrier domains
Addresses on Docomo, au, SoftBank and other Japanese carrier domains come back unknown. Carrier policy blocks the check. Here's what that means for your list. Six domains get this result. Docomo. ezweb. au.com. Two SoftBank domains. And Vodafone. The full list is on screen. Each one returns the status unknown, and the reason carrier_blocked. That code is only used for this group, which makes it easy to find.
Why it happens
This comes from carrier policy. SMTP verification is blocked on these mail domains. Trying anyway wouldn't teach us anything about the person's inbox. So the address goes through the early checks, and the policy layer ends it there. We never dial the carrier's mail server, and no email is sent. Keep two mistakes apart. It isn't invalid, because nobody has shown the mailbox is gone. It isn't valid, because nobody has shown it exists. All you have is a domain and a carrier rule. Waiting doesn't help either. This isn't a busy server or a temporary reply. It's a standing rule, so a check tomorrow gives you the same result. The code isn't retryable. And these rows are free. A carrier_blocked result uses no credits, in a single check, a bulk list or a file.
Which addresses it covers
The rule is narrow. It's these six domains, not Japan as a whole. A Japanese company on its own domain gets the normal checks. So does any domain outside this list. One file can hold both.
How to find them
To find them in a results file, filter ev_reason for carrier_blocked. The live results on a file job show the code too. A single check in the console only shows Unknown Status. Through the API, read the reason field. Retryable comes back false. Your code can route these rows straight away, with no second request.
What to do
So what should you do? Don't drop a contact because of this result. Treat the address as unconfirmed. We have no evidence that it's bad. Put these rows in their own segment, and send as usual. Then read the bounce report for that segment. A hard bounce removes the address. If there's no bounce, it stays. Six domains. One reason code. No credits. And a real send for the final answer.
Get started free
20 free credits every day you use your account, up to 600 a month. No credit card required. Start at billionverify.com.
More in Mailbox Providers
All email verification videosBillionVerify pricing
Start free, then pay for what you verify. Pick a plan or buy credits once.
Billed yearly $76.80 for the first year, then $96
Save 60%$0.00032 / per credit
All 240,000 credits arrive at once. Use them anytime.
Choose your credits
Included in every paid plan
- 240,000 credits / year
- Single email verification
- Bulk email verification
- Email Finder
- Bulk Email Finder
- Company Search
- Live SMTP mailbox check
- Real-time API + batch processing
- CSV & Excel upload support
- Comprehensive verification reports
- Workspaces and teams with spend limits
- Credits never expire
Try the AI email verification features
20 free credits every day you log in, up to 600 a month. Free AI first email verification across every feature, no credit card.
Native MCP Server integration · Catch-all reported separately · Free tier, no credit card