> For the complete documentation index, see [llms.txt](https://docs.link11.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.link11.com/product-guides/web-ddos/faq.md).

# FAQ

## **How to activate the Web DDoS Add-on Services?**

### **Zero Touch WAF**

Please follow the [Zero Touch WAF Setup](/product-guides/zero-touch-waf/setup.md) to activate the WAF Service.

### **Bot Management**

Please follow the [Bot Management Setup](/product-guides/bot-management/setup.md) to activate the Bot Management Service.

***

## **How to exchange SSL/TLS certificate?**

In order to change your TLS/SSL certificate, please follow these steps:

1. Verify the current certificate by noting the serial number.
2. Access the Web DDoS instances menu in the WebGUI and navigate to the TLS Settings tab.
3. Ensure that the TLS option is enabled and that TLS Passthrough is disabled.
4. Go to the TLS Certificate, Key & Chain section and confirm the serial number of the current certificate.

{% hint style="danger" %}
**Note:**

Please ensure that the certificate you upload is **complete** and in the **correct format**. The certificate should start with "-----BEGIN CERTIFICATE-----" and end with "-----END CERTIFICATE-----". This is important to ensure that the certificate is valid and can be properly applied to your DDoS protection service.
{% endhint %}

5\. Upload the new certificate, private key, and intermediate certificate in PEM format.

6\. Apply the changes by clicking the "Save settings" button.

Please note that this process may take a few minutes to complete, and once the new certificate is applied, you can confirm its validity by checking the serial number, which should match that of the new certificate.

***

## **Where are the attack reports?**

To access attack reports, please proceed to the [Attacks](/product-guides/web-ddos/interface/attacks.md) list. Set the appropriate date, time, and time zone. All reports that fall within the selected time period and match the attack type will then be displayed. This will give you a clear view of the type of attacks that have been launched, the level of protection provided, and the attack metrics.

***

## **How to set up alarming to receive attack notifications?**

To properly set up alarms, please refer to the alarm configuration documentation provided [here](/administration/account/interface/alarming.md). This  will guide you through the process of setting up alarms, as well as adding Alarming Rules. This will also provide information on how to customize the alarm settings to meet your specific needs.

***

## **How do I receive API access to my Web DDoS instances?**

To gain API access to your Web DDoS instances, please follow [this guide](/product-guides/web-ddos/interface/api-access.md). It will guide you through the process of setting up API access.

***

## **Why is an IP marked as the wrong country?**

The IP Geo databases are based on the Max Mind databases. These may not always be up to date. For further information, read [this](/product-guides/web-ddos/interface/geo-blocking.md).

You can check the MaxMind Database by following this link: [GeoIP2 Databases Demo | MaxMind](https://www.maxmind.com/en/geoip-demo)

***

## DDoS [HTTP Response List](/product-guides/web-ddos/interface/http-response-list.md) Questions <a href="#id-webddos-faq-ddoshttpresponselistquestions" id="id-webddos-faq-ddoshttpresponselistquestions"></a>

### **Will only the exact path be answered with the HTTP response code?**

If you only add exact paths in the URL, these will be blocked. If you add “/admin/” as a path, that path and everything that can be added behind it (for example: “/admin/files”) will be answered with the specified HTTP response.&#x20;

If you want to block only the “/admin” path, you will have to remove the “/” at the end.

### **Can regex or wildcards be used here?**

No, please follow the answer above.

### **How are query parameters handled?**

All queries are answered with the chosen HTTP responses.

### **How to see if HTTP responses are sent correctly?**

It can easily be checked by following the blocked path and checking if the Response Code page is played out.

<figure><img src="/files/VXIQYhAGtNUyQkE0te1r" alt=""><figcaption><p>Example for Error 400</p></figcaption></figure>

***

### **Can I configure Quaility-of-Service (QoS) protection?**

Within the WebDDoS and Bot Mitigation services, we offer options to choose the action to take when an IP should be blocked. These options are Block, Captcha, or Allow. Please note that these actions are global and cannot be configured per IP, IP Type, or IP range.

***

### **How is geographically distributed traffic handled?**

Link11 offers a reverse proxy based Web DDoS protection service. This service operates by providing the customer with a Link11 owned IP address to point their DNS to, and then inspecting the traffic that passes through the network. A request made by a client is directed to one of the Link11 reverse proxies; if the request is not blocked by Link11, it will be forwarded to the customer origin. The response from the origin will take the same path, and the same reverse proxy will respond to the original client.

***

### **How are new new threats and trends handled by Link11?**

Link11 is constantly improving our solutions. These improvements are focused on improving the security offered to our customers and the experience our customers have using our service. Zero Days, new attack vectors or anomalies identified in the wild are quickly incorporated into our solutions.&#x20;

Additionally, our DDoS mitigation model is designed to track normal traffic patterns. Many unknown attacks or new vectors are mitigated simply because the display traffic patterns are different from the norm.

***

### **How can I test which TLS ciphers are supported by the Link11 System?**

Please use this test service: [SSL Server Test (Powered by Qualys SSL Labs)](https://www.ssllabs.com/ssltest/index.html)

### **Are these TLS 1.2 Ciphers are supported?**

`TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`\
`TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`

Yes these ciphers are supported.
