GS Co-Browse Articles

How to start a co-browse session in the Agent Workspace

Start a co-browse session from a standard chat session so you can see and interact with the page a customer is viewing. BoldChat users refer to co-browse as ActiveAssist.

Important: You must be in an active chat and the customer must be on a page for which Customer monitoring HTML has been implemented.

Co-browse browser requirements:

  • Operator:
    • Windows ? Chrome, Firefox, Microsoft Edge
    • Mac ? Safari
  • Customer:
    • Windows ? Chrome, Firefox, Microsoft Edge
    • Windows ? Internet Explorer 9, 10, 11 (Operator unable to click links for customer)
    • Mac ? Safari (Operator unable to use back/forward buttons)
    • iOS ? Safari
    • Android ? Chrome

Privacy considerations: During a co-browse session, Operators can see the web content that the customer is watching. This content may contain personally identifiable and other sensitive information that your customer would not allow your Operators to see. To disable viewing parts of your website that contain sensitive information, you must update the HTML code of your website as described in Setting up your website for co-browse sessions.

  1. Activate a chat.
  2. Click the Co-browse icon.

    Result: The customer is prompted to allow co-browse.

  3. The customer must click Yes.

    Result: The co-browsing session begins.

    Tip: If the customer's page does not load in Bold360, ask them to refresh their browser page.
    Restriction:
    • Some page elements are known not to load properly, including inline SVG images, flash objects, iframes, and cross-domain http CSS formatting.
    • Depending on your website settings, you may not be able to interact with certain user interface elements, such as buttons, input fields, checkboxes and radio buttons. For more information on this limitation, see Setting up your website for co-browse sessions.
While co-browsing, you have the following options:
  • Back arrow ? Takes the customer's browser to the previously visited URL (like a standard browser Back button)
  • Forward arrow ? Takes the customer's browser to the next URL in the history of the visited URL
  • Reload ? Refreshes the current page being shown
  • URL and Bookmarks ? Enter a URL that opens in the customer's browser or select a predefined URL from your BoldChat bookmark library. This library is only available if you previously used the BoldChat Desktop Client to add bookmarks.
  • Highlighter ? Point out elements on the page, such as fields to fill, selections to make, or header text to read
  • Stop ? Ends the current co-browse session, but chat remains active
For information on how to set up a website for co-browse sessions, see Setting up your website for co-browse sessions.

How to start a PIN-based co-browse session in the Agent Workspace

Start a co-browse session with a customer using a PIN code. BoldChat users refer to co-browse as ActiveAssist.

Important:
  • PIN-based remote access and co-browse do not work with AI-enabled chat windows. You must use a layered or pop-up window to control your customer's computer.
  • The customer must be on a page for which Customer monitoring HTML has been implemented.

Co-browse browser requirements:

  • Operator:
    • Windows ? Chrome, Firefox, Microsoft Edge
    • Mac ? Safari
  • Customer:
    • Windows ? Chrome, Firefox, Microsoft Edge
    • Windows ? Internet Explorer 9, 10, 11 (Operator unable to click links for customer)
    • Mac ? Safari (Operator unable to use back/forward buttons)
    • iOS ? Safari
    • Android ? Chrome

Privacy considerations: During a co-browse session, Operators can see the web content that the customer is watching. This content may contain personally identifiable and other sensitive information that your customer would not allow your Operators to see. To disable viewing parts of your website that contain sensitive information, you must update the HTML code of your website as described in Setting up your website for co-browse sessions.

  1. On the left side of the Bold360 workspace, next to Live Sessions, hover your mouse over + (the plus sign) and click Start Co-Browse with PIN.

    Result: A PIN is generated and displayed on your screen.

  2. Guide your customer through these steps:
    1. Ask them to open their browser and go to either pin.bold360.com or your organization's custom PIN entry page.
    2. Ask them to enter the PIN that you see on the screen.

    Result: The customer is prompted to allow co-browse.

  3. The customer must click Yes.

    Result: The co-browsing session begins.

    Tip: If the customer's page does not load in Bold360, ask them to refresh their browser page.
    Restriction: Some page elements are known not to load properly, including inline SVG images, flash objects, iframes, and cross-domain http CSS formatting.
While co-browsing, you have the following options:
  • Back arrow ? Takes the customer's browser to the previously visited URL (like a standard browser Back button)
  • Forward arrow ? Takes the customer's browser to the next URL in the history of the visited URL
  • Reload ? Refreshes the current page being shown
  • URL and Bookmarks ? Enter a URL that opens in the customer's browser or select a predefined URL from your Bold360 bookmark library
  • Highlighter ? Point out elements on the page, such as fields to fill, selections to make, or header text to read
  • Stop ? Ends the current co-browse session, but chat remains active
