[DNS] Update proxy status page and improve information overload

public/_redirects

@@ -354,6 +354,7 @@
 /dns/foundation-dns/graphql-analytics/ /dns/additional-options/analytics/ 301
 /dns/manage-dns-records/how-to/dns-load-balancing/ /dns/manage-dns-records/how-to/round-robin-dns/ 301
 /dns/manage-dns-records/how-to/create-root-domain/ /dns/manage-dns-records/how-to/create-zone-apex/ 301
+/dns/manage-dns-records/reference/proxied-dns-records/ /dns/proxy-status/ 301
 /dns/reference/troubleshooting/ /dns/reference/recommended-third-party-tools/ 301
 /dns/zone-setups/partial-setup/convert-partial-to-full/ /dns/zone-setups/conversions/convert-partial-to-full/ 301
 /dns/zone-setups/partial-setup/convert-partial-to-secondary/ /dns/zone-setups/conversions/convert-partial-to-secondary/ 301

src/content/changelogs/rules.yaml

@@ -37,7 +37,7 @@ entries:
   - publish_date: "2024-09-20"
     title: Automatic DNS Validation for Cloudflare Rules
     description: |-
-      The Cloudflare dashboard now automatically validates [DNS records](/dns/manage-dns-records/reference/proxied-dns-records/) and [Cloudflare for SaaS custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) for rules targeting specific hostnames or URLs. To prevent misconfigured rules and ensure smoother deployments, you will get proactive warnings for missing or misconfigured DNS records and custom hostnames.
+      The Cloudflare dashboard now automatically validates [DNS records](/dns/proxy-status/) and [Cloudflare for SaaS custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/) for rules targeting specific hostnames or URLs. To prevent misconfigured rules and ensure smoother deployments, you will get proactive warnings for missing or misconfigured DNS records and custom hostnames.
 
   - publish_date: "2024-09-17"
     title: Compression Rules available to all plans with Zstandard support

src/content/changelogs/trace.yaml

@@ -18,4 +18,4 @@ entries:
   - publish_date: "2024-03-12"
     title: Cloudflare Trace now supports grey-clouded hostnames
     description: |-
