On November 18, 2026, the Level Access Platform will move to a new domain and use new Internet Protocol (IP) addresses. This article explains what you need to update and what to check after the change.
A separate network security update affects manual testing traffic. Review Group A if your organization allowlists Level Access manual testing traffic.
In this article:
- What is changing?
- Why is Level Access making this change?
- What stays the same?
- Will the old address still work?
- Which group am I in?
- What do I need to do?
- Timeline
- Other common questions
What is changing?
On November 18, 2026, the Level Access Platform will move from essentia11y.com to levelaccess.net. The platform's IP addresses will change at the same time.
Separately, Level Access manual testing traffic will begin routing through a new set of Zscaler IP addresses. If your organization allowlists manual testing traffic, ask your network or security team to add the addresses in Group A: Network allowlists.
Why is Level Access making this change?
We're moving the platform to more modern infrastructure. This improves reliability and helps us deliver future updates more efficiently. It also retires the remaining legacy essentia11y.com addresses.
We're also routing manual testing traffic through Zscaler as part of a broader security improvement initiative. This helps strengthen data security when our testers access your environments.
What stays the same?
Your account, users, data, scan history, and settings won't change. You'll log in and use the platform the same way, at the new address.
Will the old address still work?
Most links to essentia11y.com will automatically redirect to levelaccess.net. However, redirects aren't enough for some configurations. These include network allowlists, Level Access software development kits (SDKs), and access to application programming interfaces (APIs) through Swagger.
Review the groups below to find out which updates your organization needs.
Which group am I in?
All customers need to update bookmarks and saved links. Other actions depend on how your organization uses the platform.
Answer the following questions to find the sections that apply to you. You may belong to more than one group.
- Does your organization restrict access to websites or allow scanning or manual testing only from approved IP addresses or domains? This includes restrictions through a firewall, proxy, virtual private network (VPN), or security allowlist. If yes, or if you're not sure, see Group A: Network allowlists.
- Does your team use a Level Access SDK to send test results to the platform? Examples include Java, JavaScript, Ruby, Android, and iOS SDKs. If yes, see Group B: Level Access SDKs.
- Do your users log in with single sign-on (SSO) through your organization's identity provider? If yes, see Group C: Single sign-on.
- Is the platform connected to Jira Server or Jira Data Center (on-premises)? If yes, see Group D: Jira integration.
- Does your team access Level Access APIs through Swagger? If yes, see Group E: API and Swagger users.
- Do you use scheduled monitoring scans or a UserWay integration? If yes, see Group F: Monitoring and UserWay.
If you answered no to every question, follow only the steps for all customers.
If you're unsure about a question, share this article with your network, security, or development team.
What do I need to do?
All customers
Action required: Update saved links and check your workflows after the change.
- Update bookmarks, saved links, and internal documentation from
essentia11y.comtolevelaccess.net. - After the change, log in and confirm that your usual workflows run as expected.
- When searching for your organization in the platform, enter your new organization web address. Searches using the old address won't return results.
Group A: Network allowlists
Action required: Update the allowlists that apply to your organization. Complete platform scanning updates before November 18, 2026. See the manual testing section below for the separate Zscaler update.
Important: If you don't update the relevant allowlists before the changes take effect, scans or manual testing of your internal assets may not work.
Ask your network or security team to add the applicable values to your firewall, proxy, VPN, or security allowlists. Automated platform scanning and manual testing use different IP addresses.
Automated platform scanning
If your organization allowlists platform traffic so automated scans can reach internal assets, add the following values before November 18, 2026.
New production IP addresses:
3.132.25.1203.15.90.10918.116.95.24
New domain: levelaccess.net
The following platform scanning IP addresses will be retired. You can remove them after the platform change is complete:
3.18.149.1213.139.228.22213.59.58.104
Manual testing
If your organization allowlists Level Access manual testing traffic, add the following Zscaler IP addresses. These allow our testers to access your internal applications or environments.
Deadline: [Confirm the deadline for Zscaler allowlist updates before publishing.]
159.254.220.195159.254.220.227159.254.100.139159.254.100.171
These addresses are separate from the automated scanning addresses above. They support manual testing access and replace the legacy VPN-based access model.
Important: Keep both old and new allowlist values in place until the relevant change is complete.
For the platform IP address reference, see What are the platform IP addresses?
Group B: Level Access SDKs
Action required: Update your SDK configuration before November 18, 2026.
SDKs don't reliably follow redirects from the old address. If your configuration still points to essentia11y.com after the change, test results won't reach the platform.
This applies to all Level Access SDKs, including:
- Java: Cucumber, Sauce Labs, and JUnit.
- JavaScript: Karma/Jasmine and Cypress.
- Ruby.
- Android.
- iOS.
- Update the platform web address in your SDK configuration to use
levelaccess.net. - Check any continuous integration and continuous delivery (CI/CD) pipelines, environment variables, or configuration files where the address is stored.
- After the change, run a test and confirm that the results appear in the platform.
Group C: Single sign-on
Action required: Confirm that SSO works after the change. Update saved login links if needed.
You don't need to change your SSO configuration. Level Access is updating the configuration on our side so users can keep logging in as usual.
- After the change, have one or more users log in through SSO to confirm that it works.
- If your identity provider or internal process has a saved
essentia11y.comlink, update it to uselevelaccess.net. Examples include an app tile or login link. - If anyone has trouble logging in, contact Level Access Support right away.
Group D: Jira integration
Action required: Check the connection after the change and reauthorize it if needed.
Connections to Jira Server or Jira Data Center (on-premises) may disconnect during the change.
- After the change, check that issues still sync between the platform and Jira.
- If the connection has stopped working, reauthorize it from the platform's Jira integration settings.
Group E: API and Swagger users
Action required: Update Swagger links after the change.
- Use the new
levelaccess.netaddresses to access APIs through Swagger. Swagger links using the old address will no longer work. - Postman requests will redirect to the new address automatically, but we recommend updating saved addresses.
Group F: Monitoring and UserWay
Action required: Review the following impacts. Take action if you encounter an issue.
- Monitoring scans: Scans scheduled during the change window, or running when it starts, may be delayed or missing. Results will return to normal after the change.
- UserWay: When you add a website in the UserWay Widget, you receive an email with a link to the UserWay dashboard. After the change, that link will still work. However, entering your old organization web address when logging in through Level Access will cause an error. Enter your new organization web address instead.
Timeline
When is the change happening?
- Now: Review this article, identify your groups, and share the information with your network, security, and development teams.
- Before November 18, 2026: Complete platform scanning allowlist updates and SDK configuration updates.
- By the manual testing deadline: Complete Zscaler allowlist updates. See Manual testing for the deadline.
- On November 18, 2026: The platform domain and IP addresses change.
- After the platform change: Log in, confirm your workflows, and reauthorize your Jira connection if needed.
Will there be downtime?
We're planning the change to keep disruption to a minimum. Scheduled monitoring scans that fall within the change window may be delayed. We'll share the exact window before the change.
[Confirm the change window's start time, end time, time zone, and expected downtime or availability impact before publishing.]
Other common questions
Do I need to create a new account or reset my password?
No. Your existing login will work at the new address.
Will my users get a separate notice?
This update goes to account contacts. Share it with everyone who uses the platform, especially your network, security, and development teams.
My email mentioned a network security update. What is that?
Some organizations are also affected by a separate Level Access network security update. If your email mentioned it, you can plan for both changes together.
Manual testing traffic is moving to new Zscaler IP addresses. If your organization allowlists this traffic, add the addresses in Group A: Manual testing by the deadline listed there.
What if something stops working after the change?
Contact Level Access Support right away if:
- You have trouble logging in.
- Scans aren't running.
- Test results aren't appearing in the platform.
- An integration has disconnected.
Tell us which groups in this article apply to your organization so we can help you more quickly.
Who do I contact with questions?
Reply to the email from your Customer Success Manager or contact Level Access Support.
Comments
0 comments
Article is closed for comments.