Summary

  • GX Internet is not a paper-only name in the public record. Registro.br RDAP records identify AS262603 as a direct Brazilian allocation registered on September 30, 2011, with GX INTERNET E WEB HOSTING SERV DE INFORMATICA LTDA as registrant and CNPJ 10.558.721/0001-75 attached to the autonomous system and the 177.85.96.0/21 IPv4 block.
  • The public service surface points strongly toward HomeHost: IPinfo associates AS262603 with homehost.com.br, HomeHost's infrastructure page names AS262603, and Registro.br contact records list HOMEHOST Hospedagem de Sites as the administrative and abuse contact. That linkage is operationally meaningful, but it also creates a contract question because HomeHost's public terms name HOMEHOST HOSPEDAGEM DE SITES LTDA ME, CNPJ 42.011.853/0001-79, as the service provider.
  • The network footprint looks modest and specific rather than hyperscale. BGP views from bgp.tools and Hurricane Electric show three originated IPv4 /24s, no originated IPv6, and two observed IPv4 peers or upstreams. That can be enough for a focused Brazilian hosting provider, but it gives buyers concrete checks to make around redundancy, IPv6 needs, failover, and upstream concentration.
  • HomeHost's own service pages make the operational bargain explicit: customers get cloud, VPS, cPanel hosting, domain, email, support, and claimed network/service uptime guarantees, while the terms and cloud FAQ put backup responsibility substantially on the customer. For serious workloads, assurance begins with the contract, recovery tests, and escalation path, not with the brand name alone.

A registry name is only the first control point

GX INTERNET E WEB HOSTING SERV DE INFORMATICA LTDA matters because it sits at the boundary where a company name, an autonomous system, and a customer-facing hosting brand appear to meet. That boundary is where small and mid-sized infrastructure providers often become most interesting. They may not sell a global cloud story, yet they can carry regional sites, reseller platforms, email estates, control panels, and locally supported workloads that are deeply important to customers.

The first verifiable point is the Brazilian internet-number record. Registro.br's RDAP record for AS262603 identifies the autnum handle as 262603, type "DIRECT ALLOCATION," country BR, with registration on September 30, 2011 and last change on June 29, 2022. The registrant entity is GX INTERNET E WEB HOSTING SERV DE INFORMATICA LTDA, with public ID type CNPJ and identifier 10.558.721/0001-75. The related RDAP IP record for 177.85.96.0/21 ties the same entity to an allocated IPv4 range from 177.85.96.0 through 177.85.103.255.

That is useful proof of resource holding, but it is not the same as a full assurance case. Registry data tells a buyer who is named on the internet-number record and which contacts sit on the record. It does not by itself prove the current customer contract, the support desk's authority, the backup model, the real routing failover design, or whether the company shown in a shopping cart is the same legal entity that appears in network records. The public evidence has to be read as a chain.

The HomeHost link is strong, but the legal names need attention

The chain from GX Internet to HomeHost is visible in several places. IPinfo's AS262603 page lists GX INTERNET E WEB HOSTING SERV DE INFORMATICA LTDA as the AS name, country Brazil, website homehost.com.br, 1,155 hosted domains, 768 IPv4 addresses, no IPv6 addresses, ASN type "Hosting," and registry LACNIC. HomeHost's own infrastructure page says the company operates its own datacenter, describes global connectivity, states that its link totals 20 Gbps "through AS 262603," and gives a network uptime guarantee of 99.8 percent.

Registro.br's RDAP record also lists HOMEHOST Hospedagem de Sites as the administrative and abuse contact, with the email [email protected]. That is not merely a search-engine association. It places the HomeHost name inside the operational contact path for the GX Internet network resource.

At the same time, HomeHost's public corporate pages name a different legal entity. The HomeHost "Quem Somos" page lists "HOMEHOST HOSPEDAGEM DE SITES LTDA ME," CNPJ 42.011.853/0001-79, at Rua Paissandu 35 / 601 in Rio de Janeiro. The HomeHost service terms also say that the hosting terms are provided by HOMEHOST HOSPEDAGEM DE SITES LTDA ME under that CNPJ. Public CNPJ mirrors accessed during this research pass describe GX Internet under CNPJ 10.558.721/0001-75 and HomeHost under CNPJ 42.011.853/0001-79, both active and both associated with the same Paissandu 35, apartment 601 address in Rio de Janeiro.

