TRUST & SECURITY

Verify the source before you trust the request.

Use the official domain, current distribution state and a clear evidence checklist before you trust a Web4 file or request.

Official-domain checkNo public installerReport evidence checklist
A verification gateway separates rejected credential requests from a clear report
Verify identity → Reject unsafe request → Verify distribution → Capture details → Report
VERIFY THE WEB ADDRESS

Verify the web address.

Before trusting a Web4 file, message or request, check the address in your browser.

WEB4 BROWSER ADDRESShttps://web4browser.io/

Read the full address before trusting a file, message or request.

UNSAFE REQUESTS

Do not send credentials through a message channel.

This matrix defines a request boundary. It does not mean every message through these channels is fraudulent.

CredentialEmailTelegramSocial media
PasswordDO NOT SENDDO NOT SENDDO NOT SEND
One-time codeDO NOT SENDDO NOT SENDDO NOT SEND
Payment credentialsDO NOT SENDDO NOT SENDDO NOT SEND

Email

Password — DO NOT SEND

One-time code — DO NOT SEND

Payment credentials — DO NOT SEND

Telegram

Password — DO NOT SEND

One-time code — DO NOT SEND

Payment credentials — DO NOT SEND

Social media

Password — DO NOT SEND

One-time code — DO NOT SEND

Payment credentials — DO NOT SEND

DOWNLOAD AND TRIAL STATUS

Check the current access status before you trust a file.

No public installer currently offered. Test builds, if provided, use a controlled support process and include version/integrity information.

FREE ACCOUNTAvailable
WINDOWS TRIALApproval required
PUBLIC INSTALLERNot yet officially open
SECURITY BOUNDARIES

Understand where responsibilities begin and end.

01

Official Web4 information

Use the information Web4 publishes to check the web address, access status and report route.

02

Organization security practices

Credential handling, internal access and operating decisions remain with the organization using Web4.

03

Third-party websites and services

Third-party websites and services make independent decisions outside Web4 control.

No external outcome guarantee.

WHAT TO INCLUDE

What to include

Do not include passwords, one-time codes, payment credentials or unnecessary secrets.

  1. 01Affected URL
  2. 02Time
  3. 03Screenshot
  4. 04Relevant technical details
REPORT A SECURITY CONCERN

Report a security concern

[email protected]

Describe what you observed and attach only the information needed to inspect it.

NEXT LAYER

See how claims are connected to evidence and boundaries.

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.