Request logs

How to view, filter, and export individual request logs. The end of this article contains a list of log parameters and their descriptions.

What Request logs are

Request logs show detailed information about every request to your resource.

You can see the complete request context: who sent it (a bot or a person), the IP address and ASN it came from, the country it came from, what and how it requested, the action protection applied and why, and the client’s remaining fingerprints.

Request log example

Why use Request logs?

The tool helps you:

  • find a particular request by IP address, path, or another parameter;

  • understand why protection passed, blocked, or sent a request for a challenge;

  • find sources of suspicious requests;

  • find out why a particular user could not open your resource;

  • collect data to configure protection more accurately.

Here are two examples of when Request logs can help. Click a heading to expand the text.

A user says that your website is unavailable

A user tried to open your website and received a 403 Forbidden error. They contact you and provide diagnostic data from the error page: the request ID, IP address, and time.

You open Request logs, filter records by Request ID, and see that the request was blocked by Geo restrictions: access from another country was blocked, and the request came from a foreign IP address. Later, you find out that the user had a VPN enabled.

You do not change the settings because protection worked correctly. Instead, you add a hint to the 403 page that recommends disabling the VPN. Users can now solve the problem faster and contact support less often.

Protect an endpoint from overload

You open Advanced analytics on the Top requests tab and notice many requests to the /search/advanced page. This page provides advanced search on your website. The feature is useful but resource-intensive, so more requests could overload the backend.

You decide to find out who accesses this page. You open Request logs and add the filter Path = /search/advanced. The logs show that both people and bots request the page actively. The bots appear to be parsing content.

To reduce the load, you add an enforcement rule for this page: block bots (Bot, Likely bot) and give all other requests a JS challenge. As a result, the extra load disappears, and real users can use search without issues.

How to use Request logs

1. Open Request logs.

Go to Application protection → Resources. Next to the required resource, click …​ and select Request logs. The request log opens; complete all further steps there.

2. Select a tab.

If you use the Module, Hybrid, or IP transit integration option, skip this step. You have one tab with protection’s request-analysis logs.

If you use the Proxy integration option, you see two tabs:

  • Policy-evaluated contains protection’s request-analysis logs.

  • All traffic contains origin-server response times and HTTP status codes.

Select the required tab. The table below provides more details.

Why are origin response logs unavailable for Module, Hybrid, and IP transit?

Strictera does not receive this data.

With the Proxy integration option, Strictera acts as a reverse proxy and can see your servers' responses and response times. With other integration options, the responses go directly to clients without passing through Strictera, so we do not receive the required information.

All traffic Policy-evaluated

Purpose

  • Find out how quickly protection and your servers processed a request.

  • Check which HTTP code your servers returned.

Find out how protection analyzed and filtered a request:

  • which class (bot, likely bot, likely human, or human) it assigned to the request source;

  • which action it applied to the request, for example pass or block;

  • which filtering setting it used to select the action.

What the logs include

All requests.

All requests except when:

  • the request was invalid;

  • the request was sent to a domain that does not belong to your resource;

  • the requested content was stored in our cache, and protection returned it without contacting the origin server.

Why are these requests not shown on this tab?

Protection does not analyze these requests with filtering policies. It makes a simpler decision:

  • return an error for an invalid request;

  • return an error for a request to the wrong domain;

  • return cached content for a request to content stored in the cache.

Request data available

  • Datetime

  • Source country

  • Source IP

  • Status

  • User agent

  • Method

  • HTTP path

  • HTTP host

  • HTTP referer

  • Scheme

  • Query parameters

  • HTTP version

  • Upstream status

  • Upstream IP address

  • Upstream port

  • Upstream response time

  • Request time

  • Request ID

  • Datetime

  • Source country

  • Source IP

  • Action

  • Reason

  • Source class

  • User agent

  • Bot score

  • Method

  • Path

  • Host

  • HTTP referer

  • Request ID

  • Session ID

  • Netname

  • Subnet

  • ASN

  • Label explanation

  • JA3

  • SP hash (loose)

  • SP hash (medium)

  • SP hash (strict)

  • Request type

Appearance

All traffic logs for Proxy
Policy-evaluated logs for Proxy

Chart: requests per minute

Available.

Available.

Log export

Unavailable.

Available. The system sends a CSV file to the email address in your account settings.

3. Configure filters.

Logs are stored for two weeks. You can show logs for any 24-hour period within those two weeks.

By default, all logs for the last 15 minutes are shown. Use the menu on the right to change the settings.

Configure filters

Change the time range. Click Last 15 minutes and select the required period.

Add filters. Click Add filter and specify which parameters the logs you want to view must match. If you add several filters, they use AND logic: you see only requests that meet all conditions at the same time.

Example: Add the filters Country—equals any of—CN and Path—contains any of—/login.php. The table then contains only requests from China with a path that contains /login.php.

Click the button below to read a description of each filter.

Filter list

