What is .viking?
Brand TLDs operate under Specification 13 of ICANN's registry agreement. It lets a trademark owner keep every second-level name for itself, so you won't find .viking names for sale at any registrar.
ICANN's records put the delegation of .viking on February 22, 2016. Like most of the newer endings, it was applied for in the 2012 New gTLD Program round and its registry agreement was signed on April 2, 2015.
Viking River Cruises (Bermuda) Ltd. also runs one other TLD, including .cruise.
Under the hood, the root zone points to 4 name servers for .viking, every one of them reachable over IPv6. The delegation is DNSSEC-signed, so resolvers can verify that answers for .viking haven't been tampered with on the way. Registration data is published over RDAP and WHOIS (the WHOIS server is whois.nic.viking).
Same registry, other endings
1 other TLD shares this operator.
.viking FAQ
What country is .viking?
None. .viking is a generic top-level domain, so it isn't tied to any country.
Who owns the .viking domain extension?
Viking River Cruises (Bermuda) Ltd. operates .viking as its registry, under a registry agreement with ICANN.
When was .viking created?
.viking was delegated to the DNS root zone on February 22, 2016.
Is .viking a valid domain?
Yes. .viking is an active top-level domain in the DNS root zone, delegated in 2016, so .viking addresses work in every browser.
Can I buy a .viking domain?
No. .viking is a brand TLD under ICANN Specification 13, so names are reserved for Viking River Cruises (Bermuda) Ltd.
Is .viking DNSSEC-signed?
Yes, the root zone holds a DS record for .viking.
Sources
Data from IANA root zone version 2026102000. Last changed August 11, 2023. Spotted something wrong? Tell us.
