What is .americanfamily?
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 .americanfamily names for sale at any registrar.
ICANN's records put the delegation of .americanfamily on July 26, 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 July 23, 2015.
AmFam, Inc. also runs one other TLD, including .amfam.
Under the hood, the root zone points to 6 name servers for .americanfamily, every one of them reachable over IPv6. The delegation is DNSSEC-signed, so resolvers can verify that answers for .americanfamily haven't been tampered with on the way. Registration data is published over RDAP and WHOIS (the WHOIS server is whois.nic.americanfamily).
Same registry, other endings
1 other TLD shares this operator.
.americanfamily FAQ
What country is .americanfamily?
None. .americanfamily is a generic top-level domain, so it isn't tied to any country.
Who owns the .americanfamily domain extension?
AmFam, Inc. operates .americanfamily as its registry, under a registry agreement with ICANN.
When was .americanfamily created?
.americanfamily was delegated to the DNS root zone on July 26, 2016.
Is .americanfamily a valid domain?
Yes. .americanfamily is an active top-level domain in the DNS root zone, delegated in 2016, so .americanfamily addresses work in every browser.
Can I buy a .americanfamily domain?
No. .americanfamily is a brand TLD under ICANN Specification 13, so names are reserved for AmFam, Inc.
Is .americanfamily DNSSEC-signed?
Yes, the root zone holds a DS record for .americanfamily.
Sources
Data from IANA root zone version 2026102000. Last changed August 23, 2024. Spotted something wrong? Tell us.