Fix broken links

Author: RebeccaTamachiro

src/content/docs/dns/troubleshooting/email-issues.mdx

@@ -28,15 +28,15 @@ Also, if `CNAME` records are not returned by the queried nameserver (sometimes n
 
 ## Is Cloudflare Spectrum enabled on your account?
 
-Cloudflare does not proxy traffic on port 25 (SMTP) unless [Cloudflare Spectrum](/spectrum/reference/configuration-options#smtp) is enabled and configured to proxy email traffic across Cloudflare. If you do not have Spectrum enabled, then no email traffic (SMTP) will actually pass through Cloudflare, and we will simply resolve the DNS. This also means that any DNS record used to send email traffic must be DNS-only to bypass the Cloudflare network. Check [Identifying subdomains compatible with Cloudflare's proxy](/dns/manage-dns-records/reference/proxied-dns-records) for more details.
+Cloudflare does not proxy traffic on port 25 (SMTP) unless [Cloudflare Spectrum](/spectrum/reference/configuration-options#smtp) is enabled and configured to proxy email traffic across Cloudflare. If you do not have Spectrum enabled, then no email traffic (SMTP) will actually pass through Cloudflare, and we will simply resolve the DNS. This also means that any DNS record used to send email traffic must be DNS-only to bypass the Cloudflare network. Check [Identifying subdomains compatible with Cloudflare's proxy](/dns/proxy-status/) for more details.
 
 ## Contact your mail provider for assistance
 
 If your email does not work shortly after editing DNS records, contact your mail administrator or mail provider for further assistance in troubleshooting so that data about the issue can be provided to Cloudflare support.
 
 ## dc-######### subdomain
 
-The dc-##### subdomain is added to overcome a conflict created when your `SRV` or `MX` record resolves to a domain configured to [proxy](/dns/manage-dns-records/reference/proxied-dns-records) to Cloudflare.
+The dc-##### subdomain is added to overcome a conflict created when your `SRV` or `MX` record resolves to a domain configured to [proxy](/dns/proxy-status/) to Cloudflare.
 
 Therefore, Cloudflare will create a `dc-#####` DNS record that resolves to the origin IP address. The `dc-#####` record ensures that traffic for your `MX` or `SRV` record is not proxied (it directly resolves to your origin IP) while the Cloudflare proxy works for all other traffic.
 
@@ -62,7 +62,7 @@ Removing the `dc-######` record is only possible via one of these methods:
 :::caution
 
 If your mail server resides on the same IP as your web server, your MX
-record will expose your origin IP address. 
+record will expose your origin IP address.
 :::
 
 ***

src/content/docs/rules/page-rules/how-to/override-url-or-ip-address.mdx

@@ -49,7 +49,7 @@ To configure a resolve override in Page Rules, do the following:
 
 :::caution[Important remarks]
 
-- Page Rules require a [proxied DNS record](/dns/manage-dns-records/reference/proxied-dns-records) to work. Page Rules will not apply to subdomains that do not exist in DNS or are not being directed to Cloudflare.
+- Page Rules require a [proxied DNS record](/dns/proxy-status/) to work. Page Rules will not apply to subdomains that do not exist in DNS or are not being directed to Cloudflare.
 
 - The _Resolve Override_ setting only allows override of the hostname, not the path. If you need to modify the path also, you will need to either use a [Worker](/workers/runtime-apis/request/#the-cf-property-requestinitcfproperties) or combine the page rule with a [transform rule](/rules/transform/url-rewrite/).
 

src/content/docs/rules/page-rules/manage.mdx

@@ -43,7 +43,7 @@ You may also want to review the documentation on [wildcard matching](/rules/page
 
 :::note[Notes]
 
-- Page Rules require a [proxied DNS record](/dns/manage-dns-records/reference/proxied-dns-records) to work. Page Rules will not apply to subdomains that do not exist in DNS or are not being directed to Cloudflare.
+- Page Rules require a [proxied DNS record](/dns/proxy-status/) to work. Page Rules will not apply to subdomains that do not exist in DNS or are not being directed to Cloudflare.
 
 - Cloudflare does not support non-ASCII characters — such as punycode/unicode domain — in Page Rules. Instead, you could URL-encode the string using [Punycode converter](https://www.punycoder.com/).
   :::

src/content/docs/ssl/edge-certificates/universal-ssl/enable-universal-ssl.mdx

@@ -24,7 +24,7 @@ If your website or application is already live and cannot be uncovered while the
 
 * Order an [advanced certificate](/ssl/edge-certificates/advanced-certificate-manager/) before proxying traffic to Cloudflare.
 * Upload a [custom certificate](/ssl/edge-certificates/custom-certificates/) prior to migrating and then delete the certificate after your [Universal certificate is active](#verify-your-certificate-is-active).
-* Keep DNS records [**unproxied**](/dns/manage-dns-records/reference/proxied-dns-records) until your [certificate is active](#verify-your-certificate-is-active).
+* Keep DNS records [**unproxied**](/dns/proxy-status/) until your [certificate is active](#verify-your-certificate-is-active).
 
 :::note
 If your domain is using a **partial setup**, you will need to add [Domain Control Validation (DCV) records](/ssl/edge-certificates/changing-dcv-method/) to your authoritative DNS.

src/content/docs/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors.mdx

@@ -144,7 +144,7 @@ Error 520 occurs when the origin server returns an empty, unknown, or unexpected
 :::note
 
 A quick workaround while further investigating 520 errors is to either
-make the record [DNS-only](/dns/manage-dns-records/reference/proxied-dns-records)
+make the record [DNS-only](/dns/proxy-status/)
 in the Cloudflare **DNS** app or [temporarily pause Cloudflare](/fundamentals/setup/manage-domains/pause-cloudflare/).
 :::
 
@@ -218,7 +218,7 @@ Error 522 occurs when Cloudflare times out contacting the origin web server. Two
 - Packets were dropped at your origin web server.
 
 If you are using [Cloudflare Pages](/pages/), verify that you have a custom domain set up and that your CNAME record is pointed to your [custom Pages domain](/pages/configuration/custom-domains/#add-a-custom-domain).
-If you are using [Workers with a Custom Domain](/workers/configuration/routing/custom-domains/), performing a `fetch` to its own hostname will cause a 522 error. Consider using a [Route](/workers/configuration/routing/) or target another hostname instead. 
+If you are using [Workers with a Custom Domain](/workers/configuration/routing/custom-domains/), performing a `fetch` to its own hostname will cause a 522 error. Consider using a [Route](/workers/configuration/routing/) or target another hostname instead.
 
 If none of the above leads to a resolution, request the following information from your hosting provider or site administrator before [contacting Cloudflare support](/support/contacting-cloudflare-support/):
 
@@ -389,8 +389,8 @@ As a result, a valid SSL certificate is required at the origin.
 
 ## Error 530
 
-An HTTP error 530 is returned when Cloudflare is encountering an issue resolving the origin hostname. 
-In this case the body of the response contains an [1XXX error](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors) code. 
+An HTTP error 530 is returned when Cloudflare is encountering an issue resolving the origin hostname.
+In this case the body of the response contains an [1XXX error](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors) code.
 Please refer to the specific [1XXX error](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors) for troubleshooting information.
 
 ---

src/content/partials/rules/page-rule-proxied-dns-warning.mdx

@@ -5,5 +5,5 @@
 
 :::caution
 
-Page Rules require a [proxied DNS record](/dns/manage-dns-records/reference/proxied-dns-records) to work. Page Rules will not apply to subdomains that do not exist in DNS or are not being directed to Cloudflare. 
+Page Rules require a [proxied DNS record](/dns/proxy-status/) to work. Page Rules will not apply to subdomains that do not exist in DNS or are not being directed to Cloudflare.
 :::