Check the DDD and mobile length
Brazil uses +55 followed by a two-digit DDD area code. Anatel lists mobile subscriber numbers as 9XXXX-XXXX. Distinguish older eight-digit local records from the current mobile format.
DATA BUYING / ON YOUR TERMS
When buying a Brazil phone number database, separate mobile records from fixed lines and check formatting, observation times and current availability. Open the BR selection to review a masked preview and request a quote for your criteria.
Sign in to filter and quote. Availability is confirmed for your selection.
BR / +55
Number format reference: +55 · DDD · 9XXXX XXXX
Brazil uses +55 followed by a two-digit DDD area code. Anatel lists mobile subscriber numbers as 9XXXX-XXXX. Distinguish older eight-digit local records from the current mobile format.
A DDD identifies a numbering area, not where the subscriber currently lives. A city-level audience needs its own location evidence; a phone prefix alone does not establish residence.
A Brazilian number that passes numbering rules is not automatically registered on WhatsApp or Telegram. Select the platform you need and inspect its explicit registration result and observation time.
Numbering references: Anatel · Mobile numbering table ↗
Formats show structure only; X denotes a placeholder. They are not subscriber records or inventory guarantees.
START WITH YOUR MARKET
Understand the formats and checks, then confirm current availability.
Check the two-digit area code and nine-digit mobile subscriber number, then compare platform evidence and delivery fields.
Distinguish ordinary ten-digit mobile numbers from other numbering resources, and check the basis for carrier and platform labels.
Normalize domestic 0-prefix and +62 formats before comparing records; avoid a single fixed-length rule or city assumptions from mobile prefixes.
FIELDS BEFORE VOLUME
Field values depend on the source and purchased platforms. Missing values remain unknown.
| Fields | What to check |
|---|---|
identifier · country | An international-format identifier and country code. Unique numbers are counted separately from platform results. |
phone_type · carrier | Number type and carrier metadata. A numbering-range inference does not guarantee the current carrier or reachability. |
created_at | The ingestion timestamp. A 3/7/30/90-day ingestion window is not a promise of rechecking within that period. |
platform_states_json | Purchased platform facts and their observation times. Registration does not establish activity or marketing permission. |
metadata_sources_json | Metadata provenance and method information, distinguishing supplied values from numbering-rule inferences. |
CHECK BEFORE PURCHASE
This is a fabricated masked format example. Sign in for a preview of your selection; complete identifiers are delivered through paid orders.
Choose filters and review a preview ↗BEFORE YOU COMMIT
Pricing follows unique identifiers and selected criteria, with configured rates shown per 10,000 rows. Platform combinations, attribute factors and add-ons may affect the total. Confirm the quantity and review the frozen quote.
Public country pages do not publish inventory counts. Sign in and choose the country, platforms and ingestion window to see an estimate or confirmed count. Saleable quantity is checked before payment.
No. Numbering validity concerns a number’s structure and range. Registration is a fact about a particular platform. Activity needs its own method and time reference. None of these alone guarantees delivery or marketing permission.
After generation completes, the order provides a ZIP containing a CSV and manifest. The manifest records order, quantity and format information. Platform fields follow the purchased scope; historical orders retain their format version.