Skip to main content

_Incapsula_Resource

Endpoint/Incapsula

Also known as /_Incapsula_Resource, Incapsula resource, SWUDNSAI

/_Incapsula_Resource is a URL path that Imperva Incapsula serves on the protected site's own domain. Its query parameter decides what it returns: a challenge script, the captcha block page shown in an iframe, or the endpoint that accepts a solved challenge.

How to recognize it

How to recognize it
URL pattern
/_Incapsula_Resource?... in a script src or iframe src on the site's own domain
Script
/_Incapsula_Resource?SWJIYLWA=... in a script src means the site runs the ___utmvc check
Query parameters
SWUDNSAI, incident_id and xinfo on the iframe URL
Response text
Request unsuccessful. Incapsula incident ID
Cookie
incap_sh_* after the captcha step has been completed

What the query parameter tells you

/_Incapsula_Resource is not one resource but one path with several jobs. Imperva's proxy answers it on the protected site's own domain, and the query parameter after it tells you which job you are looking at:

  • ?SWJIYLWA=... in a script tag: the challenge script behind the ___utmvc cookie. On a page that otherwise loads normally, it means the site lets you in but expects the cookie on later requests. The captcha block page can load it too.
  • ?SWKMTFSR=1&e=...: the submit path that activates a generated ___utmvc cookie.
  • ?SWUDNSAI=...&xinfo=...&incident_id=... as an iframe source: the captcha block page. Your request did not get the content.
  • ?SWCGHOEL=v2&dai=...: the endpoint the captcha page posts its solved token to. A successful post sets an incap_sh_* cookie.

So /_Incapsula_Resource in a script tag on a working page means "checked", while the same path in an iframe that fills an otherwise empty page means "blocked".

The "Request unsuccessful" page

When Incapsula blocks a request with a captcha, the response is a short HTML page with a robots NOINDEX, NOFOLLOW meta tag and a full-size iframe. The iframe points at /_Incapsula_Resource?SWUDNSAI=.... A client that does not render the iframe, such as a plain HTTP client, sees only the fallback text: Request unsuccessful. Incapsula incident ID: ...

  • The incident ID is the same value as the incident_id parameter in the iframe URL. It identifies this blocked request, which is useful when you compare attempts or report a block to the site owner.
  • The captcha inside the iframe is an hCaptcha or a GeeTest challenge. It needs a token from a captcha solver; the token is posted to the SWCGHOEL endpoint.
  • After a successful post, the response sets an incap_sh_* cookie (with a Max-Age of one hour in the example in the Hyper Solutions docs), and the original request can be retried.

Is _Incapsula_Resource malware?

No. It is served from the website you are visiting, by the Imperva proxy that sits in front of it. Browser developer tools, security extensions and antivirus logs show it on every site that uses Imperva Incapsula, which is why it regularly turns up in "is this a virus?" questions. It loads challenge scripts and pages for the site's own bot protection.

The cookies around it

  • visid_incap_* and incap_ses_* are Incapsula's visitor and session cookies. The incap_ses_* values are inputs when a ___utmvc cookie is generated.
  • ___utmvc is set by the SWJIYLWA script check described above.
  • reese84 is a separate check: a sensor script on a site-specific path that issues a reese84 token. The script and its sensor POST do not use /_Incapsula_Resource.
  • incap_sh_* appears after the captcha block has been solved.

Why request-based clients run into it

The captcha block is Incapsula's answer to a client it does not trust. For request-based scraping that usually means the client failed earlier checks: a handshake that does not match Chrome's TLS fingerprint, a header order no browser sends, a missing reese84 or ___utmvc, or an IP address with a poor reputation. Fixing those is cheaper than solving captchas.

The flow is documented step by step in the Incapsula captcha block docs. The Hyper Solutions Incapsula API generates the reese84 and ___utmvc payloads that keep a session out of the block page.

Questions

What is _Incapsula_Resource?

It is a URL path that Imperva Incapsula serves on a protected site's own domain. Depending on the query parameter, it returns a challenge script, the captcha block page shown in an iframe, the path that activates a ___utmvc cookie, or the endpoint that accepts a solved captcha token.

Is _Incapsula_Resource a virus or malware?

No. It is served by the website you are visiting, through the Imperva proxy in front of it, and loads that site's bot-protection scripts and pages. It shows up in browser and antivirus logs on every site that uses Imperva Incapsula.

What does 'Request unsuccessful. Incapsula incident ID' mean?

Incapsula blocked the request and served its captcha block page instead of the content. The incident ID identifies that blocked request; it matches the incident_id parameter in the iframe URL.

What is SWUDNSAI?

SWUDNSAI is the query parameter on the _Incapsula_Resource URL that loads Incapsula's captcha block page inside the iframe. If you see it, the request was blocked rather than just checked.

How is _Incapsula_Resource related to reese84 and ___utmvc?

The ___utmvc check runs through a script on _Incapsula_Resource (the SWJIYLWA parameter). reese84 is a separate Imperva check. Its sensor script and sensor POST use a site-specific path, not _Incapsula_Resource.

Further reading

Technical review: Hyper Solutions engineering, Nov 18, 2026