Fastsoft / Guide
Practical guide
The page automatically reads public traces from Fastsoft and fixed Cloudflare-backed sites to compare exit IPs, edge colos, WARP, protocol and request times. You can run an optional Cloudflare speed test and inspect available third-party IP risk data.
How to use it
- Open the page and wait for the exit, colo, WARP and comparison table.
- Review this site’s server-validated Turnstile states for both modes; real site keys are required.
- Optionally run the speed test or reCAPTCHA v3 check, then inspect connection details and local colo history.
Example
If Fastsoft and 1.1.1.1 traces show NRT and HKG, those requests reached different colos. Compare the exit IP, protocol and your routing rules to investigate the path.
What to know
The page cannot read Cloudflare’s private Bot Management score or infer a Cloudflare plan from a domain. IPQuery risk is a third-party reference and is unknown when unavailable. Turnstile and reCAPTCHA require real public site keys and server secrets; test keys cannot assess risk. The speed test runs only after a click and can download up to 300 MB and upload 50 MB to Cloudflare’s edge.
Interpreting the results
- The trace colo, WARP, HTTP, TLS, SNI and key-exchange fields describe this browser request. IPv4/IPv6, proxies and destinations may change them.
- Each comparison row times one HTTP request, not an ICMP ping. It does not prove the destination uses a particular Cloudflare plan.
- Turnstile shows PASS only after this site’s backend validates the token with Cloudflare Siteverify. A pass here does not predict challenges elsewhere.
- Colo history stays in this browser. Observed IPs go to Fastsoft’s intelligence endpoint for IPQuery or basic IPinfo fallback and are not written to D1.
Common question
Why are CAPTCHA widgets unconfigured or the risk score unknown?
The site owner must configure the corresponding public site key and server secret. The IP intelligence source may time out or lack data; neither condition is treated as a pass or low risk.