Anti-DDoS Protection
YorkHost uses several Anti-DDoS protection solutions to guarantee the availability of your services.
Our network solutions
Gcore
Enterprise-level Anti-DDoS protection for our network infrastructure.
| Feature | Detail |
|---|---|
| Filtering capacity | Several Tbps |
| Mitigation time | < 1 second |
| Protection | Layers 3, 4 and 7 |
Web Protection
Cloudflare
Our websites, panels and APIs are protected by Cloudflare.
Custom filtering
We are currently developing custom filtering capabilities in-house. This solution will be available on a case-by-case basis for certain clients with specific needs.
Planned features:
- Custom filtering rules
- Adaptation to specific attack patterns
- Dedicated configuration per client
Contact our sales team if you are interested.
Protection network rules
Following the change of our Anti-DDoS protection solution, network rules now apply to our game servers. These rules define the port ranges that can be used depending on the hosted game.
Port ranges per game
| Service | Port range |
|---|---|
| FiveM (game) | 30000 - 30200 |
| FiveM (txAdmin) | 40000 - 40200 |
| FiveM Enhanced | 25000 - 25999 |
| Minecraft | 26000 - 26999 |
| Garry's Mod | 27000 - 27999 |
| Other games | 25000 - 25999 |
FiveM Enhanced servers currently use the 25000 - 25999 range (other games), because dedicated FiveM filters do not exist yet for this version.
Your servers are automatically configured within the correct port range. If you configure a port manually, make sure it is within the range matching your game.
DNS (port 53)
Traffic to DNS servers (port 53) is blocked by default by our protection. Only allowed DNS resolvers are reachable — here is the list (non-exhaustive):
| Resolver | IP addresses |
|---|---|
| Cloudflare | 1.1.1.1, 1.0.0.1 |
| 8.8.8.8, 8.8.4.4 | |
| Quad9 | 149.112.112.112 |
| OpenDNS | 208.67.222.222, 208.67.220.220 |
| AdGuard | 94.140.14.14, 94.140.15.15 |
| Level3 | 4.2.2.1, 4.2.2.2 |
| Yandex | 77.88.8.1, 77.88.8.8 |
| Neustar | 156.154.70.1, 156.154.71.1 |
If you need to use a DNS server that is not on the list, contact our support: we can unblock it on our side.
How does it work?
Incoming traffic → Gcore → Filtering → Your server
↓
Malicious traffic blocked
- Detection: Traffic is analyzed in real-time
- Filtering: Malicious packets are identified and blocked
- Mitigation: Only legitimate traffic reaches your server
Impact on your services
During an attack
- Slight increase in latency possible
- Some ports may be temporarily restricted
- Automatic protection without intervention on your part
Under normal conditions
- No impact on performance
- All your service ports available (within the allowed ranges, see Network rules)
- Optimal latency
Need enhanced protection?
If you are regularly targeted by attacks or have specific needs, contact our support to discuss custom protection options.