The full list of filters is below. Depending on the tab you opened in step 2, the filters shown on screen may differ.

  • Request ID—a unique request ID assigned by the system.

  • Session ID—a unique ID of the session to which the request belongs.

  • User agent—the User-Agent header value, which contains information about the client device and application.

  • Source IP—the request source IP address.

  • Hostname—the hostname or domain to which the request was sent.

  • Referer—the Referer header value, or the URL from which the client came to your resource.

  • Source class—the request source class: bot, likely bot, human, or likely human.

  • Action—the action protection applied to the request, for example passing it to your resource or blocking it.

  • Reason—why protection applied the action.

  • Rule ID—the ID of the custom rule that was triggered.

  • Country—the two-letter code of the country from which the request came.

  • Netname—the name of the network that owns the source IP address.

  • ASN—the autonomous system number of the source’s provider.

  • Subnet—the source subnet in CIDR notation.

  • SP hash (loose)—a low-strictness client fingerprint hash. It considers only basic TLS characteristics, such as cipher suites. A matching hash means a similar TLS profile. Use it for an initial grouping of traffic by client families.

  • SP hash (medium)—a medium-strictness client fingerprint hash. It considers the TLS profile, connection parameters, and general HTTP fingerprint. A matching hash means a similar client and request construction method. Use it for more precise but still resilient traffic grouping.

  • SP hash (strict)—a strict client fingerprint hash. It considers the TLS profile, connection parameters, general HTTP fingerprint, and HTTP headers. A matching hash means an almost identical request. Noticeable header changes usually result in a new hash value. Use it to match particular scenarios and clients precisely, but it is more sensitive to variations.

  • JA3—the JA3 client TLS fingerprint hash.

  • Request type—the requested content type: static (static) or dynamic (script_ajax/script). A value containing _ajax means that the request was sent to an AJAX location.

  • Method—the HTTP request method.

  • Path—the HTTP request path.

  • Query params—request parameters passed in the URL after ?.

  • Bot score—a numeric estimate of how similar the request source is to a bot based on technical and behavioral characteristics. It is calculated for sources that pass a JS challenge. The value ranges from 0 to 1: the higher the value, the more bot characteristics the source has. For details, see bot score.

  • Scheme—the protocol used to send the request: HTTP or HTTPS.

  • Upstream status—the HTTP status returned by the origin server.

  • HTTP version—the HTTP protocol version used by the client.

  • Status—the HTTP status returned to the client.

  • Upstream IP address—the origin server IP address to which the request was sent.

  • Upstream port—the origin server port to which the request was sent.

  • Upstream response time—the time from when protection sends the request to the origin server until it receives the response.

  • Request time—the total request-processing time, from when protection receives the request until it sends a response to the client.

4. Expand logs.

The list of logs matching your filters opens.

Request list

Click > at the start of a row to expand all parameters for a particular request.

Parameters of a particular request

5. View charts.

Click the chart icon to see how the number of requests matching your filters changed over time. Each bar shows the number of requests in one minute.

Chart example

This helps you assess the load on the resource visually and select appropriate rate limits for custom rules.

6. Export logs.

Export is unavailable on the All traffic tab when you use the Proxy integration option.

Click the envelope icon. The system creates a CSV file with the filtered request logs and sends it to the email address in your account settings.

Export is useful when you need to send the logs to another specialist or continue the analysis in an external service.

Parameter descriptions

The full parameter list is below. Depending on the log tab you opened, the parameter set on screen may differ.

Parameter Description Examples or possible values

Datetime

The exact time when protection received the request.

2026-07-15T11:05:02.000Z

GEO (Country)

The source country identified from the IP address.

DE

IP (Source IP)

The IP address from which the request came.

203.0.113.42

Status

The HTTP status returned to the client.

403

User agent (UA)

The User-Agent header value containing information about the browser, application, or other client.

Mozilla/5.0 (Windows NT 10.0; Win64; x64) Chrome/126.0.0.0 Safari/537.36

Method

The HTTP request method.

GET

HTTP path (Path)

The HTTP request path.

/catalog/product

HTTP host

The hostname or IP address to which the request was sent.

example.com

HTTP referer

The Referer header value with the address of the page from which the request was sent.

https://example.com/catalog

Scheme

The protocol used to send the request.

https

Query parameters

Request parameters passed in the URL after ?.

page=2&sort=price

HTTP version

The HTTP protocol version used by the client.

HTTP/1.1

Upstream status

The HTTP status returned by the origin server.

200

Upstream IP address

The origin server IP address to which the request was sent.

192.0.2.10

Upstream port

The origin server port to which the request was sent.

443

Upstream response time

The time from when protection sends a request to the origin server until it receives a response.

0.128

Request time

The total request-processing time, from when protection receives a request until it sends a response to the client.

0.135

Request ID

A unique request ID assigned by the system.

rQ7mN2kL4xA1

Session ID

A unique ID of the session to which the request belongs.

sP4kN8dR2mQ7

Action

The action protection applied to the request.

Pass—passed.

Block—blocked.

CAPTCHA—the client received a CAPTCHA.

JS-challenge—the client received a JS challenge.

Cookie-challenge—the client received a cookie challenge.

