Guard RP 100
- Protected websites: 1
- L7 request rate: 5K req/sec
- Service uplink: 150Mbps
- Traffic: Unmetered
- Email relay: Protected
- Custom SSL: Optional
WC-GUARD & GUARD RP
Choose protected dedicated infrastructure or reverse-proxy website protection. Compare the protection scope, service uplink and deployment model that fit your service.
01 / THE SHORT ANSWER
DDoS mitigation filters hostile traffic so legitimate traffic can continue toward the protected service. WC-Guard pairs a dedicated server with a published protection tier. Guard RP provides reverse-proxy website protection. Choose the delivery model first, then compare the plan’s layers, protection capacity and service uplink.
02 / HOW DDoS MITIGATION WORKS
Incoming traffic reaches a filtering boundary. Mitigation distinguishes traffic patterns, rejects malicious flow and forwards accepted traffic toward the service.
The selected protection model and plan determine the supported scope. Filtering capability is not a promise that every attack or application behaves the same way.
Trace the permitted traffic path through mitigation to the protected service.
03 / CHOOSE YOUR PROTECTION MODEL
| Your decision | WC-Guard | Guard RP |
|---|---|---|
| Service model | DDoS-protected dedicated server | Reverse-proxy website protection |
| What you receive | Published CPU, memory and storage with a protection tier | Protection for the plan’s website count |
| Dedicated hardware | Included in the listed configuration | No hardware bundle is specified |
| Website count | Not specified by these dedicated plans | 1, 5 or unlimited, depending on plan |
| Layer scope | L3/L4 on WC-Guard 20; L3/L4/L7 on WC-Guard 50; volumetric/application protection on WC-Guard 1.2+ | L3/L4/L7 plan fields; some packet-rate values require confirmation |
| Deployment | 24-48 Hours, depending on stock | 3-6 hours |
| Custom SSL / email relay | No plan-level entitlement specified | Custom SSL optional; email relay protected |
04 / WC-GUARD PROTECTED DEDICATED SERVERS
Each configuration includes dedicated hardware and its published protection scope. Protection capacity is labelled separately from the service port. Each plan lists one IPv4 address.
* Stock dependent.
20Gbps Protection
L3 | L4
50Gbps Protection
L3 | L4 | L7
1.2+Tbps Protection
Volumetric & application-level
Monthly prices are published plan prices. Confirm stock and order arrangements. Traffic is listed as unmetered; the port is a separate connection limit.
05 / GUARD RP REVERSE PROXY
A separate reverse-proxy protection service, with no dedicated CPU, memory or storage bundle specified. Compare protected websites, layer metrics and the service uplink.
Custom SSL is optional; confirm certificate handling and any additional cost. Protected email relay does not establish a mailbox or mail-hosting package.
06 / UNDERSTANDING L3, L4 & L7
| Layer | Traffic becomes more specific | What the metric means |
|---|---|---|
| L3 · Network | Network-layer traffic; RP plans publish a bit-rate protection capacity. | |
| L4 · Transport | Transport traffic patterns; packet rate is distinct from bit rate. | |
| L7 · Application | Application requests; RP plans publish requests per second. |
These are conceptual layers, not three physical appliances. WC-Guard 20Gbps lists L3/L4; WC-Guard 50Gbps lists L3/L4/L7. The top dedicated tier specifies volumetric and application-level protection. Application filtering does not establish complete network mitigation.
07 / PROTECTION CAPACITY VS UPLINK
Protection capacity describes the published mitigation tier. Uplink describes the service connection available for legitimate traffic. The two numbers belong to different parts of the service.
WC-Guard example: 1.2+Tbps protection and a 1Gbps uplink. Guard RP example: 2 Tbps+ L3 protection and a 500Mbps uplink.
Compare mitigation capacity, service port speed and application capacity separately. Each can constrain delivery.
08 / ATTACK TYPES & WORKLOAD FIT
Compare the published protection capacity and the separate service uplink. Do not treat unmetered traffic as unlimited connection speed.
Check the selected plan’s layer scope. Packet-rate and bit-rate fields describe different limits.
Review application-level coverage and published request rates. Layer 7 is not listed on WC-Guard 20Gbps.
For Guard RP, compare website count, request rate and uplink together. Confirm your application and origin requirements.
Review the protocol and delivery workload against dedicated protection. Do not assume reverse-proxy eligibility for every media protocol.
Choose the delivery model and layer scope around the exposed service. Confirm deployment and service-control requirements.
09 / MONITORING, DEPLOYMENT & SERVICE CONTROL
10 / FAQ
It uses traffic mitigation to reduce the risk of malicious traffic overwhelming a protected service. WC-Guard and Guard RP provide two different delivery models.
WC-Guard includes a dedicated server configuration and its published protection tier. Guard RP is reverse-proxy website protection, with website counts and protection metrics specified by plan.
No. Protection capacity identifies the published mitigation tier. Uplink describes the separate service connection. A high protection figure does not increase the listed server or service port speed.
L3 concerns network-layer traffic, L4 concerns transport traffic patterns, and L7 concerns application requests. Bit rate, packet rate and request rate measure different aspects of protection.
WC-Guard 20Gbps publishes Layer 3 and Layer 4 protection. WC-Guard 50Gbps lists Layers 3, 4 and 7. WC-Guard 1.2+Tbps uses volumetric and application-level protection wording.
The published setup estimate is 24-48 Hours, depending on stock. Confirm the configuration and current availability before planning deployment.
The published reverse-proxy setup estimate is 3-6 hours. Confirm your website requirements and provisioning arrangements before scheduling the change.
Custom SSL is listed as optional on all three Guard RP plans. Confirm certificate handling, configuration and any additional cost before ordering.
Mitigation reduces risk from supported attack traffic. It does not create an absolute availability guarantee. Review the selected service scope and governing agreement.
Both families publish a one-month minimum and a no-refund condition. Review the family-specific listing and Service Agreement for the applicable policy and provisions.
YOUR NEXT CONFIGURATION
Start with the service you need to protect. Then compare the plan’s layers, mitigation capacity and service connection.
Talk to Our Team ↗