What is .tickets?
.tickets entered the DNS root zone on March 25, 2015, 11 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.
XYZ.COM LLC operates a large portfolio of 35 TLDs, including .audio, .auto, .autos, .baby and .beauty.
On the technical side, .tickets is served by 4 authoritative name servers, every one of them reachable over IPv6. It is also DNSSEC-signed: the root zone carries a DS record for .tickets, which lets validating resolvers check its answers cryptographically. Registration data is published over RDAP and WHOIS (the WHOIS server is whois.nic.tickets).
Same registry, other endings
34 other TLDs share this operator.
.tickets FAQ
What does .tickets mean?
.tickets is a generic top-level domain named for the word "tickets". It doesn't belong to any country.
What country is .tickets?
None. .tickets is a generic top-level domain, so it isn't tied to any country.
Who owns the .tickets domain extension?
XYZ.COM LLC operates .tickets as its registry, under a registry agreement with ICANN.
When was .tickets created?
.tickets was delegated to the DNS root zone on March 25, 2015.
Is .tickets a valid domain?
Yes. .tickets is an active top-level domain in the DNS root zone, delegated in 2015, so .tickets addresses work in every browser.
Can I buy a .tickets domain?
.tickets names are sold through ICANN-accredited registrars. Some gTLDs restrict who can register, so read XYZ.COM LLC's policy if you're unsure.
Is .tickets DNSSEC-signed?
Yes, the root zone holds a DS record for .tickets.
Sources
Data from IANA root zone version 2026102000. Last changed August 12, 2025. Spotted something wrong? Tell us.