That pattern is not proof of a weakness. It may reflect a group structure, brand operator, legacy allocation holder, or ordinary corporate change. But for procurement it is a live question: which entity signs the customer contract, which entity controls the AS and address space, which entity handles abuse and operational notices, and which one appears on invoices, data-processing terms, and any service-credit claim? A low-friction hosting purchase can skip those questions. A business-critical workload should not.

The routed footprint is compact and checkable

GX Internet's network evidence is unusually concrete for a small provider profile. bgp.tools lists AS262603 as active and allocated under NIC.BR, registered on September 30, 2011, with three IPv4 prefixes originated and no IPv6 prefixes originated. It shows the originated prefixes as 177.85.99.0/24, 177.85.100.0/24, and 185.169.99.0/24, with observed upstreams AS9186 Onitelecom - Infocomunicacoes, S.A. and AS33182 HostDime.com, Inc. Hurricane Electric's BGP Toolkit independently shows Brazil as country of origin, three originated and announced IPv4 prefixes, zero IPv6, two observed IPv4 peers, and 768 originated IPv4 addresses.

Those are not abstract numbers. They describe the operating surface customers should test. Three /24s can support a real hosting environment, but they also make the routing design easy to inspect. A buyer can ask whether each customer-facing product depends on the same two transit paths, whether the Portuguese 185.169.99.0/24 route is part of production hosting or a separate service point, whether DNS and mail sit on the same network as web hosting, and what happens if one upstream path is degraded.

The absence of observed originated IPv6 is also a product signal. Many small business sites can still run on IPv4-only hosting, but IPv6 is no longer a niche requirement for every customer. Public-sector buyers, network-heavy SaaS operators, and teams with dual-stack monitoring expectations should treat "no originated IPv6 in public BGP views" as a question to resolve before contract signature. It may be acceptable. It should not be invisible.

The service story is cPanel hosting with cloud and VPS extensions

HomeHost's own pages describe a provider that grew from shared hosting into a broader hosting portfolio. The company history page says HomeHost began in 2006 with fewer than ten hosting servers, presents itself as one of the early Brazilian companies offering cPanel hosting, and says it has invested in infrastructure and technical staff over time. The site navigation and product pages list site hosting, WordPress hosting, Python and Node.js hosting, professional email, domain registration, reseller hosting, VPS, cloud hosting, SSL, backup, tutorials, and a customer area.

The cloud hosting page positions the offer around Private Cloud and VPS-style server control rather than an abstract hyperscale platform. Its FAQ says HomeHost delivers the server already configured and optimized with security directives, says its support team has 15 years of experience managing cPanel and Linux servers, says customers can have full root access to VPS servers through SSH or cPanel administration, and states that cloud servers include an uptime SLA of 99.9 percent with proportional credit for technical problems.

That is a familiar small-provider promise: less self-service sprawl than a hyperscaler, more local support and cPanel familiarity, and a product surface aimed at websites, email, commerce sites, agencies, and smaller server estates. The tradeoff is that the customer must inspect what is included rather than importing assumptions from larger cloud brands. Is monitoring included? Is the firewall policy managed? Are OS updates handled by HomeHost or by the customer? Are database backups, mailboxes, DNS, and off-site copies part of the purchased plan, or are they separate responsibilities?

The public pages answer some of those questions and leave others for the contract.

Backup responsibility is the clearest customer risk

The most important operational clause in the public material is not the uptime percentage. It is backup responsibility. The HomeHost cloud FAQ says plainly that HomeHost does not make backups of Private Cloud servers and that the customer needs to download backups frequently and store them outside the HomeHost server. The same page says a premium backup option can be contracted for some cases. The service terms go further for general hosting: the user is responsible for maintaining local copies of files, email, databases, and other content, while HomeHost says it has no obligation to maintain server backups and may provide restoration only depending on technical availability.

That is not unusual in low-cost or control-panel hosting, but it changes the real assurance model. A customer buying GX/HomeHost services should not treat "hosted" as "protected." The operating proof is a restore test: can the customer export a cPanel backup, restore a database, recover a mailbox, rebuild DNS, and move the site to another network if needed? If the workload has revenue, legal, or continuity value, the backup architecture should be designed outside the provider account and tested on a schedule.

