WEB4 ENVIRONMENT DIAGNOSTICS

Find the right check for the symptom you see

Start with what you can observe. Choose one focused diagnostic, then use its result to decide which browser, network, leak, request, or runtime setting to inspect next.

Start here A focused check shows one part of the current environment. Compare that result with your setup before you make any wider conclusion.

Run full check Choose an issue

5 symptom routes12 free toolsFocused interpretationOne-layer observation

Illustrative diagnostic router receiving identity, rendering, network and automation signals before returning one focused browser-environment observation. — Illustrative diagnostic router: four environment dimensions converge on one focused observation and the next setting to inspect.

QUICK PATHS

What are you troubleshooting?

Choose the symptom that best matches what you can observe now. Each route opens the smallest relevant check rather than changing the whole environment.

01Proxy will not connectTest the proxy connection and response time.Run Single Proxy Checker → 02Location or timezone mismatchCompare the observed route, region and timezone context.Run IP and Location Consistency → 03Possible real IP exposureReview WebRTC candidates against the current public route.Run WebRTC Leak Test → 04Automation is being detectedInspect automation indicators and runtime behavior.Run Bot Signal Detection → 05Profiles look too similarCompare sanitized reports for duplicated or conflicting signals.Run Profile Comparison →

FUNCTIONAL TOOL DIRECTORY

Move from symptoms to environment checks

Each destination explains the observed value, why it matters, where the check runs, and which layer to review next.

COMBINED OVERVIEWEnvironment Health CheckReview identity, rendering, network, leak and automation observations together.Run combined check →

CategoryToolWhat it measuresRuns where

IdentityBrowser Fingerprint DetailsBrowser, platform, screen, language, hardware and storage signals.Browser / on requestRun check → IdentityCanvas and WebGL StabilityRendering summaries and consistency across repeated runs.Browser / on requestRun check → AutomationBot Signal DetectionAutomation indicators and runtime behavior.Browser / on requestRun check → RequestsHTTP Header ConsistencyRequest headers and browser-exposed values.Request layerRun check → NetworkIP and Location ConsistencyPublic IP, route location, timezone and language context.Network observationRun check → NetworkSingle Proxy CheckerTemporary HTTP, HTTPS or SOCKS5 proxy connection and response time.Temporary serverRun check → LeaksWebRTC Leak TestWebRTC ICE candidates compared with the active public route.Browser / on requestRun check → LeaksDNS Leak TestDNS servers and potential resolver leaks.Temporary serverRun check → ReachabilityWebsite and Proxy CheckerTarget-site access, redirects, TLS, latency and optional proxy reachability.External targetRun check → TeamsProfile ComparisonTwo to ten sanitized reports for duplicated or conflicting signals.Imported reportRun check → PlanningProxy Traffic CalculatorEstimated bandwidth by account, session, page count and resource type.Browser / on requestRun check →

READ A RESULT

Use one check to decide what to inspect next

A result is a focused observation, not a verdict on the whole environment or an external website.

01Start with the symptomUse the issue you can see to choose a relevant route.
02Choose the checkOpen one focused tool, or the combined check when several symptoms overlap.
03Compare what it showsRead the observed value alongside the setup you expected.
04Decide what to inspect nextReview the related setting, then run the same focused check again if needed.

Each result describes one measured part of the current environment.

WHAT YOU CONFIGURED

What you configured

Your profile settings, saved configuration and chosen paths.

≠

WHAT THE TOOL SEES NOW

What the tool sees now

The real-time signals and behavior produced by the current environment.

≠

WHAT THE WEBSITE DECIDES

What the website decides

A third party makes its own decision using its own systems and policy.

A tool result does not determine or guarantee a third-party decision.

PRIVACY & PREPARATION

Know what the check needs before you start

Runs in your browser

Local checks start only when you request them. Results are shown in the current session; share only what is necessary.

Uses a temporary server

Temporary server checks use a short-lived connection and do not retain proxy credentials or complete diagnostic reports.

Uses a report you upload

Profile Comparison uses 2–10 sanitized reports. Remove personal identifiers and session data before upload.

NEXT STEP

Continue with the page that explains your next setting

Use a related product page for a deeper explanation, or return to the combined check when several symptoms are involved.

ENVIRONMENT HEALTH CHECKReview several checks togetherRun a combined review across key layers →Browser identity and rendering →Proxy and network settings →Headless and runtime checks →More Web4 help and resources →

BUILD YOUR FIRST ENVIRONMENT

Start with one persistent, isolated browser profile.

Create a free account, then apply for Windows trial access when you are ready to test Web4 Browser. Trial access is by approval.

Apply for Free Trial Create Free AccountTrial access by approval.