diff --git a/aspnetcore/blazor/fundamentals/logging.md b/aspnetcore/blazor/fundamentals/logging.md
index 46dac5507b..7ba5de33d1 100644
--- a/aspnetcore/blazor/fundamentals/logging.md
+++ b/aspnetcore/blazor/fundamentals/logging.md
@@ -860,6 +860,6 @@ Use ***either*** of the following approaches:
 * [Implement a custom logging provider in .NET](/dotnet/core/extensions/custom-logging-provider)
 * Browser developer tools documentation:
   * [Chrome DevTools](https://developer.chrome.com/docs/devtools/)
-  * [Firefox Developer Tools](https://developer.mozilla.org/docs/Tools)
+  * [Firefox Developer Tools](https://firefox-source-docs.mozilla.org/devtools-user/index.html)
   * [Microsoft Edge Developer Tools overview](/microsoft-edge/devtools-guide-chromium/)
 * [Blazor samples GitHub repository (`dotnet/blazor-samples`)](https://github.com/dotnet/blazor-samples) ([how to download](xref:blazor/fundamentals/index#sample-apps))
diff --git a/aspnetcore/blazor/javascript-interoperability/index.md b/aspnetcore/blazor/javascript-interoperability/index.md
index 3b921e9b3b..ebf93b8dc5 100644
--- a/aspnetcore/blazor/javascript-interoperability/index.md
+++ b/aspnetcore/blazor/javascript-interoperability/index.md
@@ -249,7 +249,7 @@ To disable client-side caching in browsers, developers usually adopt one of the
 
 * Disable caching when the browser's developer tools console is open. Guidance can be found in the developer tools documentation of each browser maintainer:
   * [Chrome DevTools](https://developer.chrome.com/docs/devtools/)
-  * [Firefox Developer Tools](https://developer.mozilla.org/docs/Tools)
+  * [Firefox Developer Tools](https://firefox-source-docs.mozilla.org/devtools-user/index.html)
   * [Microsoft Edge Developer Tools overview](/microsoft-edge/devtools-guide-chromium/)
 * Perform a manual browser refresh of any webpage of the Blazor app to reload JS files from the server. ASP.NET Core's HTTP Caching Middleware always honors a valid no-cache [`Cache-Control` header](https://developer.mozilla.org/docs/Web/HTTP/Headers/Cache-Control) sent by a client.
 
diff --git a/aspnetcore/blazor/security/includes/troubleshoot-server.md b/aspnetcore/blazor/security/includes/troubleshoot-server.md
index fdb2019bf7..f1c36bfe24 100644
--- a/aspnetcore/blazor/security/includes/troubleshoot-server.md
+++ b/aspnetcore/blazor/security/includes/troubleshoot-server.md
@@ -24,7 +24,7 @@ To enable debug or trace logging for Blazor WebAssembly authentication, see the
 
     * [Google Chrome](https://developers.google.com/web/tools/chrome-devtools/network) (Google documentation)
     * [Microsoft Edge](/microsoft-edge/devtools-guide-chromium/network/)
-    * [Mozilla Firefox](https://developer.mozilla.org/docs/Tools/Network_Monitor) (Mozilla documentation)
+    * [Mozilla Firefox](https://firefox-source-docs.mozilla.org/devtools-user/network_monitor/index.html) (Mozilla documentation)
   
   The documentation team responds to document feedback and bugs in articles (open an issue from the **This page** feedback section) but is unable to provide product support. Several public support forums are available to assist with troubleshooting an app. We recommend the following:
   
diff --git a/aspnetcore/blazor/security/includes/troubleshoot-wasm.md b/aspnetcore/blazor/security/includes/troubleshoot-wasm.md
index c809649831..3cd2263008 100644
--- a/aspnetcore/blazor/security/includes/troubleshoot-wasm.md
+++ b/aspnetcore/blazor/security/includes/troubleshoot-wasm.md
@@ -22,7 +22,7 @@ To enable debug or trace logging for Blazor WebAssembly authentication, see the
 
     * [Google Chrome](https://developers.google.com/web/tools/chrome-devtools/network) (Google documentation)
     * [Microsoft Edge](/microsoft-edge/devtools-guide-chromium/network/)
-    * [Mozilla Firefox](https://developer.mozilla.org/docs/Tools/Network_Monitor) (Mozilla documentation)
+    * [Mozilla Firefox](https://firefox-source-docs.mozilla.org/devtools-user/network_monitor/index.html) (Mozilla documentation)
 
   * For releases of Blazor where a JSON Web Token (JWT) is used, decode the contents of the token used for authenticating a client or accessing a server web API, depending on where the problem is occurring. For more information, see [Inspect the content of a JSON Web Token (JWT)](#inspect-the-content-of-a-json-web-token-jwt).
   
diff --git a/aspnetcore/blazor/security/webassembly/standalone-with-identity.md b/aspnetcore/blazor/security/webassembly/standalone-with-identity.md
index 1e1c761ab4..bdb6a57b23 100644
--- a/aspnetcore/blazor/security/webassembly/standalone-with-identity.md
+++ b/aspnetcore/blazor/security/webassembly/standalone-with-identity.md
@@ -301,7 +301,7 @@ If the configuration appears correct:
 
 * [Google Chrome](https://developers.google.com/web/tools/chrome-devtools/network) (Google documentation)
 * [Microsoft Edge](/microsoft-edge/devtools-guide-chromium/network/)
-* [Mozilla Firefox](https://developer.mozilla.org/docs/Tools/Network_Monitor) (Mozilla documentation)
+* [Mozilla Firefox](https://firefox-source-docs.mozilla.org/devtools-user/network_monitor/index.html) (Mozilla documentation)
 
 The documentation team responds to document feedback and bugs in articles. Open an issue using the **Open a documentation issue** link at the bottom of the article. The team isn't able to provide product support. Several public support forums are available to assist with troubleshooting an app. We recommend the following: