.app Domain Names
.app domain names, where software lives
Here the ending states what the product is before a page has finished loading. Browsers serve it over HTTPS and nothing else, exactly as they do with .dev, because HSTS preloading covers the whole zone. Register from $17.99/yr, and the renewal figure appears on screen before payment.
.app
Extension
Shown
Renewal before checkout
Live
Availability results
Free
DNS management
The Extension
Why .app?
Few strings have delivered so literally on what they say. The 2012 new-gTLD round produced this one, 2018 opened it to everybody, and applications duly moved in. Behind a .app sit download pages, progressive web apps, product sites, and the update endpoints keeping all of them current. Then there is how it sounds. Where a software product would otherwise be stuck with a hyphen or a prefix on its .com, yourname.app carries the lot, and it survives being said aloud: get it at name-dot-app.
Engineering credentials here match what .dev carries. Because the entire ending sits on the HSTS preload list, browsers refuse plain HTTP on any .app address, and no one reaches your download page over an insecure connection. When you are distributing software, that is the guarantee worth holding. You are the party named on the .app registration, WHOIS privacy is folded in, and what the renewal costs is on screen well before the card is.
Good Fit
.app works best for
- Mobile and desktop app landing pages
- Progressive web apps delivered directly off the name itself
- SaaS products whose brand is the product
- Download, update and status endpoints for software
With Every Name
Included with every domain
HTTPS-only by inheritance
HSTS preloading blankets the whole ending, so the link between a user and the app's home is encrypted on every single visit, and no misconfiguration anywhere can undo that.
The product in the address
Let the ending describe software and the whole name starts reading like a sentence. A generic suffix has to work considerably harder to lodge in anyone's head.
SSL solved before launch
As soon as the name resolves, a free certificate issues, and the ending's HTTPS requirement is satisfied without anybody having to think about it.
Common Questions
Questions about .app
Do I need anything special to host a .app?
Just a valid certificate, since browsers decline plain HTTP on this ending. Every plan we sell issues free SSL automatically, so the requirement gets met well before you notice it exists. Beyond the HTTPS rule itself, a .app behaves like any other gTLD: delegate it to whichever nameservers suit you, edit the zone however you want, and move it with an auth code.
Should the app be served from the .app, or redirected over to my .com?
Either pattern works. Certain brands park the product at the .app and the company at the .com; others run everything off one name and redirect the other permanently. Pick one canonical home, 301 the rest at it, and stick to that line. The thing to steer clear of is a pair of half-alive sites splitting your search standing between them.
Is .app suitable as a company's only domain?
Where the business is the app, yes, and a good many run precisely that way. What you weigh are the usual considerations for any ending that is not .com: pick up the classic sibling defensively where the brand warrants it, and remember that mail leaving the name still needs SPF, DKIM and DMARC published, as any sending domain does.
Keep Browsing
Other endings worth a look
Registration and renewal figures for every ending we carry are on the price list.
Read the whole domain price list or transfer a name you already hold.
Put the .app on the register before someone else does.
Search runs live against the registry, WHOIS privacy costs nothing where the registry allows it, and the renewal figure is shown before you pay.
Search .app Names