Website CDN Acceleration and Protection
A filing-free anti-DDoS CDN for corporate, ecommerce and cross-border sites: serve from the edge nearest your visitors while DDoS and CC attacks are absorbed before they reach your origin.
Get a website plan- 98%Static cache hit ratio
- 7T+DDoS mitigation capacity
- 65msAverage global latency
Four problems almost every site runs into
Most availability loss does not come from your application code, but from an unoptimised delivery path and an exposed attack surface.
Slow cross-border access
With a single-region origin, overseas visitors traverse long international paths. A three-to-five second first paint means paid traffic leaves before it sees anything.
Traffic spikes overwhelm the origin
Campaigns and viral shares multiply traffic within minutes. Origin bandwidth and database connections hit their limit, locking out legitimate users.
DDoS and CC attacks hit the origin directly
Once the origin IP is exposed, tens of Gbps of volumetric traffic or high-frequency CC requests can take the whole site offline.
Scrapers and vulnerability scanners
Content is harvested in bulk, endpoints are stuffed with credentials and admin paths are scanned continuously — driving up cost and risking a real breach.
Six core capabilities
Acceleration and security run on the same network, so there is no extra vendor to chain and no additional forwarding hop.
Delivery from the nearest edge
3,000+ nodes across six continents answer requests locally, so images, styles and scripts never travel back to the origin.
Intelligent caching
Rules by path, extension and query string lift static hit ratio to 98%, cutting origin bandwidth and load at the same time.
CN2 direct routes
CN2 GIA lines interconnected with the three major Chinese carriers stay congestion-free at peak, keeping mainland latency under 60ms.
Terabit-scale scrubbing
7T+ of mitigation capacity cleans traffic at the edge, so attack volume never lands on your origin.
Intelligent WAF and CC defence
An AI engine backed by an attack signature database blocks SQL injection, XSS and request floods, with custom rules to let genuine visitors through.
Origin shielding
Your real IP is no longer public. Fetches use an encrypted channel with allow-listing, closing off any route that bypasses the CDN.
Four steps to go live, no code changes
Onboarding is non-invasive: both cutover and rollback are a single DNS change.
Add your domain
Register the hostname to accelerate, pick regions and set the origin address.
Configure policies
Set cache rules, HTTPS certificates and protection levels, or start from an industry template.
Update DNS
Point the CNAME at your assigned endpoint; propagation typically completes within five minutes.
Observe and tune
Refine rules using real-time logs and hit-ratio reports, with full traceability for security events.
Typical results after onboarding
Ranges observed across website customers; actual results depend on site structure and traffic mix.
- 3×Faster first paint
- 60%Lower origin bandwidth cost
- 99.99%Service availability
- 5 minTime to cut over
Website acceleration and protection FAQ
No. Onboarding only requires a DNS change and usually takes effect within five minutes, after which attack traffic is scrubbed at the edge. When onboarding mid-attack we also recommend changing your origin IP and allow-listing our fetch nodes, so the attacker cannot keep hitting the exposed address directly.
It can be fixed, and no filing is needed. Slowness abroad usually comes from long international round trips; after onboarding, static assets are served from an edge node in the visitor’s own region and dynamic requests take an optimised path back to origin, typically bringing cross-border first paint from several seconds to under one second. Our nodes sit in Hong Kong, Japan and Singapore as a filing-free CDN edge, connecting back over CN2 so mainland visitors still get near-domestic speed.
It should not, and usually helps. A CDN changes neither your content nor your URL structure, so crawlers fetch the same HTML — while faster responses and higher availability are themselves ranking signals. Dedicated allow rules for search engine crawlers prevent protection policies from blocking them by mistake.
Yes. Dynamic requests are not cached, but they travel over our private backbone and CN2 routes, cutting network hops and handshake time. Admin paths are best configured as non-cacheable with an additional access control layer, balancing speed and security.
Three layers: change the origin IP at onboarding so the old one is useless; allow only our fetch ranges through the origin firewall; and enable fetch authentication so direct requests without a valid credential are rejected. Together these make the origin effectively unreachable from the public internet.
No — edge bandwidth scales elastically. We do recommend pre-warming campaign assets so the opening burst does not all hit the origin at once. A free 24-hour trial lets you validate the setup under real traffic first.
Still haven't found what you're looking for? Talk to our team.
Keep your site fast and online everywhere
Tell us where your visitors are and what is hurting today, and we will propose a caching and protection configuration to match.