Talk to a specialist

BLOG VLSM.io

IPv6 on Gov.br: progress and gaps

IPv6 reached www.gov.br, but availability of one portal does not establish complete coverage of subdomains and services. Learn to evaluate the paths your operation uses.

IPv6-only egressConnectivity and intelligence
Globe with IPv6-only outbound connections
IPv6-only egress2001:db8::24Illustrative addresses
Estimated reading time: 8 min8 sections
IPv6 on Gov.br: progress and gaps
IPv6 on Gov.br: progress and gaps
01

A concrete advance with a defined scope

In October 2025, IPv6 activation on www.gov.br was documented. This is a meaningful milestone for a prominent portal and should be recognized as progress. It does not establish that every service, subdomain, and integration in the ecosystem became fully operational over that family. Accurate wording distinguishes the announced portal from the systems encountered throughout a user journey. For an automation, the next question is which destinations actually participate in its task and which of those destinations have been functionally validated.

This article is not a census of every governmental endpoint. Its purpose is to guide coverage assessment around actual operations. A web address may be an entry point for services maintained by different teams and infrastructures. Connectivity can vary even when visual identity is shared. IPv6 presence on one page should therefore not become a promise of universal functionality, and an isolated failure should not be used to dismiss progress throughout the entire environment. Both conclusions would exceed the evidence observed.

CONNECTIONS IN MOTIONThe path of your connection
ApplicationJob or integration
ConnectivityIPv6-only egress
DestinationSystem or service
The illustrated service uses IPv6-only Internet egress. IPv4 egress requires a separate service. The animation does not represent live traffic.
02

The service journey is the unit of analysis

Consider an illustrative journey: locate a service, authenticate a user, enter information, query a record, and download a document. Each step may use a different hostname. The initial portal may respond over IPv6 while a later dependency uses IPv4, or the entire path may work over both families. Observing the first page alone cannot resolve this. Record redirects and connections required for the authorized task, distinguishing essential components from auxiliary resources such as images or measurement tools that do not determine procedure completion.

Build the inventory from known workflows and available documentation rather than indiscriminate scanning. For each endpoint, record purpose, known owner, application protocol, and its relationship to other steps. Include the test origin because a personal workstation may have a different path from the server running the bot. Inventory should locate dependencies, not collect credentials or unnecessary personal information. The resulting material supports discussion of a specific failure with technical support without resorting to broad claims about the entire Gov.br ecosystem.

03

An AAAA record is a signal, not the complete test

An AAAA record indicates that name resolution can provide an IPv6 address for that name. By itself, it does not confirm connectivity, TLS negotiation, or application functionality. Observe which name was queried, which resolver answered, and when the query occurred. In architectures using transition mechanisms, the client-visible answer may involve synthesis and needs appropriate interpretation. Diagnosis should connect DNS information with the actual path rather than treating an isolated query as a certificate that the whole application supports IPv6.

After resolution, confirm connection to the correct endpoint, certificate validation, and the expected response. Then execute the corresponding functional step. An error response may show that networking worked but authorization was missing; a timeout can have several causes. Classify results by layer and retain enough evidence to reproduce the test. This separation prevents mistaken conclusions, such as blaming an IP family for a business-rule rejection or treating any server response as proof that a government query was successfully completed.

TRAFFIC AND ADDRESSINGOne IPv6 service. IPv6-only egress.
Source2001:db8::24
Destination2001:db8::20
Return2001:db8::24
The outbound path of this service uses IPv6 only. Reaching an IPv4 destination requires a separate IPv4 service; there is no dual-stack egress. Illustrative addresses.
04

Gov.br does not represent every Brazilian government

Assessment of the federal portal should not automatically extend to states, municipalities, or entities operating their own infrastructure. Each organization may maintain different systems, contracts, and update processes. Even within one body, separate services may follow different architectures. Companies serving multiple public entities need an inventory reflecting that diversity. Classify destinations by institution and function while preserving the technical endpoint name. This identifies confirmed coverage and areas still requiring assessment without imposing one label on environments that may have substantially different operational characteristics.

Distinguish domain, service, and administrative entity as well. One domain may host several applications; one application may use several domains; an institution may share infrastructure with others. These relationships prevent counting names and directly concluding how many bodies adopted IPv6. For a public survey, establish criteria and methodology before collecting data. For maintaining an automation, focus effort on required workflows. In either case, conclusions should match the observed object and the period in which verification occurred, rather than extending beyond the documented sample.

05

Plan automation around partial coverage

While coverage varies by destination, applications need connectivity appropriate to each workflow. With VLSM.io, this means selecting an IPv4-egress service or an IPv6-egress service for each workflow. If both are needed, they are separate services; there is no dual-stack delivery.

The important point is not to remove a required path merely because the main portal gained IPv6. Keep configuration explicit, monitor the family used, and test session continuity. Where a process requires a stable source, connection changes need deliberate handling and assessment of their effects on authentication and application state throughout the complete transaction.

Connectivity does not replace authorization or change service limits. Use official APIs and channels where available and suitable for the project. For authorized RPA tasks, define concurrency, intervals, and error handling that avoid excessive load. An IPv6 failure should not trigger unlimited attempts across both families. Distinguish transient errors, unavailability, and explicit refusal, applying the appropriate policy to each. Robustness comes from understanding outcomes and controlling execution, rather than multiplying connections until one attempt appears to work without understanding why.

06

Track changes without turning assumptions into facts

Availability can change after modifications to hosting, protection, authentication, or content delivery. A compatibility inventory therefore needs dates and review. Define lightweight checks for critical workflows and investigate relevant changes while respecting the accessed environment. Record observations instead of automatically updating a conclusion about the entire institution. If an endpoint starts working over IPv6, validate its associated journey; if it stops responding, investigate possible causes before declaring that support has been removed from the service or the broader organization.

When a gap is found, describe it actionably: endpoint name, affected function, tested family, origin, timestamp, and expected result. Avoid sensitive information in shared records. Such a report lets the responsible team reproduce the issue and distinguish local failure from a service-side problem. It also supports tracking remediation without vague statements that something does not work over IPv6. Technical communication should preserve recognition of existing progress while objectively identifying components that still require changes or additional investigation before compatibility can be confirmed.

FROM CONNECTION TO RESULTTurn requirements into an observable operation.
Plan
Connect
Monitor
Destination planning, connectivity configuration, and result validation are complementary steps. The animation represents this workflow.
07

Connectivity aligned with required destinations

For companies accessing government systems, infrastructure choices should begin with required destinations and authorized tasks. Identify workflows dependent on IPv4, those validated over IPv6, and those still inconclusive. Add source, concurrency, and continuity requirements. This supports more accurate delivery planning than selecting a family by preference or reacting to news about the main portal. The plan should accommodate current conditions and allow revision as services evolve, without requiring the operation to be rebuilt whenever an external system changes its connectivity or architecture.

VLSM.io can help evaluate IPv4, IPv6, and IP Proxy options within that scope, validating paths required by the project. The objective is not to promise universal access to every government system. It is to provide connectivity aligned with known, observable requirements. Progress on www.gov.br is positive; recognizing that coverage must be examined service by service makes that evolution more useful to teams developing integrations, working with public data, and maintaining automations whose business value depends on continuous and predictable operation.

08

Institutional references

Reference documents on the topics covered in this article.