Back to BlackFox
Security & transparency

Clear protection.
Verifiable status.

BlackFox describes protections according to what the released client actually does. No inflated labels, no hidden roadmap claims and no suggestion that a VPN replaces every layer of security.

Current validation baselineBlackFox VPN 4.0 RC · Windows x64 private beta
01

Released protections

These controls are present in the Windows 4.0 release candidate. The installer remains a private, unsigned beta until organisation code signing is introduced.

Encrypted WireGuard tunnel

Protects traffic between the Windows device and the selected BlackFox server.

RELEASED AND VALIDATED

Kill switch

Blocks network traffic if the protected tunnel drops unexpectedly.

RELEASED AND VALIDATED

DNS leak protection

Keeps DNS requests on the protected path rather than allowing them to bypass the tunnel.

RELEASED AND VALIDATED

VPN server IP

Websites see the BlackFox server address instead of the device connection address.

RELEASED AND VALIDATED

Device and profile removal

Lets members retire a lost or unused device profile through the protected portal.

RELEASED AND VALIDATED
02 — Protection boundary

What a VPN protects.

BlackFox protects the network path between your device and the BlackFox server. This is particularly useful on public and shared networks, and it shields your connection address from websites.

  • Traffic carried through the encrypted tunnel
  • DNS requests while protection is active
  • Unprotected fallback after a tunnel failure
03 — Honest limitations

What it does not replace.

A VPN is one security layer. It cannot make a malicious website trustworthy, remove malware, secure weak account passwords or make activity anonymous when you sign in to an identifiable online account.

  • Keep operating systems and browsers updated
  • Use strong, unique passwords and multi-factor authentication
  • Treat unexpected links, files and login prompts with caution
04 — Responsible disclosure

Found a security issue?

Report suspected vulnerabilities privately. Include the affected component, steps to reproduce and any supporting evidence. Do not access other members’ data or disrupt the service while testing.

Send a private security report ↗