Having a domain under the .us TLD once seemed appealing to me for practical reasons: It's short, consistently inexpensive, and hasn't already sold the vast majority of its useful namespace to squatters. Unfortunately, it forbids WHOIS privacy services, which makes it a privacy and security hazard for personal domains. Pity, that.
Setting up a free *.city.state.us locality domain (2025)
131–140 of 233 posts
Re: Setting up a free *.city.state.us locality domain (2025)
#132Earlier quoted context omitted.
I managed a couple ".k12.oh.us" domains back in the day. The employees hated the domain in their email addresses, but I found it very logical. I saw all kinds screwed-up addresses in bounce messages forwarded to my company address when "can't email people in the District" tickets got sent my way (a lot of "districtname.oh.k12.us", etc). I guess it wasn't so simple for "normies". One of the schools ended up using a ".…
.gov should never have been expanded to outside the US federal government. (.com should never have been expanded to outside US-headquartered companies, either.)
Re: Setting up a free *.city.state.us locality domain (2025)
#133I had one for a long time but the isp that was the local registrar is long defunct now
Re: Setting up a free *.city.state.us locality domain (2025)
#134Earlier quoted context omitted.
Once you stop thinking of domain as an addressing tool and start thinking of them as branding, the complaints will make sense. "Dot k12 dot oh dot us" is a terrible brand name.
I have a hard time with public dollars going to "branding" but I do recognize it's a concern for some people and I'm a vastly minority opinion.
Re: Setting up a free *.city.state.us locality domain (2025)
#135Re: Setting up a free *.city.state.us locality domain (2025)
#136Anyone know why some larger cities are not listed? For example, I am noticing that Oakland, CA is missing. This would have been a major city in 1992 when the list was created as well.
Re: Setting up a free *.city.state.us locality domain (2025)
#137Having a domain under the .us TLD once seemed appealing to me for practical reasons: It's short, consistently inexpensive, and hasn't already sold the vast majority of its useful namespace to squatters. Unfortunately, it forbids WHOIS privacy services, which makes it a privacy and security hazard for personal domains. Pity, that.
you can literally write anything in the whois though registrars have forwarded me ICANN notices about having info verification for 10 years and nothing happened nothingburger
Can confirm.
I have a domain that's had outdated whois information since 2006. Nobody cares.
Even when it was up to date, it never got any spam, I suspect because the contact information was in a country that wasn't valuable to spammers.
Re: Setting up a free *.city.state.us locality domain (2025)
#138Earlier quoted context omitted.
"can be" ≠ "must be"
"can be" is used to list all possible values, which is where the confusion arises. It sounds like: ∀x, x>C v x "Might be", I think would be better.
Re: Setting up a free *.city.state.us locality domain (2025)
#139Seeing the *.k12.oh.us in the delegated subdomains brought me back to highschool. When I was little I always wondered why the city name was before k12. Didn't know it was structured like that everywhere.
When I was in my wandering days before there were search engines, I would always enter http://travel.state.*st*.us, or http://travel.*st*.us to look up tourism web sites.
It was unusual for a city or state to not have a travel.city.state.us, or travel.state.us domain.
Re: Setting up a free *.city.state.us locality domain (2025)
#140MD BALTIMORE.MD.US. alby@uunet.uu.net
I am guessing that uunet email address is not going to go anywhere!