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

Ship the product homepage

Give users a stable address for your software

A customer should find documentation, sign-in and service status from the same product homepage. A .io gives the software its own address while you decide which routes need dedicated hosts. Treat API URLs as long-lived interfaces and record them before you print or publish the name.

  • Ship the product homepage. Publish one verified description of the tool and the first task a developer can complete.
  • Map stable hostnames. Assign public documentation, sign-in and application traffic to the services that own them.
  • Verify an integration. Test a sample request and a sign-in redirect using the full product address before changing production DNS.
Your brand, brought to life with a .io domain Your brand.io above an illustrative website with layered mountain scenery and a [email protected] email card. One name for a website, email, shop and portal. yourbrand.io An address for your work. YOUR BRAND AboutWorkShopContact Your nextproject. One address for your siteand the services around it. Discover more hello@example.net Website Email Shop Portal
Possible routes for a software product, shown with a documentation address.

Registration, renewal and transfer

.io Domain Pricing

Budget the software address with certificates and service continuity in mind.

Get started

Register your software product

Kshs 5,484 / first year

Search the exact spelling before using it publicly. Check first-year and renewal prices before you publish an SDK that points at this address.

Check .io availability
Renew

Keep the address working next year

Kshs 11,716 / year

Reconcile renewal notices with finance before a high-traffic product release.

Explore registration costs
Transfer

Move a name you already use

Kshs 9,031 / transfer

Document client integration dependencies before asking the current registrar to release the name.

Move your existing .io

Check first-year and renewal prices before you publish an SDK that points at this address.

Compare the full spelling

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

Try .io and .tech with the product name, then check for collisions with the matching .com. Use .co.ke if local identity is more useful to your customers than a separate software brand.

Domain registration, renewal and transfer pricing
.ioKshs 5,484 (standard)Kshs 11,716Kshs 9,031
.techKshs 1,199 (standard)Kshs 11,547Kshs 8,862
.comKshs 1,200 (standard)Kshs 1,700Kshs 1,259
.co.keKshs 999 (standard)Kshs 1,500Kshs 1,000

Build the software product

Ways to Use Your .io Domain

Give customers a route to your software, integration guide and status page.

Find Your .io

Publish

Publish API documentation

Keep versioned examples, limits and a changelog available from the main product site.

Run

Run a developer preview

Explain what access includes and how feedback is handled before inviting people to try it.

Share

Share service status

Give subscribers a route to incident history that can still load during an application outage.

Give

Give integrations a home

Document callback hostnames and allowed redirect destinations with whoever maintains sign-in.

Prepare the new registration

.io Domain Management, Made Simple

Keep the control plane independent of whoever can deploy the application.

DNS management

Assign public documentation, sign-in and application traffic to the services that own them.

Nameserver control

Export shared records and confirm alias targets before moving documentation, status or API traffic.

Renewal management

Put the domain on the same ownership register as production credentials and certificates.

Transfer support

Document client integration dependencies before asking the current registrar to release the name.

Manage your domain

Why Choose Truehost for Your .io Domain?

Maintain a recovery mailbox that remains accessible during a DNS or mail outage.

Set the website destination

Test externally reachable links with a fresh browser and a sample request.

Assign the contact inbox

Separate developer support from automatic service notices.

Check recovery permissions

Limit changes to critical hostnames to the team that owns their stability.

Separate service

Choose a mailbox

Separate developer support from automatic service notices. Browse email plans.

Separate service

Build the public page

Use a small product page to explain the supported environments and link the documentation. Explore the builder.

Review the cost of the software product, web service and inbox before you commit.

Test the first public route

How to Use Your .io Domain

Test a sample request and a sign-in redirect using the full product address before changing production DNS.

  • Ship the product homepage
  • Map stable hostnames
  • Verify an integration
Check .io availability
A .io domain connected to four servicesThe domain routes people to a public website, email, shop and customer portal. .ioYOUR DOMAINexample.net WEBSITEPublic presenceEMAILTeam inboxesSHOPProducts and ordersPORTALCustomer service
example.netProduct overview and supported environments.

Plan the destinations

Build Around One Memorable Address

Reserve the main page for the software product. Use the other routes only when they need to operate separately.

Customer TaskIllustrative DestinationWhat Visitors Find
Read about the toolexample.netProduct overview and supported environments.
Open the developer consoleaccount.example.netHosted developer console and access settings.
Find integration docshelp.example.netVersioned integration guides and change history.
Ask a technical question[email protected]Technical contact for integration questions.

