Rank #1 on Google Maps
India English
Kenya English
United Kingdom English
South Africa English
Nigeria English
United States English
United States Español
Indonesia English
Bangladesh English
Egypt العربية
Tanzania English
Ethiopia English
Uganda English
Congo - Kinshasa English
Ghana English
Côte d’Ivoire English
Zambia English
Cameroon English
Rwanda English
Germany Deutsch
France Français
Spain Català
Spain Español
Italy Italiano
Russia Русский
Japan English
Brazil Português
Brazil Português
Mexico Español
Philippines English
Pakistan English
Türkiye Türkçe
Vietnam English
Thailand English
South Korea English
Australia English
China 中文
Somalia English
Canada English
Canada Français
Netherlands Nederlands

Plan hostnames

A product address that works from launch day

Put release notes, download links and contact information on a site your team controls. Use the main name for the public product and split off docs or status only when they need their own service. Configure HTTPS on every web hostname you plan to publish.

  • Plan hostnames. Choose which service handles the public site, documentation and account sign-in. List the exact hostnames that will go into release notes.
  • Provision HTTPS. Issue and verify a certificate for each public hostname while you are setting up the site. Do not rely on an HTTP redirect to bootstrap a browser visit.
  • Test a first visit. Open the new site in a clean browser. Test navigation, downloads and login callbacks from links a user will actually receive.
Your brand, brought to life with a .app domain Your brand.app above an illustrative website with layered mountain scenery and a [email protected] email card. One name for a website, email, shop and portal. yourbrand.app An address for your work. YOUR BRAND AboutWorkShopContact Your nextproject. One address for your siteand the services around it. Discover more hello@yourbrand.app Website Email Shop Portal
A product address can connect launch information, documentation, and a separately hosted application.

Registration, renewal and transfer

.app Domain Pricing

Budget the domain and its web deployment separately. Your launch checklist should name who pays the registrar and who owns issuance and renewal for every public certificate.

Get started

Reserve the product address

Kshs 1,484 / first year

Search the exact spelling before using it publicly. Verify that each platform linked from the public name can serve a custom .app hostname over HTTPS.

Check .app availability
Renew

Plan for post-launch renewal

Kshs 2,768 / year

Confirm the registrar invoice before it is due, particularly if the company payment method changes.

Explore registration costs
Transfer

Move the name into the company account

Kshs 2,700 / transfer

Bring the registration to the account your software team maintains. Keep TLS and DNS changes out of the same window unless the rollout explicitly coordinates them.

Move your existing .app

Check the brand spelling and the term in the initial quote. Keep enough setup time to provision HTTPS before the public launch.

Compare product domain choices

Compare .app, .io, .com, .co.ke prices

Choose .app when you want the address to point to a software product and your platforms can serve it over HTTPS. An .io or .com may suit a broader product portfolio. Consider .co.ke if the site mainly supports a Kenya-specific business.

Domain registration, renewal and transfer pricing
.appKshs 1,484 (standard)Kshs 2,768Kshs 2,700
.ioKshs 5,484 (standard)Kshs 11,716Kshs 9,031
.comKshs 1,200 (standard)Kshs 1,700Kshs 1,259
.co.keKshs 999 (standard)Kshs 1,500Kshs 1,000

Launch and support examples

Ways to Use Your .app Domain

Give your product a home for downloads, documentation and support. Browsers require HTTPS on .app, so have a certificate ready before sharing the address.

Find Your .app

Give

Give mobile users an official launch page

Put verified store links beside screenshots and supported platforms. Test the route on a phone without the app already installed.

Publish

Publish documentation independently

Send developers to a stable guide for the current release. If documentation lives on a separate host, check certificate provisioning before linking to it.

Run

Run a support or status page

Publish incident updates and a support contact people can use when the application is unavailable. Keep the status service separate if it needs to survive the main application going offline.

Make

Make a web application easy to find

Use a memorable public address for sign-in or send visitors there from the product site. Verify redirect URLs and session behavior after any DNS change.

Track your DNS and certificates

.app Domain Management, Made Simple

Maintain a list of exact hostnames and where their certificates are renewed. Keep it together with the domain expiry date, app-store links and sign-in callbacks.

DNS management

Issue and verify a certificate for each public hostname while you are setting up the site. Do not rely on an HTTP redirect to bootstrap a browser visit.

Nameserver control

DNS can point the root, docs and status names to different services. Check whether each one can issue its certificate before publishing its hostname.

