Nexinon

CEP Lookup

Look up the address for a Brazilian CEP (postal code), or find CEPs for an address.

The CEP or address you type is sent to the Nexinon server, which queries the public ViaCEP source on your behalf and caches the result (public data — the address for a CEP, unrelated to who looked it up) for up to 30 days, for faster responses on later lookups. The CEP/address you type is never logged.

The API behind this tool

This tool queries ViaCEP, a free public API with no access key required — the Nexinon server does the lookup on your behalf and caches the result (public data) for up to 30 days, so your IP is never exposed directly to the source on every repeated lookup.

Direct lookup

https://viacep.com.br/ws/{cep}/json/

Reverse search

https://viacep.com.br/ws/{uf}/{cidade}/{logradouro}/json/

Example response
{
  "cep": "01001-000",
  "logradouro": "Praça da Sé",
  "complemento": "lado ímpar",
  "unidade": "",
  "bairro": "Sé",
  "localidade": "São Paulo",
  "uf": "SP",
  "ibge": "3550308",
  "gia": "1004",
  "ddd": "11",
  "siafi": "7107"
}

What CEP is

CEP (Código de Endereçamento Postal) is Brazil's postal code system, created by the postal service (Correios) in 1972 to organize mail delivery across the country. Every CEP has 8 digits and identifies, with a precision that varies by region, anything from an entire municipality (small localities) to a single street, a street segment, or even a specific large recipient (companies with high mail volume, such as banks and government agencies, can have their own dedicated CEP).

The structure of the 8 digits

The CEP's 8 digits follow a geographic hierarchy, left to right: the 1st digit identifies the region (0-9, e.g. 0 is São Paulo city and surroundings, 2 is Rio de Janeiro/Espírito Santo); the 2nd, the sub-region within it; the 3rd, the sector; the 4th and 5th, the subsector; and the last 3, after the dash, form the subsector divider — the finest level, which can narrow down to a specific street or a large recipient. In practice, the more specific the last digits, the more precise the address identified.

Why some addresses don't have a specific CEP

In small municipalities, without enough mail volume to justify splitting the territory into several codes, a single CEP (usually ending in -000) covers the entire city — this isn't a lookup failure, it's how Correios organizes those localities. In large cities, it's rare (but not impossible) for a long street to span more than one CEP depending on the stretch.

Frequently asked questions

A CEP is just a code — it points to an address range, it doesn't replace the address itself (house/building number, complement). Always double-check the exact number alongside the CEP when filling out a form.

It's usually the generic CEP of a small municipality, one that still doesn't have enough mail volume to justify splitting into several codes by neighborhood or street — see "Why some addresses don't have a specific CEP", above.

From the public ViaCEP API (viacep.com.br), free and requiring no access key — see "The API behind this tool", above.

It's a requirement of the ViaCEP API itself, not of this tool — below 3 characters the search becomes too ambiguous (it could match dozens of different streets), and the source rejects the query.

Usually because the street name is written very differently from the official postal service registry (abbreviations, accents, "Avenida" vs. "Av.") — try variations of the name, or double-check the city/state.

The lookup always queries ViaCEP, but the result is cached on our server for up to 30 days — an address is data that changes very rarely, so the response may come from an earlier lookup, with no practical impact on accuracy.

No. Only the lookup result (the address for a CEP, public data) is cached — what you type is never logged in any access or application log.

Nexinon Principles

Server

Server-side execution — data is sent to Nexinon during processing

No account needed

Use it now, no account or password.

Free

No usage limits, no paid plan.

Trustworthy content

Full explanation behind every tool, not just the result.
See the live proof — Trust Center

Other Records tools

View all