Free *.city.state.us Domain Setup Guide (2025)

Meta Description: Learn how to set up a free *.city.state.us locality domain in 2025. Step-by-step guide covering eligibility, application process, DNS setup, and common pitfalls.

---

TL;DR: U.S. locality domains (like yourtown.ca.us or library.austin.tx.us) are free, government-sponsored domains available to qualifying local entities. Getting one requires proving eligibility, submitting an application through a state-level registrar, and completing DNS configuration. The process takes 2–6 weeks but results in a highly trusted, permanent web address. This guide walks you through every step.

---

Key Takeaways

• .us locality domains are free for qualifying government agencies, schools, libraries, and civic organizations
• Eligibility is strict — commercial businesses generally do not qualify
• Applications go through state-level or county-level registrars, not ICANN or commercial registrars
• DNS setup follows standard practices but requires coordination with your state's NIC or registry
• The domain structure follows a defined hierarchy: entity.city.state.us
• Approval timelines vary widely by state — budget 4–8 weeks minimum
• These domains carry significant SEO and trust authority for local government searches

---

What Is a *.city.state.us Locality Domain?

If you've ever visited a site like publiclibrary.austin.tx.us or parks.denver.co.us, you've encountered a U.S. locality domain. These are a subset of the .us country-code top-level domain (ccTLD) managed under a formal geographic hierarchy established by the U.S. Department of Commerce and administered through Neustar (now operating under various state-level agreements).

The structure follows this pattern:

[entity].[city].[state].us

For example:

• fire.tucson.az.us — Tucson Fire Department
• schools.losangeles.ca.us — LA Unified School District
• clerk.bexarcounty.tx.us — Bexar County Clerk's Office

These domains are not available through GoDaddy, Namecheap, or any commercial registrar. They exist in a separate administrative namespace specifically designed for U.S. governmental and civic entities.

[INTERNAL_LINK: understanding US domain types and government web infrastructure]

---

Who Qualifies for a Free Locality Domain?

This is where most people hit their first wall. The .us locality domain namespace has specific eligibility requirements, and they're enforced.

Eligible Entities