For information on how to set up a website for co-browse sessions, see Setting up your website for co-browse sessions.

How to start a co-browse session

Start a co-browse session from a standard chat session so you can see and interact with the page a customer is viewing.

Important: You must be in an active chat and the customer must be on a page for which Customer monitoring HTML has been implemented.

Co-browse browser requirements:

  • Agent:
    • Windows ? Chrome, Firefox, Microsoft Edge
    • Mac ? Safari
  • Customer:
    • Windows ? Chrome, Firefox, Microsoft Edge
    • Windows ? Internet Explorer 9, 10, 11 (agent unable to click links for customer)
    • Mac ? Safari (agent unable to use back/forward buttons)
    • iOS ? Safari
    • Android ? Chrome

Privacy considerations: During a co-browse session, agents can see the web content that the customer is watching. This content may contain personally identifiable and other sensitive information that your customer would not allow your agents to see. To disable viewing parts of your website that contain sensitive information, you must update the HTML code of your website as described in Setting up your website for co-browse sessions.

  1. Activate a chat.
  2. Click the Co-browse icon.

    Result: The customer is prompted to allow co-browse.

  3. The customer must click Yes.

    Result: The co-browsing session begins.

    Tip: If the customer's page does not load in Bold360, ask them to refresh their browser page.
    Restriction:
    • Some page elements are known not to load properly, including inline SVG images, flash objects, iframes, and cross-domain http CSS formatting.
    • Depending on your website settings, you may not be able to interact with certain user interface elements, such as buttons, input fields, checkboxes and radio buttons. For more information on this limitation, see Setting up your website for co-browse sessions.
While co-browsing, you have the following options:
  • Back arrow ? Takes the customer's browser to the previously visited URL (like a standard browser Back button)
  • Forward arrow ? Takes the customer's browser to the next URL in the history of the visited URL
  • Reload ? Refreshes the current page being shown
  • URL and Bookmarks ? Enter a URL that opens in the customer's browser or select a predefined URL from your BoldChat bookmark library. This library is only available if you previously used the BoldChat Desktop Client to add bookmarks.
  • Highlighter ? Point out elements on the page, such as fields to fill, selections to make, or header text to read
  • Stop ? Ends the current co-browse session, but chat remains active
For information on how to set up a website for co-browse sessions, see Setting up your website for co-browse sessions.

How to start a PIN-based co-browse session

Start a co-browse session with a customer using a PIN code.

Important:
  • PIN-based remote access and co-browse do not work with AI-enabled chat windows. You must use a layered or pop-up window to control your customer's computer.
  • The customer must be on a page for which Customer monitoring HTML has been implemented.

Co-browse browser requirements:

  • Agent:
    • Windows: Chrome, Firefox, Microsoft Edge
    • Mac: Safari
  • Customer:
    • Windows: Chrome, Firefox, Microsoft Edge
    • Windows: Internet Explorer 9, 10, 11 (agent unable to click links for customer)
    • Mac: Safari (agent unable to use back/forward buttons)
    • iOS: Safari
    • Android: Chrome

Privacy considerations: During a co-browse session, agents can see the web content that the customer is watching. This content may contain personally identifiable and other sensitive information that your customer would not allow your agents to see. To disable viewing parts of your website that contain sensitive information, you must update the HTML code of your website as described in Setting up your website for co-browse sessions.

  1. On the left side of the Agent Workspace, next to Live Sessions, hover your mouse over + (the plus sign) and click Start Co-Browse with PIN.

    Result: A PIN is generated and displayed on your screen.

  2. Guide your customer through these steps:
    1. Ask them to open their browser and go to either pin.bold360.com or your organization's custom PIN entry page.
    2. Ask them to enter the PIN that you see on the screen.

    Result: The customer is prompted to allow co-browse.

  3. The customer must click Yes.

    Result: The co-browsing session begins.

    Tip: If the customer's page does not load in the Agent Workspace, ask them to refresh their browser page.
    Restriction: Some page elements are known not to load properly, including inline SVG images, flash objects, iframes, and cross-domain http CSS formatting.
