To access analytics for your DNS Firewall, use the Cloudflare API.
Alternatively, set up Logpush to deliver DNS Firewall logs to a storage service, SIEM, or log management provider.
When analyzing why Cloudflare DNS Firewall responded in one way or another to a specific query, consider the
responseReason log field.
The following table provides a description for each of the values that might be returned as a response reason:
|Response was successfully served, either from Cloudflare cache or forwarded from the upstream.
|Response could not be fetched from the upstream due to the upstream failing to respond.
|Response could not be fetched from the upstream due to the upstream responding with
|Query is invalid and cannot be processed.
|Query of type
ANY was blocked according to your DNS Firewall settings (
|Query was rate limited according to your DNS Firewall settings.
|Response for Chaos class was successfully served.
|Query was blocked as part of random prefix attack mitigation.
|There was an unknown error.