Your service runs on a Hong Kong server that already sits behind scrubbing. Simple, but you migrate onto it.
Traffic hits a protected IP first, gets scrubbed, and clean traffic is forwarded to your origin. You keep your current server and hide its real IP.
Protection is priced by defense capacity. Tell us the largest attack you have seen and whether it was volumetric or CC, so you do not pay for capacity you will not use.
Protection fails if attackers know the origin IP. Change the origin IP when you move behind protection and do not expose it in DNS history or mail headers.
| Option | Migration needed | Best for |
|---|---|---|
| Hong Kong high-defense server | Yes | New deployments, or when the current host cannot handle attacks |
| High-defense IP in front of your origin | No | Keeping an existing server, TCP/UDP services, games |
| Web protection with CDN | No | Websites and APIs facing CC or layer-7 floods |
Mainland high-defense nodes need an ICP filing. Hong Kong does not, and it still has short routes to mainland users.
How much defense capacity do I need?It depends on the attacks you actually face. Tell us the largest one and we size to that, rather than selling the biggest package.
I'm under attack now. How fast can this be set up?Mark the request as urgent and message us on Telegram. Urgent requests are handled first; timing depends on the option and the vendor.
How do I get a price?Fill the form below or message us on Telegram with your service type and attack history.