While co-browsing, you have the following options:
  • Back arrow: Takes the customer's browser to the previously visited URL (like a standard browser Back button)
  • Forward arrow: Takes the customer's browser to the next URL in the history of the visited URL
  • Reload: Refreshes the current page being shown
  • URL and Bookmarks: Enter a URL that opens in the customer's browser or select a predefined URL from your Digital DX bookmark library
  • Highlighter: Point out elements on the page, such as fields to fill, selections to make, or header text to read
  • Stop: Ends the current co-browse session, but chat remains active
For information on how to set up a website for co-browse sessions, see Setting up your website for co-browse sessions.

Set up your PIN entry page for remote control or co-browse

You can customize the Bold360 PIN invitation experience to match your company's branding and standards. An integrated PIN entry form behaves identical to pin.bold360.com, meaning your customers use it to contact an agent and enter the PIN that launches a remote access session.

Important: An agent can create a PIN based session even when they have reached their chat limits or have set their status to unavailable. PIN sessions go directly to remote control once the customer has granted permission and downloaded the applet.
Note: PIN-based remote access and co-browse do not work with AI-enabled chat windows. You must use a layered or pop-up window to control your customer's computer.
  1. In the Web Admin Center, go to Customers > PIN Invitation.

    Result: The PIN Invitation page is displayed.

  2. Select Enable PIN invitation.
  3. The following options allow you to customize your implementation of this feature.
    Option Description
    Website Associate the PIN invitation with a website.
    Chat Window Select the Chat Window you want customers to see upon connection.
    Timeout Set the length of validity for the PIN code.


    Figure 1. PIN timeout, as seen by agent
  4. Copy the generated HTML and send it to your web developer for implementation on your site.
  5. Save your changes.

Setting up your website for co-browse sessions

With co-browse, agents can view the exact web page a customer is seeing and provide assistance by highlighting items or filling out forms on a customer's behalf.

Once a customer has engaged in a live communication, agents with proper permission can initiate an co-browse session. The customer is prompted to grant permission to the agent. Once permission is granted, the co-browsing session begins.

Important: PIN-based remote access and co-browse do not work with AI-enabled chat windows. You must use a layered or pop-up window to control your customer's computer.
Requirements and permissions
Your website pages must use Customer Monitoring HTML.
Co-browse can be used on both secure and non-secure pages with customers using a recent version of any modern browser (for example, Chrome, Firefox, IE11+, and other leading browsers).
Agents must be in a permission group that is allowed to use co-browse.
View-only co-browse sessions
You can mark fields, buttons, and selectors, such as checkboxes and radio buttons as view-only to prevent agents from acting on behalf of the customer during a co-browse session. To do this, go to your site's HTML code and add the property cobrowse="viewonly" to any of the mentioned HTML elements.
Example: <input type="text" cobrowse="viewonly" name="creditCardAccountNumber" value=""/>
This way, agents can see what customers are doing but cannot interact with view-only user interface elements. Agents can still highlight a these interface elements to draw customers' attention.
Privacy ? Masking sensitive fields
Mask fields to prevent agents from seeing sensitive info during a co-browse session. To do this, go to your site's HTML code and add the property cobrowse="false" to any text field that you want to prevent agents from seeing.
Example: <input type="text" cobrowse="false" name="creditCardAccountName" value=""/>
Privacy ? Masking sensitive sections
Mask HTML elements to prevent agents from seeing sensitive information during a co-browse session. To do this, go to your site's HTML code and add the property ignore="true" to any element you want to prevent agents from seeing.
Example: <div ignore="true">Security Access Key: A7fDFUJkjleoiuxcv7df==</div>
Tip: If the page layout depends on an element you want to mask, first encase the sensitive element inside another element that will not impact the page layout if ignored.
Mobile
When a customer is using a mobile device, the agent can view the page with the same dimensions as the customer.
How co-browse works ? A brief technical description
Bold360 actively monitors the content of the visited page and sends changes to the agent. Bold360 only looks at page content as an HTML document. The document and display size tracking generally gives the agent a very similar rendering of the page as what the customer sees. The actual view of the page can vary between mobile/desktop devices and based on display/font/size settings in the browser and the dimension/resolution of the screen. All page functionality will be present for the agent and the customer, but placement, rendering and word wrapping may potentially differ. For example, elements on the edge of the screen for the agent might be positioned off the screen for the customer.
Security
The customer's page contents and actions are sent to the servers exclusively over SSL (even if the page is not secure.)

Announcements

Join the DX Community!

Meet fellow DX pros, ask questions, and learn best practices.

Join the DX Community

Featured

Allowlists and the Bold360 platform

Allowlists and the Digital DX AI platform

