Ukrnames and the cost of keeping Ukrainian domains reachable

The first price is not a domain

The most revealing Ukrnames tariff is not the annual price of a .UA name. It is the price of putting a physical machine in a Kharkiv data center and accepting what that means during war. Ukrnames advertises colocation from 1,600 hryvnia per month for a 1U server or switch, with power paid separately, a shared 1Gbps port, unlimited traffic subject to a 15TB monthly fair-use point, one IPv4 address and IPv6 allocation. It then prices electricity compensation as a separate monthly cost: a 100W device is shown at 1,704 hryvnia per month, 200W at 3,407 hryvnia, 500W at 8,518 hryvnia and 1,000W at 17,035 hryvnia (https://www.ukrnames.com/eng/colocation/). That is the first hard economic clue. In peacetime, the customer might read those numbers as ordinary hosting arithmetic. In Kharkiv, they are a bill for staying reachable when power, access, traffic and physical infrastructure cannot be treated as background conditions.

The same colocation page makes the contract more explicit. Ukrnames says it operates two data centers in Kharkiv, uses two 10Gbps connections to separate providers, has biometric access, diesel-generator backup with automatic start, round-the-clock support, video surveillance and security, N+1 cooling and fire-extinguishing systems. It also says guaranteed data-center uptime is at least 99.3 percent annually, average response time is up to 30 minutes, customer equipment access is available around the clock except curfew in wartime, and if a data center is shelled and customer equipment is damaged, that is treated as force majeure beyond the provider's liability (https://www.ukrnames.com/eng/colocation/). The business mechanism is unusually visible. Continuity is priced. Some risk is absorbed by the provider through power, cooling, support and network design. Some risk is left with the customer through force majeure, backup responsibility and the absence of colocation DDoS protection.

That is why Ukrainian Internet Names Center should be read as more than a domain-name shop. The company behind Ukrnames is a registrar, hoster, colocation seller, autonomous-system operator and payments interface. It gives customers small invoices for domain renewal, shared hosting, VPS, SSL and DNS, but the larger economic product is trust under stress. A customer pays the registrar to keep a name registered, the DNS usable, the account recoverable, abuse disputes bounded by rules, and hosting or colocated infrastructure working well enough that the company, NGO, public body or software service remains visible. War changes the price of every one of those tasks. It raises the value of local Ukrainian support and local routes, but it also raises the input cost of producing resilience.

The governing argument is simple: Ukrnames monetizes the last mile of confidence for Ukrainian internet presence. Its defensibility does not come from owning a global cloud platform. It comes from the dense bundle of small but essential functions that make a Ukrainian web identity hard to lose: a registrar credential, .UA and local-domain administration, a Kharkiv hosting footprint, payment methods that clear quickly, network resources, route relationships, support rules, and a public contract that tells customers where the provider stops carrying risk. The better question is not whether Ukrnames is large. It is whether these small infrastructure functions become more valuable when staying online in Ukraine becomes a daily operating cost.

A registrar turns legal identity into recurring trust

The identity record is stronger than the directory snapshot suggests. Ukrnames' own information page says Ukrainian Internet Names Center LLC was founded in 2007, lists its main activities as domain registration, web hosting and SSL certificates, gives a Kharkiv address at Heroiv Pratsi 28A, and says the brand has been an official .UA domain registrar and ICANN-accredited registrar since 2008 (https://www.ukrnames.com/eng/info/). IANA's registrar identifier table lists registrar ID 1436 as "Center of Ukrainian Internet Names (UKRNAMES)", with accredited status and an RDAP endpoint at https://rdap.ukrnames.com/ (https://www.iana.org/assignments/registrar-ids/registrar-ids.xhtml). ICANN's accredited registrar list also identifies Center of Ukrainian Internet Names (UKRNAMES) under IANA ID 1436 in Ukraine, with public contact details (https://www.icann.org/en/contracted-parties/accredited-registrars/list-of-accredited-registrars). Hostmaster's Ukrainian registrar page lists the registrar handle ua.ukrnames, identifies the Ukrainian-language legal entity as the Ukrainian Internet Names Center LLC, places it in Kharkiv, and marks DNSSEC in the registrar table (https://www.hostmaster.ua/registrars/).

Those records matter because registrar trust is a licensing and process business before it is a retail website. A customer buying a .UA, COM.UA, ORG.UA, .COM or SSL-linked service is not merely buying a line in a shopping cart. It is buying the provider's ability to keep a domain under correct sponsorship, process renewal and transfer events, respect registry and dispute rules, maintain contacts, and prevent a clerical or account failure from becoming a public outage. Ukrnames' pricing page makes this retail layer visible. It lists .COM registration, renewal and transfer at 824 hryvnia, COM.UA at 715 hryvnia, ORG.UA at 588 hryvnia, .UA at 3,526 hryvnia and the Cyrillic .UKR equivalent in its English table at 999 hryvnia; restore fees are materially higher, including 7,052 hryvnia for .UA and 1,505 hryvnia for COM.UA (https://www.ukrnames.com/eng/domain/prices/).

The spread between registration and restore is not only a late-payment penalty. It is a signal about what failure costs. A domain that enters deletion or redemption is no longer a routine annual expense. It is an urgent identity-recovery problem. For a business that depends on email, invoices, app logins, public procurement, customer support or donations, missing a renewal can interrupt work far beyond the registrar fee. Ukrnames' value is therefore partly preventative. It sells cheap recurring orderliness so that customers avoid expensive disorder.

The .UA rules sharpen the point. Ukrnames' .UA page describes .UA as the prestigious national domain, says more than 25,000 names are registered in the zone, and states that registration requires a trademark valid in Ukraine. It also says .UA applications are moderated by the administrator and may take from one to 14 days; the first pending application temporarily blocks the same domain from being registered through another registrar; after expiration, the domain has a 28-day auto-renew grace period and a 30-day redemption period; and the domain cannot be renewed if the underlying trademark has expired (https://www.ukrnames.com/eng/domain/prices/ua/). By contrast, Ukrnames' COM.UA page describes that zone as the most popular Ukrainian commercial domain, with more than 300,000 names, no documentation requirement, automatic registration after payment, and the same grace and redemption timing pattern (https://www.ukrnames.com/eng/domain/prices/com.ua/). The economics differ by zone: .UA is slower, more documentary and more brand-sensitive; COM.UA is faster and broader. A registrar that can manage both sells not just names but appropriate friction.

Unit economics run through payments and prepaid discipline

The payment terms show why the company can serve small customers without turning every invoice into a support burden. Ukrnames' payment page emphasizes automated self-service ordering. It accepts bank payment, Privat24 using EDRPOU code 35351405, Visa and Mastercard through LiqPay and WayForPay, and cryptocurrency through Whitepay for Bitcoin, Ethereum and Tether. Card payments are described as fully automated and credited immediately; cryptocurrency payments are also described as automated after processing, but the customer must send the exact amount shown in the invoice (https://www.ukrnames.com/eng/info/payment-methods/). That payment design matters. A registrar-hosting provider cannot earn good margins if every low-value renewal requires manual reconciliation. Immediate crediting protects the customer from expiration and protects the provider from carrying unpaid service.

The public offer agreement reinforces the same discipline. Ukrnames' service agreement says services are provided on 100 percent prepayment, in Ukraine's national currency, at tariffs in force at the time of provision; services are considered paid when funds are received; late or missing payment may lead to suspension or stoppage; and customers must provide true and accurate information. It also says lack of accurate contact information, or failure to respond to contact-confirmation requests within 15 days, can lead to termination or suspension (https://www.ukrnames.com/eng/info/agreement/). Those terms are not unusual in hosting. In wartime infrastructure economics they are central. The provider cannot make continuity promises while financing thousands of unpaid or unreachable accounts. Prepayment and contact discipline convert a messy customer base into something the provider can support.

The legal and financial filings visible through Ukrainian company data add scale. Opendatabot's record for EDRPOU 35351405 identifies Ukrainian Internet Names Center LLC, registration date September 25, 2007, Kharkiv address, statutory capital of 88,000 hryvnia, main activity of data processing, hosting and related activities, and director Oleksandr Loboda. It also reports 2025 revenue of 14,416,400 hryvnia, 2025 net profit of 97,900 hryvnia and 2025 assets of 1,352,200 hryvnia, while showing public-procurement activity with buyers including PrivatBank and several state or quasi-public bodies (https://opendatabot.ua/c/35351405). Those numbers should not be overread as audited investor diligence. They are still useful: a company with more than 14 million hryvnia in reported revenue and less than 100,000 hryvnia in net profit is not showing a fat-margin software business. It looks more like a working infrastructure service provider where registry costs, power, staff, network, payment fees, hardware, taxes and support consume most of the invoice.

That margin profile explains why small contractual details matter. The domain pricing FAQ says prices depend on exchange rates, registrar costs and the domain-zone administration cost, and that prices are valid at order time (https://www.ukrnames.com/eng/domain/prices/). In other words, the provider does not want to promise a stable hryvnia price when upstream registry or currency inputs move. Hosting and VPS pages then add the recurring-service side. General shared hosting begins at 181 hryvnia per month for the "First SSD" plan with one website, 2GB SSD, unlimited traffic, email and MySQL, while the "5 websites SSD" plan is 240 hryvnia per month (https://www.ukrnames.com/eng/hosting/). Ukrainian hosting plans are higher: the U15 plan is 290 hryvnia per month for 15GB and one website, U25 is 541 hryvnia for 25GB and five websites, and U35 is 750 hryvnia for 35GB and 10 websites, with backup to another data center and DDoS-related qualifications (https://www.ukrnames.com/eng/hosting/ukraine/). KVM VDS in Ukraine starts at 399 hryvnia per month for VM1-KVM with two cores, 2GB RAM, 20GB SSD, one IPv4 address and 5TB traffic (https://www.ukrnames.com/eng/vds/).

Those prices make Ukrnames accessible to small Ukrainian organizations. They also leave little room for sloppy support or unmanaged risk. If a customer pays 181 or 399 hryvnia per month, the provider cannot behave like a bespoke managed-services firm. It must automate provisioning, billing, renewals, DNS, abuse handling, backups and support triage. The high-value economic asset is not any one plan. It is the operating system of rules that lets many small contracts remain profitable enough to keep alive.

The network evidence makes the hosting claim more concrete

Many domain registrars resell hosting without owning meaningful internet infrastructure. Ukrnames' public routing record suggests a more substantial position. RIPEstat's overview for AS197726 identifies the holder as "UKRNAMES-AS Ukrainian Internet Names Center LTD" and shows the ASN as announced (https://stat.ripe.net/data/as-overview/data.json?resource=AS197726). RIPE's RDAP record for aut-num 197726 shows AS197726, status active, registration in April 2011, the registrant organization Ukrainian Internet Names Center LTD, and associated administrative, technical and abuse contacts (https://rdap.db.ripe.net/autnum/197726). A RIPE database search shows the UKRNAMES-AS aut-num importing and exporting through providers including Maxnet and Pitline, exchanging at DTEL-IX, and announcing AS-UKRNAMES (https://rest.db.ripe.net/search.json?query-string=AS197726&source=ripe&type-filter=aut-num&flags=no-filtering).

RIPEstat's announced-prefixes endpoint for AS197726 lists 17 announced prefixes, including 195.123.248.0/22, 91.231.84.0/23, 91.231.86.0/23, 185.112.12.0/23, 185.112.14.0/23, 193.9.28.0/24, 195.64.154.0/23, several 195.123.* /24s, 212.86.110.0/24, 212.86.111.0/24, 212.86.113.0/24, and the IPv6 prefix 2a02:128:2::/48 (https://stat.ripe.net/data/announced-prefixes/data.json?resource=AS197726). Hurricane Electric's BGP summary for AS197726 reports 17 originated and announced prefixes, 11 RPKI-valid originated prefixes, no invalids, and DTEL-IX participation in Kyiv at IPv4 address 193.25.180.154 (https://bgp.he.net/AS197726). BGP.tools likewise presents AS197726 as registered to Ukrainian Internet Names Center LTD and shows valid route-origin status for many of the visible prefixes (https://bgp.tools/as/197726).

PeeringDB adds the commercial flavor. Its network record names Ukrainian Internet Names Center, aka Ukrnames LLC, lists ASN 197726, IRR set AS-UKRNAMES, looking glass https://lg.ukrnames.com/, 30 IPv4 prefixes, one IPv6 prefix, 5-10Gbps traffic level, a balanced traffic ratio and an open peering policy (https://www.peeringdb.com/net/26832). The PeeringDB interconnection record shows Ukrnames at DTEL-IX's public peering fabric with a 10Gbps port, route-server peering enabled and operational status true (https://www.peeringdb.com/api/netixlan?net_id=26832). DTEL-IX describes itself as a Ukrainian internet exchange point with public peering, route-server service, traffic-management benefits, transit savings, fault-tolerance advantages and connection options across Ukrainian facilities (https://dtel-ix.net/en/). Its public-peering page explicitly markets peering as a way to improve connectivity, reserve routes, improve fault tolerance and manage outgoing traffic (https://dtel-ix.net/en/srvc/public-peering).

For customers, this evidence does not prove perfect uptime. It does prove the host is not just a brochure wrapped around someone else's shared server. Ukrnames appears in the routing layer, operates a public AS, announces its own prefixes, has upstreams and peers, exposes a looking-glass address, and participates in a Ukrainian exchange environment. That gives the company more knobs to turn when traffic, upstream prices or local reachability change. It also creates costs: transit, peering, routers, address management, abuse response, RPKI hygiene, technical staff and incident handling. The network makes the value proposition more credible, but it also puts Ukrnames in the infrastructure business rather than pure retail.

The DNS-WHOIS anycast clue is small but important

There is another network clue that belongs in the economics, even though it should not be inflated into a grand platform claim. RIPEstat's overview for AS49227 identifies the holder as "TCI-ANYCAST-NET Ukrainian Internet Names Center LTD" and shows the ASN as announced (https://stat.ripe.net/data/as-overview/data.json?resource=AS49227). RIPEstat's announced-prefixes endpoint shows 195.123.192.0/24 as the announced prefix for AS49227 (https://stat.ripe.net/data/announced-prefixes/data.json?resource=AS49227). The RIPE database object describes the AS name as TCI-ANYCAST-NET, includes the description "TCI DNS-WHOIS ANYCAST", ties the organization to Ukrainian Internet Names Center LTD, and shows route-policy relationships through AS197726 and other providers (https://rest.db.ripe.net/search.json?query-string=AS49227&source=ripe&type-filter=aut-num&flags=no-filtering).

This does not mean Ukrnames runs a global anycast estate comparable to large public-DNS providers. It means the company has a visible technical footprint around DNS-WHOIS service that is more specialized than ordinary shared hosting. Anycast matters economically because DNS and registry-adjacent services are judged by reachability, latency, route diversity and operational discipline. A customer may never ask which AS handles a support page, but a registrar's reputation depends on these invisible layers. When DNS or WHOIS infrastructure is unreliable, the failure feels larger than a single website outage because it can affect discovery, ownership verification, automation and trust in the registrar itself.

The anycast record also clarifies why Ukrnames' margins should be read with care. A retail customer sees a 715-hryvnia COM.UA renewal or a 399-hryvnia VDS plan. Behind that invoice sit specialized resources that must be maintained even when individual customer revenue is small: autonomous systems, route objects, DNS service, abuse mailboxes, registry procedures, account recovery and support staff who understand domain states. These shared costs make the business look deceptively simple from the outside. It is easy to see a domain price and compare it with another storefront. It is harder to see whether the provider has enough technical depth to keep the registration and resolution environment coherent when Ukraine's power, routes or payment systems are stressed.

The role-contact record for AS49227 makes the operating surface more concrete. The RIPE role object associated with the Ukrnames network separates support, billing, spam and attack contact channels, including support@ukrnames.com, info@ukrnames.com and abuse@ukrnames.com (https://rest.db.ripe.net/search.json?query-string=AS49227&source=ripe&type-filter=aut-num&flags=no-filtering). That division is not glamorous, but it is the plumbing of trust. A provider that cannot sort billing from technical support and abuse will struggle to keep upstreams, registries and customers aligned. In wartime conditions, that administrative order becomes more valuable because every exception has a higher chance of arriving during an outage, curfew, bank delay or staffing disruption.

Kharkiv is both asset and risk

Ukrnames' location is not an incidental footnote. The company gives a Kharkiv legal address, correspondence address and data-center location, and its colocation page describes two data centers in Kharkiv (https://www.ukrnames.com/eng/info/contacts/; https://www.ukrnames.com/eng/colocation/). Kharkiv gives the brand local substance: support, facilities and infrastructure are not abstract claims. But since February 2022, it also turns the business into a case study in how internet-service resilience is produced under military and energy stress.

Ukraine's internet has repeatedly shown the unusual combination of damage and adaptation. RIPE Labs' "Ukraine as a Laboratory of Internet Resilience" argues that Ukraine's internet did not collapse despite damaged cables, destroyed power infrastructure, cyberattacks and missile strikes, and cites estimates that by August 2023 roughly a quarter of telecom infrastructure had been damaged or destroyed while the World Bank put sector damage costs at $1.6 billion as of February 2023 (https://labs.ripe.net/author/eliza-rohotska/ukraine-as-a-laboratory-of-internet-resilience/). The Internet Society's Pulse report gives Ukraine an Internet Resilience Score of 62 out of 100 and records DNSSEC adoption at 41 percent, close to the European average in its 2026 view (https://pulse.internetsociety.org/en/reports/ua/). Those are country-level indicators, not Ukrnames-specific performance data. They still frame the market: resilience has become an operating condition, not a marketing adjective.

Cloudflare's measurements show how power and military attacks translate directly into internet traffic. In its first-quarter 2026 disruption summary, Cloudflare reported that Russian attacks on energy infrastructure caused Ukrainian connectivity disruptions in January 2026, including a January 26 attack on Kharkiv energy infrastructure that produced an observed roughly 50 percent traffic drop in Kharkiv beginning around 19:15 local time, with recovery through January 27 as power was restored (https://blog.cloudflare.com/q1-2026-internet-disruption-summary/). Cloudflare's earlier one-year war review described October 2022 attacks on Ukrainian energy infrastructure that pushed national traffic about 35 percent below the prior week's level, with Kharkiv down about 80 percent at one point (https://blog.cloudflare.com/one-year-of-war-in-ukraine/). NetBlocks also recorded early-war connectivity disruptions in Ukraine in February 2022, including fixed-line losses around Kharkiv amid explosions (https://netblocks.org/reports/internet-disruptions-registered-as-russia-moves-in-on-ukraine-W80p4k8K). Internet Society Pulse separately recorded March 2023 reductions after missile attacks, with Kharkiv among the affected regions (https://pulse.internetsociety.org/en/shutdowns/internet-connectivity-reduced-in-ukraine-march-2023/).

This context changes the meaning of Ukrnames' service promises. A diesel generator, another data center for backups, two 10Gbps provider links, remote restart, server monitoring by SMS, separate backup servers, IP-KVM, support ticketing and curfew-qualified access are not deluxe features in that environment. They are the working machinery behind a domain, VPS or colocated server that does not disappear after an energy hit. At the same time, the public terms prevent romantic overstatement. Ukrnames does not say it can defeat war. It says data-center shelling is force majeure, colocation DDoS protection is not provided, and customer backup responsibility remains real. That is economically important because it tells customers what they are buying: improved continuity, not immunity.

The provider's own backup policy draws the line. Ukrnames says it does not provide mandatory backups for shared hosting, VPS/VDS or dedicated servers unless otherwise specified, that customers are obliged to back up their own data on their own schedule and at their own expense, and that any emergency backups maintained by the provider do not transfer liability for customer content to the provider (https://www.ukrnames.com/eng/info/backup-policy/). Hosting plans may advertise backup features, and the Ukrainian hosting page mentions automatic backup to another data center, but the general legal policy remains clear. The customer buys infrastructure and certain support functions; the customer still owns data-protection discipline. That division of responsibility is exactly what a low-margin provider needs in a high-risk geography.

Abuse handling is a cost center, not only a policy page

Registrar and hosting trust also depends on abuse discipline. Ukrnames' contact and registrar pages point abuse issues to abuse@ukrnames.com (https://www.ukrnames.com/eng/domain/registrar/ukrnames.ua). RIPE organization records for Ukrainian Internet Names Center show abuse contact references and operational emails tied to Ukrnames (https://rest.db.ripe.net/ripe/organisation/ORG-UINC1-RIPE.json?unfiltered). The company's hosting and VDS rules prohibit malware, unauthorized access, phishing, spam, fraud, piracy, gambling and unnecessary network load, and they reserve blocking or deletion rights in cases such as non-payment or policy violations (https://www.ukrnames.com/eng/info/hosting-rules/; https://www.ukrnames.com/eng/info/vds-rules/). The support regulation says account data changes are handled by email or the account panel rather than by phone or chat, that identity documents can be required for owner changes, and that support mail is handled around the clock in priority order (https://www.ukrnames.com/eng/info/support-reglament/).

Those rules are not just legal boilerplate. A registrar-hoster attracts both legitimate small businesses and hostile or careless users. The provider must process spam complaints, phishing notices, trademark and domain disputes, account-takeover risk, fake contact data, unpaid services, DDoS spillover, hacked CMS installations and customer frustration. Abuse work consumes staff time, and poor abuse handling can harm upstream relationships, domain accreditation, search reputation, customer trust and payment-provider relationships. If the provider is too permissive, it becomes a bad-neighborhood host. If it is too aggressive, it alienates small customers who depend on fast restoration. The economic value lies in credible moderation at low unit cost.

The public review record gives a noisy but useful market signal. Trustpilot lists Ukrnames with a TrustScore of 3.8 out of 5 based on 36 reviews, a profile claimed in April 2024, and a distribution heavily tilted toward five-star reviews but with a visible one-star minority (https://www.trustpilot.com/review/ukrnames.com). Trustpilot reviews are opinions, not verified service telemetry. Still, the pattern is commercially relevant. Positive reviews praise low price, fast support, SSL/domain service and long-term use. A March 2026 negative review alleged a domain-theft issue; Ukrnames' public reply pointed the complainant toward UDRP or UA-DRP dispute procedures and said the registrar cannot revoke or transfer a domain without proper legal grounds (https://www.trustpilot.com/review/ukrnames.com). That reply is more informative than the rating. It shows the registrar presenting itself as a rule-bound intermediary rather than a customer-service court.

The WHOIS and domain-help pages reflect the same posture. Ukrnames' WHOIS guidance says real registrant data may be hidden by privacy services, that fictitious data can lead to denial of domain service, that most domains have a 28-day post-expiration period where technically possible, and that hold statuses such as clientHold or serverHold can stop DNS resolution (https://www.ukrnames.com/eng/whois/). These are mundane details until a domain breaks. Then they become the customer's path back to public reachability. A provider that can explain, enforce and document those processes has an asset that is hard to see in revenue tables.

Service boundaries are part of the product

Ukrnames' support pages also show a provider trying to define what is included before crisis turns every problem into an emergency. The VDS administration rules say administrative work may include operating-system installation or update, control-panel installation, service troubleshooting, backup configuration to a server in Ukrnames data centers, password resets, firewall setup, website transfer, server restart and SSL installation. The same page warns that backup configuration does not include further monitoring and that firewall setup is not DDoS protection (https://www.ukrnames.com/eng/info/vds-administration-rules/). This is a small but important economic distinction. The provider sells useful hands-on help, but it does not promise to become a full outsourced IT department for the monthly price of a low-cost VPS.

The distinction matters most for customers who buy continuity without understanding shared responsibility. A small company may believe that "hosting" means someone else is watching everything. Ukrnames' public terms say something narrower: the provider can install, restart, configure and support within defined limits; the customer remains responsible for content, application code, backups, payment, contact accuracy and legal use. That scope control is how a provider keeps a low-ticket service from becoming unbounded labor. It is also how the customer learns what else must be bought from specialists: CDN, web-application security, external backups, managed administration, monitoring or incident response.

Reseller economics point in the same direction. Ukrnames' reseller page offers volume-based rates, individual price terms and payment options for partners who resell domains through Ukrnames (https://www.ukrnames.com/eng/domain/reseller/). Resellers can increase volume without the company acquiring every end customer directly, but they also push the provider toward reliable automation, clear account controls and predictable support. A reseller relationship is only valuable if the upstream registrar does not surprise the partner with opaque billing, inconsistent renewals or slow technical responses. In that sense, Ukrnames' consumer-facing simplicity and partner-facing reliability are the same asset viewed from different sides.

These boundaries make the business less dramatic but more intelligible. Ukrnames is not promising to solve every Ukrainian internet risk. It is packaging a set of narrow, repeatable tasks that customers can afford and that the provider can still perform under stress: register the name, process payment, keep DNS editable, host the site, rent the VDS, place the server, answer the ticket, enforce the rules, maintain the routes and make responsibility clear. The value is cumulative. Each task is small; losing several at once is a business interruption.

Competition prices the difference between Ukrainian locality and global convenience

Ukrnames operates in a market where customers can choose among Ukrainian registrars, local hosts, regional providers and global infrastructure. NIC.UA markets itself as a main Ukrainian registrar and advertises domains and hosting with entry pricing from 44.59 hryvnia for some new domains (https://nic.ua/en). Imena.ua sells .UA registration and prolongation at 3,528 hryvnia per year and explains the trademark requirement for .UA domains (https://www.imena.ua/en/domains/zones/ua?switch-locale=). HOSTiQ presents itself as a reliable Ukrainian hosting provider with a 30-day trial and charity-hosting positioning during the war (https://hostiq.ua/eng/; https://hostiq.ua/eng/charity-hosting/). International retailers can also sell Ukrainian-related domains. EuroDNS, for example, has advertised COM.UA and .UA domain registration at euro-denominated prices that are much higher than Ukrnames' local hryvnia price points (https://www.eurodns.com/domain-extensions/com.ua-domain-registration; https://www.eurodns.com/domain-extensions/ua-domain-registration).

The competitive question is therefore not whether a customer can find a domain cheaper somewhere on the internet. Some can. The question is what bundle they want. A foreign reseller may be convenient for a multinational that centralizes domains across countries, wants a single invoice, and cares less about Ukrainian-language support or local payment channels. A Ukrainian SME, public contractor, NGO, media project or regional software firm may prefer a domestic registrar that can process Privat24, local bank invoices, local-law disputes, Ukrainian domain-zone rules, local support and local hosting in the same account. Ukrnames' payment page, domain-zone pages and service menu are built for that second world.

Hosting competition is similarly layered. A small business can buy global cloud services, use a Ukrainian host, rent a VPS abroad, use a website builder, or host minimal workloads itself. Ukrnames' shared and VDS plans do not compete with hyperscale cloud on global feature depth. They compete on convenience, price, domain adjacency, local support, local data-center choice and enough control for ordinary web operations. The Ukrainian hosting page emphasizes SSD/NVMe, 24/7 support, DDoS-protection language, a choice of data center, cPanel, CloudLinux, MultiPHP, MySQL and backups (https://www.ukrnames.com/eng/hosting/). The VDS page emphasizes KVM virtualization, root access, quick installation, additional IPv4 addresses and a Ukrainian data-center option (https://www.ukrnames.com/eng/vds/). For many customers, that is the relevant competitive set: not "can this replace AWS," but "can this keep my Ukrainian web presence working without a full IT department."

The comparison also exposes the customer-dependency risk. If customers become more sophisticated, they may separate domains, DNS, email, hosting, backups, CDN, WAF and cloud compute across specialist providers. If they remain price-sensitive and local, they may stay with bundled registrar-hosting accounts. Ukrnames benefits when customers value simplicity and local control. It loses share of wallet when customers decide that continuity requires multi-provider architecture, managed security, global CDN, independent backup and external DNS. War can push in both directions. It can increase loyalty to a Ukrainian provider that answers quickly in crisis. It can also push risk managers to diversify away from any single Kharkiv-centered supplier.

Public-sector clues show utility, not dependence

The Opendatabot record's procurement information is useful because it shows that Ukrnames services appear in public or institutional purchasing channels, including buyers such as PrivatBank and government-linked entities, with 220 tenders in the visible record and annual sales amounts that vary by year (https://opendatabot.ua/c/35351405). These are not giant transformation contracts. The visible examples include small domain, certificate or hosting-like purchases, sometimes measured in hundreds or a few thousand hryvnia. That is exactly the point. Domain and hosting providers often sit inside essential procurement not as strategic megaprojects but as low-value recurring vendors that keep public-facing services, certificates and domains functioning.

This produces a different kind of customer dependency. Ukrnames is unlikely to be systemically important because any one public contract is enormous. It can be important because many institutions may need ordinary internet administrative work done reliably and cheaply. A public buyer does not need a board presentation to renew a domain. It needs the service not to lapse, the invoice to match procurement rules, support to answer, and ownership records to be correct. That is less glamorous than cloud transformation, but it is infrastructure in practice.

The reported 2025 revenue and profit also fit a high-volume utility model rather than a venture-style growth model. A little more than 14 million hryvnia in revenue can support a real small provider, especially if much of the work is automated. It does not create much cushion for major capex, large compensation increases, sustained fuel shocks, significant hardware replacement or a serious security incident. The low reported profit makes the business more sensitive to operational shocks than the domain storefront might suggest. If energy costs rise, upstream terms worsen, payment fees increase, staff costs rise, abuse loads increase or currency-linked registry costs move against the company, margin can vanish quickly.

That fragility does not make the company weak in market terms. It describes the economics of local internet infrastructure. Many essential providers are not highly profitable; they survive through volume, routine, disciplined payment terms, low overhead and trust earned over years. Ukrnames' founding year, registrar credentials and public routing footprint suggest persistence. The open question is how much reinvestment the business can support while Kharkiv infrastructure risk remains elevated.

What would most change the judgment

The one fact that would most change the judgment is verified service continuity during major Kharkiv power and connectivity incidents. Public country-level reports show that Kharkiv traffic has suffered sharp drops during attacks and outages, but they do not identify whether Ukrnames' facilities, DNS, customer hosting or control panel remained available, degraded gracefully, or failed. A credible status history, customer outage data, independent latency and DNS measurements, or documented restoration times for the January 2026 Kharkiv disruptions would be more valuable than another generic claim about resilience. It would tell customers whether the paid continuity bundle works under the exact stress it is meant to handle.

The second most important missing fact is cost pass-through. Ukrnames' colocation page prices electricity compensation and discloses force majeure, but public records do not show fuel contracts, generator runtime, UPS battery age, insurance, SLA-credit history, backup success rates, or whether power and network price changes are passed through quickly enough to protect margin. For a lender or acquirer, these are not minor diligence questions. They are the line between a stable recurring-revenue service and a low-margin operator carrying unpriced wartime infrastructure risk.

The third missing fact is customer concentration by product. Domain registration, shared hosting, VDS, colocation, SSL and public-procurement work have different margins, risks and churn. The public evidence does not show how much of Ukrnames' revenue comes from recurring domain fees, how much from hosting, how much from colocation, how much from reseller activity and how much from one-off support or procurement. A revenue mix weighted toward domains may be more stable but lower-margin and registry-dependent. A mix weighted toward Kharkiv colocation may be more differentiated but more exposed to physical risk. A mix weighted toward shared hosting may be scalable but abuse-heavy.

Evidence register

The public identity and registrar layer is supported by Ukrnames' company information page, IANA registrar ID 1436, ICANN's accredited-registrar list and Hostmaster's Ukrainian registrar table: https://www.ukrnames.com/eng/info/, https://www.iana.org/assignments/registrar-ids/registrar-ids.xhtml, https://www.icann.org/en/contracted-parties/accredited-registrars/list-of-accredited-registrars and https://www.hostmaster.ua/registrars/. Together they support the conclusion that Ukrainian Internet Names Center is a real Kharkiv legal and registrar operator, not merely a domain brand.

The company and procurement layer is supported by Opendatabot's EDRPOU record for code 35351405: https://opendatabot.ua/c/35351405. It supports the legal-entity, founding-date, director, activity, statutory-capital, 2025 revenue/profit/assets and public-procurement signals used in this essay. The record is a public-data source, not a full audit file.

The network layer is supported by RIPEstat, RIPE RDAP, RIPE database search, PeeringDB, BGP.he, BGP.tools, PeeringDB netixlan data and DTEL-IX pages: https://stat.ripe.net/data/as-overview/data.json?resource=AS197726, https://stat.ripe.net/data/announced-prefixes/data.json?resource=AS197726, https://rdap.db.ripe.net/autnum/197726, https://rest.db.ripe.net/search.json?query-string=AS197726&source=ripe&type-filter=aut-num&flags=no-filtering, https://www.peeringdb.com/net/26832, https://www.peeringdb.com/api/netixlan?net_id=26832, https://bgp.he.net/AS197726, https://bgp.tools/as/197726, https://dtel-ix.net/en/ and https://dtel-ix.net/en/srvc/public-peering. These sources support AS197726, route, peering, DTEL-IX and looking-glass claims.

The wartime-infrastructure layer is supported by RIPE Labs, Cloudflare, NetBlocks and Internet Society Pulse: https://labs.ripe.net/author/eliza-rohotska/ukraine-as-a-laboratory-of-internet-resilience/, https://blog.cloudflare.com/q1-2026-internet-disruption-summary/, https://blog.cloudflare.com/one-year-of-war-in-ukraine/, https://netblocks.org/reports/internet-disruptions-registered-as-russia-moves-in-on-ukraine-W80p4k8K, https://pulse.internetsociety.org/en/reports/ua/ and https://pulse.internetsociety.org/en/shutdowns/internet-connectivity-reduced-in-ukraine-march-2023/. These do not prove Ukrnames' uptime. They support the market context that Ukrainian, and especially Kharkiv, connectivity and power conditions have been materially stressed.

The customer-signal and competitor layer is supported by Trustpilot, NIC.UA, Imena.ua, HOSTiQ and EuroDNS pages: https://www.trustpilot.com/review/ukrnames.com, https://nic.ua/en, https://www.imena.ua/en/domains/zones/ua?switch-locale=, https://hostiq.ua/eng/, https://hostiq.ua/eng/charity-hosting/, https://www.eurodns.com/domain-extensions/com.ua-domain-registration and https://www.eurodns.com/domain-extensions/ua-domain-registration. These are market signals rather than verified financial evidence. They help explain customer perception, substitute choices and price framing.

What a buyer would pay for

A buyer, lender, acquirer, large customer or regulator should not pay for Ukrnames as if it were a high-growth cloud platform. The defensible asset is a working Ukrainian continuity bundle: accredited registrar status, long operating history, local-domain process knowledge, automated payments, low-ticket recurring relationships, a Kharkiv hosting footprint, AS197726, Ukrainian peering, support rules, abuse handling and public procurement familiarity. The discount should attach to thin reported profit, incomplete public outage data, Kharkiv physical risk, force-majeure exposure, customer backup responsibility, colocation power costs, unknown product mix and the absence of independently verified service metrics. The proof to demand is concrete: uptime and DNS-resolution logs during Kharkiv incidents, revenue by product, churn by customer segment, registry cost exposure, fuel and power pass-through terms, backup restoration statistics, abuse workload metrics, SLA-credit history, peering/transit contracts, insurance terms and evidence that the two-data-center Kharkiv design actually protects customers during power and access disruption.

That diligence posture also protects the public interpretation. Ukrnames does not need to be transformed into a symbol to be important. It is important because thousands of small internet acts need someone to do them correctly: renew a domain, keep DNS delegated, process a payment, answer a support ticket, reject a bad transfer, suspend an abusive host, route a prefix, keep a server powered and tell a customer honestly where the provider's responsibility ends. In wartime Ukraine, those small acts become resilience economics. The blackout price is not only diesel or bandwidth. It is the price of institutional memory, account discipline and enough local infrastructure to keep names resolving when ordinary assumptions fail.

The investment question is therefore deliberately modest. Ukrnames is not a story about conquering global cloud demand from Kharkiv. It is a story about whether a disciplined local operator can keep earning trust from customers whose websites, mail domains, certificates and hosted systems are too ordinary to attract strategic attention but too important to fail quietly. That is a smaller prize, and in Ukraine it may be the more durable one.