Cloudflare IP ranges
Cloudflare uses 15 IPv4 blocks and 7 IPv6 blocks, covering about 1.5 million unique IPv4 addresses, announced from AS13335. IPDebrief has analysed 4,848 addresses in these ranges; 3 (0.1%) currently carry a higher risk score.
- IPv4 blocks
- 15
- IPv6 blocks
- 7
- Unique IPv4 addresses
- 1,524,736
- Analysed addresses
- 4,848
- Higher risk
- 0.1%
Range data updated 2026-11-07
About Cloudflare
Cloudflare operates a global network that provides CDN, DNS, DDoS protection and reverse-proxy services for millions of websites, plus the 1.1.1.1 public resolver and the WARP client. Cloudflare publishes the small set of large ranges its edge uses, and most traffic to sites behind Cloudflare arrives at the origin from these addresses.
What traffic from Cloudflare addresses usually means
Requests from Cloudflare ranges to your origin server are normally proxied visitor traffic; the visitor's real address is in the CF-Connecting-IP header. Outbound requests can also come from Cloudflare Workers and WARP users, so treat Cloudflare addresses as shared infrastructure rather than as the identity of a single user.
How to verify a Cloudflare IP address
To trust proxied traffic, allow only Cloudflare's published ranges to reach your origin and only then read the visitor address from the CF-Connecting-IP header; a header sent from any other address can be forged.
Largest Cloudflare IPv4 ranges
104.16.0.0/13172.64.0.0/13104.24.0.0/14162.158.0.0/15198.41.128.0/17108.162.192.0/18141.101.64.0/18173.245.48.0/20
Cloudflare networks (ASNs)
Recently analysed Cloudflare addresses
- 104.20.22.42
- 104.21.38.159
- 172.71.199.67
- 162.158.77.201
- 172.64.150.16
- 104.18.37.240
- 104.20.24.1
- 172.66.151.220
- 104.21.90.73
- 104.18.10.15
- 172.67.148.87
- 172.67.72.36
- 172.70.173.129
- 104.18.42.54
- 162.159.143.108
- 104.26.10.133
- 104.16.4.34
- 108.162.193.111
- 104.20.32.100
- 2606:4700:4700::1001
- 2606:4700:4700::1111
- 108.162.218.35
- 162.159.143.159
- 104.17.74.206
- 104.21.13.28
- 104.18.28.7
- 104.18.20.164
- 104.22.99.96
- 162.158.157.235
- 108.162.236.197
- 104.26.6.148
- 172.71.199.37
- 104.22.196.139
- 104.22.108.112
- 172.70.173.39
- 162.158.61.105
- 104.23.252.16
- 104.18.29.211
- 104.20.38.66
- 104.21.63.180
- 172.70.109.241
- 104.22.196.66
- 172.71.191.131
- 172.64.151.229
- 104.16.144.212
- 104.16.145.212
- 172.66.0.165
- 162.158.61.61
- 104.21.22.218
- 162.159.134.234
- 104.21.38.143
- 104.26.0.226
- 104.26.1.226
- 104.17.243.40
- 104.21.55.91
- 104.16.5.65
- 108.162.218.210
- 104.18.42.126
- 104.26.3.157
- 172.66.170.69
Frequently asked questions
How many IP addresses does Cloudflare have?
Cloudflare uses 15 IPv4 and 7 IPv6 address blocks. After merging overlapping ranges, the IPv4 blocks cover about 1.5 million unique addresses. Counts change as the provider adds, retires or transfers address space.
How can I check if an IP address belongs to Cloudflare?
Enter the address in the IPDebrief IP lookup. If it falls inside one of Cloudflare's ranges, the profile names the provider alongside the announcing network, location and risk signals. To trust proxied traffic, allow only Cloudflare's published ranges to reach your origin and only then read the visitor address from the CF-Connecting-IP header; a header sent from any other address can be forged.
Which ASN does Cloudflare use?
Cloudflare announces its address space from AS13335. An autonomous system number identifies the network that routes the addresses on the internet; each ASN page lists the analysed addresses observed in that network.
Is traffic from Cloudflare IP addresses safe?
Requests from Cloudflare ranges to your origin server are normally proxied visitor traffic; the visitor's real address is in the CF-Connecting-IP header. Outbound requests can also come from Cloudflare Workers and WARP users, so treat Cloudflare addresses as shared infrastructure rather than as the identity of a single user. Of the 4,848 Cloudflare addresses IPDebrief has analysed, 3 (0.1%) currently score as higher risk, so judge each address on its own profile.
Where does this IP range data come from?
Ranges are compiled from address lists the operator publishes and from global routing data, refreshed regularly. Address-level risk comes from independent observations of each address, recomputed in the background.