To use Genesys DX, you may want to allowlist certain URLs so that its connected services are able to connect.

We recommend you add the following URLs to your network's allowlist:

  • *.boldchat.com, *bold360.com, *.bold360usercontent.com  - Genesys' service for adding chat to websites
  • *.nanorep.co ? The site for customers who have access to the Bold360 AI platform (Service, Advise, and Acquire)
  • authentication.logmeininc.com, auth.bold360.com - LogMeIn's sign-in service
  • launch.bold360.com, myaccount.logmeininc.com, profile.logmeininc.com - LogMeIn's MyAccount page, where you can manage and access all your LogMeIn products

*** Please note that *.logmeininc.com domains and IP Addresses/ranges are only needed temporarily while the BoldChat/Bold360 platforms complete their migration to Genesys architecture.

Note: This list includes sub-domains for the listed domains, so it is advisable to use wildcard rules wherever possible when you allow or block any LogMeIn service on your network. Specifically, we recommend you to allow *bold360.com and *logmeininc.com. The services themselves communicate using port 443 (HTTPS/SSL) and port 80, so you don't need to open any additional ports within a firewall.

LogMeIn IP ranges

We recommend you add LogMeIn domains and URLs to your network's allowlist instead of allowing LogMeIn IP ranges. If that is not feasible, refer to the list of LogMeIn IP addresses.

CIDR Notation Numeric IP Range Netmask Notation
67.217.80.0/23 67.217.80.0 - 67.217.81.255 67.217.80.0 255.255.254.0
95.172.70.0/24 95.172.70.0 - 95.172.70.255 95.172.70.0 255.255.255.0
173.199.52.0/23 173.199.52.1 - 173.199.53.254 173.199.52.0 255.255.254.0

IP addresses for the sign in service

To sign in to your Bold360 work environment, you must allow LogMeIn's sign-in service. To do that by IP addresses, add the following IPs to your firewall settings:

  • 34.199.209.240
  • 35.173.84.18
  • 78.108.120.24
  • 173.199.2.47
  • 173.199.4.47

Email addresses for the sign in service

Make sure you allow the following email addresses so that identity-related and authentication emails are received:

  • noreply@logmein.com
  • support@bold360.com

Third-party IP Ranges

You must also allowlist ranges for these third-party services based upon your use of these service providers:

Email Domains

For email invitations and correspondences from us and the BoldChat/Bold360 software, we recommend allowing the following email domains through your email's spam and allowlist filters.

  • noreply@logmein.com
  • support@bold360.com

*** Please note that *.logmeininc.com domains and IP Addresses/ranges are only needed temporarily while the BoldChat/Bold360 platforms complete their migration to Genesys architecture.

 

Update as of January 18, 2022

Beginning on October 9, 2021, additional changes are taking place as part of the migration process of the DX platform from LMI to Genesys. The failover will take place in 3 stages from LMI on-premise data centers to Genesys cloud-based environment which provides robustness, flexibility and better scalability to the DX platform.

[ACTION] - If you allow list Agent (formerly known as BoldChat) by domain (preferred to DNS or IP allowlisting), you will need to allowlist the following domains in your organization's network/firewall:

  • bold360.com
  • boldchat.com

Alternatively, you can allowlist the following DNS servers:

Ireland

  • eub-app16-01.boldchat.com
  • eub-app16-02.boldchat.com
  • eub-app16-03.boldchat.com
  • eub-app16-04.boldchat.com
  • eub-app16-05.boldchat.com
  • eub-app16-06.boldchat.com
  • eub-app16-07.boldchat.com
  • eub-app16-08.boldchat.com
  • eub-app16-09.boldchat.com
  • eub-app16-10.boldchat.com
  • eub-app16-11.boldchat.com
  • eub-app16-12.boldchat.com

Frankfurt

  • eub-app17-01.boldchat.com
  • eub-app17-02.boldchat.com
  • eub-app17-03.boldchat.com
  • eub-app17-04.boldchat.com
  • eub-app17-05.boldchat.com
  • eub-app17-06.boldchat.com
  • eub-app17-07.boldchat.com
  • eub-app17-08.boldchat.com
  • eub-app17-09.boldchat.com
  • eub-app17-10.boldchat.com
  • eub-app17-11.boldchat.com
  • eub-app17-12.boldchat.com

