0 last week
0 last month
149 active domains
125 domains with DNS records
Domains from 1 countries
149 domains with RDAP and WHOIS records
Includes 15 unique IPs hosting active domains
A metric that estimates network influence and trust, based on the link structure of domains using .in.us TLD
The average PageRank score reflecting the SEO authority of websites with the .in.us TLD
| TLD | Domain | TLD suffix | Country | IP address | Technologies | PR value | Harmonic value | Detected hosts count | DNS last data checked | DNS Status | DNS records | RDAP/WHOIS last data checked | RDAP/WHOIS method | Domain creation date | Domain expiration date | Domain last changed | Registrar | RDAP/WHOIS Record |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| us | state.in.us | in.us | United States (US) | 208.40.244.66 | 0.00000015762 | 14,541,714.00 | 2026/05/25 | 1 | {"A": ["208.40.244.66"], "NS": ["addi... | 2026/04/21 | WHOIS | 2003/02/06 | 2027/02/05 | 2026/02/11 | US Locality Zone Manager | {"raw_response": ... | ||
| us | fishers.in.us | in.us | United States (US) | 141.193.213.10 | ["Cloudflare"] | 0.00000006147 | 14,577,084.00 | 2026/05/28 | 1 | {"A": ["141.193.213.10", "141.193.213... | 2026/04/13 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | |
| us | steuben.in.us | in.us | United States (US) | 66.249.239.95 | 0.00000004760 | 17,105,140.00 | 2026/05/25 | 1 | {"A": ["66.249.239.95"], "NS": ["pdns... | 2026/04/18 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | ||
| us | huntington.in.us | in.us | United States (US) | 15.197.183.30 | ["NGINX", "Google Analytics"] | 0.00000004686 | 17,071,400.00 | 2026/05/21 | 1 | {"A": ["15.197.183.30"], "MX": [{"hos... | 2026/04/21 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | |
| us | delaware.in.us | in.us | ["Google Tag Manager", "NGINX", "Goog... | 0.00000004545 | 17,093,104.00 | 2026/05/22 | 1 | {"NS": ["ns1.localitymanagement.us", ... | 2026/04/15 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | |||
| us | boone.in.us | in.us | ["Apache HTTP Server"] | 0.00000004416 | 17,091,914.00 | 2026/05/22 | 1 | {"NS": ["ns1.localitymanagement.us", ... | 2026/04/17 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | |||
| us | johnson.in.us | in.us | ["Google Tag Manager", "NGINX"] | 0.00000004348 | 17,064,702.00 | 2026/05/29 | 1 | {"NS": ["ns1.localitymanagement.us", ... | 2026/04/13 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | |||
| us | bloomington.in.us | in.us | United States (US) | 188.114.96.3 | 0.00000003839 | 16,986,682.00 | 2026/05/20 | 1 | {"A": ["188.114.96.3", "188.114.97.3"... | 2026/04/14 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | ||
| us | henry.in.us | in.us | United States (US) | 63.206.44.251 | 0.00000002943 | 16,943,282.00 | 2026/05/20 | 1 | {"A": ["63.206.44.251"], "MX": [{"hos... | 2026/04/15 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | ||
| us | columbus.in.us | in.us | United States (US) | 54.172.125.244 | ["Google Tag Manager", "NGINX", "Face... | 0.00000002796 | 14,454,866.00 | 2026/05/27 | 1 | {"A": ["54.172.125.244"], "MX": [{"ho... | 2026/04/16 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | |
| us | adams.in.us | in.us | United States (US) | 208.90.189.165 | ["ASP.NET"] | 0.00000001822 | 14,332,432.00 | 2026/05/18 | 1 | {"A": ["208.90.189.165"], "NS": ["ns1... | 2026/04/21 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/04/15 | US Locality Zone Manager | {"raw_response": ... | |
| us | ellettsville.in.us | in.us | United States (US) | 15.197.145.36 | ["Google Tag Manager", "NGINX"] | 0.00000001145 | 14,296,335.00 | 2026/05/19 | 1 | {"A": ["15.197.145.36"], "MX": [{"hos... | 2026/04/21 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | |
| us | aurora.in.us | in.us | United States (US) | 185.146.167.199 | ["Apache HTTP Server", "WordPress", "... | 0.00000001085 | 14,296,833.00 | 2026/05/25 | 1 | {"A": ["185.146.167.199"], "MX": [{"h... | 2026/04/15 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | |
| us | bedford.in.us | in.us | United States (US) | 192.185.6.132 | ["ASP.NET", "Microsoft IIS"] | 0.00000000909 | 14,297,465.00 | 2026/05/20 | 1 | {"A": ["192.185.6.132"], "MX": [{"hos... | 2026/04/13 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | |
| us | butler.in.us | in.us | United States (US) | 13.248.222.104 | 0.00000000864 | 14,296,211.00 | 2026/05/23 | 1 | {"A": ["13.248.222.104"], "MX": [{"ho... | 2026/04/18 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | ||
| us | edinburgh.in.us | in.us | United States (US) | 15.197.183.30 | ["Google Tag Manager", "NGINX"] | 0.00000000835 | 14,315,365.00 | 2026/05/20 | 1 | {"A": ["15.197.183.30"], "MX": [{"hos... | 2026/04/18 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | |
| us | rochester.in.us | in.us | United States (US) | 35.208.127.20 | ["Google Tag Manager"] | 0.00000000797 | 14,296,400.00 | 2026/05/29 | 1 | {"A": ["35.208.127.20"], "MX": [{"hos... | 2026/04/21 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | |
| us | evansville.in.us | in.us | United States (US) | 63.206.44.251 | 0.00000000630 | 6,767,307.00 | 2026/05/25 | 1 | {"A": ["63.206.44.251"], "MX": [{"hos... | 2026/04/14 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | ||
| us | east-chicago.in.us | in.us | United States (US) | 63.206.44.251 | 0.00000000446 | 8,344,154.00 | 2026/05/24 | 1 | {"A": ["63.206.44.251"], "MX": [{"hos... | 2026/04/21 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | ||
| us | new-albany.in.us | in.us | United States (US) | 63.206.44.251 | 0.00000000446 | 8,344,154.00 | 2026/05/20 | 1 | {"A": ["63.206.44.251"], "MX": [{"hos... | 2026/04/16 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | ||
| us | noblesville.in.us | in.us | United States (US) | 209.43.47.40 | ["Cloudflare"] | 0.00000000414 | 10,032,203.00 | 2026/05/23 | 1 | {"A": ["209.43.47.40"], "MX": [{"host... | 2026/04/16 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | |
| us | marion.in.us | in.us | United States (US) | 63.206.44.251 | 0.00000000407 | 10,485,723.00 | 2026/05/20 | 1 | {"A": ["63.206.44.251"], "MX": [{"hos... | 2026/04/14 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | ||
| us | richmond.in.us | in.us | United States (US) | 63.206.44.251 | 0.00000000405 | 12,379,467.00 | 2026/05/19 | 1 | {"A": ["63.206.44.251"], "MX": [{"hos... | 2026/04/16 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | ||
| us | grissom-afb.in.us | in.us | United States (US) | 63.206.44.251 | 0.00000000000 | 0.00 | 2026/05/21 | 1 | {"A": ["63.206.44.251"], "MX": [{"hos... | 2026/04/17 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... | ||
| us | lawrenceburg.in.us | in.us | United States (US) | 206.162.193.46 | 0.00000000000 | 0.00 | 2026/05/24 | 1 | {"A": ["206.162.193.46"], "MX": [{"ho... | 2026/04/13 | WHOIS | 2003/02/05 | 2027/02/04 | 2026/02/10 | US Locality Zone Manager | {"raw_response": ... |
The largest database of live domains and detailed information about them, designed to boost your digital strategies.
| Technology | Count Domain | Percentage of Technology |
|---|---|---|
| Google Tag Manager | 13 | 24.07 |
| NGINX | 11 | 20.37 |
| Apache HTTP Server | 7 | 12.96 |
| Google Analytics | 6 | 11.11 |
| Cloudflare | 3 | 5.56 |
| PHP | 3 | 5.56 |
| WordPress | 3 | 5.56 |
| ASP.NET | 2 | 3.70 |
| WooCommerce | 2 | 3.70 |
| 1 | 1.85 | |
| Google reCAPTCHA | 1 | 1.85 |
| LiteSpeed Web Server | 1 | 1.85 |
| Microsoft IIS | 1 | 1.85 |
| Country | Count Domain | Percentage of Country |
|---|---|---|
| 127 | 85.23 | |
| United States (US) | 22 | 14.77 |
Within the .us country-code space, .in.us denotes the Indiana locality hierarchy; it functions as a governed second-level zone rather than a standalone extension. In our taxonomy, we analyze .in.us domains and related .in.us websites as an administrative namespace primarily used by public-sector bodies, school districts, libraries, and community programs with an Indiana nexus. Policies typically emphasize U.S. presence and purpose, while naming reflects municipalities or agencies. From our current index, we see active registrations across country, and live hosts responding today, indicating selective but stable web deployment. These measurements help benchmark adoption versus visibility across this geography-focused segment. Download .in.us domain datasets from webatla.
The .us locality framework has operated for decades to organize government and community presence beneath state codes; .in.us follows these conventions with Indiana-specific delegations and structured naming. In practice, .in.us domains and .in.us websites typically mirror civic functions, using standardized labels for municipalities, counties, and education entities, which supports recognizability and governance clarity. Our live telemetry shows domains publishing DNS, with newly discovered last week and overall last month, signaling very low churn and cautious expansion. Such patterns often correlate with budget cycles and policy-driven procurement rather than retail marketing dynamics. We track continuity, deprecations, and DNS posture across time to surface operational trends for stakeholders. Download longitudinal .in.us datasets from webatla.
Organizations select this namespace to convey jurisdictional alignment, legal accountability, and geographic precision. For public agencies, school districts, and libraries, .in.us domains reinforce Indiana identity while helping residents find authoritative resources; for contractors and civic initiatives, .in.us websites can signal affiliation or project scope. Our dataset shows live sites out of active records, with publishing DNS, suggesting many holdings support redirects, internal systems, or reserved future use within a single jurisdiction (). We evaluate SSL adoption, response health, and host density to compare visibility against peer state-local spaces. Decision-makers can map service coverage, while researchers quantify digital reach and resilience across agencies and districts. Download the complete .in.us datasets from webatla today.
The largest database of live domains and detailed information about them, designed to boost your digital strategies.
Yes, you can view examples to see the file format and the amount of information provided. You can download them on the Pricing page, under each package.
All files are provided in CSV format. If you need a different format (XML, JSON, SQL), please contact our support team.
You need to make a purchase on our website. Once the payment is complete, you will receive a download link for the files in your selected package.
We only offer package solutions. You can check out our packages and pricing on the Pricing page.
