When a domain is routing through Cloudflare, there may be times when we are looking to identify the Cloudflare data center, that is serving your request(s).
You can determine the Cloudflare data center serving requests for your browser by visiting – http://checkthedns.com/cdn-cgi/trace.
(Note: replace checkthedns.com with your domain)
Example output: (Note the colo field from the output.)
fl=557f101
h=checkthedns.com
ip=(your public IP address will appear here)
ts=(redacted)
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36
colo=DFW
sliver=010-dfw05
http=http/3
loc=US
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
rbi=off
kex=X25519In the example above, we can see that the value of colo is DFW, indicating that Cloudflare data center serving our requests, is located in Dallas/Fort Worth.
Note: Cloudflare’s globally distributed Anycast network automatically routes visitor requests to the nearest Cloudflare data center.
A map of Cloudflare data centers is listed on the Cloudflare status page, sorted by continent. The three-letter code in the data center name is the IATA code of the nearest major international airport.
Additional information:
Cloudflare is a large network of servers that can improve the security, performance, and reliability of anything connected to the Internet.
Cloudflare does this by serving as a reverse proxy for your web traffic. All requests to and from your origin flow through Cloudflare and — as these requests pass through the Cloudflare network — various rules and optimizations are applied.
When your traffic is proxied through Cloudflare before reaching your origin server, your application gets additional security, performance, and reliability benefits, right out of the box!