We are very happy to announce the recent 4.9.0 release of The dashboard that contains several major features and improvements.

Two Factor Authentication
Two Factor Authentication adds an extra layer of protection to The dashboard's authentication process. If enabled, the user is asked to provide the second-factor code, in addition to the standard username & password authentication. Currently, we support mobile applications (like Google Authenticator) to provide the second-factor codes.

Industry Benchmark Graph
The industry benchmark graph is visible on the dashboard homepages of all unprotected accounts. The main benefit it brings is that it allows users to compare their bot traffic (the bad, commercial, and good bot ratios) to the "industry average" - the average ratios calculated based on DataDome accounts.

Enhanced endpoint management
Endpoints can now be managed (created and updated) via The dashboard's Management section.

Captcha stats filtered by endpoints
We have added filtering by endpoints to The dashboard's homepage. This addition allows our users to filter the homepage's data, including the captcha passed stats, by selected endpoints.

We are proud to release the new Fastly version which contains a few improvements.

Get more information in the Changelog Fastly

v1.10 (2019-12-05)

• Parse only valid and not-passing response from DataDome Backend.
• Reduce number of used objects inside request.

We are proud to release the new F5 iRule version which contains a few improvements.

Get more information in the Module F5 iRule

v1.2 (2019-10-31)

• Use streaming to inject JS tag.
• Introduce an easy way to log headers that is injecting by datadome, and log time that datadome used.

We are very happy to announce a new, 4.8.0 release of The dashboard that includes the following feature:

• the Rate Limiting Response

The Rate Limiting feature allows you to fine-tune the responses applied to the traffic reaching your endpoints based on the specified number of hits.

This Response allows you to define a volume threshold (by providing the number of hits) below which the traffic should be allowed, and select a captcha or block response to the traffic that exceeds the threshold.

The Rate Limiting feature can be applied to any chosen good and commercial bot traffic (AI rules) and to all Custom Rules. Read more

We are proud to release the new F5 iRule version which contains a few improvements.

Get more information in the Module F5 iRule

v1.1 (2019-10-09)

• Never try to apply datadome headers to not datadome call
• Collect response body only when DATADOME_js is defined
• Simplified timeout logic: now we use only one, global timeout instead timeout and wait parameters

We are proud to release the new Fastly version which contains a few improvements.

Get more information in the Changelog Fastly

v1.9 (2019-10-04)

• Force restart request in case of any unexpected errors from DataDome Backend.

We are proud to release the new Fastly version which contains a few improvements.

Get more information in the Changelog Fastly

v1.8 (2019-10-01)

• DNS based georouting was fixed, moved away from region specified backends.

We are proud to release the new Fastly version which contains a few improvements.

Get more information in the Changelog Fastly

v1.7 (2019-09-20)

• Performance improvement by moving restart logic into vcl_fetch.

We are very happy to announce a new, 4.7 release of The dashboard that includes the following feature:

• the Timeboxing Response

The Timeboxing feature allows you to fine-tune the responses applied to the traffic reaching your endpoints based on the specified time. With a few simple settings, you will be able to control when to allow and when to block the traffic matching a chosen Custom or AI rule.

The Timeboxing feature can be applied to any chosen good and commercial bot traffic (AI rules) and to all Custom Rules. Read more

We are proud to release the new Fastly version which contains a few improvements.

Get more information in the Changelog Fastly

v1.6 (2019-08-28)

• Performance improvement by using a Fastly regions for georouting
• Backends moved to VCL for easier configuration
• Switched our regex to req.url.ext instead of req.url.