Coverage

Which provider covers which country — and how well.

Choose a provider to see its coverage. The darker the country, the deeper the data: house-number level, street level or city level.Choose a provider to see its coverage. The lighter the country, the deeper the data: house-number level, street level or city level.

Address Validation API from Google Maps Platform, in 40 regions; USPS CASS-certified in the US.

Countries covered: 40
Good (house number): 2
Medium (street): 36
Basic (city/postcode): 2

Source: Google Maps Platform, Address Validation API coverage, October 8, 2026

GoodConfirmed down to house number or premise.
MediumConfirmed down to the street.
BasicConfirmed down to city or postcode.
Not coveredThis provider has no data for the country.

Find a country

Table view

Demo

Test an address

Enter an address and see how Google Address Validation validates it — with corrections and details.

No result yet

Fill in an address or pick an example, then validate it. The result shows the status, corrections and what Address Validation iO would do.

Email verification: four services, independent of country

Email addresses aren’t tied to a country, so there’s no map here. Address Validation iO checks them in two steps: first a plausibility check inside Address Validation iO, then verification by an email provider. Here’s what each service checks and what it returns.

Plausibility check · inside Address Validation iO, no external provider
Verification · Bouncer, Loqate or Amazon SES

Addresses that fail step 1 are not sent to a provider.

Address Validation iO plausibility check
Offline Check · built into Address Validation iO
Checks whether an address can be an email address at all: structure, permitted characters and a well-formed domain. It also flags addresses at known throwaway services and suggests a fix when the domain is one typo away from a common mail provider (gmial.com → gmail.com). It runs inside Address Validation iO before any provider is asked, so a malformed address never costs a paid check. It doesn’t tell you whether the mailbox exists.
Returns
Plausible · Not plausible
Bouncer
Email provider
Checks the syntax, the domain’s DNS/MX records and performs a handshake with the receiving mail server, without sending an email. Flags catch-all domains, disposable addresses, free mail providers, shared inboxes like info@ and full mailboxes, and suggests a correction for likely typos.
Returns
Deliverable · Risky · Undeliverable · Unknown · Score 0–100
Data processing: EU (Frankfurt)
Source: Bouncer API documentation, November 2026
Loqate
Email provider · also an address provider
Checks the syntax, whether the domain can receive email, and whether the mail server accepts mail for this mailbox. Identifies catch-all domains and disposable addresses, and rates the bounce risk.
Returns
Valid · Valid (catch-all) · Invalid · Timeout · Risk: low / medium / high / unknown
See Loqate’s address coverage ↑Source: Loqate Email Validation documentation, November 2026
Amazon SES
Email provider
Email Validation from Amazon Simple Email Service. Checks the syntax and the domain’s DNS records and estimates whether the mailbox exists, without sending an email. Flags shared inboxes like info@, disposable addresses and randomly typed input. Every check comes with a confidence level.
Returns
Delivery likelihood: high / medium / low
Source: Amazon SES Developer Guide, Email Validation, November 2026

What each service checks

Check	Address Validation iO plausibility check	Bouncer	Loqate	Amazon SES
Syntax and format	Documented	Documented	Documented	Documented
Domain and DNS/MX records	Not documented	Documented	Documented	Documented
Mailbox check with the mail server	Not documented	Documented	Documented	Documented¹
Catch-all domains	Not documented	Documented	Documented	Not documented
Disposable addresses	Documented	Documented	Documented	Documented
Shared inboxes (info@, support@)	Not documented	Documented	Not documented²	Documented
Full mailbox	Not documented	Documented	Not documented²	Not documented
Free mail provider	Not documented	Documented	Not documented	Not documented
Random input	Not documented	Not documented	Not documented	Documented
Typo suggestion	Documented	Documented	Not documented	Not documented
Rating	Not documented	Score 0–100	Risk level	Confidence level

documented by the providernot documented

¹Amazon SES returns this as an estimate with a confidence level.
²Not part of Loqate’s real-time response.

No service can guarantee that an email arrives. How conclusive a result is depends on the receiving mail server: catch-all domains accept every address, and servers that don’t respond lead to results like “risky”, “unknown” or “timeout”.

Test an email address below ↓

