What is .save?
.save entered the DNS root zone on June 7, 2016, 10 years ago. It came out of ICANN's New gTLD Program, the 2012 application round that grew the root from 22 generic TLDs to well over a thousand.
Amazon Registry Services, Inc. operates a large portfolio of 51 TLDs, including .amazon, .audible, .author, .book and .bot.
On the technical side, .save is served by 8 authoritative name servers, every one of them reachable over IPv6. It is also DNSSEC-signed: the root zone carries a DS record for .save, which lets validating resolvers check its answers cryptographically. Registration data is published over RDAP.
Same registry, other endings
50 other TLDs share this operator.
.save FAQ
What does .save mean?
.save is a generic top-level domain named for the word "save". It doesn't belong to any country.
What country is .save?
None. .save is a generic top-level domain, so it isn't tied to any country.
Who owns the .save domain extension?
Amazon Registry Services, Inc. operates .save as its registry, under a registry agreement with ICANN.
When was .save created?
.save was delegated to the DNS root zone on June 7, 2016.
Is .save a valid domain?
Yes. .save is an active top-level domain in the DNS root zone, delegated in 2016, so .save addresses work in every browser.
Can I buy a .save domain?
.save names are sold through ICANN-accredited registrars. Some gTLDs restrict who can register, so read Amazon Registry Services, Inc.'s policy if you're unsure.
Is .save DNSSEC-signed?
Yes, the root zone holds a DS record for .save.
Sources
Data from IANA root zone version 2026102000. Last changed February 14, 2025. Spotted something wrong? Tell us.