The .systems domain is an open generic top-level domain (gTLD) operated by Identity Digital for IT, infrastructure and engineering teams. It is a descriptive extension favoured by agencies, ops teams and platform brands, and is open to anyone with no registration restrictions.
.systems at a glance
Source: IANA root zone database & registry data · methodology
Where to register a .systems domain
Prices are indicative and set by each registrar; renewal rates may differ from first-year promotions. Links may be sponsored. tldlist.us is an independent reference and not a registrar.
What does .systems mean?
The .systems extension is a descriptive top-level domain built around the word systems — the language of IT, infrastructure, platforms and the teams that keep them running. It was delegated in 2014 in the new-gTLD wave that added hundreds of meaningful, plain-English endings to the address bar. Where a neutral extension like .com tells a visitor nothing about what the site does, .systems sets an expectation immediately: servers, networks, integrations, operations — the plumbing layer of technology rather than a consumer app.
It is operated by Identity Digital, the registry that runs a large portfolio of these keyword TLDs, and it sits in the same family as .tools and .software. Because the whole family shares one operator and one rulebook, a .systems name behaves predictably — the same open registration policy, the same broad registrar support, and pricing in the familiar $20-ish band. The result is an extension that reads as deliberately technical: you choose it because "systems" is the right word for what you do.
Who uses .systems?
The core audience is technical: managed-service providers, DevOps and platform teams, systems integrators, automation and embedded-hardware shops, and agencies whose work is infrastructure rather than front-end design. A consultancy might run its brand on northwind.systems; an internal platform team could host its docs and dashboards on a clean .systems name instead of a deep subfolder of the corporate site.
It is also handy for naming a thing rather than a company — a product line, a control plane, an internal tooling hub. Because registration is open with no proof-of-eligibility, an engineer can grab the exact descriptive name they want for a side project or a status page in minutes. People weighing it up usually compare it with .tech for a broader technology feel, or with .io and .app when the project is closer to a product than a platform.
.systems registration rules and requirements
There are none beyond the basics. .systems is a fully open generic TLD: anyone in any country can register one, with no requirement to run an IT firm, no business licence, no local presence and no identity documents. Registration is first-come, first-served — whoever registers an available name first holds it, for as long as they keep renewing. The only universal obligation is the standard ICANN contact-information policy that applies to every gTLD, alongside Identity Digital's standard registry terms accepted through your registrar.
How much does a .systems cost?
A .systems runs about $20 per year at mainstream registrars — among the more affordable Identity Digital keyword TLDs, though still above a $11 .com. Pricing is consistent because the registry publishes one wholesale rate, so differences between registrars mostly come down to markup and whether a first-year promotion is running. As always, check the renewal price rather than just the introductory offer.
| Registrar | Typical .systems price (per year) |
|---|---|
| Cloudflare Registrar | At wholesale cost |
| Porkbun | ~$20/yr |
| Namecheap | ~$20–23/yr |
| Premium names | $100s+ one-off |
Is .systems good for SEO?
Not directly. Google and Bing do not give a .systems page a ranking edge over a .com — the extension is not a ranking factor, even though it contains a relevant word. The benefit is human: an address like northwind.systems signals an IT or infrastructure focus to the person reading it, which can lift trust and click-through among a technical audience. That is a branding advantage, not an algorithmic one. To weigh it against other options, see our guide on how to compare and choose a TLD.
.systems vs alternatives
Its nearest neighbours are its Identity Digital siblings and the broader tech extensions. .tools fits a single utility or toolkit better than a whole operation; .software points at a shipped product rather than the infrastructure around it; and .tech casts a wider net across all of technology. For a leaner, more startup-flavoured name many teams reach for .io instead. .systems is the right pick precisely when "systems" describes the work — infrastructure, integration, operations — better than any of those alternatives.
.systems pros and cons
Pros
- Descriptive — instantly signals an IT, infrastructure or platform focus.
- Open to anyone, anywhere, with no eligibility checks or paperwork.
- One of the cheaper Identity Digital keyword TLDs (~$20/yr).
- Plenty of short, exact-match names still available.
Cons
- Still pricier than a .com or a budget new gTLD.
- Niche, technical feel — not ideal for consumer-facing brands.
- Long word that some prefer to shorten to .io or .dev.
- No ranking advantage despite containing a keyword.
Example .systems websites
- northwind.systems — a representative pattern for a systems-integration or managed-services brand.
- status.example.systems — ops teams often host status pages and dashboards on a descriptive .systems name.
- docs.example.systems — internal platform and infrastructure documentation sits naturally here.