Phone

Phone validation: three services, independent of country

Phone numbers aren’t tied to a map region, so there’s no coverage map here. Address Validation iO checks phone numbers with three services: its own Offline Check, AWS Carrier Lookup and Loqate. All three tell you whether a number is valid and what kind of number it is; they differ in what else they return.

Offline Check
Built into Address Validation iO · free · also checks email addresses
Checks the number against its country’s numbering plan, using the metadata of Google’s libphonenumber: whether the number can exist, its line type, its country and the normalized international format. It runs on Address Validation iO’s own servers, is free and makes no external call. Address Validation iO also runs it before every paid provider, so a number that can’t exist is answered at once, without a paid check. It doesn’t contact the network, so it can’t tell you the carrier or whether the number is in use.
Returns
Mobile · Landline · VoIP · Other · Invalid
What you get back
Validity
Whether the number can exist under its country’s numbering plan: length and number range.
Line type
Mobile, landline, VoIP or other, read from the number range.
Country
The country the number belongs to.
Normalized format
The number in international E.164 format.
AWS Carrier Lookup
Phone provider
Carrier Lookup from AWS End User Messaging. Checks whether a phone number is valid and returns the number type (mobile, landline or other), the country, the normalized international format and the carrier.
Returns
Mobile · Landline · Other · Invalid
What you get back
Validity
Whether the number is valid for its country.
Number type
Mobile, landline or other.
Country
The country the number belongs to.
Normalized format
The number in international E.164 format.
Carrier
The network operator, where the lookup returns one.
Source: AWS End User Messaging SMS, Carrier Lookup, November 2026
Loqate
Phone provider · also an address and email provider
Checks whether the format and length fit the number’s country, confirms the carrier and, for mobile numbers, queries the network’s Home Location Register (HLR) to see whether the number is active. Also reports whether a mobile number has been ported or is roaming.
Returns
Valid · Invalid · Maybe · Type: mobile / landline / VoIP
“Maybe” means: the format is valid, but the network didn’t confirm whether the number is active.
What you get back
Validity
Valid, invalid or maybe.
Number type
Mobile, landline or VoIP.
International and national format
The number as dialed from abroad and as dialed within its country.
Country prefix
The international dialing code, e.g. 49.
Carrier
Name and country of the network that currently serves the number; for mobile numbers also the network codes (MCC/MNC).
Porting
For mobile numbers: whether the number moved to another network, and its original network.
Roaming
For mobile numbers: whether the number is currently roaming, and in which network.
See Loqate’s address coverage ↑Source: Loqate Phone Validation documentation, November 2026

The Offline Check works from the numbering plan alone, so it can’t tell you the carrier or whether a number is in use. AWS Carrier Lookup doesn’t confirm that a number is currently reachable, and for ported numbers it may still show the original carrier. Loqate checks mobile numbers against the network’s register, but returns “maybe” when the network doesn’t answer. None of the services tells you who a number belongs to.

Test a phone number below ↓

Demo

Test an email address or phone number

See how Address Validation iO checks the email address and phone number of an order, with the providers set up for this demo.

Live demo: phone checks run through the Address Validation iO API. Please don’t enter personal data.

Shopify Plus

Address suggestions while typing (Shopify Plus)

Checkout suggests complete addresses from postal data and replaces Shopify’s own autocomplete. Available in these 14 countries:

NLNetherlands
BEBelgium
DEGermany
LULuxembourg
ATAustria
CHSwitzerland
FRFrance
GBUnited Kingdom
ESSpain
DKDenmark
NONorway
FIFinland
SESweden
ITItaly

Methodology

How we grade coverage

Use the best provider for every country

Are you an address data provider? Become a partner

Coverage map

Test an address

Email verification: four services, independent of country

Address Validation iO plausibility check

Bouncer

Loqate

Amazon SES

What each service checks

Phone validation: three services, independent of country

Offline Check

AWS Carrier Lookup

Loqate

Test an email address or phone number

Email

Phone

Address suggestions while typing (Shopify Plus)

How we grade coverage

Loqate

Smarty

Google Address Validation

Postcode.eu

Email verification

Phone validation

What the levels mean — and don’t

Use the best provider for every country