.in Addresses: 10.7% Invalid, 22.7% Unknown | BounceZero

.in Addresses on Lead Lists
44.2% Confirmed Valid: What the 2026 Benchmark Says

.in is the country domain used in India. Across 7,976 .in addresses verified by BounceZero between April and October 2026, 10.7% were invalid, 18.3% catch-all, 22.7% unknown and 44.2% confirmed valid. Catch-all and unknown together mean a large share cannot be confirmed.

By Ayoub Lebda, founder of BounceZero, a UK-registered email verification service |10 October 2026 |3 min read

.in: verification results against the benchmarks

Every .in address BounceZero verified for customers between April and October 2026, beside the corpus benchmarks. The remainder of each row to 100% is risky and role results.

SegmentAddressesInvalidCatch-allUnknownConfirmed valid
.in7,97610.7%18.3%22.7%44.2%
All non-freemail domains (business and ISP)6,514,88414.5%2.3%27.0%32.6%
Business domains only (consumer ISP and freemail excluded)1,269,91922.9%9.4%22.5%40.3%
All freemail1,415,15417.6%1.1%2.1%74.0%

Non-freemail includes consumer ISP mailboxes; a business-only cut is on the benchmarks page. Method and every other cut: Lead List Quality Benchmarks 2026. Risky and role on the .in row: 4.1%.

Why .in looks like this

Indian B2B lists are freemail-heavy; the .in business domains that do appear verify reasonably well.

Indian B2B lists are freemail-heavy, with Gmail dominant, and the .in company domains that appear verify reasonably well. The split between freemail and company domain is the first cut to make on any Indian list. India's Digital Personal Data Protection Act requires consent for personal data processing, and the freemail share is where that applies. Indian company domains tend to belong to IT services firms, exporters and larger manufacturers, and their gateways answer probes normally. The freemail share is where the bounces and the consent obligations concentrate. Lists sold for Indian outreach often blend the two without labelling them, so the first verification run doubles as the audit that reveals the blend.

Where .in sits among country domains

On confirmed-invalid rate, .in ranks 17 of 23 country domains in the corpus, just behind .ae at 10.8%, ahead of .ch at 9.3%.

On unknown rate, .in ranks 7 of 23 country domains in the corpus, just behind .org at 25.0%, ahead of .fi at 22.1%.

On confirmed-valid share, .in ranks 12 of 23 country domains in the corpus, just behind .fr at 47.5%, ahead of .be at 40.5%.

How to read these rates: they are BounceZero's probe outcomes on customer lists over April to October 2026, not a census of .in mailboxes. Unknown and catch-all measure what verification could not confirm, which depends on the provider's gateway policy during the window as much as on the addresses. The lists are the ones customers chose to upload, so segments dominated by a few large uploads carry their age and source. Method and limitations: benchmarks page.

Reading each result on .in

Unknown

About one in 4 .in addresses cannot be confirmed either way. That is gateway behaviour, not a verdict; route those contacts to phone or LinkedIn and re-check after a week.

Invalid

.in runs at 10.7% confirmed invalid, ordinary for a list that has not been checked in a while; the failures are closed mailboxes and should be removed.

Catch-all

Catch-all is the defining trait here: 18.3% of .in addresses accept anything, so finder guesses look valid and bounce later. Hold them out of cold sequences entirely.

Confirmed valid

Just over 44% confirmed valid: reachable today, re-verified before every send, since only 19.2% of addresses were still valid 90 days after a check in BounceZero's decay study.

.in in practice: routing and re-checks

Separate freemail from .in business domains before judging a list, and verify both.

Role addresses such as info@ and sales@ make up 16.8% of .in addresses in the corpus. Role addresses rarely reach a person; prefer named contacts.

Go deeper

Frequently asked questions

What percentage of .in email addresses are invalid?

10.7% of 7,976 .in addresses verified by BounceZero between April and October 2026 were confirmed invalid, against 14.5% across non-freemail domains and 17.6% across freemail.

How many .in addresses return unknown, and what does that mean?

22.7%. Unknown means the mailbox could not be confirmed either way, usually because the gateway deferred the probe. BounceZero refunds unknown results; re-check after a week or use a second channel.

Is .in a catch-all domain?

Partly: 18.3% of .in addresses sat behind a catch-all accept, so the server took any address and the mailbox could not be confirmed.

What share of .in addresses are safe to email?

44.2% confirmed valid at verification time. Keep bounces under 2% and complaints under 0.3% on the send, and re-verify the segment before every send.

Verify a list with .in addresses on it

Upload the file and see valid, invalid, catch-all and unknown per row, with the .in segment against this benchmark. 100 free checks a month, unknowns refunded.

AL

Written by

Ayoub Lebda

Founder, BounceZero - Email-infrastructure engineer

Ayoub built BounceZero's 5-stage validation pipeline, its dedicated BGP-announced IP infrastructure, and the Patroni HA PostgreSQL cluster behind every verification. Previously built high-volume email delivery infrastructure. Trained at 1337 Benguerir (École 42 network, 2019). Open-source: bgp_analyzer.

Lead list quality by provider and country

Invalid, catch-all and unknown rates per email provider and country domain, 2026