Skip to main content

1. Bot Identification

Legitimate Nexus Inclusion scanning traffic identifies itself using the following User-Agent string:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36 Nexus-Inclusion-Bot (+https://www.nexusinclusion.com/)

How to use this identifier:

  • Match on the substring Nexus-Inclusion-Bot when validating traffic.
  • Use it to allowlist, log, or monitor Nexus Inclusion requests.
  • Traffic that does not contain this token is not from our scanner.

2. What the Scanner Does

The Nexus Inclusion Accessibility Scanner performs automated accessibility assessments against recognised accessibility standards and best practices.

Standards and guidance referenced

  • WCAG 2.0 AA
  • WCAG 2.1 AA
  • WCAG 2.2 AA
  • European Accessibility Act (EAA)
  • Americans with Disabilities Act of 1990 (ADA)
  • Section 508 of the Rehabilitation Act
  • Accessible Canada Act (ACA)
  • New Zealand Government Web Accessibility Standard 1.2
  • Disability Discrimination Act 1992 (DDA) (Australia)
  • Equality Act 2010 (UK)

Automated checks may include

  • Page structure validation
  • Heading hierarchy analysis
  • Alternative text verification
  • Form accessibility assessment
  • Keyboard navigation testing
  • Colour contrast evaluation
  • ARIA implementation review
  • Semantic HTML analysis
  • Accessibility metadata collection

3. What the Scanner Does Not Do

The scanner is designed solely for accessibility assessment. It does not perform:

  • Penetration testing
  • Vulnerability scanning
  • Security testing
  • Credential attacks
  • Denial-of-service testing
  • Exploit validation
  • Any attempt to gain unauthorised access

4. Infrastructure

  • The Nexus Inclusion platform operates on Amazon Web Services (AWS) infrastructure hosted within the European Union.
  • Scanner traffic may originate from AWS-hosted infrastructure and managed AWS IP ranges.
  • Source IP addresses may change over time due to the nature of cloud infrastructure, so User-Agent matching is more reliable than IP allowlisting.

5. Responsible Crawling

The scanner is designed to minimise impact on target systems. The service:

  • Uses controlled request rates
  • Limits concurrent requests
  • Implements retry and backoff mechanisms
  • Responds appropriately to rate-limiting responses
  • Avoids excessive requests to individual resources

6. Cloudflare Verification

For organisations using Cloudflare, Nexus Inclusion traffic can typically be identified using the following expression:

http.user_agent contains "Nexus-Inclusion-Bot"

Depending on your security requirements, this rule may be used to:

  • Bypass managed challenges
  • Skip bot protection checks
  • Exempt authorised assessments from accessibility testing restrictions

7. Report an Issue

If you believe Nexus Inclusion scanning activity is causing operational issues, please contact us and include:

  • Date and time of the activity
  • Source IP address
  • Requested URL
  • Relevant log entries

Our team will investigate and respond as quickly as possible.

8. Contact Us

Nexus Inclusion