All integrationsUtilities

Cloudflare Trace

Trace a request through Cloudflare's network with its free, keyless trace endpoint: get the public IP address and country Lodol calls out from, the Cloudflare data center that answers, and the HTTP and TLS versions and time Cloudflare saw.

actions
4

Actions

Steps a workflow can run in Cloudflare Trace.

  • Run a traceTrace a request from Lodol to Cloudflare's network and get what Cloudflare saw: the public IP address it came from and that address's country, the Cloudflare data center that answered, the HTTP and TLS versions and key exchange used, and the time. Useful for finding the address to allow in a firewall. Choose IPv4, IPv6 or either. No API key required.
  • Check a site for CloudflareCheck whether a website is served through Cloudflare by asking it for Cloudflare's trace page, which only sites on Cloudflare have. Returns which data center answered, the Ray ID and Server header, and the trace itself when the site shows it. A site that refuses its trace is still recognised by Cloudflare's headers, and redirects are followed, so a domain that forwards to its www address is checked there. No API key required.
  • Get a data centerLook up one of Cloudflare's data centers by its three-letter code, such as the one a trace or a site check names, and get its city, country, region and current status from Cloudflare's status page. No API key required.
  • List data centersList Cloudflare's data centers, more than 300 around the world, with their city, country, region and current status from Cloudflare's status page, in order of city. Optionally only one region or country, those whose name contains some text, or only those operational or not. No API key required.

Automate Cloudflare Trace with Lodol.

Connect Cloudflare Trace, then hand Lodol the job in Slack, Claude or ChatGPT.

Free plan, no credit card