Redirect—the client received a redirect.

Reason

Why protection applied the action.

There are 29 possible reasons:

Open the full list of reasons

mobile_app—traffic classified as traffic from a legitimate mobile application.

local_white—a request from an IP address that you added to the white list.

user_blocked_by_score—analysis of the user’s actions and characteristics identified the user as not legitimate. The user’s requests are blocked starting with this one.

local_whdr—a request with an allowed HTTP header. Requests with this header are passed without checks.

protection_disabled—protection is disabled. This applies both when protection is disabled for the specific location that received the request and when it is disabled for the whole resource.

white—a request from an officially verified bot that performs a useful task on the internet, such as a search engine crawler or uptime monitoring service. Protection continuously checks and updates the list of such bots. Their requests are passed without checks by default.

conn_blocked_by_hosting—the subnet has a poor reputation and often sends bot requests.

local_whdrl—a request with an allowed HTTP header with limited trust. Protection passes such requests without checks until their number exceeds the set limit, for example 2,000 requests per minute. The filtering policy configured for your resource checks all requests above the limit.

conn_blocked_by_no_cookie—the request had to contain a Strictera cookie but did not.

user_blocked—the request came from a blocked user. The decision to block the user was made during one of their previous requests.

check_force—according to the current security policy, this request requires an additional challenge.

captcha_pass—the user completed a CAPTCHA successfully recently and confirmed that they are legitimate.

captcha_set_cookie_redirect—the user has already completed a CAPTCHA successfully. Strictera is now setting a cookie that lets the user access your resource without challenges for some time.

behavior_pass—behavioral analysis identified the user as legitimate.

user_blocked_by_behavior—behavioral analysis detected anomalous activity. The user’s requests are blocked starting with this one.

custom_white_bot—we allowlisted this type of traffic at your request.

set_cookie_redirect—a cookie is being set as part of a cookie challenge.

local_bgeo—the request came from a country that you blocked in Geo restrictions.

captcha_invalid—the user did not complete the CAPTCHA correctly.

invalid_uid—protection detected changes to the cookie, so the traffic is suspicious.

white_corp—the request came from a subnet that we allowlisted at your request.

user_blocked_by_no_correct_cookie—the user sent a request without the required cookie, which indicates that the user is not legitimate. The user’s requests are blocked starting with this one.

ip_blocked_by_spec—a per-IP rate limit was exceeded.

ip_blocked—this IP address recently sent suspicious requests and is temporarily blocked. To find out why it was first blocked, open the logs of previous requests from this IP address.

invalid_method—the client used an HTTP request method that is incompatible with the location that received the request.

local_black—the request came from an IP address that you added to the black list.

cookie_disabled—the client cannot set the required cookie.

user_blocked_by_spec—the user exceeded one of the rate limits set by the protection policy for your resource. The user’s requests are blocked starting with this one.

user_blocked_by_rate—the user exceeded the system rate limit for dynamic content. The user’s requests are blocked starting with this one.

Source class

The class assigned to the client after request analysis.

Bot—bot.

Likely bot—most likely a bot.

Likely human—most likely a person.

Human—person.

Bot score

A numeric estimate of how similar the request source is to a bot based on technical and behavioral characteristics.

Calculated for sources that pass a JS challenge. The value ranges from 0 to 1 in increments of 0.1:

0—the source does not appear to be a bot;

0.1 to 0.9—the source has bot characteristics; the higher the value, the more characteristics it has;

1—the source is definitely identified as a bot.

For details, see bot score.

Subnet

The subnet to which the IP address that sent the request belongs.

192.168.1.0/24

ASN

The number and name of the autonomous system, or provider, that owns the request source IP address.

64496

Netname

The registered network name for the IP address range that contains the request source IP address.

Example City Telephone Network

Label explanation

The characteristics used by protection to determine the client’s source class.

incomplete matching of parameters: l3/l4 parameters is suspicious; ssl parameters is typical; headers parameters is typical;

JA3

The JA3 client TLS fingerprint hash.

1853fc69934911ef336d46bb3ae6114f

SP hash (loose)

A low-strictness client fingerprint hash. It considers only basic TLS characteristics, such as cipher suites. A matching hash means a similar TLS profile. Use it for an initial grouping of traffic by client families.

6580053349536791840

SP hash (medium)

A medium-strictness client fingerprint hash. It considers the TLS profile, connection parameters, and general HTTP fingerprint. A matching hash means a similar client and request construction method. Use it for more precise but still resilient traffic grouping.

2894249210178919151

SP hash (strict)

A strict client fingerprint hash. It considers the TLS profile, connection parameters, general HTTP fingerprint, and HTTP headers. A matching hash means an almost identical request. Noticeable header changes usually result in a new hash value. Use it to match particular scenarios and clients precisely, but it is more sensitive to variations.

2894249210178919183

Request type

The requested content type: static or dynamic.

script—a dynamic-content request sent to a non-AJAX location.

script_ajax—a dynamic-content request sent to an AJAX location.

static—a static-content request.