-      Even if the hostname is [not proxied by Cloudflare](/dns/manage-dns-records/reference/proxied-dns-records/#dns-only-records), Cloudflare Trace will now return all the configurations that Cloudflare would have applied to the request.
+      Even if the hostname is [not proxied by Cloudflare](/dns/proxy-status/#dns-only-records), Cloudflare Trace will now return all the configurations that Cloudflare would have applied to the request.

src/content/docs/byoip/service-bindings/magic-transit-with-cdn.mdx

@@ -123,7 +123,7 @@ You can periodically check the service binding status using the [List Service Bi
 
 ## 3. Create address maps
 
-Once you have configured your IPs to have CDN service, you can use <GlossaryTooltip term="address map" link="/byoip/address-maps/">address maps</GlossaryTooltip> to specify which IPs should be used by Cloudflare in DNS responses when a record is <GlossaryTooltip term="proxy status" link="/dns/manage-dns-records/reference/proxied-dns-records/#proxied-records">proxied</GlossaryTooltip>.
+Once you have configured your IPs to have CDN service, you can use <GlossaryTooltip term="address map" link="/byoip/address-maps/">address maps</GlossaryTooltip> to specify which IPs should be used by Cloudflare in DNS responses when a record is <GlossaryTooltip term="proxy status" link="/dns/proxy-status/">proxied</GlossaryTooltip>.
 
 You can choose between two different scopes:
 

src/content/docs/cache/concepts/default-cache-behavior.mdx

@@ -59,7 +59,7 @@ Cloudflare’s CDN provides several cache customization options:
 
 <FeatureTable id="network.max_upload_size" />
 
-If you require a larger upload, group requests smaller than the upload thresholds or upload the full resource through an [unproxied (grey-clouded) DNS record](/dns/manage-dns-records/reference/proxied-dns-records/).
+If you require a larger upload, group requests smaller than the upload thresholds or upload the full resource through an [unproxied (grey-clouded) DNS record](/dns/proxy-status/).
 
 ### Cacheable size limits
 

src/content/docs/cache/get-started.mdx

@@ -22,7 +22,7 @@ Cloudflare caches static content based on the following factors:
 * Origin headers that indicate <GlossaryTooltip term="dynamic content">dynamic content</GlossaryTooltip>
 * Cache rules that bypass cache on cookie
 
-Cloudflare only caches resources within the Cloudflare data center that serve the request. Cloudflare does not cache off-site or third-party resources, such as Facebook or Flickr, or content hosted on [unproxied (grey-clouded)](/dns/manage-dns-records/reference/proxied-dns-records/) DNS records.
+Cloudflare only caches resources within the Cloudflare data center that serve the request. Cloudflare does not cache off-site or third-party resources, such as Facebook or Flickr, or content hosted on [unproxied (grey-clouded)](/dns/proxy-status/) DNS records.
 
 ## Learn the basics
 

src/content/docs/cache/how-to/cache-rules/index.mdx

@@ -11,7 +11,7 @@ Cache Rules can be created in the [dashboard](/cache/how-to/cache-rules/create-d
 
 :::note[Notes]
 
-Cache Rules require that you [proxy the DNS records](/dns/manage-dns-records/reference/proxied-dns-records/) of your domain (or subdomain) through Cloudflare.
+Cache Rules require that you [proxy the DNS records](/dns/proxy-status/) of your domain (or subdomain) through Cloudflare.
 
 Rules can be versioned. Refer to the [Version Management](/version-management/) documentation for more information.
 

src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx

@@ -11,7 +11,7 @@ Cache-tag purging makes multi-file purging easier because you can instantly bulk
 ## General workflow for cache-tags
 
 1. Add tags to the `Cache-Tag` HTTP response header from your origin web server for your web content, such as pages, static assets, etc.
-2. [Ensure your web traffic is proxied](/dns/manage-dns-records/reference/proxied-dns-records/) through Cloudflare.
+2. [Ensure your web traffic is proxied](/dns/proxy-status/) through Cloudflare.
 3. Cloudflare associates the tags in the `Cache-Tag` HTTP header with the content being cached.
 4. Use specific cache-tags to instantly purge your Cloudflare CDN cache of all content containing that cache-tag from your dashboard or [using our API](/api/resources/cache/methods/purge/).
 5. Cloudflare forces a [cache MISS](/cache/concepts/cache-responses/#miss) on content with the purged cache-tag.

src/content/docs/calls/turn/custom-domains.mdx

@@ -32,7 +32,7 @@ Any DNS provider, including Cloudflare DNS can be used to set up a CNAME for cus
 :::note
 
 
-If Cloudflare's authoritative DNS service is used, the record must be set to [DNS-only or "grey cloud" mode](/dns/manage-dns-records/reference/proxied-dns-records/#dns-only-records).\`
+If Cloudflare's authoritative DNS service is used, the record must be set to [DNS-only or "grey cloud" mode](/dns/proxy-status/#dns-only-records).\`
 
 
 :::

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works.mdx

@@ -20,7 +20,7 @@ To give the SaaS provider permission to route traffic through their zone, any cu
 
 ## With O2O
 
-If you have your own Cloudflare zone (`example.com`) and your zone contains a [proxied DNS record](/dns/manage-dns-records/reference/proxied-dns-records/) matching the custom hostname (`mystore.example.com`) with a **CNAME** target defined by the SaaS Provider, then O2O will be enabled.
+If you have your own Cloudflare zone (`example.com`) and your zone contains a [proxied DNS record](/dns/proxy-status/) matching the custom hostname (`mystore.example.com`) with a **CNAME** target defined by the SaaS Provider, then O2O will be enabled.
 
 <Example>
 

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/bigcommerce.mdx

@@ -35,7 +35,7 @@ To enable O2O on your account, [create](/dns/manage-dns-records/how-to/create-dn
 
 For more details about a BigCommerce setup, refer to their [support guide](https://support.bigcommerce.com/s/article/Cloudflare-for-Performance-and-Security?language=en_US#orange-to-orange).
 
-If you cannot activate your domain using [proxied DNS records](/dns/manage-dns-records/reference/proxied-dns-records/), reach out to your account team.
+If you cannot activate your domain using [proxied DNS records](/dns/proxy-status/), reach out to your account team.
 
 
 :::

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/shopify.mdx

@@ -35,7 +35,7 @@ To enable O2O on your account, [create](/dns/manage-dns-records/how-to/create-dn
 
 For questions about Shopify setup, refer to their [support guide](https://help.shopify.com/en/manual/domains/add-a-domain/connecting-domains/connect-domain-manual).
 
-If you cannot activate your domain using [proxied DNS records](/dns/manage-dns-records/reference/proxied-dns-records/), reach out to your account team or the [Cloudflare Community](https://community.cloudflare.com).
+If you cannot activate your domain using [proxied DNS records](/dns/proxy-status/), reach out to your account team or the [Cloudflare Community](https://community.cloudflare.com).
 
 
 :::

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/wpengine.mdx

@@ -35,7 +35,7 @@ To enable O2O for a specific hostname within a Cloudflare zone, [create](/dns/ma
 
 For questions about WP Engine setup, refer to their [support guide](https://wpengine.com/support/wordpress-best-practice-configuring-dns-for-wp-engine/#Point_DNS_Using_CNAME_Flattening).
 
-If you cannot activate your domain using [proxied DNS records](/dns/manage-dns-records/reference/proxied-dns-records/), reach out to your account team.
+If you cannot activate your domain using [proxied DNS records](/dns/proxy-status/), reach out to your account team.
 
 
 :::

src/content/docs/cloudflare-one/policies/gateway/egress-policies/dedicated-egress-ips.mdx

@@ -112,9 +112,9 @@ Regardless of egress location, the IP geolocation will match the assigned dedica
 
 To physically egress from a specific location, traffic must be proxied to Cloudflare via IPv4. The end user connects to the nearest Cloudflare data center, but Cloudflare will internally route their traffic to egress from the dedicated location configured in your [egress policies](/cloudflare-one/policies/gateway/egress-policies/). Therefore, the connected data center shown in the user's WARP client preferences may not match their actual egress location.
 
-We are able to offer better IPv4 performance when users visit domains proxied by Cloudflare (also known as an [orange-clouded](/dns/manage-dns-records/reference/proxied-dns-records/#proxied-records) domain). In this scenario, IPv4 traffic will physically egress from the most performant data center in our network while still appearing to egress from your dedicated location.
+We are able to offer better IPv4 performance when users visit domains proxied by Cloudflare (also known as an [orange-clouded](/dns/proxy-status/) domain). In this scenario, IPv4 traffic will physically egress from the most performant data center in our network while still appearing to egress from your dedicated location.
 
-For example, assume you have a primary dedicated egress IP in Los Angeles and a secondary dedicated egress IP in New York. A user in Las Vegas would see Las Vegas as their connected data center. If they go to a site not proxied by Cloudflare ([gray-clouded](/dns/manage-dns-records/reference/proxied-dns-records/#dns-only-records)), such as `espn.com`, they will egress from Los Angeles (or whichever city is in the matching egress policy). If they go to an orange-clouded site such as `cloudflare.com`, they will physically egress from Las Vegas but use Los Angeles as their IP geolocation.
+For example, assume you have a primary dedicated egress IP in Los Angeles and a secondary dedicated egress IP in New York. A user in Las Vegas would see Las Vegas as their connected data center. If they go to a site not proxied by Cloudflare ([gray-clouded](/dns/proxy-status/#dns-only-records)), such as `espn.com`, they will egress from Los Angeles (or whichever city is in the matching egress policy). If they go to an orange-clouded site such as `cloudflare.com`, they will physically egress from Las Vegas but use Los Angeles as their IP geolocation.
 
 #### IPv6
 

src/content/docs/data-localization/how-to/cache.mdx

@@ -11,7 +11,7 @@ In the following sections, we will give you some details about how to configure
 
 ## Regional Services
 
-To configure Regional Services for hostnames [proxied](/dns/manage-dns-records/reference/proxied-dns-records/) through Cloudflare and ensure that [eligible assets](/cache/concepts/default-cache-behavior/) are cached only in-region, follow these steps for the dashboard or API configuration:
+To configure Regional Services for hostnames [proxied](/dns/proxy-status/) through Cloudflare and ensure that [eligible assets](/cache/concepts/default-cache-behavior/) are cached only in-region, follow these steps for the dashboard or API configuration:
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 

src/content/docs/data-localization/how-to/cloudflare-for-saas.mdx

@@ -11,7 +11,7 @@ In the following sections, we will give you some details about how to configure
 
 ## Regional Services
 
-To configure Regional Services for both hostnames [proxied](/dns/manage-dns-records/reference/proxied-dns-records/) through Cloudflare and the fallback origin, follow these steps for the dashboard or API configuration:
+To configure Regional Services for both hostnames [proxied](/dns/proxy-status/) through Cloudflare and the fallback origin, follow these steps for the dashboard or API configuration:
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 

src/content/docs/data-localization/how-to/durable-objects.mdx

@@ -10,7 +10,7 @@ In the following sections, we will give you some details about how to configure
 
 ## Regional Services
 
-To configure Regional Services for hostnames [proxied](/dns/manage-dns-records/reference/proxied-dns-records/) through Cloudflare and ensure that processing of a Durable Object (DO) occurs only in-region, follow these steps:
+To configure Regional Services for hostnames [proxied](/dns/proxy-status/) through Cloudflare and ensure that processing of a Durable Object (DO) occurs only in-region, follow these steps:
 
 1. Follow the steps in the Durable Objects [Get Started](/durable-objects/get-started/) guide.
 2. [Restrict Durable Objects to a jurisdiction](/durable-objects/reference/data-location/#restrict-durable-objects-to-a-jurisdiction), in order to control where the DO itself runs and persists data, by creating a jurisidictional subnamespace in your Worker’s code.

src/content/docs/data-localization/how-to/load-balancing.mdx

@@ -11,9 +11,9 @@ In the following sections, we will give you some details about how to configure
 
 ## Regional Services
 
-You can load balance traffic at different levels of the networking stack depending on the [proxy mode](/load-balancing/understand-basics/proxy-modes/): Layer 7 (`HTTP/S`) and Layer 4 (`TCP`) are supported; however, `DNS-only` is not supported, as it is not [proxied](/dns/manage-dns-records/reference/proxied-dns-records/).
+You can load balance traffic at different levels of the networking stack depending on the [proxy mode](/load-balancing/understand-basics/proxy-modes/): Layer 7 (`HTTP/S`) and Layer 4 (`TCP`) are supported; however, `DNS-only` is not supported, as it is not [proxied](/dns/proxy-status/).
 
-To configure Regional Services for hostnames [proxied](/dns/manage-dns-records/reference/proxied-dns-records/) through Cloudflare and ensure that the Load Balancer is available only in-region, follow these steps for the dashboard or API configuration:
+To configure Regional Services for hostnames [proxied](/dns/proxy-status/) through Cloudflare and ensure that the Load Balancer is available only in-region, follow these steps for the dashboard or API configuration:
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 

src/content/docs/data-localization/how-to/pages.mdx

@@ -11,7 +11,7 @@ In the following sections, we will give you some details about how to configure
 
 ## Regional Services
 
-To configure Regional Services for hostnames [proxied](/dns/manage-dns-records/reference/proxied-dns-records/) through Cloudflare and ensure that processing of a Pages project occurs only in-region, follow these steps for the dashboard or API configuration:
+To configure Regional Services for hostnames [proxied](/dns/proxy-status/) through Cloudflare and ensure that processing of a Pages project occurs only in-region, follow these steps for the dashboard or API configuration:
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 

src/content/docs/data-localization/how-to/r2.mdx

@@ -12,7 +12,7 @@ In the following sections, we will give you some details about how to configure
 
 ## Regional Services
 
-To configure Regional Services for hostnames [proxied](/dns/manage-dns-records/reference/proxied-dns-records/) through Cloudflare and ensure that processing of requesting objects from a [R2 Bucket](/r2/buckets/) occurs only in-region, follow these steps:
+To configure Regional Services for hostnames [proxied](/dns/proxy-status/) through Cloudflare and ensure that processing of requesting objects from a [R2 Bucket](/r2/buckets/) occurs only in-region, follow these steps:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select an account.
 2. Go to the **R2** tab.

src/content/docs/data-localization/how-to/workers.mdx

@@ -10,7 +10,7 @@ In the following sections, we will give you some details about how to configure
 
 ## Regional Services
 
-To configure Regional Services for hostnames [proxied](/dns/manage-dns-records/reference/proxied-dns-records/) through Cloudflare and ensure that processing of a Workers project occurs only in-region, follow these steps:
+To configure Regional Services for hostnames [proxied](/dns/proxy-status/) through Cloudflare and ensure that processing of a Workers project occurs only in-region, follow these steps:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select an account.
 2. Go to the **Workers & Pages** tab.

src/content/docs/dns/additional-options/dns-zone-defaults.mdx

@@ -32,6 +32,6 @@ For primary zones:
 
 For secondary zones:
 
-- [Secondary DNS override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/): Enable the options to use Cloudflare [proxy](/dns/manage-dns-records/reference/proxied-dns-records/) and add `CNAME` records at your zone apex.
+- [Secondary DNS override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/): Enable the options to use Cloudflare [proxy](/dns/proxy-status/) and add `CNAME` records at your zone apex.
 
   Multi-provider DNS does not apply as a setting for secondary zones, as this is already a required behavior for this setup. `SOA` record and the `NS` record TTL are defined on your external DNS provider and only transferred into Cloudflare.

src/content/docs/dns/additional-options/index.mdx

@@ -2,7 +2,7 @@
 pcx_content_type: navigation
 title: Additional options
 sidebar:
-  order: 8
+  order: 12
   group:
     hideIndex: true
 ---

src/content/docs/dns/cname-flattening/index.mdx

@@ -2,7 +2,7 @@
 pcx_content_type: concept
 title: CNAME flattening
 sidebar:
-  order: 7
+  order: 9
   label: About
 ---
 

src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx

@@ -25,7 +25,7 @@ CNAME flattening occurs by default for all plans when your domain uses a CNAME r
 
 ## For all CNAME records
 
-For zones on paid plans, you can choose to flatten all CNAME records. This option is useful for <GlossaryTooltip term="proxy status">DNS-only (unproxied)</GlossaryTooltip> CNAME records. [Proxied records](/dns/manage-dns-records/reference/proxied-dns-records/#proxied-records) are flattened by default as they return Cloudflare anycast IPs.
+For zones on paid plans, you can choose to flatten all CNAME records. This option is useful for <GlossaryTooltip term="proxy status">DNS-only (unproxied)</GlossaryTooltip> CNAME records. [Proxied records](/dns/proxy-status/) are flattened by default as they return Cloudflare anycast IPs.
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 

src/content/docs/dns/dns-firewall/index.mdx

@@ -2,7 +2,7 @@
 pcx_content_type: overview
 title: DNS Firewall
 sidebar:
-  order: 10
+  order: 15
 
 ---
 

src/content/docs/dns/dnssec/index.mdx

@@ -2,7 +2,7 @@
 pcx_content_type: how-to
 title: DNSSEC
 sidebar:
-  order: 6
+  order: 8
 
 ---