> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/api-documentation/api-reference/api--api-security/types/objects/cf-info.md).

# cfInfo

Cloudflare runtime enrichment data for an API endpoint.

### Examples

```graphql
type CfInfo {
  runtimeStatus: String
  requestCount: Float
  lastSeen: String
  matchType: String
  wafBlockCount: Float
  wafBotBlockCount: Float
  wafTopAttackerIps: [String]
  wafTopCountries: [String]
  wafAttackSources: [String]
  wafLastAttackAt: String
  zone: String
  host: String
  allMatchedZones: [String]
}
```

### Fields

| Field                        | Description                                                                                   | Supported fields |
| ---------------------------- | --------------------------------------------------------------------------------------------- | ---------------- |
| runtimeStatus `String`       | Cloudflare runtime status: ACTIVE, INACTIVE, ZOMBIE, SHADOW                                   |                  |
| requestCount `Float`         | Number of requests observed via Cloudflare in the last scan window                            |                  |
| lastSeen `String`            | ISO timestamp of the last request observed via Cloudflare                                     |                  |
| matchType `String`           | How the endpoint was matched against CF traffic: EXACT, NORMALIZED, or UNMATCHED              |                  |
| wafBlockCount `Float`        | Total number of WAF block events in the last 72 hours                                         |                  |
| wafBotBlockCount `Float`     | Number of WAF blocks attributed to bot management (source='bm') in the last 72 hours          |                  |
| wafTopAttackerIps `[String]` | Top attacker IPs by frequency (up to 5) from WAF events in the last 72 hours                  |                  |
| wafTopCountries `[String]`   | Top attacking countries by frequency (up to 3) from WAF events in the last 72 hours           |                  |
| wafAttackSources `[String]`  | WAF rule sources that triggered blocks (e.g. firewallrules, bm, ratelimit)                    |                  |
| wafLastAttackAt `String`     | ISO timestamp of the most recent WAF block event                                              |                  |
| zone `String`                | Cloudflare zone name where this endpoint was observed (e.g. "example.com")                    |                  |
| host `String`                | Host header from CF traffic where this endpoint was matched (e.g. "API.example.com")          |                  |
| allMatchedZones `[String]`   | All Cloudflare zone names that observed this endpoint — first entry is the primary match zone |                  |

### References

#### Fields with this object:

* [{} ApiSecurityItem.cfInfo](/api-documentation/api-reference/api--api-security/types/objects/api-security-item.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ox.security/api-documentation/api-reference/api--api-security/types/objects/cf-info.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.