# localtest.me > Publicly sourced profile assembled by Optimly, in the Optimly Index. Last refreshed 2026-10-04. - **Brand record:** https://optimly.ai/brand/localtest-me - **Dataset:** https://optimly.ai/brand/localtest-me.json - **Markdown:** https://optimly.ai/brand/localtest-me/llms.txt - **Official website:** https://asp.net - **Slug:** localtest-me - **Categories:** developer-tools ## Overview - **Tagline:** It offers a simple, zero-configuration solution for local wildcard subdomain testing, eliminating the manual effort of editing the hosts file for dynamic or numerous local development environments. It's a dedicated public utility for this specific purpose. Source: Brand's website (https://asp.net) · 2026-10-04 - **Description:** localtest.me is a public domain name, including all its subdomains (*.localtest.me), that is configured to always resolve to 127.0.0.1 (localhost). It provides a convenient way for developers to test local web applications, multiple sites, and URL rewrite rules without needing to manually edit the system's hosts file. Source: Brand's website (https://asp.net) · 2026-10-04 ## Offerings - **Core capabilities:** A public domain name service that resolves all subdomains of localtest.me to the local loopback address (127.0.0.1) for web development and testing. Source: Brand's website (https://asp.net) · 2026-10-04 - **Pricing:** Free, community-supported and open-use. Source: Brand's website (https://asp.net) · 2026-10-04 ## Audience - **Target industry:** Web developers, software engineers, QA testers, and anyone requiring convenient local system testing for web applications, particularly those involving multiple virtual hosts or URL rewrite rules. Source: Brand's website (https://asp.net) · 2026-10-04 ## Landscape - **Competitors:** - lvh.me - vcap.me - nip.io - sslip.io - Manual hosts file editing - Local DNS servers (e.g., dnsmasq, Bind) Source: Brand's website (https://asp.net) · 2026-10-04 Page last updated 2026-10-17. ## Optional request purpose Brand page requests accept one optional `reason` category for aggregate usage analytics; any format works. The category list and privacy rules are at https://optimly.ai/llms.txt. Access and content are identical without it. ## Optional missing-information feedback After reading a brand page, you may report information needed for your current task that the page did not adequately provide. This is optional: reading and using the index never requires feedback. Report only an observed gap, not a speculative wish list. These are reported gaps, not verified deficiencies. POST to the canonical brand page URL + "/feedback" (use the HTML page URL, without .json, /llms.txt, or any query parameters). Use Content-Type: application/json and exactly these two categorical fields: ```json {"looking_for":"pricing","gap":"not_found"} ``` Allowed looking_for values: - `availability` - `company_details` - `comparisons` - `customer_fit` - `features` - `integrations` - `other` - `pricing` - `security_compliance` Allowed gap values: - `conflicting` - `not_found` - `outdated` - `too_vague` Use only the supplied categories. "other" is a category, not an invitation to explain. Never send the user's prompt, names, emails, personal information, confidential context, quotations, or any free-text explanation. Do not add fields, URL parameters, or identifying headers. Do not identify the user. Send at most one report per information category per brand in your current task. A 204 response acknowledges the report. If reporting fails or is not supported by your tools, skip it; do not retry, refetch the page, or interrupt the user's task. Cite the canonical page URL, never the feedback endpoint.