Choose only the services you need

Build More Around Your .io Domain

Choose tools that support the day-to-day work behind the software product.

See hosting options

Review the name as printed

.io Domain Name Rules

Write the full name where readers of the software product will first encounter it. Check the exact spelling with us before you rely on accent or script support. NIC.IO applies its published allocation rules and checks existing names.

Accepted in a .io name

  • Choose a label readers of the software product can remember.
  • Keep numbers only if they belong to the public name.
  • Use an internal hyphen where it helps people read separate words.
  • Check registry language support before choosing accented characters.

Not accepted

  • A dash at the beginning or end of the label.
  • Spaces inside the label.
  • Underscores separating words.
  • A label blocked by the registry’s reservation rules.
Check Sample Spellings
CandidateFormat CheckExplanation
example.ioValid spellingAn ordinary ASCII label suits a software product.
your-name.ioValid spellingThe dash separates two parts of the label.
-example.ioInvalid spellingA dash at the beginning needs to be removed.
exam_ple.ioInvalid spellingReplace the underscore with an allowed character.

Before applying

Your .io Registration Checklist

NIC.IO accepts applicants from any legal jurisdiction for direct second-level .io names. The registry publishes different rules for third-level registrations and requires two operating nameservers for a second-level request.

Registration details

  • Legal owner
  • Production domain approver
  • External recovery mailbox
  • SDK and API hostnames

Prepare for the site separately

  • Callback inventory
  • Documentation owner
  • Incident channel owner
  • Renewal approver

Before you register

Review the proposed name

Callback inventory

Check the conditions

Check first-year and renewal prices before you publish an SDK that points at this address.

Plan the handover

Test a sample request and a sign-in redirect using the full product address before changing production DNS.

Evidence for the .io namespace

.io Domain Facts

Public .io datasets give independently measured counts. Their collection coverage varies. An official registry-wide total was unavailable for this snapshot.

1,861,635
names in the AllZonefiles.io dataset
16 November 2026
+14,433
30-day change in dataset coverage
Through 16 November 2026
1,389,963
names observed by DomainTools
November 2026 snapshot

The AllZonefiles.io dataset listed 1,861,635 names on 16 November 2026. Its 30-day change can include existing registrations newly discovered by the collector. DomainTools reported its own observed count in a separate November snapshot.

.io Registry and Registration Specifications

Check first-year and renewal prices before you publish an SDK that points at this address.

Read registry policies
Registry IdentityRegistry record for .io
Namespace reference
Property.io requirement
Illustrative addressexample.net illustrates the label and suffix pattern.
DNS levelThe registrable label sits directly to the left of .io.
NamespaceCountry-code top-level domain for the British Indian Ocean Territory.
Registry operatorInternet Computer Bureau Limited
Delegation recordIANA root zone record for .io
Typical useDomains for software products and developer tools
Registration RulesChoose valid name characters
Application reference
Property.io requirement
Registration eligibilityNIC.IO accepts applicants from any legal jurisdiction for direct second-level .io names. The registry publishes different rules for third-level registrations and requires two operating nameservers for a second-level request.
Term selectionCompare the term with your product commitment and verify the exact annual or multi-year quote in checkout.
Label lengthUse the size permitted by the registry, within the DNS limit of 63 octets per label.
Ordinary ASCII spellingUse Latin letters a–z, digits, and permitted internal hyphens.
Internationalised labelsCheck the exact spelling with us before you rely on accent or script support. NIC.IO applies its published allocation rules and checks existing names.
CaseA change in letter case does not create a distinct DNS name.
Name across extensionsEach ending used for the software product is a separate registration.
Registration policyPublished terms for .io
DNS & Registry ServicesConnect the software product
DNS configuration reference
Property.io requirement
Operating nameserversNIC.IO requires at least two for a direct second-level request.
Account contactsExternal recovery mailbox should be reachable when the site is down.
Registry lookupNIC.IO registry service
Web settingsVerify TLS for API clients and sign-in callbacks as well as the public homepage.
Lifecycle & ProtectionRegistrar changes and recovery
Recovery reference
Property.io requirement
Moves between registrarsConfirm the transfer procedure with the current registrar and review NIC.IO’s terms.
ExpiryReview registry guidance and confirm the domain status with us.

