> .corp, .home, and .lan are also reserved, just not codified into an RFC yet.
They aren't reserved as the term is usually used for domains. Reservations don't exist in outside of those codified in RFCs; the IANA is the party that reserves domains and the full current list of reserved special use domains is here:
Note that of those domains you falsely describe as reserved, .home was suggested as a special use domain in RFC 7788, but that was updated by RFC 8375 to the reserved domain .home.arpa.
.home, .corp, and .mail (but not .lan, AFAICT) are subject to a ICANN policy decision against granting delegations as TLDs, though, which means they won't become real TLDs while that policy is in effect (it doesn't mean they won't get reserved for a use which might conflict with what you might adopt them for, the way .local has for some uses, though.)
They aren't reserved as the term is usually used for domains. Reservations don't exist in outside of those codified in RFCs; the IANA is the party that reserves domains and the full current list of reserved special use domains is here:
https://www.iana.org/assignments/special-use-domain-names/sp...
More general info on reserved domains is here:
https://www.iana.org/domains/reserved
Note that of those domains you falsely describe as reserved, .home was suggested as a special use domain in RFC 7788, but that was updated by RFC 8375 to the reserved domain .home.arpa.
.home, .corp, and .mail (but not .lan, AFAICT) are subject to a ICANN policy decision against granting delegations as TLDs, though, which means they won't become real TLDs while that policy is in effect (it doesn't mean they won't get reserved for a use which might conflict with what you might adopt them for, the way .local has for some uses, though.)