US East (N. Virginia)

  • b-app18-01.boldchat.com
  • b-app18-02.boldchat.com
  • b-app18-03.boldchat.com
  • b-app18-04.boldchat.com
  • b-app18-05.boldchat.com
  • b-app18-06.boldchat.com
  • b-app18-07.boldchat.com
  • b-app18-08.boldchat.com
  • b-app18-09.boldchat.com
  • b-app18-10.boldchat.com
  • b-app18-11.boldchat.com
  • b-app18-12.boldchat.com
  • b-app18-13.boldchat.com
  • b-app18-14.boldchat.com
  • b-app18-15.boldchat.com
  • b-app18-16.boldchat.com
  • b-app18-17.boldchat.com
  • b-app18-18.boldchat.com
  • b-app18-19.boldchat.com
  • b-app18-20.boldchat.com
  • b-app18-21.boldchat.com
  • b-app18-22.boldchat.com
  • b-app18-23.boldchat.com
  • b-app18-24.boldchat.com
  • b-app18-25.boldchat.com
  • b-app18-26.boldchat.com
  • b-app18-27.boldchat.com
  • b-app18-28.boldchat.com
  • b-app18-29.boldchat.com
  • b-app18-30.boldchat.com
  • b-app18-31.boldchat.com
  • b-app18-32.boldchat.com
  • b-app18-33.boldchat.com
  • b-app18-34.boldchat.com
  • b-app18-35.boldchat.com
  • b-app18-36.boldchat.com
  • b-app18-37.boldchat.com
  • b-app18-38.boldchat.com
  • b-app18-39.boldchat.com
  • b-app18-40.boldchat.com
  • b-app18-41.boldchat.com
  • b-app18-42.boldchat.com
  • b-app18-43.boldchat.com
  • b-app18-44.boldchat.com
  • b-app18-45.boldchat.com
  • b-app18-46.boldchat.com
  • b-app18-47.boldchat.com
  • b-app18-48.boldchat.com
  • b-app18-49.boldchat.com
  • b-app18-50.boldchat.com
  • b-app18-51.boldchat.com
  • b-app18-52.boldchat.com
  • b-app18-53.boldchat.com
  • b-app18-54.boldchat.com
  • b-app18-55.boldchat.com
  • b-app18-56.boldchat.com
  • b-app18-57.boldchat.com
  • b-app18-58.boldchat.com
  • b-app18-59.boldchat.com
  • b-app18-60.boldchat.com

US West (Oregon)

  • b-app19-01.boldchat.com
  • b-app19-02.boldchat.com
  • b-app19-03.boldchat.com
  • b-app19-04.boldchat.com
  • b-app19-05.boldchat.com
  • b-app19-06.boldchat.com
  • b-app19-07.boldchat.com
  • b-app19-08.boldchat.com
  • b-app19-09.boldchat.com
  • b-app19-10.boldchat.com
  • b-app19-11.boldchat.com
  • b-app19-12.boldchat.com
  • b-app19-13.boldchat.com
  • b-app19-14.boldchat.com
  • b-app19-15.boldchat.com
  • b-app19-16.boldchat.com
  • b-app19-17.boldchat.com
  • b-app19-18.boldchat.com
  • b-app19-19.boldchat.com
  • b-app19-20.boldchat.com
  • b-app19-21.boldchat.com
  • b-app19-22.boldchat.com
  • b-app19-23.boldchat.com
  • b-app19-24.boldchat.com
  • b-app19-25.boldchat.com
  • b-app19-26.boldchat.com
  • b-app19-27.boldchat.com
  • b-app19-28.boldchat.com
  • b-app19-29.boldchat.com
  • b-app19-30.boldchat.com
  • b-app19-31.boldchat.com
  • b-app19-32.boldchat.com
  • b-app19-33.boldchat.com
  • b-app19-34.boldchat.com
  • b-app19-35.boldchat.com
  • b-app19-36.boldchat.com
  • b-app19-37.boldchat.com
  • b-app19-38.boldchat.com
  • b-app19-39.boldchat.com
  • b-app19-40.boldchat.com
  • b-app19-41.boldchat.com
  • b-app19-42.boldchat.com
  • b-app19-43.boldchat.com
  • b-app19-44.boldchat.com
  • b-app19-45.boldchat.com
  • b-app19-46.boldchat.com
  • b-app19-47.boldchat.com
  • b-app19-48.boldchat.com
  • b-app19-49.boldchat.com
  • b-app19-50.boldchat.com
  • b-app19-51.boldchat.com
  • b-app19-52.boldchat.com
  • b-app19-53.boldchat.com
  • b-app19-54.boldchat.com
  • b-app19-55.boldchat.com
  • b-app19-56.boldchat.com
  • b-app19-57.boldchat.com
  • b-app19-58.boldchat.com
  • b-app19-59.boldchat.com
  • b-app19-60.boldchat.com
     