Renewal management

Record who can approve domain renewal and who monitors certificate renewal. They are two separate tasks.

Transfer support

Keep owner access with the company. Make sure someone outside the deployment team can review a time-sensitive registrar notice.

Manage your domain

Why Choose Truehost for Your .app Domain?

Use separate registrar and application accounts that your company can recover. Ongoing access matters long after the engineer who connected the first deployment moves on.

Test HTTPS before launch

Check the bare and www destinations in a clean browser. A certificate error can stop the visit before the redirect reaches the canonical host.

Route product and security mail

Route product feedback to the support queue even during site maintenance. Mail service remains separate from the browser’s HTTPS policy.

Remove outdated access

Remove stale administrator access promptly. Keep ownership review on the same schedule as checks for abandoned subdomains.

Separate service

Give support a public address

Set up a monitored security or customer support contact using our email options. Browse email plans.

Separate service

Prepare a public release page

When choosing our builder or another platform, verify custom hostname and certificate support before connecting the launch site. Explore the builder.

Confirm whether hosted certificates are included with the plan you choose and how they are renewed.

Test every advertised hostname

How to Use Your .app Domain

Open the new site in a clean browser. Test navigation, downloads and login callbacks from links a user will actually receive.

  • Plan hostnames
  • Provision HTTPS
  • Test a first visit
Check .app availability
A .app domain connected to four servicesThe domain routes people to a public website, email, shop and customer portal. .appYOUR DOMAINexample.net WEBSITEPublic presenceEMAILTeam inboxesSHOPProducts and ordersPORTALCustomer service
example.netPlan valid certificates for the launch site, account route and separately hosted documentation.

Map docs, login and support

Build Around One Memorable Address

Map the root, documentation and application login to distinct hostnames only when there is an operational reason. Use the reserved examples below to plan the layout.

Customer TaskIllustrative DestinationWhat Visitors Find
Plan hostnamesexample.netLaunch information and verified download destinations.
Accountaccount.example.netProduct sign-in with its own certificate and callbacks.
Provision HTTPShelp.example.netDocumentation, release history and support guidance.
Email[email protected]A route to reach the team during an outage.

Find HTTPS-capable services

Build More Around Your .app Domain

Start with TLS support and deployment ownership. Choose the simplest service that brings the main product site and documentation online with reliable certificate renewal.

See hosting options

Validate the release name

.app Domain Name Rules

Test the label in the app-store listing, public documentation and a release message. Keep its typing and pronunciation separate from any decision about app naming rules. Check Google Registry’s applicable IDN tables and the exact spelling offered in our search before naming your product.

Accepted in a .app name

  • Choose the label that will appear in the public store listing.
  • Digits can distinguish a product when they are part of its brand.
  • Place a hyphen within the label, away from both edges.
  • Check Charleston Road Registry’s IDN tables for the chosen script.

Not accepted

  • Do not begin or end with a dash.
  • Do not paste spaces or underscored code identifiers into the search box.
  • Use a subdomain for docs or status rather than a dot inside the registration label.
  • Check trade-mark and store naming separately.
Check Sample Spellings
CandidateFormat CheckExplanation
example.appValid spellingA label suitable for a launch-page search.
your-name.appValid spellingThe dash sits between letters, where it is permitted.
-example.appInvalid spellingA leading hyphen is invalid.
exam_ple.appInvalid spellingAn identifier from source code may include unsuitable characters.

Before applying

Your .app Registration Checklist

Google Registry’s .app registration policy requires registrars to disclose the HTTPS requirement. Plan for a supported certificate and hosting configuration before you announce the address.

Registration details

  • Company or product owner
  • Deployment and domain approvers
  • Recovery address outside production DNS
  • Spelling used in stores and release notes

Prepare for the site separately

  • Product-name rights
  • HTTPS-capable public hosting
  • Certificate owner for each hostname
  • Domain renewal and login callback inventory

Before you register

Review the proposed name

Check the chosen name alongside the registered product brand.

Check the conditions

Provision certificates for the actual public hostnames. Browsers require HTTPS for .app destinations.

Plan the handover

Use an independent account recovery channel that can work through an application outage.

Product-domain registrations

.app Domain Facts

The June 2026 registry transaction report counted 1,478,674 .app registrations at month-end.

1,478,674
.app domains at the end of June
At the end of June 2026
+89,042
net growth since the May report
May to June 2026
120,196
new registered names after add grace
June 2026 transaction report