The terms also say hosting is intended for users with technical knowledge and that HomeHost's team will answer technical questions but does not assume training responsibility for users lacking basic knowledge. That makes the support model more explicit. It is support for a technical service, not an outsourced operations department unless the customer buys and documents that scope separately.

Local support is a real advantage only when escalation is real

HomeHost presents local-language support as part of the value proposition. The support page routes users to WhatsApp, support email at [email protected], and phone numbers for several Brazilian cities, including Sao Paulo, Rio de Janeiro, Brasilia, Belo Horizonte, Recife, Porto Alegre, Florianopolis, Salvador, Fortaleza, Vitoria, Goiania, Cuiaba, Curitiba, and Campinas. The footer gives support hours of Monday to Friday from 08:00 to 00:00 and Saturday to Sunday from 09:00 to 18:00. For a Brazilian small business or agency, that is more concrete than a global ticket queue with no local phone surface.

But support hours and phone numbers are still only access points. For infrastructure governance, the stronger questions are about authority and escalation: can first-line support restart a VPS, escalate a routing issue, restore from a managed backup product, or approve service credits? Does abuse handling share the same contact path as technical support? Are incident notices posted publicly or only sent to account contacts? Are there maintenance windows? The public material shows the front door; the buyer has to verify the runbook behind it.

That is where GX Internet's resource evidence and HomeHost's support surface come together. If AS262603 is the network under the service, network incidents will not always look like ordinary control-panel tickets. A serious customer should have both support and abuse/registry contact expectations documented, especially if mail deliverability, DNS hosting, or customer-facing ecommerce depends on those prefixes.

Locality can help, but only with evidence of where data lives

GX Internet and HomeHost have a Brazilian identity trail, Rio de Janeiro corporate addresses, Brazilian support channels, and Brazilian internet-number records. HomeHost's infrastructure page also says it operates its own datacenter and names connectivity partners. For customers concerned with data locality, language, jurisdiction, and support proximity, those are meaningful signals. They may make a local provider more attractive than a global platform for a Brazilian website, agency reseller stack, or cPanel-heavy small business portfolio.

Still, locality is not a synonym for data-sovereignty proof. Public BGP and registry records show resource control and routing. They do not prove the exact physical location of every backup, mirror, support tool, customer database, or third-party service. IPinfo's observed pingable IPs include responses associated with Sao Paulo and Lisbon, and BGP views show a 185.169.99.0/24 prefix described as HOMEHOST-PT-1 in Hurricane Electric's view. That does not mean customer data is or is not stored in Portugal.

It means customers with strict locality requirements should ask for a service-specific data-location statement, backup-location statement, and subprocessors or upstream-provider list.

The same discipline applies to sovereignty claims in reverse. A local provider can improve jurisdictional fit, support access, and latency for some workloads. It can also concentrate risk if backups, DNS, support credentials, and production servers all sit in one account or one operational team. The right question is not "local or global?" It is "which parts of the service are local, which parts are outsourced or routed through partners, and how does the customer recover if one layer fails?"

The buyer's checklist is the story

GX Internet should be assessed as a verifiable infrastructure lead, not as a brand shortcut. The evidence supports a real Brazilian network allocation connected to HomeHost's public hosting business. It supports a compact BGP footprint, a cPanel and VPS-oriented service portfolio, public support channels, and clear statements about uptime and backup responsibility. It also reveals a legal-name split that deserves ordinary procurement attention before a buyer treats the service as operating assurance.

For low-risk sites, that may be enough: a local hosting provider, Portuguese support, familiar control panels, and a visible AS. For regulated content, revenue sites, SaaS dependencies, mail-heavy organizations, or agencies hosting client portfolios, the next step should be documentary rather than rhetorical. Confirm the contracting entity. Confirm whether GX Internet or HomeHost appears on invoices and service commitments. Confirm IPv6 requirements. Confirm how AS262603 is protected from upstream failure. Confirm backup scope, restoration time, and off-provider copies.

Confirm whether the SLA applies to the exact product being purchased, and how credits are requested.

The public record does not say "avoid." It says "verify the operating chain." GX Internet's value is that there is enough public evidence to ask precise questions. The risk is that a buyer stops at the name, the price, or the promise of local support. In hosting, assurance is not the presence of a company in a registry. It is the alignment between the company in the registry, the brand in the contract, the network that carries the service, the people who answer during an incident, and the customer's tested path back to service when something fails.