Skip to content

Document Safari's lack of *.localhost domain support #36374

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Nov 21, 2025
Merged

Document Safari's lack of *.localhost domain support #36374

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3b23bfa
Initial plan
Copilot Nov 19, 2025
26bd26e
Add Safari compatibility note to localhost-tld.md
Copilot Nov 19, 2025
130f318
Apply suggestions from code review - clarified "client" app.
wadepickett Nov 19, 2025
fb7930a
Update aspnetcore/test/localhost-tld.md
wadepickett Nov 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions aspnetcore/test/localhost-tld.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ description: Learn how using localhost as top-level domain can make testing easi
monikerRange: '>= aspnetcore-10.0'
ms.author: tdykstra
ms.custom:
ms.date: 08/26/2025
ms.date: 11/19/2025
title: Support for the .localhost top-level domain
uid: test/localhost-tld
---
Expand All @@ -23,7 +23,9 @@ ASP.NET Core's built-in HTTP server, Kestrel, correctly treats any `*.localhost`

## Browser compatibility

While web browsers automatically resolve `*.localhost` names to the local loopback address, other apps might treat `*.localhost` names as regular domain names and attempt to resolve them via their corresponding DNS stack. If your DNS configuration doesn't resolve `*.localhost` names to an address, they fail to connect. You can continue to use the regular `localhost` name to address your apps when not in a web browser.
While most modern evergreen browsers automatically resolve `*.localhost` names to the local loopback address, Safari on macOS doesn't support this feature. In Safari, you should use the regular `localhost` name instead of `*.localhost` domain names.

Other apps might treat `*.localhost` names as regular domain names and attempt to resolve them via their corresponding DNS stack. If your DNS configuration doesn't resolve `*.localhost` names to an address, they fail to connect. You can continue to use the regular `localhost` name to address your apps when not in a web browser.

## HTTPS development certificate

Expand Down