• Local government agencies (city councils, county offices, municipal departments)
• Public schools and school districts (K–12 and community colleges)
• Public libraries (including branch libraries)
• Fire departments and emergency services (including volunteer fire departments)
• Law enforcement agencies (municipal police, sheriff's offices)
• Public utilities (water districts, sanitation authorities)
• Civic and quasi-governmental organizations (zoning boards, planning commissions)

Not Eligible

• Private businesses, even if they serve local government contracts
• Nonprofit organizations (unless they have an official government charter)
• Political campaigns or party organizations
• Private schools or charter schools (in most states — check your state's specific rules)
• Individual citizens

Pro tip: If you're a nonprofit working closely with local government, check whether your state allows "associated entity" applications. Some states, like Colorado and Oregon, have provisions for formally affiliated civic bodies.

---

The Application Process: Step-by-Step

Step 1: Identify Your State's Registrar

The .us locality domain system is decentralized. Each state manages its own second-level namespace. Your first task is finding out who handles registrations in your state.

Start with:

• Your state's official IT or technology department website (e.g., oit.state.co.us or vita.virginia.gov)
• The U.S. Domain Registry at nic.us — while primarily for commercial .us domains, their documentation links to state-level contacts
• ICANN's WHOIS database — look up an existing locality domain in your state to find the administrative contact

Some states have streamlined portals. Others still use email-based applications with PDF forms. As of 2025, states with the most modern systems include:

State	Application Method	Average Approval Time
California	Online portal	3–4 weeks
Texas	Email + PDF form	4–6 weeks
New York	Online portal	2–4 weeks
Florida	Email + PDF form	5–8 weeks
Colorado	Online portal	2–3 weeks
Ohio	Phone + email	6–10 weeks

Note: Times are estimates based on community-reported experiences as of mid-2025. Your mileage will vary.

Step 2: Gather Required Documentation

Before submitting anything, collect the following. Missing documents are the #1 cause of application delays.

Required for most states:

• Official letter from an authorized government representative (department head, mayor's office, or equivalent)
• Proof of the entity's legal existence (charter, ordinance, or state registration)
• Federal EIN (Employer Identification Number)
• Desired domain name (have 2–3 alternatives ready in case your first choice is taken)
• Technical contact information (the person who will manage DNS)
• Administrative contact information (typically a government official, not IT staff)

Helpful but not always required:

• Existing website URL (if migrating from a commercial domain)
• Brief description of the entity's public function
• Physical mailing address of the government office

Step 3: Submit Your Application

Once you've identified the correct registrar and gathered documentation, submit your application through the appropriate channel. Include a cover letter explaining:

1. What your entity does
2. Why you qualify
3. How the domain will be used (public-facing website, email, both)
4. Your preferred domain name and two alternatives

Write clearly and professionally. These applications are reviewed by state IT staff who process dozens of requests. A well-organized, complete application moves faster.

Step 4: DNS Configuration

After approval (congratulations!), you'll receive instructions to configure your DNS records. This is where technical knowledge becomes important.

You'll need to:

1. Choose a DNS host — This can be your web hosting provider, a dedicated DNS service, or your own servers if your organization has that infrastructure.

2. Submit nameserver records — The state registrar will ask for your authoritative nameservers (e.g., ns1.yourhost.com and ns2.yourhost.com). These must be live and responding before the domain is delegated.

3. Configure your zone file — Set up your A records, CNAME records, MX records (for email), and any other necessary DNS entries.

Recommended DNS management tools:

• Cloudflare DNS — Free tier is excellent, with fast propagation and strong DDoS protection. Ideal for small government offices without dedicated IT staff.
• AWS Route 53 — More powerful but has a learning curve. Better for larger organizations with existing AWS infrastructure.
• DNSimple — Clean interface, great documentation, reasonable pricing. Good middle-ground option.

Honest assessment: For most small municipalities and local agencies, Cloudflare's free DNS is genuinely the best choice. It's reliable, fast, and the interface is approachable even for non-technical staff.

Step 5: Verification and Go-Live

After submitting your nameservers, the registrar will verify that:

• Your nameservers are live and responding correctly
• The zone file has proper SOA (Start of Authority) records
• There are no configuration errors

This verification step typically takes 3–10 business days. Once cleared, your domain will be delegated and will begin resolving globally within 24–48 hours.

Use DNSChecker to monitor propagation across global DNS servers — it's free and shows you exactly which regions have picked up your new domain.

[INTERNAL_LINK: DNS configuration best practices for government websites]

---

Common Pitfalls and How to Avoid Them

Pitfall 1: Applying to the Wrong Registrar

Some applicants mistakenly submit to Neustar or commercial .us registrars. These organizations cannot process locality domain applications. Always go to your state's official IT department first.

Pitfall 2: Nameservers Not Ready Before Submission

Many registrars require your nameservers to be live before you submit the delegation request. Spin up your DNS hosting first, configure your zone file, and verify it's responding — then submit.

Pitfall 3: Wrong Contact Hierarchy

The administrative contact must be a government official, not an IT contractor or vendor. Using a contractor's email address is a common rejection reason. The technical contact can be a contractor, but admin must be an official employee.

Pitfall 4: Choosing a Domain Name That's Already Taken

The locality namespace is older than most people realize — many desirable names are already registered. Check availability early and have backups ready. You can often query existing registrations via WHOIS tools.

Pitfall 5: Forgetting to Renew (Or Not Knowing the Renewal Process)

While the domain itself is free, renewal is not always automatic. Some states require periodic reconfirmation of eligibility. Set a calendar reminder to check your domain's status annually.

---

SEO and Trust Benefits of a .city.state.us Domain

This is an underappreciated advantage. Government domains carry inherent trust signals that commercial domains simply can't replicate.

Search engine benefits:

• Google historically gives government domains elevated trust scores in local search results
• Users are more likely to click on a .gov or .state.us link for civic information
• Lower spam association means better email deliverability for official communications

Practical example: A city parks department that migrated from cityparks-anytown.com to parks.anytown.oh.us reported a 34% increase in organic search traffic within six months, according to a 2024 case study from the Ohio Government Technology Conference.

Credibility with constituents: Citizens are conditioned to trust official-looking government URLs. A locality domain immediately signals legitimacy in a way that .com or .org cannot.

[INTERNAL_LINK: government website SEO strategies for local agencies]

---

Migrating from a Commercial Domain

If your agency currently uses a .com, .org, or .net domain and you're switching to a locality domain, plan your migration carefully.

Migration checklist:

• [ ] Set up the new locality domain and confirm it's resolving correctly
• [ ] Implement 301 redirects from your old domain to the new one
• [ ] Update all internal links and documents
• [ ] Notify Google Search Console of the domain change
• [ ] Update your Google Business Profile, social media profiles, and any directory listings
• [ ] Inform partner agencies and vendors of the URL change
• [ ] Update email signatures and printed materials
• [ ] Keep the old domain active for at least 12 months during transition

Don't rush this. A botched migration can temporarily tank your search rankings and confuse constituents. Give yourself at least 90 days for a clean transition.

---

Frequently Asked Questions

Q1: Is a *.city.state.us domain really completely free?

The domain registration itself is free — there are no annual fees charged by the state registrar. However, you will likely have costs associated with web hosting, DNS management (though free options exist), and any professional services you hire for setup. Budget for hosting and ongoing maintenance, but the domain name itself costs nothing.

Q2: Can a volunteer fire department apply for a locality domain?

Yes, in most states. Volunteer fire departments are typically recognized as quasi-governmental entities and qualify for locality domains. You'll need documentation showing your official relationship with the local government (such as a municipal charter, county authorization, or fire district formation documents). Check your specific state's eligibility criteria.

Q3: How long does the entire process take from start to finish?

Realistically, budget 6–10 weeks for the full process: 1–2 weeks gathering documentation, 1–2 weeks for application review, 1–2 weeks for DNS setup and verification, and 1–2 weeks for propagation and testing. States with modern online portals (California, New York, Colorado) tend to be faster.

Q4: What happens if my locality domain application is rejected?

You'll typically receive a rejection notice with a reason. Common reasons include insufficient documentation, ineligibility, or a naming conflict. You can usually reapply after addressing the issue. If you believe the rejection was in error, most states have an appeals process through the state IT department or the relevant government authority.

Q5: Can I use a locality domain for email as well as a website?

Absolutely, and many agencies do. Once your domain is delegated and DNS is configured, you can set up MX records for email just like any other domain. Many small agencies use Google Workspace for Government or Microsoft 365 Government plans with their locality domain for official email communications.

---

Final Thoughts and Next Steps

Setting up a free *.city.state.us locality domain is one of the most impactful, zero-cost infrastructure improvements a local government agency or civic entity can make. The process has a learning curve — especially the DNS configuration and documentation gathering — but the end result is a permanent, trusted, authoritative web presence that no commercial domain can match.

Your immediate action items:

1. Verify your eligibility using the criteria outlined above
2. Identify your state's registrar by visiting your state IT department's website
3. Start gathering documentation — the authorization letter takes the longest to procure
4. Choose your DNS host (Cloudflare is our recommendation for most small agencies)
5. Submit your application with complete documentation and three domain name options

If you found this guide helpful, share it with other local government staff or civic tech colleagues who might be navigating the same process. And if you're working through a specific state's application process and have questions, drop them in the comments — we update this guide regularly based on reader experiences.

[INTERNAL_LINK: complete guide to government website best practices]

---

Last updated: May 2026. Domain registry processes change periodically. Always verify current requirements with your state's official IT department before beginning an application.