.nfl
Generic top-level domain
Nobody outside the registry can register here. .nfl is a brand TLD run by NFL Reg Ops LLC, which under ICANN's Specification 13 means its operator is the only permitted registrant. ds reports names here as PRIVATE rather than AVAILABLE, and leaves the zone out of --tld all unless you pass --private include. See Brand and reserved TLDs.
- Registration
- Closedno public names
- Operator
- NFL Reg Ops LLC
- Lookup
- RDAPanswers for it
- DNSSEC
- Signed1 DS record in the root
- Level
- Secondmybrand.nfl
Check a name
Names under .nfl cannot be registered, but ds will still tell you what the registry says.
ds mybrand --tld nflAdd --where for the registrars and the registry's rules, --registry for the server that answered, or --all-info for everything at once.
What it costs
No registrar in the price table bundled with ds quotes .nfl, so the CLI prints no figure beside it — one of 927 such TLDs. That is a gap in the table as often as it is a TLD nobody sells, though here it is neither: the zone is closed. See Prices for supplying your own table with --pricing-file.
Who can register
Nobody outside NFL Reg Ops LLC — see the note at the top of this page.
How ds answers for it
RDAP first, WHOIS second — the same order for every TLD. .nfl has an RDAP service and no WHOIS entry, so every answer is authoritative RDAP.
- RDAP
https://rdap.nic.nflFrom IANA's bootstrap, refreshed when this page was built. The lookup ishttps://rdap.nic.nfl/domain/mybrand.nfl— a 404 means the name is free.
ds mybrand --tld nfl --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .nfl today. See Accuracy notes.
The registry
From IANA's delegation record for .nfl. .nfl is a generic TLD.
- Run by
- NFL Reg Ops LLCBased in United States of America. Delegated 2016-06-03, record last updated 2024-05-11.
- Registry site
- www.nfl.comWhere the registry documents .nfl — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
- Published services
rdap.nic.nflWhat the registry itself tells IANA it runs. They agree with whatdsasks.- Name servers
a.nic.nflb.nic.nflc.nic.nflns4.dns.nic.nflns5.dns.nic.nflns6.dns.nic.nflThe 6 authoritative servers for the .nfl zone — what the root delegates to. Nothingdsqueries directly; they are what makes a registered name resolve.
What it is
Derived from the root zone and ICANN's registry list — each one is a fact with a source.
genericIANA Root Zone Database types it "generic"brandICANN records Specification 13 — a brand TLD, closed to the publicnew-gtldICANN delegated it on or after 2013-10-23, when the 2013 round opened — seedelegated
In the root zone
The delegation itself, read out of the root zone — serial 2026090900, on 2026-09-09. The registry section above is IANA's record of what .nfl was delegated to; this is what the root actually answers with when a resolver asks it where .nfl lives.
- Delegated to
a.nic.nfl37.209.192.92001:dcd:1::9b.nic.nfl37.209.194.92001:dcd:2::9c.nic.nfl37.209.196.92001:dcd:3::9ns4.dns.nic.nfl156.154.156.1222610:a1:1074::7ans5.dns.nic.nfl156.154.157.1222610:a1:1075::7ans6.dns.nic.nfl156.154.158.1222610:a1:1076::7a
dsqueries: these servers know which names exist, not who registered them.- DNSSEC
- Signed — 1 DS record in the root
- key 7234RSA/SHA-256 · SHA-256
EC15A3B4D86192561C46BC1EBB72AA65BF5BF9C9D07A32EE736157EBADD447BB
- key 7234RSA/SHA-256 · SHA-256
Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net nfl. NS and dig +norec @a.root-servers.net nfl. DS.