Simpler, faster but less accurate way to check if a connection is behind a proxy
project_private_api_key
was used here since you may be firing the call from environments that do not pass the referer.
If your call is being fired from the browser and from the domain associated with your project, you can use the project_public_api_key
instead.
The <unique_rand_string>
should be replaced with a unique string. You can use a uuid or any other unique identifier that you can generate.
This is done so that the underlying platform of browser that you use does not cache the requests.
The session_id
should be unique per call/project in this case. You can use a uuid or any other unique identifier that you can generate.
The short
parameter tells the check engine that this is a short run, we are not expecting more data to flow and that we should perform the checks as fast as possible.
tka
field is the unique identifier of the check being performed. It is needed in the advanced section, should you want to pursue that route.
tka
value that we got from the first request.
<unique_rand_string>
should be replaced with a unique string. Yes, different from the one used in the first request and yes, different for each request.
Keep note of the <tka>
value being used in two places here. Since one of the tests we perform is a DNS leak test, we need the tka
in the subdomain as well.
If you omit it from the subdomain part, the DNS leak test will not be performed.
Since the unique_rand_string
and tka
are separated by an underscore, make sure that your generated unique_rand_string
does not contain any underscores.
unique_rand_string
be?