Xingdun SCDN · secure acceleration

Speed and protection
should not be two purchases

Xingdun puts content delivery, WAF, CC and DDoS mitigation and bot analytics on the same edge nodes, and includes an OV certificate. Three tiers priced by traffic; onboarding is one CNAME, the origin stays untouched.

Report origin Pick a tier Add the CNAME Tune the rules

Five assumptions about CDNs

None of them is wrong exactly, each mistakes a part for the whole.

What people say

  • A CDN only makes pages faster
  • A WAF means no CDN needed
  • Content delivery needs origin changes
  • Small sites never need this
  • Certificates cost extra

Reality

  • WAF and CC defence sit at the edge; speed is a side effect
  • An origin WAF cannot absorb a flood, the edge can
  • One CNAME, no code and no certificate changes on the origin
  • 3TB for just over eight hundred a year; one crawl costs more
  • Every instance includes an OV cert with auto-renewal

Six things in a one-minute setup

No extra boxes, no code changes: configure these once at the edge.

Minute onboarding

No origin changes and no extra servers; one CNAME and it is live.

Edge WAF

Rule sets run on the nodes, so attack traffic never reaches the origin.

OV cert included

Each instance carries an OV certificate renewed across its lifecycle.

IPv6 dual stack

The origin stays as it is; the edge answers IPv6 on its behalf.

Flexible billing

Pay by traffic or by committed bandwidth, either model works.

Any cloud mix

Public, private or hybrid origin: no vendor change required.

Three tiers, priced by traffic

SMB series at ten percent below list; overage is billed on top of the quota, one domain included.

Feature
SMB · Basic 3TB, enough to start ¥810/yr (list 900)
Recommended SMB · Business 5TB, adds CC defence ¥1,710/yr (1,900)
SMB · Advanced 8TB, heavy traffic ¥3,510/yr (3,900)
Traffic quota 3TB 5TB 8TB
Price per year ¥810 ¥1,710 ¥3,510
List price per year ¥900 ¥1,900 ¥3,900
Domains included 1 1 1
Onboarding CNAME CNAME CNAME
Custom WAF rules 10 20 20
Cacheable file size 200MB 200MB 500MB
Uploaded certs 1 2 2
Dedicated certs Not supported 1 2
DDoS defence (L4) Not supported 5 Gbps 8 Gbps
CC defence Not supported Automatic Automatic
Bot & rate limiting Not supported Not supported Not supported

Bot detection, rate limiting, HTTP/2, WebSocket, log push and elastic DDoS are not available on any tier. Basic has no CC defence, so floods force an upgrade.

Four steps to go live

The origin can stay as it is; cache and defence rules are tuned once, then you watch traffic and alerts.

01

Report site and origin

Origin IP, current certificate, average traffic and historical peak.

02

Pick a tier

3TB if it is comfortable; go Business if the site has been flooded.

03

Add one CNAME

Point the record at the edge; the origin code and certificate stay.

04

Tune the defence rules

Cache policy, WAF rule set and certificate mounted in one pass.

Before you buy

What the three tiers leave out

Xingdun is good at combining delivery with baseline defence, but it is not universal. These decide the fit.

  • No bot detection or rate limiting; anti-crawl leans on WAF rules
  • Basic lacks CC defence; a flood forces an upgrade at once
  • One domain only; subdomains need a separate extension pack
  • No WebSocket or HTTP/2 optimisation; assess long connections
  • Metered by TB, overage billed; check quota before a campaign
Size my traffic

Size your traffic

Send the domain, where the origin sits, average traffic and peak. We will say whether 3TB is enough, whether you need CC defence, and the order of onboarding.

  • Estimating at average times 1.5 leaves sensible headroom; if you have run a campaign or been crawled, give us that peak instead of the average.
CAPTCHA image