Keep control of your address

What Happens If .io Expires?

A failed renewal can disrupt API clients, redirects and authentication. Tie the renewal date to your production change calendar. See NIC.IO’s renewal policy.

01Resolving

Active

Put the domain on the same ownership register as production credentials and certificates.

02Action due

Renewal Due

Reconcile renewal notices with finance before a high-traffic product release.

03Past the due date

Expired

Check the registrar status if API lookups and mail both stop working.

04If restoration is available

Suspended

Review NIC.IO’s renewal policy and ask us which options apply to the actual domain status.

05After release

Cancelled

If the address can no longer be recovered, revise SDK defaults, webhook settings, client notices and certificate configuration.

Check the quoted period

Plan the Registration Beyond Year One

Compare the term with your product commitment and verify the exact annual or multi-year quote in checkout.

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.
.io 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 5,484Kshs 5,484No savingSearch domains
2 yearsKshs 17,200Kshs 17,200No savingSearch domains
3 yearsKshs 28,916Kshs 28,916No savingSearch domains
4 yearsKshs 40,632Kshs 40,632No savingSearch domains
5 yearsKshs 52,348Kshs 52,348No savingSearch domains

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

Make a registrar change

Already Have a .io Domain?

Document client integration dependencies before asking the current registrar to release the name.

Transfer — Kshs 9,031
  1. 01

    Check ownership and status

    Inventory the public hosts, redirect destinations and service accounts before changing the registration.

  2. 02

    Obtain the transfer code

    Confirm the transfer procedure with the current registrar and review NIC.IO’s terms.

  3. 03

    Start the transfer with us

    Keep the existing nameserver setup unless you intend to move it. Verify API and status links from outside your network.

Questions about a software product

.io Domain FAQs

Give customers a route to your software, integration guide and status page.

Can a Kenyan company register .io?

Yes, NIC.IO allows applicants from any legal jurisdiction to request a direct second-level name. Use accurate registrant details and follow its published name and operating nameserver rules.

What does a .io cost to keep?

Start with the initial charge from checkout, then budget renewal independently. Pay attention to the exact spelling, especially if the search identifies a name-specific price.

.io registration and renewal
ChargeCurrent KES priceWhen it applies
RegistrationKshs 5,484Your first year
RenewalKshs 11,716Keeping your registration active

See current prices.

Does .io stand for input/output?

Developers often read it that way. IANA classifies .io as the country-code domain for the British Indian Ocean Territory.

Could the .io domain change in future?

IANA currently lists .io as active. ICANN has explained that future treatment depends on what happens to the IO code in ISO 3166-1. Keep control of an alternative address if the domain will underpin critical services.

Should my API use the main address?

A dedicated API hostname can make it easier to change the public site independently. Treat it as a public interface once customers integrate with it.

Keep a version inventory for the API routes clients actually call. Before moving a hostname, check pinned URLs in SDKs, customer firewall rules and any partner documentation you do not control.

What do I check before moving my app?

Write down every client-facing hostname, callback and webhook. Test from a clean client and confirm that integrations accept the certificate on the new destination.

Can I keep documentation on another host?

Yes. Point the documentation hostname to your chosen service using its DNS instructions. Preserve existing paths or redirect them individually.

Where should the status page live?

Choose hosting that can still respond when the application is down. Keep an independent way for customers to find service updates if DNS itself is affected.

Put the fallback route in onboarding documentation before an incident. A status page shares the same failure path if both the page and the only way to reach it rely on the same DNS or hosting account.

Can a contractor manage releases?

Give release staff the deployment access they need. Record company ownership and registrar recovery separately so it survives personnel changes.

Can I transfer an existing .io?

Check its status with the losing registrar and follow the current NIC.IO transfer process. Record your DNS configuration so a move does not disrupt clients.

Ask who receives the transfer confirmation and whether any expired or disputed status affects the move. Schedule the change outside a planned rollout, when you can distinguish registration trouble from an application regression.

Is .tech a substitute for .io?

Either can serve a software brand. Compare how each name appears in code, how customers read it aloud and what you will pay to keep it.

What if I miss a .io renewal?

Check the registered expiry and ask us about the recovery options available now. Keep customers informed through a channel that does not depend on the domain.

Domains for software products and developer tools

Ready for Your .io Domain?

Give customers a route to your software, integration guide and status page.

Check availabilityReview renewalConnect your services