PingOne

Verifying that custom domain traffic is routing to Cloudflare

There are several ways to confirm that your custom domain is routing traffic to Cloudflare after a migration.

  • Check the Custom Domain and Email Trust page:

    • In the PingOne admin console, go to Settings > Domains.

      If the Cloudflare Active label displays on the custom domain entry, traffic is routing to Cloudflare.

  • Check the ping-endpoint.json file for the "server": "v2" property:

    • From a terminal window, run the following command, where <customDomainHostname> is the hostname of your custom domain:

      > curl -H "Cache-Control: no-cache, no-store, must-revalidate" \
    -H "Pragma: no-cache" \
    -H "Expires: 0" \
    "https://<customDomainHostname>/.well-known/ping-endpoints.json"

      If traffic is routing to Cloudflare, the response will be similar to the following example, in which the "server": "v2" JSON property is included at the end of the response:

      {
  "uploadUrl":
  "https://uploads.pingone.com/environments/418ffffe-44aa-4072-8535-549a9fffbd0f",
  "apiUrl":
  "https://api.pingone.com/v1/environments/418ffffe-44aa-4072-8535-549a9fffbd0f",
  "authUrl": "https://<customDomainHostname>",
  "assetsUrl": "https://assets.pingone.com",
  "server": "v2"
}

  • Use the nslookup command:

    • In a terminal window, enter the following command:

      > nslookup <customDomainHostname>

      If the custom domain is routing to Cloudflare, the response contains several instances of *.ping-ccd.com and will look similar to the following example:

      Server:		127.0.0.1
Address:	127.0.0.1#53

Non-authoritative answer:
<customDomainHostname>	canonical name = 7e1b1a54-3402-40c0-acb2-882fca387e5b.edge1.pingone.com.
7e1b1a54-3402-40c0-acb2-882fca387e5b.edge1.pingone.com	canonical name = cloudflare.ping-ccd.com.
Name:	cloudflare.ping-ccd.com
Address: 220.120.117.32

      If your custom domain was created between March 17, 2025 and August 11, 2025, the name in the response will look something like <UUID>.ping.ccd.com.

      This example also assumes the organization resides in the North America (US) region. If your organization is in a different region, the end of the canonical name differs depending on that region:

      • North America (Canada): ping-ccd.ca

      • Europe: ping-ccd.eu

      • Australia: ping-ccd.com.au

      • Asia-Pacific: ping-ccd.asia

      • Singapore: ping-ccd.sg