Comparing the May and June ICANN files gives a net rise of 89,042 sponsored names. June’s transaction columns contain 120,196 additions after add grace. This measures domains rather than application installs or downloads. View the May and June 2026 reports.

.app Registry and Registration Specifications

Check the .app HTTPS policy before choosing a platform for your product site, documentation or browser-based login.

Read registry policies
Registry IdentityGoogle Registry and HTTPS
Namespace reference
Property.app requirement
Illustrative addressexample.net illustrates the label and suffix pattern.
DNS levelThe registrable label sits directly to the left of .app.
Software namespaceGoogle Registry’s generic ending supports web apps and product sites. A store listing is a separate decision.
Registry operatorCharleston Road Registry Inc. (Google Registry)
Delegation recordIANA root zone record for .app
Typical useDomains for software teams · HTTPS required for websites
Registration RulesValidate a product name
Application reference
Property.app requirement
Secure launchReserve your chosen spelling after checking availability. Provision HTTPS before inviting users to a browser destination.
Product budgetConfirm the term in the cart and keep certificate and runtime subscriptions separate from registrar billing.
DNS name lengthAllow up to 63 octets for one label at the DNS level. Check the applicable table for encoded spellings.
Ordinary ASCII spellingUse Latin letters a–z, digits, and permitted internal hyphens.
Internationalised labelsCheck Google Registry’s applicable IDN tables and the exact spelling offered in our search before naming your product.
Names and routesThe DNS name is case-insensitive. A path used for your app’s callback may behave differently.
Application portfolioIf the company buys other endings, keep their DNS records and renewals in the same inventory.
Registration policyPublished terms for .app
DNS & Registry ServicesRoute DNS and certificate issuance
DNS configuration reference
Property.app requirement
DNS delegationChoose which service handles the public site, documentation and account sign-in. List the exact hostnames that will go into release notes.
Operational contactDirect registrar notices to someone authorised to act even when the primary application is down.
Registration lookupICANN Registration Data Lookup
TLS coverageRecord where the apex, docs and account hostnames get certificates and how renewal works.
Lifecycle & ProtectionKeep release links available
Recovery reference
Property.app requirement
Move without reissuing TLSGet the transfer code from the old registrar and plan any DNS or certificate changes independently.
Product outageDistinguish registrar expiry from a DNS or certificate failure before troubleshooting sign-in.

Keep control of your address

What Happens If .app Expires?

Losing the product domain can interrupt logins, package documentation and customer support. Put domain renewal on the launch and operational calendars. See ICANN’s Expired Registration Recovery Policy.

01Resolving

Active

Record who can approve domain renewal and who monitors certificate renewal. They are two separate tasks.

02Action due

Renewal Due

Confirm the registrar invoice before it is due, particularly if the company payment method changes.

03Past the due date

Expired

If a hostname suddenly fails, check the domain, DNS and certificate independently before deciding which service to repair.

04If restoration is available

Suspended

Ask for the current registry status and recovery quote immediately if the registration expired.

05After release

Cancelled

If another holder can register the address, remove it from OAuth allowlists, app-store records and customer instructions.

Keep registration on the operations calendar

Plan the Registration Beyond Year One

Choose the registration period in the storefront and record its end date beside the product’s operational renewals. Set a separate certificate alert.

Current catalogue prices. Savings compare the total with one year of registration plus annual renewals at today’s rates. Future renewal rates may change. Only available priced terms are listed.
.app domain registration totals in KES. Total price covers the full selected term and includes any applicable registration offer. Regular year-by-year cost is regular one-year registration plus annual renewals at today’s rates, without promotional discounts. Savings are the difference between these two totals.
TermTotal registration priceRegular year-by-year costRegistration + annual renewalsSavingsAction
1 yearKshs 1,484Kshs 1,484No savingSearch domains
2 yearsKshs 4,252Kshs 4,252No savingSearch domains
3 yearsKshs 7,020Kshs 7,020No savingSearch domains
4 yearsKshs 9,788Kshs 9,788No savingSearch domains
5 yearsKshs 12,556Kshs 12,556No savingSearch domains

Select your term in checkout. Domain availability, applicable promotions, premium-name pricing and taxes are confirmed there.

Move the registrar without changing the deployment

Already Have a .app Domain?

Bring the registration to the account your software team maintains. Keep TLS and DNS changes out of the same window unless the rollout explicitly coordinates them.

