Geotargeting

curl -x https://network.joinmassive.com:65535 \
     -U '{PROXY_USERNAME}-country-US-zipcode-10001:{API_KEY}' \
     https://cloudflare.com/cdn-cgi/trace

​

Country, subdivision, city, zipcode

​

Geotargeting rules

• country key must always persist if any of the geo parameters is specified. Otherwise, HTTP 400 is returned.
• If more than one geo key is specified, the server finds an appropriate node strictly matching all the parameters. The only exception is zipcode: if specified, city key is ignored.
  • Details:
    • If both subdivision and zipcode are provided, the city is ignored.
    • If both zipcode and city are provided, the city is ignored.
    • If subdivision and city are provided, both are strictly matched.

​

Zipcode Notes

• United States: 5
• Canada: 3
• United Kingdom: 2-4
• Brazil: 5
• Ireland: 3
• Japan: 7 (specified for the first 6. The last digit defaults to 1)
• Netherlands: 4
• Portugal: 7 (accurate for the first 4. The last 3 often default to -001)
• Singapore: 2

​

Examples

​

Country

curl -x https://network.joinmassive.com:65535 \
     -U '{PROXY_USERNAME}-country-US:{API_KEY}' \
     https://cloudflare.com/cdn-cgi/trace

​

Country and city

curl -x https://network.joinmassive.com:65535 \
     -U '{PROXY_USERNAME}-country-US-city-New%20York:{API_KEY}' \
     https://cloudflare.com/cdn-cgi/trace

​

Country and subdivision

curl -x https://network.joinmassive.com:65535 \
     -U '{PROXY_USERNAME}-country-US-subdivision-NY:{API_KEY}' \
     https://cloudflare.com/cdn-cgi/trace

​

Country and zipcode

curl -x https://network.joinmassive.com:65535 \
     -U '{PROXY_USERNAME}-country-US-zipcode-10001:{API_KEY}' \
     https://cloudflare.com/cdn-cgi/trace