From 6cce0bf7fc1295a3d6ccbb194cd8220725c8a9d4 Mon Sep 17 00:00:00 2001 From: Andre Jesus Date: Thu, 27 Feb 2025 12:39:38 +0000 Subject: [PATCH] [Radar] Add DNS insights changelog and release note entry --- public/_redirects | 1 + .../radar/2025-02-27-radar-dns-insights.mdx | 32 ++++++++++ src/content/docs/radar/glossary.mdx | 10 ++-- .../{changelog.mdx => release-notes.mdx} | 4 +- src/content/release-notes/radar.yaml | 58 ++++++++++--------- 5 files changed, 70 insertions(+), 35 deletions(-) create mode 100644 src/content/changelog/radar/2025-02-27-radar-dns-insights.mdx rename src/content/docs/radar/{changelog.mdx => release-notes.mdx} (90%) diff --git a/public/_redirects b/public/_redirects index 07b10d48849d635..4f5604ddbced5f7 100644 --- a/public/_redirects +++ b/public/_redirects @@ -991,6 +991,7 @@ # radar /fundamentals/radar/ /radar/ 301 /fundamentals/radar/glossary/ /radar/glossary/ 301 +/radar/changelog/ /radar/release-notes/ 301 # railgun /railgun/user-guide/increase-logging/ /railgun/user-guide/troubleshooting/increase-logging/ 301 diff --git a/src/content/changelog/radar/2025-02-27-radar-dns-insights.mdx b/src/content/changelog/radar/2025-02-27-radar-dns-insights.mdx new file mode 100644 index 000000000000000..34ec12160e6493c --- /dev/null +++ b/src/content/changelog/radar/2025-02-27-radar-dns-insights.mdx @@ -0,0 +1,32 @@ +--- +title: DNS Insights in Cloudflare Radar +description: Expanded DNS insights with new API endpoints for 1.1.1.1 resolver aggregated traffic data +products: + - radar +date: 2025-02-27T15:00:00Z +--- + +[**Radar**](/radar/) has expanded its DNS insights, providing visibility into aggregated traffic and usage trends observed by our [1.1.1.1](/1.1.1.1/) DNS resolver. +In addition to global, location, and ASN traffic trends, we are also providing perspectives on protocol usage, query/response characteristics, and DNSSEC usage. + +Previously limited to the [`top`](/api/resources/radar/subresources/dns/subresources/top/) locations and ASes endpoints, we have now introduced the following endpoints: + +- [`timeseries`](/api/resources/radar/subresources/dns/subresources/timeseries/): Retrieves DNS query volume over time. +- [`summary`](/api/resources/radar/subresources/dns/subresources/summary/): Retrieves summaries of DNS query distribution across ten different dimensions. +- [`timeseries_group`](/api/resources/radar/subresources/dns/subresources/timeseries_groups/): Retrieves timeseries data for DNS query distribution across ten different dimensions. + +For the `summary` and `timeseries_groups` endpoints, the following dimensions are available, displaying the distribution of DNS queries based on: + +- `cache_hit`: Cache status (hit vs. miss). +- `dnsssec`: DNSSEC support status (secure, insecure, invalid or other). +- `dnsssec_aware`: DNSSEC client awareness (aware vs. not-aware). +- `dnsssec_e2e`: End-to-end security (secure vs. insecure). +- `ip_version`: IP version (IPv4 vs. IPv6). +- `matching_answer`: Matching answer status (match vs. no-match). +- `protocol`: Transport protocol (UDP, TLS, HTTPS or TCP). +- `query_type`: Query type (`A`, `AAAA`, `PTR`, etc.). +- `response_code`: Response code (`NOERROR`, `NXDOMAIN`, `REFUSED`, etc.). +- `response_ttl`: Response TTL. + + +Learn more about the new Radar DNS insights in our [blog post](https://blog.cloudflare.com/new-dns-section-on-cloudflare-radar/), and check out the [new Radar page](https://radar.cloudflare.com/dns). diff --git a/src/content/docs/radar/glossary.mdx b/src/content/docs/radar/glossary.mdx index 952fd1fe36288d7..57b143cdebea47d 100644 --- a/src/content/docs/radar/glossary.mdx +++ b/src/content/docs/radar/glossary.mdx @@ -50,7 +50,7 @@ Learn more about our route leak detection system design and usages in [How we d ## BGP origin hijacks -[BGP origin hijack](https://en.wikipedia.org/wiki/bgp_hijacking) is one type of BGP anomaly where networks falsely announce +[BGP origin hijack](https://www.cloudflare.com/learning/security/glossary/bgp-hijacking/) is one type of BGP anomaly where networks falsely announce ownership for groups of IP addresses (prefixes) that they do not own, control, or route to. A BGP origin hijack can redirect Internet traffic to the hijacker from its legitimate destination, causing data loss with potential leak of private/confidential information. @@ -90,7 +90,7 @@ Cloudflare Speed Test measures latency multiple times over the course of the tes ## Content categories -Cloudflare uses a variety of data sources to categorize domains. Using Cloudflare Radar, you can view the content categories associated with a given domain. Cloudflare customers using Cloudflare Gateway or [1.1.1.1 for Families](https://one.one.one.one/family/) can decide to block certain categories, like "Adult Content", in addition to security threats like malware and phishing. +Cloudflare uses a variety of data sources to categorize domains. Using Cloudflare Radar, you can view the content categories associated with a given domain. Cloudflare customers using Cloudflare Gateway or [1.1.1.1 for Families](/1.1.1.1/setup/#1111-for-families) can decide to block certain categories, like "Adult Content", in addition to security threats like malware and phishing. In some cases, a domain may be miscategorized. For example, a social media site might be categorized as "Shopping & Auctions". If you believe a domain is miscategorized, or a domain has not yet been categorized, please provide your suggested category using [this form](https://radar.cloudflare.com/domains/feedback) to bring it to our attention. @@ -99,11 +99,11 @@ In some cases, a domain may be miscategorized. For example, a social media site The [Domain Name System (DNS)](https://www.cloudflare.com/learning/dns/what-is-dns/) is a network service that is most commonly used to translate human-readable domain names into numerical IP addresses that computers can use to talk to each other. It is an essential Internet service, and is also used to look up other network-related information. -The data displayed on Radar for DNS is based on aggregated and anonymized DNS lookups to Cloudflare's [1.1.1.1](https://one.one.one.one/dns/) public resolver service. +The data displayed on Radar for DNS is based on aggregated and anonymized DNS lookups to Cloudflare's [1.1.1.1](/1.1.1.1/) public resolver service. ## Domain rankings -Domain Rankings is based on our anonymized and aggregated [1.1.1.1 resolver](https://one.one.one.one/dns/) data, complies with our [privacy policy](https://www.cloudflare.com/en-gb/privacypolicy/), and aims to identify the top most popular domains that reflect how people use the Internet globally. Domain Rankings’ popularity metric is best described as the estimated number of unique users that access a domain over some period of time. +Domain Rankings is based on our anonymized and aggregated [1.1.1.1 DNS resolver](/1.1.1.1/) data, complies with our [privacy policy](https://www.cloudflare.com/en-gb/privacypolicy/), and aims to identify the top most popular domains that reflect how people use the Internet globally. Domain Rankings’ popularity metric is best described as the estimated number of unique users that access a domain over some period of time. Trending domains are domains which are currently experiencing an increase in popularity. Domains Trending Today are domains spiking in popularity, reflecting increased interest potentially related to a particular event or a topic. Domains Trending This Week are domains that have steadily grown in popularity, reflecting an increase of their user base over the week. @@ -119,7 +119,7 @@ An early warning signal that an Internet outage may be underway on a given netwo ## Internet services ranking -Internet services ranking is based on our anonymized and aggregated [1.1.1.1 resolver](https://one.one.one.one/dns/) data, complies with our [privacy policy](https://www.cloudflare.com/en-gb/privacypolicy/), and aims to identify the top most popular Internet services that reflect how people use the Internet globally. A service represents one or more domains aggregated together. Ranking popularity metric is best described as the estimated number of unique users that access domains associated with a service, over some period of time. +Internet services ranking is based on our anonymized and aggregated [1.1.1.1 DNS resolver](/1.1.1.1/) data, complies with our [privacy policy](https://www.cloudflare.com/en-gb/privacypolicy/), and aims to identify the top most popular Internet services that reflect how people use the Internet globally. A service represents one or more domains aggregated together. Ranking popularity metric is best described as the estimated number of unique users that access domains associated with a service, over some period of time. ## Internet traffic trends diff --git a/src/content/docs/radar/changelog.mdx b/src/content/docs/radar/release-notes.mdx similarity index 90% rename from src/content/docs/radar/changelog.mdx rename to src/content/docs/radar/release-notes.mdx index 6b289e5b3fff8e4..fc4ea517989aa38 100644 --- a/src/content/docs/radar/changelog.mdx +++ b/src/content/docs/radar/release-notes.mdx @@ -1,6 +1,6 @@ --- -pcx_content_type: changelog -title: Changelog +pcx_content_type: release-notes +title: Release notes release_notes_file_name: - radar sidebar: diff --git a/src/content/release-notes/radar.yaml b/src/content/release-notes/radar.yaml index f3af11c45cd2367..ff11d0412b4a612 100644 --- a/src/content/release-notes/radar.yaml +++ b/src/content/release-notes/radar.yaml @@ -1,10 +1,14 @@ --- -link: "/radar/changelog/" +link: "/radar/release-notes/" productName: Radar productLink: "/radar/" productArea: Developer platform productAreaLink: /workers/platform/changelog/platform/ entries: + - publish_date: "2025-02-27" + title: Add DNS endpoints + description: |- + * Added [DNS endpoints](/api/resources/radar/subresources/dns/). - publish_date: "2025-02-04" title: Add Internet services ranking, robots.txt, and AI inference endpoints description: |- @@ -22,28 +26,28 @@ entries: title: Add more meta information's description: |- * Added meta.lastUpdated to all summaries and top endpoints (timeseries and timeseriesGroups already had this). - * Fix meta.dateRange to return date ranges for all requested series. + * Fixed meta.dateRange to return date ranges for all requested series. - publish_date: "2023-11-16" - title: Add new Layer 3 endpoints and Layer 7 dimensions + title: Add new layer 3 endpoints and layer 7 dimensions description: |- - * Added Layer 3 [top origin locations](/api/resources/radar/subresources/attacks/subresources/layer3/subresources/top/subresources/locations/methods/origin/) + * Added layer 3 [top origin locations](/api/resources/radar/subresources/attacks/subresources/layer3/subresources/top/subresources/locations/methods/origin/) and [top target location](/api/resources/radar/subresources/attacks/subresources/layer3/subresources/top/subresources/locations/methods/target/). - * Added Layer 7 Summaries by `http_method`, `http_version`, `ip_version`, `managed_rules`, `mitigation_product`. - * Added Layer 7 Timeseries Groups by `http_method`, `http_version`, `ip_version`, `managed_rules`, `mitigation_product`, `industry`, `vertical`. - * Added Layer 7 Top by `industry`, `vertical`. - * Deprecated Layer 7 timeseries groups without dimension. + * Added layer 7 Summaries by `http_method`, `http_version`, `ip_version`, `managed_rules`, `mitigation_product`. + * Added layer 7 Timeseries Groups by `http_method`, `http_version`, `ip_version`, `managed_rules`, `mitigation_product`, `industry`, `vertical`. + * Added layer 7 Top by `industry`, `vertical`. + * Deprecated layer 7 timeseries groups without dimension. * To continue getting this data, switch to the new [timeseries group by mitigation_product](/api/resources/radar/subresources/attacks/subresources/layer7/subresources/timeseries_groups/methods/mitigation_product/) endpoint. - * Deprecated Layer 7 summary without dimension. + * Deprecated layer 7 summary without dimension. * To continue getting this data, switch to the new [summary by mitigation_product](/api/resources/radar/subresources/attacks/subresources/layer7/subresources/summary/methods/mitigation_product/) endpoint. * Added new [Error codes](/radar/get-started/error-codes/). - publish_date: "2023-10-31" - title: Add new Layer 3 direction parameter + title: Add new layer 3 direction parameter description: |- - * Added a `direction` parameter to all Layer 3 endpoints. Use together with `location` parameter to filter by origin or + * Added a `direction` parameter to all layer 3 endpoints. Use together with `location` parameter to filter by origin or target location [timeseries groups](/api/resources/radar/subresources/attacks/subresources/layer3/subresources/timeseries_groups/methods/vector/). - publish_date: "2023-09-08" title: Add Connection Tampering endpoints @@ -56,35 +60,35 @@ entries: * Added Regional Internet Registry (see field `source` in response) to [get asn by id](/api/resources/radar/subresources/entities/subresources/asns/methods/get/) and [get asn by ip](/api/resources/radar/subresources/entities/subresources/asns/methods/ip/) endpoints. - * Stopped collecting data in the old Layer 3 data source. - * Updated Layer 3 + * Stopped collecting data in the old layer 3 data source. + * Updated layer 3 [timeseries](/api/resources/radar/subresources/attacks/subresources/layer3/methods/timeseries/) endpoint - to start using the new Layer 3 data source by default, fetching the old data source now requires sending the parameter + to start using the new layer 3 data source by default, fetching the old data source now requires sending the parameter `metric=bytes_old`. - * Deprecated Layer 3 summary endpoint, this will stop receiving data after 2023-08-14. + * Deprecated layer 3 summary endpoint, this will stop receiving data after 2023-08-14. * To continue getting this data, switch to the new [timeseries group protocol](/api/resources/radar/subresources/attacks/subresources/layer3/subresources/summary/methods/protocol/) endpoint. - * Deprecated Layer 3 timeseries groups endpoint, this will stop receiving data after 2023-08-14. + * Deprecated layer 3 timeseries groups endpoint, this will stop receiving data after 2023-08-14. * To continue getting this data, switch to the new [timeseries group protocol](/api/resources/radar/subresources/attacks/subresources/layer3/subresources/timeseries_groups/methods/protocol/) endpoint. - publish_date: "2023-07-31" - title: Fix HTTP timeseries endpoint urls + title: Fix HTTP timeseries endpoint URLs description: |- - * Updated HTTP `timeseries` endpoints urls - to `timeseries_groups` ([example](/api/resources/radar/subresources/http/subresources/timeseries_groups/methods/browser_family/)) + * Updated HTTP `timeseries` endpoints URLs + to [`timeseries_groups`](/api/resources/radar/subresources/http/subresources/timeseries_groups/) due to consistency. Old timeseries endpoints are still available, but will soon be removed. - publish_date: "2023-07-20" title: Add URL Scanner endpoints description: |- - * Added [urlscanner endpoints](/api/resources/url_scanner/). For more information, refer to [URL Scanner](/radar/investigate/url-scanner/). + * Added [URL Scanner endpoints](/api/resources/url_scanner/). For more information, refer to [URL Scanner](/radar/investigate/url-scanner/). - publish_date: "2023-06-20" - title: Add Quality endpoints + title: Add Internet quality endpoints description: |- - * Added [quality endpoints](/api/resources/radar/subresources/quality/). + * Added [Internet quality endpoints](/api/resources/radar/subresources/quality/). - publish_date: "2023-06-07" - title: Add BGP stats, pfx2as and moas endpoint + title: Add BGP stats, pfx2as and moas endpoints description: |- * Added BGP [stats](/api/resources/radar/subresources/bgp/subresources/routes/methods/stats/), [pfx2as](/api/resources/radar/subresources/bgp/subresources/routes/methods/pfx2as/) @@ -107,13 +111,11 @@ entries: - publish_date: "2023-01-11" title: Add new layer 3 dataset description: |- - * Added new Layer 3 data source and related endpoints. - * Updated Layer 3 + * Added new layer 3 data source and related endpoints. + * Updated layer 3 [timeseries](/api/resources/radar/subresources/attacks/subresources/layer3/methods/timeseries/) endpoint to support fetching both current and new data sources. For retro-compatibility reasons, fetching the new data source requires sending the parameter `metric=bytes` else the current data source will be returned. - * Deprecated old Layer 3 endpoints - [TimeseriesGroups](/api/resources/radar/subresources/attacks/subresources/layer3/subresources/timeseries_groups/methods/get/) and - [Summary](/api/resources/radar/subresources/attacks/subresources/layer3/subresources/summary/methods/get/). + * Deprecated old layer 3 endpoints timeseries_groups and summary. Users should upgrade to newer endpoints.