[ACTION] - If you allow-list Agent (formerly known as BoldChat) by IP, here are the IPs you will need to allow list in your organization in order to avoid connectivity issues with the new Data Center on March 5th:

Ireland

  • 34.246.13.84
  • 54.155.23.252
  • 46.137.48.149
  • 34.254.28.102 5
  • 2.49.80.82
  • 63.33.229.51
  • 54.75.218.75
  • 54.216.206.26
  • 34.246.145.123
  • 52.212.90.186 5
  • 4.77.148.81
  • 34.251.74.92

Frankfurt

  • 3.122.210.241
  • 18.192.113.151
  • 3.68.175.68
  • 18.196.140.195
  • 3.68.178.202
  • 18.194.200.171
  • 18.198.110.95
  • 18.192.7.127
  • 3.65.55.253
  • 3.64.238.21
  • 3.64.109.185
  • 18.198.123.19

US East (N. Virginia)

  • 107.20.174.150
  • 18.214.187.122
  • 18.233.1.191
  • 18.233.79.13
  • 18.233.95.16
  • 18.235.217.246
  • 23.20.109.244
  • 23.20.253.55
  • 23.21.167.45
  • 3.225.82.217
  • 3.231.116.10
  • 3.233.101.193
  • 3.233.111.68
  • 3.89.11.143
  • 34.194.220.164
  • 34.195.70.224
  • 34.206.233.8
  • 34.224.220.30
  • 34.228.50.168
  • 34.230.132.34
  • 34.234.140.16
  • 34.236.195.183
  • 34.236.241.191
  • 34.236.83.24
  • 35.153.29.169
  • 35.168.4.139
  • 35.174.34.186
  • 35.175.163.252
  • 44.193.104.84
  • 44.193.127.42
  • 44.193.247.199
  • 44.194.100.181
  • 44.194.137.67
  • 44.194.208.207
  • 44.194.25.105
  • 44.194.73.45
  • 44.195.9.217
  • 52.20.221.203
  • 52.207.76.221
  • 52.3.185.243
  • 52.44.154.238
  • 52.71.46.102
  • 52.71.71.29
  • 52.86.214.10
  • 54.144.250.111
  • 54.147.215.157
  • 54.152.188.62
  • 54.156.114.221
  • 54.156.48.172
  • 54.160.133.4
  • 54.160.196.54
  • 54.161.46.241
  • 54.163.230.72
  • 54.164.146.233
  • 54.166.248.29
  • 54.198.148.121
  • 54.226.231.169
  • 54.236.144.76
  • 54.84.163.19
  • 75.101.233.126

US West (Oregon)

  • 34.210.135.97
  • 34.213.254.212
  • 35.160.120.77
  • 35.161.150.98
  • 35.167.75.41
  • 35.80.158.24
  • 35.80.170.11
  • 35.80.194.13
  • 35.80.219.155
  • 35.81.101.126
  • 35.81.88.49
  • 35.82.204.234
  • 35.82.9.197
  • 35.83.116.129
  • 44.224.251.121
  • 44.226.244.84
  • 44.228.212.110
  • 44.230.126.250
  • 44.230.250.92
  • 44.231.153.96
  • 44.231.91.181
  • 44.232.19.77
  • 44.233.171.9
  • 44.237.129.5
  • 44.237.13.169
  • 44.237.28.122
  • 44.237.55.136
  • 44.238.219.222
  • 44.239.247.221
  • 44.241.208.142
  • 44.242.45.116
  • 44.242.53.108
  • 52.11.10.7
  • 52.12.160.123
  • 52.12.220.61
  • 52.13.124.118
  • 52.24.130.127
  • 52.32.198.76
  • 52.32.241.86
  • 52.35.142.151
  • 52.36.48.105
  • 52.38.106.12
  • 52.38.150.246
  • 52.40.239.227
  • 52.40.30.115
  • 52.41.198.141
  • 52.41.47.191
  • 54.184.129.107
  • 54.184.178.79
  • 54.184.90.24
  • 54.188.53.58
  • 54.200.230.213
  • 54.200.68.184
  • 54.201.26.44
  • 54.203.206.223
  • 54.212.170.137
  • 54.212.95.24
  • 54.69.131.234
  • 54.69.177.37
  • 54.69.85.11