Transfer — Kshs 2,700
  1. 01

    Check ownership and status

    List public DNS targets, certificate validators and sign-in callbacks before beginning the registrar change.

  2. 02

    Obtain the transfer code

    Check the name’s lock and obtain its transfer code. Keep settings that would otherwise trigger a certificate or hostname change.

  3. 03

    Start the transfer with us

    Once the receiving account shows the domain, test a first HTTPS visit, sign-in and the published documentation links.

Questions for a product launch

.app Domain FAQs

Check HTTPS, documentation hosts, login redirects and the effect of a registrar move on a running application.

Can browsers open a .app site over plain HTTP?

Plan for HTTPS from the first visit. .app is HSTS preloaded, so compatible browsers attempt a secure connection. A server serving only HTTP will not provide a usable browser destination.

Before launch, check the exact URL that a new user will open from a store listing or installation guide. Test the apex and any advertised www address separately. If one is meant to redirect, it still needs to complete the secure connection before the browser can follow that redirect. Use a separate deployment check for certificate renewal, especially when the main site and the documentation live on different platforms.

How much should we budget after launch?

Check our separate renewal amount and the term offered in the cart. Include the budgets for the public site, application platform and any paid certificate service separately.

.app registration and renewal
Registrar costQuoted KES priceWhen the product team pays
RegistrationKshs 1,484Your first year
RenewalKshs 2,768Keeping your registration active

See current prices.

Do docs and support subdomains need HTTPS too?

Yes, plan for certificates on your public .app web subdomains. Confirm each third-party service can provision one for its custom hostname.

Make a small certificate inventory with one row per published web hostname. List the platform that issues each certificate, the mechanism that verifies control and the team that gets failure alerts. Change the registry or DNS separately from a certificate migration when possible. If a hostname is no longer needed, remove the public link and check which old app versions or documentation pages might still send traffic there.

Must my product be in an app store?

No. A .app site can be a web application, a launch page, product documentation or a portal. An app-store listing remains a separate step.

Can I register before the application is ready?

Yes. Reserve the address, arrange account ownership and test HTTPS before posting a link to the product.

Can I use a free certificate?

A certificate trusted by the browsers you support can work. Check your hosting provider’s issuance and renewal process, and test the actual public hostname.

Confirm how the host provisions certificates for custom domains and what it needs from DNS. Test renewal behavior instead of relying on a certificate you installed manually during launch. If the certificate covers several hostnames, check that the host presents the intended one for each connection. The store listing, browser app and documentation may all use different redirect paths, so verify each with a clean browser.

Does a certificate automatically cover every hostname?

Check which names it lists. A wildcard for direct subdomains differs from an apex certificate, and deeper names may require separate coverage.

Can an app-store listing link to this domain?

You can use it for your published product, support and privacy pages. Check the links from the store listing and keep the destinations stable across releases.

Use stable addresses for support and privacy information so published app versions can still refer to them after a redesign. Open the links on a device that does not already have the application, and ensure they land on the intended secure hostname. If you run a staged rollout, document which site offers current download instructions and how customers should reach support if the latest release is unavailable.

Does HTTPS change how email is hosted?

The browser policy is for web access. Configure mail separately with the providers and records you choose for your project.

Can the product run on one host and docs on another?

Yes. Publish the DNS records for each destination and test their certificates independently before you release links.

Inventory DNS and callbacks before distributing hostnames across providers. A login provider may require an exact HTTPS callback, while a docs host may need validation records for a custom name. Test with the origins that users will use, then verify links from the product site to the docs and back. Treat certificate checks and authentication checks as separate tasks in the launch checklist.

What should we test after a transfer?

Check the domain’s new account, nameservers, TLS certificate delivery and sign-in callback URLs. A registrar change and a hosting migration are separate operations.

What if only the certificate has expired?

Renew or reissue the certificate with your hosting or certificate provider. Check the registrar account separately to confirm that the domain remains registered.

If a browser reports a certificate problem, compare the certificate’s dates and names with the hostname being served. Check that DNS points to the intended platform and whether a load balancer or CDN presents its own certificate. Check the domain expiry date in the registrar account separately. A working support mailbox can remain online while a browser connection fails, because those services use different records and endpoints.

Domains for software teams · HTTPS required for websites

Ready for Your .app Domain?

Find the product name, then verify HTTPS on the launch, documentation and support destinations before sending visitors there.

Check availabilityReview renewalConnect your services