VoidFort puts a personal WAF in front of your site in 5 minutes. Your origin becomes unreachable. Start with a free audit.
NO_CARD_REQUIRED · PDF_TO_EMAIL · ZERO_FOOTPRINT
Three response layers. No vulnerabilities exposed. Origin never reached.
Simulation only, no real scanning. Your IP address goes to api.ipify.org when the page loads. The domain you type goes to Google Public DNS (dns.google) to look up its IP. Details
This is an illustration, not a recording of a node. Decoys, the labyrinth, behavioral analysis and bans shared between nodes are planned, not available. The tarpit holds IPs banned by CrowdSec and is switched on by support on request. Want a real report on your domain?
Real scan →Eight attack vectors. Each neutralized before your origin ever sees a packet.
Automated scanners map open ports and fingerprint your stack. The node exposes only ports 80 and 443. If the scanner's IP is banned by CrowdSec, the node can hold its connection for about 30 seconds without a single byte, then drop it. Support turns this on per site on request.
Botnets send waves of HTTP requests to exhaust your origin. The node applies per-IP rate limits and WAF rules and closes abusive connections. Volumetric L3/L4 floods are a different class: the datacenter network stops them (protected IP option, planned).
SQL injection, cross-site scripting, and path traversal target unpatched application logic. Every request passes through OWASP CRS, malicious payloads blocked at rule level before touching your app.
Automated floods test millions of username/password pairs from leaked databases. A per-IP limit (10 to 300 requests per 10 seconds) cuts off a fast brute force: the connection is dropped without a reply. Repeat offenders can be escalated to a CrowdSec ban. A slow spray from thousands of IPs stays under the per-IP limit.
Attackers probe DNS history, TLS certificates, and subdomain enumeration to find your real IP. Every query returns a Shield node address, your origin stays invisible.
Known vulnerabilities in CMS plugins, server software, and frameworks are weaponised within hours of disclosure. Signature-based blocking stops exploit payloads before they reach your stack.
Armies of bots rotate User-Agents and IPs to harvest your content. The node cuts off fast crawlers with a per-IP limit and blocks IPs known to CrowdSec. A browser check (redirect or JS proof of work) stops scrapers without a browser engine; headless browsers can pass it. Bots that spread requests over many IPs are harder to stop: TLS fingerprinting and behavioral analysis are planned.
Credential spray from many residential IPs (1 request per IP) does not hit a per-IP rate limit. The node does not stop it with the limit. Behavioral analysis and bans shared between nodes are planned.
Six independent layers. Each specialized. Together, they make you disappear.
Traffic runs through a VPS that belongs to you. Not shared infrastructure. Your origin IP stays out of DNS records, TLS certificates, and scan results. Anycast routing across multiple PoPs available on the Private CDN tier.
Thousands of inspection rules cover SQL injection, cross-site scripting, path traversal, and remote code execution. Blocked requests carry no Server header. A site can be set to drop the connection without any reply.
HTTP floods are filtered on the node: a per-IP request limit, WAF rules, cutoffs by IP, country, and path. A volumetric L3/L4 flood fills the link before packets reach any server, so only the datacenter network can stop it. A protected IP option for that is planned.
Server headers stripped. Framework signatures erased. Version banners removed. Responses look identical to generic traffic. No fingerprint, no targeted exploit chain.
Planned, not available yet: TLS handshake fingerprinting and pattern analysis for bots that spoof browser User-Agents or spread requests over many IPs. Today the node cuts fast bots off with a per-IP limit and CrowdSec bans, and can ask visitors for a browser check.
Planned, not available yet: a ban from one Shield node reaches the other nodes of the network. Today a ban applies on the node where it was issued.
Enter your domain. VoidFort spins up an isolated scanner, the audit arrives as a PDF within 15 minutes. The VPS self-destructs after delivery.
One click and VoidFort deploys your WAF node. Firewall, IDS, and rules are ready with no manual setup.
Update DNS. Your origin becomes invisible. Real-time attack telemetry activates. You're a ghost.
No. Cloudflare is shared infrastructure, your traffic runs alongside millions of other sites. VoidFort gives you a dedicated personal node. No shared rules. No traffic data mixing. No rate-limit contention.
Security headers, TLS, email security (SPF, DKIM, DMARC), subdomains, and whether your real server IP is exposed. The paid Deep Scan adds open ports, Nuclei templates (CVEs, exposed panels, misconfigurations) and hidden files.
No. Your existing server stays untouched. VoidFort Shield is a reverse proxy in front of it. You only update DNS.
Up to 15 minutes after domain verification. The PDF report is emailed when the scan ends.
Destroyed immediately after delivering your report. Zero footprint: no data retained on the scanning VPS.
Defense in the dark. No credit card. No footprint.
We use Google Analytics to count visits and see which pages are used. It sets cookies and sends data to Google. It loads only if you accept. Privacy policy
