Last update : February 2018 SELECT ALL SELECT NONE
Protocol Category Description
Diameter Authentication This is the Diameter protocol application, an authentication, authorization and accounting protocol for computer networks.It is described in RFC 3588.
RADIUS Access Authentication This flow emulates the RADIUS Access [RFC 2138] protocol. Random username variations may be specified by placing *'s in the username field, which will be replaced by a random numeric digit. Similarly, x's may be used to specify a random digit in the calling or called station IDs. A range of framed IPs may be specified using slash notation (Ex: 192.168.0.0/16 will generate an IP in the range of [192.168.0.0, 192.168.255.255]. Note that settings will not be modified by the CTM when a token is used in any field that accepts alphanumeric characters. Values provided in the flow settings are treated as defaults, used when the same setting is not provided in a particular action.
RADIUS Accounting Authentication This application flow emulates the RADIUS Accounting [RFC 2866] protocol. Random username variations may be specified by placing *'s in the username field, which will be replaced by a random numeric digit. Similarly, x's may be used to specify a random digit in the calling or called station IDs. A range of framed IPs may be specified using slash notation (Ex: 192.168.0.0/16 will generate an IP in the range of [192.168.0.0, 192.168.255.255].
TACACS+ Authentication TACACS+ - Terminal Access Controller Access-Control System Plus is an authentication, authorization and accounting (AAA) protocol developed by Cisco. The protocol is documented by the Network Working Group's INTERNET-DRAFT: draft-grant-tacacs-02.txt
AIM6-Keyserver Chat/IM This application flow simulates an authentication to the AOL Instant Messenger version 6 infrastructure. This flow is typically used in conjunction with the other AIM6 application flows; namely, AIM6-Switchboard and AIM6-Rendezvous.
AIM6-Rendezvous Chat/IM This application flow simulates sending and receiving files via AOL Instant Messenger version 6's Rendezvous file transfer infrastructure. This flow is typically used in conjunction with the other AIM6 application flows; namely, AIM6-Keyserver and AIM6-Switchboard. Specifically, users and peers should signal the sending and receiving of files via the AIM6-Switchboard actions of "IM: Start File Transfer" and "IM: Accept File Transfer."
AIM6-Switchboard Chat/IM This application flow simulates sessions associated with the AOL Instant Messenger version 6 switchboard. This includes initial post-authentication client configuration, chatting, and file transfer signaling. This flow is typically used in conjunction with the other AIM6 application flows; namely, AIM6-Keyserver and AIM6-Rendezvous.
AOL Instant Messenger Chat/IM Sends a random AOL Instant Messenger flow
CiscoSpark Aug17 Chat/IM Cisco Spark is a work collaboration platform developed by Cisco which includes instant messaging, video conferencing, file sharing and other features. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Discord Dec17 Chat/IM The use use of the Discord website as of December 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen AOL Chat Jan14 Chat/IM Emulates the use of the AOL Chat (AIM) website as of January 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen AOLChat Apr14 Chat/IM Emulates the use of the AOL Chat (AIM) website as of April 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen AOLChat Jul14 Chat/IM Emulates the use of the AOL Chat (AIM) website as of July 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen AOLChat Mar14 Chat/IM Emulates the use of the AOL Chat (AIM) website as of March 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen AOLchat Oct14 Chat/IM Emulates the use of the AOL Chat (AIM) website as of October 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen AolChat Jun14 Chat/IM Emulates the use of the AOL Chat (AIM) website as of June 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Aolchat Apr15 Chat/IM Emulates the use of the AOL Chat (AIM) website as of April 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat Apr17 Chat/IM Emulates the use of the AOL Chat (AIM) website as of April 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat Aug14 Chat/IM Emulates the use of the AOL Chat (AIM) website as of August 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Aolchat Aug16 Chat/IM Emulates the use of the AOL Chat (AIM) website as of August 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat Aug17 Chat/IM Emulates the use of the AOL Chat (AIM) website as of August 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat Dec14 Chat/IM Emulates the use of the AOL Chat (AIM) website as of December 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Aolchat Dec16 Chat/IM Emulates the use of the AOL Chat (AIM) website as of December 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat Feb15 Chat/IM Emulates the use of the AOL Chat (AIM) website as of February 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Aolchat Feb17 Chat/IM Emulates the use of the AOL Chat (AIM) website as of February 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat Jan15 Chat/IM Emulates the use of the AOL Chat (AIM) website as of January 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Aolchat Jan17 Chat/IM Emulates the use of the AOL Chat (AIM) website as of January 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat Jul16 Chat/IM Emulates the use of the AOL Chat (AIM) website as of July 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat Jul17 Chat/IM Emulates the use of the AOL Chat (AIM) website as of July 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat Jun17 Chat/IM Emulates the use of the AOL Chat (AIM) website as of June 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat Mar17 Chat/IM Emulates the use of the AOL Chat (AIM) website as of March 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat May15 Chat/IM Emulates the use of the AOL Chat (AIM) website as of May 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat May17 Chat/IM Emulates the use of the AOL Chat (AIM) website as of May 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat Nov14 Chat/IM Emulates the use of the AOL Chat (AIM) website as of November 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Aolchat Nov15 Chat/IM Emulates the use of the AOL Chat (AIM) website as of November 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat Nov16 Chat/IM Emulates the use of the AOL Chat (AIM) website as of November 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat Oct16 Chat/IM Emulates the use of the AOL Chat (AIM) website as of October 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat Sep15 Chat/IM Emulates the use of the AOL Chat (AIM) website as of September 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat Sep16 Chat/IM Emulates the use of the AOL Chat (AIM) website as of September 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolchat Sep17 Chat/IM Emulates the use of the AOL Chat (AIM) website as of September 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Web-ICQ Feb14 Chat/IM Emulates the use of Web-ICQ as of February 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Web-ICQ Jan14 Chat/IM Emulates the use of Web-ICQ as of January 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Web-ICQ Mar14 Chat/IM Emulates the use of Web-ICQ as of March 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen WebICQ Apr14 Chat/IM Emulates the use of Web-ICQ as of Apr 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen WebICQ Apr15 Chat/IM Emulates the use of Web-ICQ as of Apr 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen WebICQ Aug14 Chat/IM Emulates the use of Web-ICQ as of Aug 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen WebICQ Feb15 Chat/IM Emulates the use of Web-ICQ as of Feb 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen WebICQ Jan15 Chat/IM Emulates the use of Web-ICQ as of Jan 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen WebICQ Jul14 Chat/IM Emulates the use of Web-ICQ as of July 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen WebICQ Jun14 Chat/IM Emulates the use of Web-ICQ as of Jun 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen WebICQ May15 Chat/IM Emulates the use of Web-ICQ as of May 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen WebICQ Nov14 Chat/IM Emulates the use of Web-ICQ as of Nov 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen WebICQ Oct14 Chat/IM Emulates the use of Web-ICQ as of Oct 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Webicq Apr17 Chat/IM Emulates the use of the Web-ICQ website as of April 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq Aug16 Chat/IM Emulates the use of the Web-ICQ website as of August 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq Aug17 Chat/IM Emulates the use of the Web-ICQ website as of August 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq Dec14 Chat/IM Emulates the use of Web-ICQ as of Dec 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Webicq Dec16 Chat/IM Emulates the use of the Web-ICQ website as of December 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq Dec17 Chat/IM Emulates the use of the Web-ICQ website as of December 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq Feb17 Chat/IM Emulates the use of the Web-ICQ website as of February 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq Jan17 Chat/IM Emulates the use of the Web-ICQ website as of January 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq Jan18 Chat/IM Emulates the use of the Web-ICQ website as of January 2018. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions.
Evergreen Webicq Jul17 Chat/IM Emulates the use of the Web-ICQ website as of July 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq Jun17 Chat/IM Emulates the use of the Web-ICQ website as of June 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq Mar17 Chat/IM Emulates the use of the Web-ICQ website as of March 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq May17 Chat/IM Emulates the use of the Web-ICQ website as of May 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq Nov15 Chat/IM Emulates the use of Web-ICQ as of Nov 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq Nov16 Chat/IM Emulates the use of the Web-ICQ website as of November 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq Nov17 Chat/IM Emulates the use of the Web-ICQ website as of November 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq Oct16 Chat/IM Emulates the use of the Web-ICQ website as of October 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq Oct17 Chat/IM Emulates the use of the Web-ICQ website as of October 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq Sep15 Chat/IM Emulates the use of Web-ICQ as of Aug 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq Sep16 Chat/IM Emulates the use of the Web-ICQ website as of September 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Webicq Sep17 Chat/IM Emulates the use of the Web-ICQ website as of September 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoo Chat Feb14 Chat/IM Emulates the use of the Yahoo Chat website as of February 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoo Chat Jan14 Chat/IM Emulates the use of the Yahoo Chat website as of January 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoo Chat Oct17 Chat/IM Emulates the use of the Yahoo Chat website as of October 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen YahooChat Apr14 Chat/IM Emulates the use of the Yahoo Chat website as of April 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen YahooChat Jul14 Chat/IM Emulates the use of the Yahoo Chat website as of July 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen YahooChat Jun14 Chat/IM Emulates the use of the Yahoo Chat website as of June 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen YahooChat Mar14 Chat/IM Emulates the use of the Yahoo Chat website as of March 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoochat Apr15 Chat/IM Emulates the use of the Yahoo Chat website as of April 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat Apr17 Chat/IM Emulates the use of the Yahoo Chat website as of April 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat Aug14 Chat/IM Emulates the use of the Yahoo Chat website as of August 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoochat Aug16 Chat/IM Emulates the use of the Yahoo Chat website as of August 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat Aug17 Chat/IM Emulates the use of the Yahoo Chat website as of August 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat Dec14 Chat/IM Emulates the use of the Yahoo Chat website as of December 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoochat Dec16 Chat/IM Emulates the use of the Yahoo Chat website as of December 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat Dec17 Chat/IM Emulates the use of the Yahoo Chat website as of December 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat Feb15 Chat/IM Emulates the use of the Yahoo Chat website as of February 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoochat Feb17 Chat/IM Emulates the use of the Yahoo Chat website as of February 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat Jan15 Chat/IM Emulates the use of the Yahoo Chat website as of January 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoochat Jan17 Chat/IM Emulates the use of the Yahoo Chat website as of January 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat Jan18 Chat/IM Emulates the use of the Yahoo Chat website as of January 2018. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions.
Evergreen Yahoochat Jul17 Chat/IM Emulates the use of the Yahoo Chat website as of July 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat Jun17 Chat/IM Emulates the use of the Yahoo Chat website as of June 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat Mar17 Chat/IM Emulates the use of the Yahoo Chat website as of March 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat May15 Chat/IM Emulates the use of the Yahoo Chat website as of May 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat May17 Chat/IM Emulates the use of the Yahoo Chat website as of May 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat Nov14 Chat/IM Emulates the use of the Yahoo Chat website as of November 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoochat Nov15 Chat/IM Emulates the use of the Yahoo Chat website as of November 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat Nov16 Chat/IM Emulates the use of the Yahoo Chat website as of November 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat Nov17 Chat/IM Emulates the use of the Yahoo Chat website as of November 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat Oct14 Chat/IM Emulates the use of the Yahoo Chat website as of October 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoochat Oct16 Chat/IM Emulates the use of the Yahoo Chat website as of October 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat Sep15 Chat/IM Emulates the use of the Yahoo Chat website as of September 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat Sep16 Chat/IM Emulates the use of the Yahoo Chat website as of September 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoochat Sep17 Chat/IM Emulates the use of the Yahoo Chat website as of September 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Gadu Gadu Chat/IM This is the Gadu Gadu Polish instant messaging and voice chat protocol.
Google Hangouts Chat/IM Google Hangouts is a communication platform developed by Google which includes instant messaging, video chat, SMS and VOIP features. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Google Talk Chat/IM Google Talk is a voice and instant messaging application. This application emulates a Google Talk session between one local user and one or more peer users. Fields left blank will be populated with random values.
Google Talk (Deprecated) Chat/IM Google Talk is a voice and instant message communication service. This version has been deprecated. Fields left blank will be populated with random values.
Gtalk UDP Helper Chat/IM Gtalk Protocol UDP Helper uses exchange actions to send/receive voice data and file transfer data via UDP call
Internet Relay Chat Chat/IM The IRC (Internet Relay Chat) protocol is for use with text based conferencing.
Microsoft Lync SIPe Chat/IM This protocol emulates Microsoft Lync 2013 SIPe traffic
Mxit Desktop Chat/IM The desktop version of South African-created mobile social network. This application emulates mxit session between one local user and one or more peer users. Fields left blank will be populated with random values.
OSCAR Chat/IM The OSCAR protocol is used by America Online's Instant Messenger (AIM) and ICQ services. AIM and ICQ both use the OSCAR backend to retrieve buddy lists, send and receive messages, and much more. Note that the OSCAR specification does not support IPv6 in its encodings, meaning that OSCAR messages that encode IP address information will always assume an IPv4 network neighborhood.
OSCAR File Transfer Chat/IM This application flow emulates sending and receiving files via OSCAR's file transfer infrastructure. This flow is typically used in conjunction with the OSCAR application flow. Specifically, users and peers should signal the sending and receiving of files via the OSCAR "Send File" and "Accept File" actions.
QQ Chat/IM This application flow emulates a Tencent QQ Instant Messenger session between one local user and one or more peer users. Fields left blank will be populated with random values.
QQLive Chat/IM Simulates a QQLive Streaming TV flow.
Skype V6 Chat/IM Skype is a freemium voice-over-IP service and instant messaging client, currently developed by the Microsoft Skype Division.
WeChat Chat/IM WeChat is a mobile text and voice messaging service owned by Tencent, China. HTTP is used in some of the WeChat actions however a lot of data transfer is done directly over TCP even though standard HTTP ports numbers are used. Note that most WeChat data is encrypted using a proprietary format.
Webmail Orange Chat/IM This application flow emulates Webmail Orange access over HTTP.
WhatsApp Chat/IM WhatsApp is a mobile messaging protocol for iPhone and Android which allows users to exchange messages without having to pay for SMS.
XMPP (Jabber) Chat/IM This protocol emulates the XMPP Instant Messaging Application Protocol.
Yahoo IM Chat/IM The Yahoo Instant Messenger (currently version 11.5.0.155-us) uses the YMSG protocol (currently version 19)
Box Oct17 Data Transfer/File Sharing Box is a cloud content management platform that provides file sharing and collaboration services. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Dropbox Data Transfer/File Sharing This flow emulates the Dropbox Client protocol used for syncing files between a client and the Dropbox cloud storage service.
Dropbox Nov17 Data Transfer/File Sharing The use of the Dropbox website as of November 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
DropboxPaper May17 Data Transfer/File Sharing Simulates the use of the Dropbox Paper website as of May 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
FTP Data Transfer/File Sharing File Transfer Protocol is used for transferring files over TCP between clients and servers [RFCs 959,2428]. Note, the "Server Name" parameter is used only in "Custom" profiles. The Server Data Port Range can accept a range for random port selection (i.e. 2048-4095).
FileSharePro Mar16 Data Transfer/File Sharing WWW File Share Pro can help you share files on the internet or on the local area network. This app emulates the use of the WWW File Share Pro application as of March 2016. Note that this protocol uses dynamically created flows to simulate all of the various interactions performed under the covers by a modern web browser. Because there may be lots of these dynamic flows and a lot of data generated on these flows, it may take a long time during profile creation and test initialization. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. Also all the interactions to a host can be removed by deleting that host from the Hosts list.
Geneve Data Transfer/File Sharing Geneve is used to support network virtualization use cases, where tunnels are typically established to act as a backplane between the virtual switches residing in hypervisors, physical switches, or middleboxes or other appliances.
GoogleDocs May17 Data Transfer/File Sharing Google Docs is an online word processor that lets you create and format documents and work with other people. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
GoogleSheets Oct 17 Data Transfer/File Sharing Google Sheets is web application that allows user to create, edit, or share excel sheet with others using web browser only. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
GoogleSlides Sept 17 Data Transfer/File Sharing Google Slides is a web application that allows user to create, edit, or share presentations with others using web browser only. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Gopher Data Transfer/File Sharing Gopher is a protocol for publishing, searching, and retrieving internet resources. [RFC 1436]
HTTP Data Transfer/File Sharing This application flow emulates HTTP sessions according to RFC2616.
IPP Data Transfer/File Sharing This application flow emulates client print jobs using the Internet Printing Protocol (IPP) [RFC 2911].
NNTP Data Transfer/File Sharing Network News Transfer Protocol (NNTP) [RFC 977, RFC 3977]
NetBIOS Data Transfer/File Sharing Emulates a NetBIOS Protocol Session Flow [RFC 1001].
QUIC - Quick UDP Internet Connections Data Transfer/File Sharing This flow emulates QUIC (Quick UDP Internet Connections) which is an experimental transport layer network protocol developed by Google and implemented in 2013. QUIC supports a set of multiplexed connections between two endpoints over User Datagram Protocol (UDP), and was designed to provide security protection equivalent to TLS/SSL, along with reduced connection and transport latency, and bandwidth estimation in each direction to avoid congestion. QUIC's main goal is to optimize connection-oriented web applications currently using TCP.
RPC NFSv3 Data Transfer/File Sharing RPC NFSv3 Protocol is a method for client systems to use a filesystem on a remote host computer. The protocol is supported by RPC.
Rsync Data Transfer/File Sharing The rsync protocol synchronizes files and directories from one location to another while minimizing data transfer.
SMB Data Transfer/File Sharing The Server Message Block (SMB) protocol is used for providing shared access to files, serial ports, printers and other communicaitons between nodes on a network.
SMB File Stress Data Transfer/File Sharing The SMB File Stress Super Flow actions allow the following actions: Authenticate a local user account on the remote system to an SMB or SMB2 share using NTLM or LanManager credentials. Write random or user imported file contents to an SMB or SMB2 Share. Write supersedes existing files. Append random or user imported file contents to an already existing file on an SMB or SMB2 Share or create a new file if it does not exist, Read the entire contents of a remote file on an SMB or SMB2 share. This remote file can already exist or be written by the Write or Append Actions. Verfify the entire contents of a remote file on an SMB or SMB2 share. Keep in mind that verification starts at the beginning of a file if you have used both write and append actions prior to the verify action. Delete a file from an SMB or SMB2 share. Disconnect from an SMB or SMB2 Share and Logoff the local user account. To maintain unique file names across multiple Write, Append, Read, Verify, and Delete actions, the 'File Name' field in each of the actions should utilize the %f and %g parameters. The %f identifies the flow and the %g identifies the goto iteration. Example: file-%f-%g,txt
SMBv2 Data Transfer/File Sharing The Server Message Block (SMB) protocol is used for providing shared access to files, serial ports, printers and other communicaitons between nodes on a network. This flow emulates version 2 of the protocol.
SPDY v2 Data Transfer/File Sharing The SPDY Protocol adds a framing layer for multiplexing multiple, concurrent streams across a single TCP connection (or any reliable transport stream). The framing layer is optimized for HTTP-like request-response streams. This version of the SPDY protocol has no SSL support.
ShareFile Apr17 Data Transfer/File Sharing Emulates the use of the ShareFile website as of April 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Soup TCP Data Transfer/File Sharing Soup (TCP) is a lightweight point-to-point protocol, built on top of TCP/IP sockets that allows delivery of a set of sequenced messages from a server to a client in real-time.SoupTCP guarantees that the client receives each message generated by the server in sequence, even across underlying TCP/IP socket connection failures.
TCP Over DNS Data Transfer/File Sharing A protocol that tunnels a TCP payload over the DNS protocol by encoding the data in DNS request name/response TXT Resource Record.
TFTP Data Transfer/File Sharing This application flow emulates a TFTP session. TFTP is a very simple protocol used to transfer files. Its description can be found in RFC 1350.
WebDAV Data Transfer/File Sharing Web-based Distributed Authoring and Versioning is a set of extensions to the HTTP protocol which allows users to collaboratively edit and manage files on remote web servers. Described in RFC 4918.
Apache Cassandra Database Apache Cassandra is an open source distributed database management system designed to handle large amounts of data across many commodity servers.
DB2 Database DB2 is an RDBMS from IBM. Version 9 is used here.
Informix Database This application flow emulates an Informix session [RFC 1035].
JIRA Database JIRA is an issue tracking product developed by Atlassian. This application simulates logging into a JIRA server, listing issues, creating a new issue and logging out.
MSSQL Database This application flow emulates a Microsoft SQL Server session [RFC 1035].
MongoDB Database MongoDB is a cross-platform document-oriented database. Classified as a NoSQL database, MongoDB eschews the traditional table-based relational database structure in favor of JSON-like documents with dynamic schemas (MongoDB calls the format BSON), making the integration of data in certain types of applications easier and faster
MySQL Database This application flow simulates an MySQL Database session.
Oracle Database This application flow emulates an Oracle Database session.
PostgreSQL Database This application flow emulates the PostgreSQL protocol.
SQLMon Database This application flow emulates an SQLMon query against an Oracle Database.
Sybase Database This application flow emulates a Sybase ASE Database session. Sybase Adaptive Server Enterprise (ASE) is a high-performance relational database management system for mission-critical, data-intensive environments
TDS - MS SQL Server 2012 Database The Tabular Data Stream (TDS) Protocol is an application-level protocol used for the transfer of requests and responses between clients and database server systems. Microsoft SQL Server 2012 was released to manufacturing on March 6, 2012 by Microsoft. It is a relational database management system.
WHOIS Database The nickname service, better known as WHOIS. RFC 3912 describes the service as "a TCP-based transaction-oriented query/response protocol that is widely used to provide information services to Internet users."
AWS Console Oct17 Distributed Computing AWS Management Console (AWS Console) is a web-based interface for users to manage and monitor the Amazon infrastructure suite, such as EC2, IAM, EBS, S3, SQS, Amazon Elastic MapReduce, and Amazon CloudFront, etc. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
AWS EC2 Nov17 Distributed Computing EC2 (Elastic Compute Cloud) is one of the services provided by Amazon Web Services(AWS). It provides secure, resizable compute capacity in the cloud and allows users to create, launch, and terminate virtual machine instances as needed and paying by the seconds for the active usage. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
AWS S3 Oct17 Distributed Computing S3 (Simple Storage Service) is one of the services provided by Amazon Web Services(AWS). It allows users to store, manage and retrieve any amount of data on the web with scalability, high availability, and low latency at commodity costs. This service is provided through web service interfaces including REST, SOAP and BitTorrent. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Amazon EC2 Distributed Computing This protocol emulates the HTTP/HTTPS Amazon EC2 REST API.
Amazon S3 Distributed Computing This protocol emulates the HTTP Amazon S3 REST API.
Citrix Distributed Computing Citrix is a virtualization application which allows users to launch remote applications from a local desktop environment. Additionally, different virtual channels may be assigned different priority levels so administrators can ensure QoS for certain subsets of Citrix traffic.
CoAP Distributed Computing The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation. It is frequently used for Internet of Things (IoT) networks.
DCE RPC Distributed Computing The DCE/RPC is the Distributed Computing Environment/Remote Procedure Calls protocol. It is primarily used by Microsoft Exchange and Outlook.
Git over HTTPs Distributed Computing This protocol emulates the Git Version Control Protocol over HTTPs.
Google Drive Aug17 Distributed Computing Google Drive is a cloud storage and synchronization service that allows users to create and share files and synchronize them across devices. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Google Drive June 2014 Distributed Computing Emulates the use of the Google Drive website as of June 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
HDFS NameNode RPC Distributed Computing This is the protocol used by the NameNode in order to allow HDFS clients to perform NameNode actions such as file operations.
HDFS Xceiver Distributed Computing This is the protocol used to carry out data transfer between HDFS replicas in Hadoop.
Hadoop MapReduce JobTracker RPC Distributed Computing This is the protocol used by the MapReduce JobTracker in order to allow Hadoop clients to submit and manage the progress of MapReduce jobs.
MQTT Distributed Computing MQTT is a Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designedso as to be easy to implement.These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.
Memcached Distributed Computing Memcached is a distributed memory caching system. It is often used to speed up dynamic database-driven websites by caching data and objects in RAM to reduce the number of times an external data source (such as a database or API) must be read.
Microsoft OneDrive Mar15 Distributed Computing Emulates the use of the OneDrive website as of March 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
NORM Distributed Computing The Negative-ACKnowledgment (NACK) Oriented Reliable Multicast (NORM) protocol can provide reliable transport of data from one or more senders to a group of receivers over an IP multicast network.
Office 365 Excel Jul 17 Distributed Computing The use of the Office 365 Excel website as of July 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Office 365 OneNote Sep17 Distributed Computing The use of the Office 365 OneNote website as of August 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Office 365 PowerPoint Online Aug17 Distributed Computing The use of the Office 365 PowerPoint website as of August 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Office365 Sway Jul15 Distributed Computing Emulates the use of the Microsoft Office 365 Sway website as of July 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Office365 Word Online Jul17 Distributed Computing The use of the Office 365 Word website as of July 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
OpenStack Swift Object Storage Protocol Distributed Computing OpenStack Object Storage is an object-based storage system that stores content and metadata as objects. You create, modify, and get objects and metadata by using the Object Storage API, which is implemented as a set of Representational State Transfer (REST) web services.
Perforce Distributed Computing Perforce is a commercial, proprietary revision control system. The Perforce server manages a central database and a master repository of file versions. Perforce clients communicate with the server via TCP/IP using a proprietary RPC and streaming protocol. Users submit changed files together in changelists, which are applied as atomic commits.
RTPS Distributed Computing Data Distribution Service/Real Time Publish Subscribe (DDS-RTPS) is a standard "wire protocol" that allows DDS implementations from multiple vendors to inter-operate. It is now often used for Internet of Things (IoT) networks.
VMware VMotion Distributed Computing VMware VMotion is a protocol that enables the live migration of running virtual machines from one physical server to another with zero downtime, continuous service availability and complete transaction integrity.
Salesforce ERP/CRM Salesforce provides a cloud based customer relationship management (CRM) product. Here we emulate the basic Salesforce actions when the Lightning user interface is used. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
AOL Mail Nov13 Email/WebMail This flow simulates the use of the AOL Mail as of November 2013. It supports logging in and out, receiving email and sending email with and without attachments. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen AOL Mail Jan14 Email/WebMail Emulates the use of the AOL Mail website as of January 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen AOLMail Apr14 Email/WebMail Emulates the use of the AOL Mail website as of April 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen AOLMail Jun14 Email/WebMail Emulates the use of the AOL Mail website as of June 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen AOLMail Mar14 Email/WebMail Emulates the use of the AOL Mail website as of March 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen AOLmail Aug14 Email/WebMail Emulates the use of the AOL Mail website as of August 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen AOLmail Jul14 Email/WebMail Emulates the use of the AOL Mail website as of July 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Aolmail Apr15 Email/WebMail Emulates the use of the AOL Mail website as of April 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail Apr17 Email/WebMail Emulates the use of the AOL Mail website as of April 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail Aug16 Email/WebMail Emulates the use of the AOL Mail website as of August 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail Aug17 Email/WebMail Emulates the use of the AOL Mail website as of August 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail Dec14 Email/WebMail Emulates the use of the AOL Mail website as of December 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Aolmail Dec17 Email/WebMail Emulates the use of the AOL Mail website as of December 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail Feb15 Email/WebMail Emulates the use of the AOL Mail website as of February 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Aolmail Feb17 Email/WebMail Emulates the use of the AOL Mail website as of February 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail Jan15 Email/WebMail Emulates the use of the AOL Mail website as of January 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Aolmail Jan17 Email/WebMail Emulates the use of the AOL Mail website as of January 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail Jan18 Email/WebMail Emulates the use of the AOL Mail website as of January 2018. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions.
Evergreen Aolmail Jul17 Email/WebMail Emulates the use of the AOL Mail website as of July 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail Jun17 Email/WebMail Emulates the use of the AOL Mail website as of June 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail Mar17 Email/WebMail Emulates the use of the AOL Mail website as of March 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail May15 Email/WebMail Emulates the use of the AOL Mail website as of May 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail May17 Email/WebMail Emulates the use of the AOL Mail website as of May 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail Nov14 Email/WebMail Emulates the use of the AOL Mail website as of November 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Aolmail Nov15 Email/WebMail Emulates the use of the AOL Mail website as of November 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail Nov16 Email/WebMail Emulates the use of the AOL Mail website as of November 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail Nov17 Email/WebMail Emulates the use of the AOL Mail website as of November 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail Oct14 Email/WebMail Emulates the use of the AOL Mail website as of October 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Aolmail Oct16 Email/WebMail Emulates the use of the AOL Mail website as of October 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail Oct17 Email/WebMail Emulates the use of the AOL Mail website as of October 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail Sep15 Email/WebMail Emulates the use of the AOL Mail website as of September 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail Sep16 Email/WebMail Emulates the use of the AOL Mail website as of September 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Aolmail Sep17 Email/WebMail Emulates the use of the AOL Mail website as of September 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Apr14 Email/WebMail Emulates the use of the Gmail website as of April 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Gmail Apr15 Email/WebMail Emulates the use of the Gmail website as of April 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Apr17 Email/WebMail Emulates the use of the Gmail website as of April 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Aug14 Email/WebMail Emulates the use of the Gmail website as of August 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Gmail Aug16 Email/WebMail Emulates the use of the Gmail website as of August 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Aug17 Email/WebMail Emulates the use of the Gmail website as of August 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Dec13 Email/WebMail Emulates Gmail ,a free advertising-supported email service provided by Google. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Gmail Dec14 Email/WebMail Emulates the use of the Gmail website as of December 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Gmail Dec16 Email/WebMail Emulates the use of the Gmail website as of December 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Dec17 Email/WebMail Emulates the use of the Gmail website as of December 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Feb14 Email/WebMail Emulates the use of the Gmail website as of February 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Gmail Feb15 Email/WebMail Emulates the use of the Gmail website as of February 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Gmail Feb17 Email/WebMail Emulates the use of the Gmail website as of February 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Jan14 Email/WebMail Emulates the use of the Gmail website as of January 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Gmail Jan15 Email/WebMail Emulates the use of the Gmail website as of January 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Gmail Jan17 Email/WebMail Emulates the use of the Gmail website as of January 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Jan18 Email/WebMail Emulates the use of the Gmail website as of January 2018. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions.
Evergreen Gmail Jul17 Email/WebMail Emulates the use of the Gmail website as of July 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Jun14 Email/WebMail Emulates the use of the Gmail website as of June 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Gmail Jun17 Email/WebMail Emulates the use of the Gmail website as of June 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Mar14 Email/WebMail Emulates the use of the Gmail website as of March 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Gmail Mar17 Email/WebMail Emulates the use of the Gmail website as of March 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail May15 Email/WebMail Emulates the use of the Gmail website as of May 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail May17 Email/WebMail Emulates the use of the Gmail website as of May 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Nov14 Email/WebMail Emulates the use of the Gmail website as of November 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Gmail Nov15 Email/WebMail Emulates the use of the Gmail website as of November 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Nov16 Email/WebMail Emulates the use of the Gmail website as of November 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Nov17 Email/WebMail Emulates the use of the Gmail website as of November 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Oct14 Email/WebMail Emulates the use of the Gmail website as of October 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Gmail Oct16 Email/WebMail Emulates the use of the Gmail website as of October 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Oct17 Email/WebMail Emulates the use of the Gmail website as of October 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Sep15 Email/WebMail Emulates the use of the Gmail website as of September 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Sep16 Email/WebMail Emulates the use of the Gmail website as of September 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Gmail Sep17 Email/WebMail Emulates the use of the Gmail website as of September 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen REdiffmail Nov14 Email/WebMail Emulates the use of the Rediffmail website as of November 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Rediffmail Apr14 Email/WebMail Emulates the use of the Rediffmail website as of April 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Rediffmail Apr15 Email/WebMail Emulates the use of the Rediffmail website as of April 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Apr17 Email/WebMail Emulates the use of the Rediffmail website as of April 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Aug14 Email/WebMail Emulates the use of the Rediffmail website as of August 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Rediffmail Aug16 Email/WebMail Emulates the use of the Rediffmail website as of August 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Aug17 Email/WebMail Emulates the use of the Rediffmail website as of August 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Dec13 Email/WebMail Emulates Rediffmail , a web-based email-service provided by Rediff.com This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Rediffmail Dec14 Email/WebMail Emulates the use of the Rediffmail website as of December 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Rediffmail Dec16 Email/WebMail Emulates the use of the Rediffmail website as of December 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Dec17 Email/WebMail Emulates the use of the Rediffmail website as of December 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Feb14 Email/WebMail Emulates the use of the Rediffmail website as of February 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Rediffmail Feb15 Email/WebMail Emulates the use of the Rediffmail website as of February 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Rediffmail Feb17 Email/WebMail Emulates the use of the Rediffmail website as of February 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Jan14 Email/WebMail Emulates the use of the Rediffmail website as of January 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Rediffmail Jan15 Email/WebMail Emulates the use of the Rediffmail website as of January 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Rediffmail Jan17 Email/WebMail Emulates the use of the Rediffmail website as of January 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Jan18 Email/WebMail Emulates the use of the Rediffmail website as of January 2018. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions.
Evergreen Rediffmail Jul14 Email/WebMail Emulates the use of the Rediffmail website as of July 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Rediffmail Jul17 Email/WebMail Emulates the use of the Rediffmail website as of July 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Jun14 Email/WebMail Emulates the use of the Rediffmail website as of June 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Rediffmail Jun17 Email/WebMail Emulates the use of the Rediffmail website as of June 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Mar14 Email/WebMail Emulates the use of the Rediffmail website as of March 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Rediffmail Mar17 Email/WebMail Emulates the use of the Rediffmail website as of March 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail May15 Email/WebMail Emulates the use of the Rediffmail website as of May 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail May17 Email/WebMail Emulates the use of the Rediffmail website as of May 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Nov15 Email/WebMail Emulates the use of the Rediffmail website as of November 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Nov16 Email/WebMail Emulates the use of the Rediffmail website as of November 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Nov17 Email/WebMail Emulates the use of the Rediffmail website as of November 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Oct14 Email/WebMail Emulates the use of the Rediffmail website as of October 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Rediffmail Oct16 Email/WebMail Emulates the use of the Rediffmail website as of October 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Oct17 Email/WebMail Emulates the use of the Rediffmail website as of October 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Sep15 Email/WebMail Emulates the use of the Rediffmail website as of September 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Sep16 Email/WebMail Emulates the use of the Rediffmail website as of September 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediffmail Sep17 Email/WebMail Emulates the use of the Rediffmail website as of September 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Rediifmail Aug17 Email/WebMail Emulates the use of the Rediffmail website as of August 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windows LiveMail Apr14 Email/WebMail Emulates the use of the WindowsLiveMail website as of April 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Windows LiveMail Dec13 Email/WebMail Emulates the use of the WindowsLiveMail website as of December 2013. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Windows LiveMail Feb14 Email/WebMail Emulates the use of the WindowsLiveMail website as of February 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Windows LiveMail Jan14 Email/WebMail Emulates the use of the WindowsLiveMail website as of January 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Windows Livemail Mar14 Email/WebMail Emulates the use of the WindowsLiveMail website as of March 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen WindowsLiveMail Oct17 Email/WebMail Emulates the use of the WindowsLiveMail website as of October 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen WindowsLivemail Jun14 Email/WebMail Emulates the use of the WindowsLiveMail website as of June 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Windowslievmail Dec16 Email/WebMail Emulates the use of the WindowsLiveMail website as of December 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Apr15 Email/WebMail Emulates the use of the WindowsLiveMail website as of April 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Apr17 Email/WebMail Emulates the use of the WindowsLiveMail website as of April 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Aug14 Email/WebMail Emulates the use of the WindowsLiveMail website as of August 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Windowslivemail Aug16 Email/WebMail Emulates the use of the WindowsLiveMail website as of August 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Aug17 Email/WebMail Emulates the use of the WindowsLiveMail website as of August 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Dec14 Email/WebMail Emulates the use of the WindowsLiveMail website as of December 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Windowslivemail Dec17 Email/WebMail Emulates the use of the WindowsLiveMail website as of December 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Feb15 Email/WebMail Emulates the use of the WindowsLiveMail website as of February 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Windowslivemail Feb17 Email/WebMail Emulates the use of the WindowsLiveMail website as of February 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Jan15 Email/WebMail Emulates the use of the WindowsLiveMail website as of January 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Windowslivemail Jan17 Email/WebMail Emulates the use of the WindowsLiveMail website as of January 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Jan18 Email/WebMail Emulates the use of the WindowsLiveMail website as of January 2018. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Jul17 Email/WebMail Emulates the use of the WindowsLiveMail website as of July 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Jun17 Email/WebMail Emulates the use of the WindowsLiveMail website as of June 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Mar17 Email/WebMail Emulates the use of the WindowsLiveMail website as of March 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail May15 Email/WebMail Emulates the use of the WindowsLiveMail website as of May 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail May17 Email/WebMail Emulates the use of the WindowsLiveMail website as of May 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Nov14 Email/WebMail Emulates the use of the WindowsLiveMail website as of November 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Windowslivemail Nov15 Email/WebMail Emulates the use of the WindowsLiveMail website as of November 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Nov16 Email/WebMail Emulates the use of the WindowsLiveMail website as of November 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Nov17 Email/WebMail Emulates the use of the WindowsLiveMail website as of November 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Oct14 Email/WebMail Emulates the use of the WindowsLiveMail website as of October 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Windowslivemail Oct16 Email/WebMail Emulates the use of the WindowsLiveMail website as of October 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Sep15 Email/WebMail Emulates the use of the WindowsLiveMail website as of September 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Sep16 Email/WebMail Emulates the use of the WindowsLiveMail website as of September 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Windowslivemail Sep17 Email/WebMail Emulates the use of the WindowsLiveMail website as of September 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoo Mail Dec13 Email/WebMail Emulates the use of the Yahoo Mail website as of December 2013. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoo Mail Feb14 Email/WebMail Emulates the use of the Yahoo Mail website as of February 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoo Mail Jan14 Email/WebMail Emulates the use of the Yahoo Mail website as of January 2014. Yahoo Mail loads much of the user data at the beginning of the webmail session, hence the presence of settings in some actions where they otherwise might not necessarily occur. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen YahooMail Jun14 Email/WebMail Emulates the use of the Yahoo Mail website as of June 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen YahooMail Mar14 Email/WebMail Emulates the use of the Yahoo Mail website as of March 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen YahooMail Oct17 Email/WebMail Emulates the use of the Yahoo Mail website as of October 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Apr14 Email/WebMail Emulates the use of the Yahoo Mail website as of April 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoomail Apr15 Email/WebMail Emulates the use of the Yahoo Mail website as of April 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Apr17 Email/WebMail Emulates the use of the Yahoo Mail website as of April 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Aug14 Email/WebMail Emulates the use of the Yahoo Mail website as of August 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoomail Aug16 Email/WebMail Emulates the use of the Yahoo Mail website as of August 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Aug17 Email/WebMail Emulates the use of the Yahoo Mail website as of August 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Dec14 Email/WebMail Emulates the use of the Yahoo Mail website as of December 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoomail Dec16 Email/WebMail Emulates the use of the Yahoo Mail website as of December 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Dec17 Email/WebMail Emulates the use of the Yahoo Mail website as of December 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Feb15 Email/WebMail Emulates the use of the Yahoo Mail website as of February 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoomail Feb17 Email/WebMail Emulates the use of the Yahoo Mail website as of February 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Jan15 Email/WebMail Emulates the use of the Yahoo Mail website as of January 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoomail Jan17 Email/WebMail Emulates the use of the Yahoo Mail website as of January 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Jan18 Email/WebMail Emulates the use of the Yahoo Mail website as of January 2018. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions.
Evergreen Yahoomail Jul14 Email/WebMail Emulates the use of the Yahoo Mail website as of July 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoomail Jul17 Email/WebMail Emulates the use of the Yahoo Mail website as of July 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Jun17 Email/WebMail Emulates the use of the Yahoo Mail website as of June 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Mar17 Email/WebMail Emulates the use of the Yahoo Mail website as of March 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail May15 Email/WebMail Emulates the use of the Yahoo Mail website as of May 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail May17 Email/WebMail Emulates the use of the Yahoo Mail website as of May 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Nov14 Email/WebMail Emulates the use of the Yahoo Mail website as of November 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoomail Nov15 Email/WebMail Emulates the use of the Yahoo Mail website as of November 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Nov16 Email/WebMail Emulates the use of the Yahoo Mail website as of November 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Nov17 Email/WebMail Emulates the use of the Yahoo Mail website as of November 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Oct14 Email/WebMail Emulates the use of the Yahoo Mail website as of October 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoomail Oct16 Email/WebMail Emulates the use of the Yahoo Mail website as of October 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Sep15 Email/WebMail Emulates the use of the Yahoo Mail website as of September 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Sep16 Email/WebMail Emulates the use of the Yahoo Mail website as of September 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoomail Sep17 Email/WebMail Emulates the use of the Yahoo Mail website as of September 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
GMX Webmail Email/WebMail GMX Mail is a web mail application that is popular in Germany.
GMX Webmail Attachment Email/WebMail This application flow simulates the attachment features of the GMX Webmail interface.
Gmailclassic Email/WebMail Google Webmail Classic. A free, advertising-supported email service provided by Google. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. You can remove all the interactions to a host by deleting that host from the Hosts list.
Gmx Aug16 Email/WebMail Emulates the use of the GMX Mail website as of August 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Google Mail Email/WebMail Google Webmail. A free, advertising-supported email service provided by Google. This protocol supercedes the deprecated the "Gmail" protocol.
Hotmail Email/WebMail This application flow simulates sending e-mail message via the MSN Hotmail web mail interface.
Hotmail Attachment Email/WebMail This application flow emulates the attachment features of the Hotmail web mail interface.
IMAPv4-Advanced Email/WebMail This application flow emulates an IMAPv4 e-mail session [RFC 1035][RFC 3501]. Fields left blank will be populated with random values. Actions which are described as "sequences," such as Login, Retrieve Mail, and Quit are compound actions, comprising several messages between a client and a server.
Laposte Webmail Email/WebMail laposte.net is a webmail service provided by La Poste, the mail service of France. It providing @laposte.net email addresses and hosts for approximately 1.6 million active email accounts. This protocol emulates logging into and out of the service, retrieving email from the in-box, sending a messsage wihout any attachments and sending a message with two attachments. Tokens can be used the email subject and body parameters as well as in the attachments in order to facilitate testing legal interception (LI) systems. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. You can remove all the interactions to a host by deleting that host from the Hosts list.
Mail.ru Email/WebMail Russian Webmail Mail.ru is the largest free e-mail service of Runet and the third most popular Russian website. This protocol emulates the common actions for the mail.ru webmail client.
Microsoft Exchange Email/WebMail This is the Microsoft Exchange email, calendaring, and contact management protocol used between Microsoft Exchange Server 2010 and Microsoft Outlook 2010.
Office 365 Outlook Calendar Jul15 Email/WebMail Emulates the use of the Office 365 Outlook Calendar website as of July 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Office 365 Outlook Tasks Jan18 Email/WebMail The use of the Office365 Outlook Task website as of January 2018. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Office365 Outlook Mail Jul17 Email/WebMail The use of the Office 365 Outlook Mail website as of July 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Outlook Web Access Email/WebMail This application flow emulates sending e-mail message via the Outlook web mail interface.
POP3-Advanced Email/WebMail Emulates a POP3 [RFC 1939] e-mail session. Fields left blank will be populated with random values.
Rediffmail Email/WebMail This protocol simulates the rediffmail NG Indian webmail service. Supported actions are: Load page, Login, Read and download attachment, Send with attachment, Compose draft, and Logout. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. You can remove all the interactions to a host by deleting that host from the Hosts list.
SMTP Email/WebMail This application flow simulates an SMTP Transaction. "Client Profile" and "Server Profile" must be set to "Custom" in order to honor their respective custom banners.
Windows Live Mail Email/WebMail Windows Live Mail. This protocol superceeds the hotmail protocol. A person using hotmail.com would, in fact, now be using Windows Live Mail.
Yahoo Mail Email/WebMail This application flow emulates Yahoo web-based email exchanges over HTTP.
Yahoo Mail (Classic) Email/WebMail This is the classic version of the Yahoo Mail protocol. Almost all accounts for Yahoo have been aggresively converted away from this and it only exists for a few holdouts.
ADP Dec17 Enterprise Applications ADP website is the main portal for the services and software provided by ADP LLC - a provider of human resources management for businesses, for example, pay roll and tax, benefits administration, talent management, etc. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
AMQP Enterprise Applications This protocol emulates AMQP v0.9.1 traffic generated with RabbitMQ server and Ruby Bunny clients. AMQP (Asynchronous Message Queuing Protocol) is an open standard application layer protocol for message-oriented middleware. RabbitMQ is an open source message broker software that implements AMQP, with client libraries available across all major programming languages.
Appogee Leave Mar17 Enterprise Applications Appogee HR is a Cloud Solution Provider providing software as service applications. Appogee Leave is their online absence management system for tracking PTO, vacation and other staff absences. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Appointy Mar17 Enterprise Applications Appointy is an all-in-one online scheduling software for restaurants. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
BFD Control Enterprise Applications Bidirectional Forwarding Detection (BFD) is used to detect faults between two forwarding engines connected by a link. BFD Control packets are used in BFD primary mode named 'Asynchronous mode'.
Concur Jan17 Enterprise Applications Emulates the use of the Concur Solutions website as of January 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Confluence Nov17 Enterprise Applications Confluence is a content collaboration tool developed by Atlassian. User can create and share documents in the form of Wiki pages; organize them under different spaces and projects; and manage the access to them. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
DCE RPC Endpoint Mapper (EPM) Enterprise Applications This is the Endpoint Mapper Service for DCE/RPC on Windows. It is used to multiplex services without well-known ports. Clients may query the EPM for a service's current port number. It is similar to the portmapper service on Unix.
DCE RPC Exchange Directory RFR Enterprise Applications The DCE RPC Exchange Directory RFR RPC Service is used by clients to access the global catalog.
DCE RPC MAPI Enterprise Applications The DCE RPC Messaging Application Programming Interface Service is used by Exchange clients for sending and retriving mail.
DocuSign Dec17 Enterprise Applications DocuSign provides electronic signature technology and digital transaction management services for facilitating electronic exchanges of contracts and signed documents. DocuSign's features include authentication services, user identity management and workflow automation. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
GoDaddy Nov17 Enterprise Applications GoDaddy is a website that provides services for domain name registration, website building and web hosting. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
HL7 Enterprise Applications Health Level Seven (HL7) is a set of standards for transfer clinical and administrative data between software applications used by health care providers. This application simulates the lower layer protocol (LLP, sometimes referred to a MLLP for Minimum LLP) used when transferring the data in the non-XML pipe and hat form.
Jira Service Desk Oct17 Enterprise Applications Jira Service Desk Cloud is a place for employees to ask for help, report incidents, or request new services. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
LPD Enterprise Applications LPD is the Line Printer Daemon protocol [RFC 1179], used for sending print jobs to either a printer queue or directly to a printer.
Meraki Nov17 Enterprise Applications Cisco Meraki provides unified management of mobile devices, Macs, PCs, and the entire network from a centralized dashboard. Enforce device security policies, deploy software and apps, and perform remote, live troubleshooting on thousands of managed devices. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Multicast Enterprise Applications This flow simulates raw multicast clients and servers [RFC 1112].
Paypal Enterprise Applications PayPal is a global e-commerce business allowing payments and money transfers to be made through the Internet. Online money transfers serve as electronic alternatives to paying with traditional paper methods, such as checks and money orders.
Raw Enterprise Applications This flow is used to generate raw data. By default, it will use random source and target ports.
Restaurant 7Shifts Mar17 Enterprise Applications 7shifts is an employee scheduling application designed for restaurants. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
SAP Enterprise Applications Session Announcement Protocol (SAP) broadcasts multicast session informaition [RFC 2974].
STOMP Enterprise Applications STOMP 1.2 (Simple or Streaming Text Orientated Messaging Protocol, version 1.2) is a simple interoperable protocol designed for asynchronous message passing between clients via mediating servers. It defines a text based wire-format for messages passed between these clients and servers.
SharePoint Sep14 Enterprise Applications Emulates the use of the SharePoint as of Sep 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Slack Oct17 Enterprise Applications Simulates the use of the Slack website as of October 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Zendesk Nov17 Enterprise Applications The use of the Zendesk website as of November 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Amazon Financial Amazon is a large online retailer. This protocol can be used to emulate an Amazon user performing the following actions - loading the signin page. - signing in. - searching for an item. - selecting the item to view the details. - returning to the search list. - selecting another item to view its details. - adding that item to the shopping cart. - proceeding to checkout. - reentering the signin password when prompted. - selecting the address to ship to. - selecting free shipping. - continuing to the payment page. - submitting credit card information. - continuing to the shipping information page. - selecting the shipping address from the address book. - confirming the order. - signing out. Note that this protocol uses dynamically created flows to simulate all of the various interactions performed under the covers by a modern web browser. Because there may be lots of these dynamic flows and a lot of data generated on these flows, it may take a long time during profile creation and test initialization. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. Also all the interactions to a host can be removed by deleting that host from the Hosts list.
Certify Jun17 Financial Emulates the use of the Certify website as of June 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Ebay Jan15 Financial Emulates the use of the eBay as of Jan 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
FIX Financial This is the Financial Information eXchange Application Protocol.
ITCH Financial A protocol for NASDAQ trades.
Instacart Financial Instacart: Online grocery shopping. Login, search for items, add them to a cart and then proceed to checkout. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
OUCH 4.1 Financial OUCH 4.1 (over TCP). This is a protocol used by the NASDAQ stock exchange.
Okazii Financial Okazii.ro is a popular Romanian online auction website similar to eBay.com Note that this protocol uses dynamically created flows to simulate all of the various interactions performed under the covers by a modern web browser. Because there may be lots of these dynamic flows and a lot of data generated on these flows, it may take a long time during profile creation and test initialization.
Seamless Financial Seamless Web based restaurant ordering. The site allows users to order food for delivery and takeout from restaurants. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Angry Birds Friends Sep15 Games Angry Birds Friends This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Everquest Dec15 Games Everquest is a 3D fantasy-themed massively multiplayer online role-playing game. This app emulates downloading the game and logging in. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Minecraft 1.8.9 Games Minecraft is a game about breaking and placing blocks. At first, people built structures to protect against nocturnal monsters, but as the game grew players worked together to create wonderful, imaginative things.
Pokemon GO Aug16 Games Pokemon Go is a free-to-play location-based, augmented reality game developed by Niantic for iOS and Android devices. In the game, players use the smart device's GPS and camera to capture, battle, and train virtual creatures, called Pokemon, who appear on the screen as if they were in the same real-world location as the player. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Steam Games Steam is a digital distribution, digital rights management, multiplayer and communications platform. It is used to distribute games and related media online, from small independent developers to larger software houses.
World of Warcraft Games This application flow emulates an online session of the World of Warcraft video game.
ActiveSync Mobile This is version 14 of the Exchange ActiveSync protocol which is used for e-mail, contacts, and calendaring. Exchange ActiveSync uses binary XML formatted data over HTTP/HTTPS.
BlackBerry Enterprise E-Mail Mobile This flow represents e-mail traffic shared between a BlackBerry device and a BlackBerry Enterprise Server.
Google Play Mobile Google Play uses HTTP and HTTPS to search, view, and download media and applications. A version 4 client is used here.
TUMe Mobile TUMe Instant Messaging and Voice Chat Protocol
TVUPlayer Mobile TVUPlayer. The emulation of a player used to stream a video and audio broadcast protocol which uses peer to peer real time packet replication. Although many parameters can be specified on different actions, parameters such as "Channel Id" only need to be specified on the first action that uses it and the value specified will be used in any actions that require it within the same flow.
The_Weather_Channel Nov 16 Mobile The Weather Channel (TWC) is an application which broadcasts weather forecasts as well as weather related news stories. This simulation is of an iPhone user browsing the various items on and off the main page. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Viber Call Mobile The call session for the Viber mobile application protocol
Viber Login Mobile The login session for the Viber mobile application protocol
WAP 1.2 Mobile Wireless Application Protocol (WAP) is a protocol used to access information over a mobile wireless network. This flow emulates a WAP browser that uses the Wireless Session Protocol (WSP).
YouTube Music Sep16 Mobile YouTube Music is the Android version of YouTube, a video-sharing website headquartered in San Bruno, California, United States, that lets you watch and listen to a nearly endless catalog of music. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
iMessage Mobile iMessage is accessible through the Messages app on an iPhone, iPad or iPod touch running iOS 5 or later or on a Mac running OS X Mountain Lion or later. For users who have an active data connection, Messages will check with Apple if the recipient has iMessage set up. If so, Messages will seamlessly transition from SMS to iMessage.
iTunes Mobile Apple uses iTunes (ITMS) as the protocol for several applications, including iTunes, App Store, iBooks, and Game Center.
GTP-C Simulated Mobility GPRS (General Packet Radio Service) Tunnelling Protocol-Control. This is the control portion of the GTP protocol used in mobile 3GPP networks to tunnel a handset's IP data traffic to the proper GSN (GPRS Support Node).
GTP-U Simulated Mobility GPRS (General Packet Radio Service) Tunnelling Protocol-User Data. This is the user data portion of the GTP protocol used in mobile 3GPP networks to tunnel a handset's IP data traffic to the proper GSN (GPRS Support Node).
GTPv2-C Mobility The control plane protocol used in the 3GPP/LTE Enhanced PacketCore
KakaoTalk Mobility KakaoTalk is a mobile app which provides free voice calls and text messaging. Messaging can be one on one or group chats.
S1AP Mobility The S1 Application Part (S1AP) is the 3GPP/LTE signaling protocol within the control plane between the E-UTRAN and the evolved packet core (EPC). Its services include managing the SAE Bearer channel, the transfer of initial context, and providing mobility functions for user equipment (UE).
AppleJuice P2P AppleJuice is a German Peer-to-Peer file sharing protocol.
BitTorrent Peer P2P This application flow simulates the BitTorrent peer-to-peer protocol
BitTorrent Tracker P2P This application flow simulates a BitTorrent peer talking to a tracker server.
Bitcoin P2P Bitcoin is a peer-to-peer online payment system. The unit of account is also called bitcoin. Bitconin transactions are verified by network nodes and record in a public distributed ledger called block chain.
Gnutella 0.6 P2P This is the Gnutella peer-to-peer protocol v0.6. It should be used with the "Gnutella-Ultrapeer" and "Gnutella-Leave" protocols for maximum realism.
Gnutella-Leaf P2P Gnutella is a popular peer-to-peer file sharing protocol, and is the basis for applications such as LimeWire, Morph500, Mutella, and others. Modern Gnutella networks are generally composed of "ultrapeers" and "leaves". This flow simulates the communcations between a local client and remote ultrapeer.
Gnutella-Ultrapeer P2P Gnutella is a popular peer-to-peer file sharing protocol, and is the basis for applications such as LimeWire, Morph500, Mutella, and others. Modern Gnutella networks are generally composed of "ultrapeers" and "leaves." This flow simulates the communcations between a local client and remote ultrapeer.
PPLive P2P Simulates a PPLive Streaming TV flow.
PPTP P2P The Point to Point Tunneling Protocol [RFC 2637] allows the Point to Point Protocol (PPP) to be tunneled through an IP network. This flow emulates the control plane portion of PPTP.
SopCast P2P SopCast (Streaming over P2P). A protocol for streaming video and audio broadcasts using peer to peer networking.
Soulseek P2P Soulseek is a filesharing protocol based on peer-to-peer technology with support for virtual rooms allowing people with the same interests to share information, and chat freely using real-time messages in public or private.
Winny P2P Winny is a Japanese peer-to-peer (P2P) file-sharing protocol loosely inspired by the design principles behind the Freenet network, which makes user identities untraceable.
eDonkey P2P eDonkey is a decentraliced peer-to-peer file sharing protocol.
uTorrent P2P uTorrent Transport Protocol (uTP) is a lightweight BitTorrent protocol that makes incredibly efficient use of network bandwidth while reducing network problems.
RDP Remote Access This application flow simulates an RDP (Remote Desktop Protocol) session.
RFB Remote Access RFB(Remote Frame Buffer) Protocol for remote access to graphical user interfaces.
Rexec Remote Access Rexec Protocol is a cleartext protocol used for sending a command to the UNIX server host from the client host.
Rlogin Remote Access Rlogin Protocol is a cleartext protocol used for logging into the UNIX server host from the client host.
Rsh Remote Access Rsh Protocol is a cleartext protocol used for sending a command to the UNIX server host from the client host.
SOCKS 5 Remote Access Socket Secure (SOCKS) is an Internet protocol that routes network packets between a client and server through a proxy server. SOCKS5 additionally provides authentication so only authorized users may access a server. Practically, a SOCKS server proxies TCP connections to an arbitrary IP address.
Telnet Remote Access This application flow emulates the Telnet remote access protocol described in RFC 854.
BACnet/IP SCADA BACnet is a communications protocol for building automation and control networks and was designed for applications such as heating, ventilating, and air-conditioning control, lighting control, access control, and fire detection systems and their associated equipment. The BACnet protocol provides mechanisms for computerized building automation devices to exchange information, regardless of the particular building service they perform.
DNP3 SCADA Distributed Network Protocol (DNP3) is a set of communications protocols used between components in process automation systems. Its main use is in utilities such as electric and water companies. Its main purpose is to ensure communications between various types of data acquisition and control equipment. It plays a crucial role in SCADA systems, where it is used by SCADA Master Stations (aka Control Centers), Remote Terminal Units (RTUs), and Intelligent Electronic Devices (IEDs). It is primarily used for communications between a master station and RTUs or IEDs.
ECHONET-Lite SCADA This protocol emulates ECHONET Lite running over UDP. ECHONET Lite is a ECHONET Lite Communication Middleware Specification defined by the ECHONET CONSORTIUM.
Ethernet/IP SCADA EtherNet/IP is an industrial Ethernet network that combines standard Ethernet technologies with the media-independent Common Industrial Protocol or CIP. EtherNet/IP is one of the leading industrial Ethernet networks in the world and is widely used in a range from industries including factory, hybrid and process.
IEC104 SCADA A SCADA protocol. IEC104 transmits data measurements from monitoring devices, such as temperature or pressure sensors, across an industrial control system.
Manufacturing Message Specification SCADA This protocol implements the IEC61850 Manufacturing MessageSpecification ISO9506 (MMS)
Modbus SCADA Modbus is a serial communications protocol for use with its programmable logic controllers.
OPC UA SCADA The OPC Unified Architecture (UA), released in 2008, is a platform independent service-oriented architecture that integrates all the functionality of the individual OPC Classic specifications into one extensible framework.
Profinet PNIO-CM SCADA Profinet is a family of SCADA protocols defined in the PROFINET Open Industrial Ethernet standard provided by the PROFIBUS User Organization. PNIO-CM is the Profinet IO Context Manager protocol which runs over UDP DCERPC version 4.
S7comm SCADA S7comm (S7 Communication) is a Siemens proprietary protocol that runs between programmable logic controllers (PLCs) of the Siemens S7-300/400 family. It is used for PLC programming, exchanging data between PLCs, accessing PLC data from SCADA (supervisory control and data acquisition) systems and diagnostic purposes.
DICOM Secure Data Transfer DICOM stands for Digital Imaging and Communications in Medicine. It is a standard for handling, storing, printing, and transmitting information in medical imaging. The standard includes an application level communications protocol that uses TCP/IP to communicate between systems.
DTLS Secure Data Transfer The Datagram Transport Layer Security (DTLS) protocol provides communications privacy for datagram protocols. DTLS allows datagram-based applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. The DTLS protocol is based on the stream-oriented Transport Layer Security (TLS) protocol and is intended to provide similar security guarantees. The datagram semantics of the underlying transport are preserved by the DTLS protocol - the application will not suffer from the delays associated with stream protocols, but will have to deal with packet reordering, loss of datagram and data larger than a datagram network packet size.
HTTPS Simulated Secure Data Transfer This application flow simulates HTTPS (TLS) sessions. Please note that this protocol does not make use of the SSL encryption engine.
SSH Secure Data Transfer The Secure Shell (SSH) is a protocol for secure remote login and other secure network services over an insecure network. It is described in RFC 4253.
TOR Secure Data Transfer Tor is free software and an open network that helps defend against traffic analysis, a form of network surveillance that threatens personal freedom and privacy, confidential business activities and relationships, and state security.
Kelihos Command-and-Control Botnet Security Kelihos Botnet is a peer-to-peer botnet, where individual botnet nodes are capable of acting as command-and-control servers for the entire botnet.
Mirai Command-and-Control Botnet Security Mirai Botnet is a centrally managed botnet, where individual botnet nodes are able to exchange messages with a shared Command and Control server over TCP port 23.
OCSP over HTTP Security The Online Certificate Status Protocol (OCSP) is an Internet protocol used for obtaining the revocation status of an X.509 digital certificate. It is described in RFC 6960 and is on the Internet standards track. It was created as an alternative to certificate revocation lists (CRL), specifically addressing certain problems associated with using CRLs in a public key infrastructure (PKI). Messages communicated via OCSP are encoded in ASN.1 and are usually communicated over HTTP. The "request/response" nature of these messages leads to OCSP servers being termed OCSP responders. The certificates which are checked via OCSP can be configured via
OpenVPN Security OpenVPN is an open source software application that implements virtual private network (VPN) techniques for creating secure point-to-point or site-to-site connections in routed or bridged configurations and remote access facilities. It uses a custom security protocol that utilizes SSL/TLS for key exchange. It is capable of traversing network address translators (NATs) and firewalls.
Airbnb Social Networking/Search Airbnb is a rental site for lodging. Hosts offer their properties for rent, desscribing them with text and photos and setting up a calendar with the dates when the property is available. Once Airbnb has verified the host's identity guests can browse the site and book a stay. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Ali Social Networking/Search Emulates the use of the Alibaba website as of May 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Baidu Oct16 Social Networking/Search Emulates the use of the Baidu website as of October 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Baidutieba Jun16 Social Networking/Search Emulates the use of the BaiduTieba website as of June 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Bing Social Networking/Search This application represents Microsoft Bing search engine requests and responses.
Blogger Aug13 Social Networking/Search Emulates the use of the Blogspot website as of August 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
BuzzFeed Nov 16 Social Networking/Search BuzzFeed is a social news and entertainment web site where users can easily navigate to the latest items that are currently creating the most 'buzz'. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Candy Crush Saga Sep15 Social Networking/Search Emulates the use of the Candycrash website as of September 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Doodle Jul15 Social Networking/Search Doodle is a scheduling tool from Google, that helps people find common times for meetings. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Apr14 Social Networking/Search Emulates the use of the Facebook website as of April 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Facebook Apr15 Social Networking/Search Emulates the use of the Facebook website as of April 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Apr17 Social Networking/Search Emulates the use of the Facebook website as of April 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Aug14 Social Networking/Search Emulates the use of the Facebook website as of August 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Facebook Aug16 Social Networking/Search Emulates the use of the Facebook website as of August 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Aug17 Social Networking/Search Emulates the use of the Facebook website as of August 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Dec13 Social Networking/Search Evergreen Facebook Dec 13 This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Facebook Dec14 Social Networking/Search Emulates the use of the Facebook website as of December 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Facebook Dec17 Social Networking/Search Emulates the use of the Facebook website as of December 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Feb14 Social Networking/Search Emulates the use of the Facebook website as of February 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Facebook Feb15 Social Networking/Search Emulates the use of the Facebook website as of February 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Facebook Feb17 Social Networking/Search Emulates the use of the Facebook website as of February 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Jan14 Social Networking/Search Emulates the use of the Facebook website as of January 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Facebook Jan15 Social Networking/Search Emulates the use of the Facebook website as of January 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Facebook Jan17 Social Networking/Search Emulates the use of the Facebook website as of January 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Jan18 Social Networking/Search Emulates the use of the Facebook website as of January 2018. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions.
Evergreen Facebook Jul14 Social Networking/Search Emulates the use of the Facebook website as of July 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Facebook Jul17 Social Networking/Search Emulates the use of the Facebook website as of July 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Jun14 Social Networking/Search Emulates the use of the Facebook website as of June 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Facebook Jun17 Social Networking/Search Emulates the use of the Facebook website as of June 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Mar14 Social Networking/Search Emulates the use of the Facebook website as of March 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Facebook Mar17 Social Networking/Search Emulates the use of the Facebook website as of March 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook May15 Social Networking/Search Emulates the use of the Facebook website as of May 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook May17 Social Networking/Search Emulates the use of the Facebook website as of May 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Nov14 Social Networking/Search Emulates the use of the Facebook website as of November 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Facebook Nov15 Social Networking/Search Emulates the use of the Facebook website as of November 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Nov16 Social Networking/Search Emulates the use of the Facebook website as of November 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Nov17 Social Networking/Search Emulates the use of the Facebook website as of November 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Oct14 Social Networking/Search Emulates the use of the Facebook website as of October 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Facebook Oct16 Social Networking/Search Emulates the use of the Facebook website as of October 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Oct17 Social Networking/Search Emulates the use of the Facebook website as of October 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Sep15 Social Networking/Search Emulates the use of the Facebook website as of September 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Sep16 Social Networking/Search Emulates the use of the Facebook website as of September 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Facebook Sep17 Social Networking/Search Emulates the use of the Facebook website as of September 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Apr14 Social Networking/Search Emulates the use of the Twitter website as of April 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Twitter Apr15 Social Networking/Search Emulates the use of the Twitter website as of April 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Apr17 Social Networking/Search Emulates the use of the Twitter website as of April 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Aug14 Social Networking/Search Emulates the use of the Twitter website as of August 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Twitter Aug16 Social Networking/Search Emulates the use of the Twitter website as of August 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Aug17 Social Networking/Search Emulates the use of the Twitter website as of August 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Dec 13 Social Networking/Search Emulates the use of the twitter.com website as of December 2013. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Twitter Dec14 Social Networking/Search Emulates the use of the Twitter website as of December 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Twitter Dec16 Social Networking/Search Emulates the use of the Twitter website as of December 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Dec17 Social Networking/Search Emulates the use of the Twitter website as of December 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Feb14 Social Networking/Search Emulates the use of the Twitter website as of February 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Twitter Feb15 Social Networking/Search Emulates the use of the Twitter website as of February 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Twitter Feb17 Social Networking/Search Emulates the use of the Twitter website as of February 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Jan14 Social Networking/Search Emulates the use of the Twitter website as of January 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Twitter Jan15 Social Networking/Search Emulates the use of the Twitter website as of January 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Twitter Jan17 Social Networking/Search Emulates the use of the Twitter website as of January 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Jan18 Social Networking/Search Emulates the use of the Twitter website as of January 2018. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions.
Evergreen Twitter Jul14 Social Networking/Search Emulates the use of the Twitter website as of July 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Twitter Jul17 Social Networking/Search Emulates the use of the Twitter website as of July 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Jun14 Social Networking/Search Emulates the use of the Twitter website as of June 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Twitter Jun17 Social Networking/Search Emulates the use of the Twitter website as of June 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Mar14 Social Networking/Search Emulates the use of the Twitter website as of March 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Twitter Mar17 Social Networking/Search Emulates the use of the Twitter website as of March 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter May15 Social Networking/Search Emulates the use of the Twitter website as of May 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter May17 Social Networking/Search Emulates the use of the Twitter website as of May 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Nov14 Social Networking/Search Emulates the use of the Twitter website as of November 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Twitter Nov15 Social Networking/Search Emulates the use of the Twitter website as of November 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Nov16 Social Networking/Search Emulates the use of the Twitter website as of November 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Nov17 Social Networking/Search Emulates the use of the Twitter website as of November 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Oct14 Social Networking/Search Emulates the use of the Twitter website as of October 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Twitter Oct16 Social Networking/Search Emulates the use of the Twitter website as of October 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Oct17 Social Networking/Search Emulates the use of the Twitter website as of October 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Sep15 Social Networking/Search Emulates the use of the Twitter website as of September 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Sep16 Social Networking/Search Emulates the use of the Twitter website as of September 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Twitter Sep17 Social Networking/Search Emulates the use of the Twitter website as of September 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoo Groups Dec13 Social Networking/Search Emulates the use of the YahooGroups website as of December 2013. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoo Groups Jan14 Social Networking/Search Emulates the use of the YahooGroups website as of January 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen YahooGroups Apr14 Social Networking/Search Emulates the use of the YahooGroups website as of April 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen YahooGroups Feb14 Social Networking/Search Emulates the use of the YahooGroups website as of February 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen YahooGroups Jun14 Social Networking/Search Emulates the use of the YahooGroups website as of June 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen YahooGroups Mar14 Social Networking/Search Emulates the use of the YahooGroups website as of March 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen YahooGroups Oct17 Social Networking/Search Emulates the use of the YahooGroups website as of October 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups Apr15 Social Networking/Search Emulates the use of the YahooGroups website as of April 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups Apr17 Social Networking/Search Emulates the use of the YahooGroups website as of April 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups Aug16 Social Networking/Search Emulates the use of the YahooGroups website as of August 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups Aug17 Social Networking/Search Emulates the use of the YahooGroups website as of August 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups Dec14 Social Networking/Search Emulates the use of the YahooGroups website as of December 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoogroups Dec16 Social Networking/Search Emulates the use of the YahooGroups website as of December 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups Dec17 Social Networking/Search Emulates the use of the YahooGroups website as of December 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups Feb15 Social Networking/Search Emulates the use of the YahooGroups website as of February 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoogroups Feb17 Social Networking/Search Emulates the use of the YahooGroups website as of February 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups Jan15 Social Networking/Search Emulates the use of the YahooGroups website as of January 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoogroups Jan17 Social Networking/Search Emulates the use of the YahooGroups website as of January 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups Jan18 Social Networking/Search Emulates the use of the YahooGroups website as of January 2018. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions.
Evergreen Yahoogroups Jul17 Social Networking/Search Emulates the use of the YahooGroups website as of July 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups Jun17 Social Networking/Search Emulates the use of the YahooGroups website as of June 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups Mar17 Social Networking/Search Emulates the use of the YahooGroups website as of March 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups May15 Social Networking/Search Emulates the use of the YahooGroups website as of May 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups May17 Social Networking/Search Emulates the use of the YahooGroups website as of May 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups Nov14 Social Networking/Search Emulates the use of the YahooGroups website as of November 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoogroups Nov15 Social Networking/Search Emulates the use of the YahooGroups website as of November 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups Nov16 Social Networking/Search Emulates the use of the YahooGroups website as of November 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups Nov17 Social Networking/Search Emulates the use of the YahooGroups website as of November 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups Oct14 Social Networking/Search Emulates the use of the YahooGroups website as of October 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Evergreen Yahoogroups Sep15 Social Networking/Search Emulates the use of the YahooGroups website as of September 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups Sep16 Social Networking/Search Emulates the use of the YahooGroups website as of September 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evergreen Yahoogroups Sep17 Social Networking/Search Emulates the use of the YahooGroups website as of September 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Facebook Social Networking/Search Facebook is a social network whose aim is "to make the world more open and connected." Please note that the data produced by this flow is subject to the "Content Fidelity" setting within the Application Simulator and Client Simulator components. A content fidelity of "High" is appropriate for Super Flows intended for use in Client Simulator, while a content fidelity of "Normal" is better suited for Super Flows that enact both client and server messages.
Flickr Social Networking/Search Flickr is an image hosting and video hosting website owned by Yahoo. This protocol implements the following actions: 1. Flickr Login. 2. Fetching a user's home page. 3. Viewing photos. 4. Uploading a new photo. 5. Loading the galleries page. 6. Selecting and viewing a gallery.
Giphy Jan17 Social Networking/Search Emulates the use of the Giphy website as of January 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Google Analytics Aug16 Social Networking/Search Google Analytics is a freemium web analytics service offered by Google that tracks and reports website traffic. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Google Cache Jul16 Social Networking/Search Google takes a snapshot of each page it examines and caches (stores) that version as a back-up. The cached version is what Google uses to judge if a page is a good match for your query. Practically every search result includes a Cached link. Clicking on that link takes you to the Google cached version of that web page, instead of the current version of the page. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Google Calendar Aug14 Social Networking/Search Emulates the use of the Google Calendar website as of August 2014. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Google Earth Social Networking/Search Google Earth is a 3D mapping application for desktop and mobile devices. Version 6.2 on Windows Vista is emulated here.
Google Location Services Aug16 Social Networking/Search Google Location Services provides an estimated location of a client based on information about the WiFi routers and cell towers closest to the client, and the strength of their WiFi or cell signals. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Google Maps Social Networking/Search Google Maps is a web-based mapping application for desktop and mobile devices.
Google Plus Sept 17 Social Networking/Search Google Plus is an internet based social network that is owned and operated by Google. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Google Safe Browsing Aug16 Social Networking/Search Google Safe Browsing is a blacklist service provided by Google that provides lists of URLs for web resources that contain malware or phishing content. The Google Chrome, Apple Safari and Mozilla Firefox web browsers use the lists from the Google Safe Browsing service for checking pages against potential threats. Google also provides a public API for the service. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Google Search Social Networking/Search Google Search, a very popular web search engine that uses HTTP.
Google Translate Jun16 Social Networking/Search Google Translate is a free multilingual statistical machine translation service provided by Google to translate text from one language into another. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Google Voice Actions Aug16 Social Networking/Search Google Voice Actions let users quickly complete tasks in your app using voice commands. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Instagram Nov14 Social Networking/Search Instagram emulation based on November 2014 protocol. Instagram is a web based photo and video sharing site owned by Facebook. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
LinkedIn Dec17 Social Networking/Search LinkedIn is a social networking website used for professional networking, including employers posting jobs and job seekers posting their CVs. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Office 365 Outlook People Jul15 Social Networking/Search Emulates the use of the Office 365 Outlook People website as of July 2015. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Pinterest Jun17 Social Networking/Search Pinterest is a free photo sharing website. Users can upload, save, sort, and manage photos and videos by pinning them on private or public pinboards. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
RSS Social Networking/Search RSS (Really Simple Syndication) is an XML-based Web content syndication format. All RSS files must conform to the W3C XML 1.0 specification.
Reddit Social Networking/Search Reddit is a social news website where its users can submit content, in the form of a link or a text post. The system is effectively a Web based bulletin board.
Snapchat May15 Social Networking/Search Snapchat This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Snapdeal Sep16 Social Networking/Search Snapdeal is an online marketplace, based in New Delhi, India. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Tinder Sep16 Social Networking/Search Tinder is a location-based social search service application (using Facebook) that facilitates communication between mutually interested users, allowing matched users to chat. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Twitter Social Networking/Search Twitter is a real-time information network that connects a user to the latest stories, ideas, opinions and news about what they find interesting.
Uber Jun15 Social Networking/Search Uber This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Weibo Feb14 Social Networking/Search Sina Weibo, a China-based microblogging service. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Wikipedia Search Social Networking/Search Wikipedia is a free, collaboratively edited and multilingual Internet encyclopedia supported by the non-profit Wikimedia Foundation. This protocol provides actions which simulate the loading of the first Wikipedia web page followed by actions simulating an initial search from that page and then actions loading the resulting page. An "Open Search (incremental search)" action is also provided. The "General File Request/Response" and "General JavaScript Request/Response" actions are used to request and serve up the images and scripts which result from loading the various web pages.
Wordpress1310 Social Networking/Search wordpress is a free and open source blogging tool and content-management system. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Yahoo Search Social Networking/Search Yahoo Search, a WWW search engine owned and operated by Yahoo! Inc.
Yammer Nov 16 Social Networking/Search Yammer, Inc. is a freemium enterprise social network service that was launched in 2008 and sold to Microsoft in 2012. Yammer is used for private communication within organizations and is an example of enterprise social software. Access to a Yammer network is determined by a user's Internet domain so that only individuals with appropriate email addresses may join their respective networks. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evernote Apr17 Storage Emulates the use of Evernote Mobile iOS as of April 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Evernote Desktop Aug17 Storage Emulates the use of the Evernote Desktop website as of August 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Google Cloud Storage Sep16 Storage Google Cloud Storage is a RESTful online file storage web service for storing and accessing data on Google's infrastructure. The service combines the performance and scalability of Google's cloud with advanced security and sharing capabilities. It is an Infrastructure as a Service (IaaS), comparable to Amazon S3 online storage service. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Google Keep Jun16 Storage Google Keep is a note taking application developed by Google. It is available as a mobile app for the Android and iOS mobile operating systems and as a web application. This flow simulates the web application. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Google Photos Jul17 Storage Google Photos is a photo sharing and storage service developed by Google. It's was formerly a part of Google+. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
iCloud Web Storage This protocol emulates the Apple iCloud web based client. The protocol supports actions for the calendar, push, reminders, notes and contacts services.
Apache ZAB System/Network Admin The Apache ZooKeeper Atomic Broadcast (ZAB) is the protocol used by ZooKeeper to propagate state changes. ZooKeeper allows distributed processes to coordinate with each other through a shared hierarchal namespace which is organized similarly to a standard file system.
Border Gateway Protocol System/Network Admin This is the Border Gateway Protocol (BGP), version 4, as specified in RFC 4271. It is an inter-Autonomous System routing protocol.
CAPWAP System/Network Admin The Control And Provisioning of Wireless Access Points (CAPWAP) Protocol enables an Access Controller (AC) to manage a collection of Wireless Termination Points (WTPs).
Classic STUN System/Network Admin This application flow emulates a Simple Traversal of UDP through NAT (STUN, RFC 3489) session. Note that for sensible STUN messages, network and CIDR mask values should match the configured Network Neighborhood values.
DNS System/Network Admin This is the Domain Name System protocol, as described in RFCs 1034 and 1035.
Finger System/Network Admin The finger protocol is used to retrieve user account status from a remote system. [RFC 742]
Google App Engine Aug16 System/Network Admin Google App Engine is a platform for building scalable web applications and mobile backends. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Google Cloud Messaging System/Network Admin This protocol emulates the Google Cloud Messaging service, a free service that enables developers to send messages between servers and client apps. This includes downstream messages from servers to client apps, and upstream messages from client apps to servers.
Google Cloud Print Aug16 System/Network Admin Google Cloud Print is a Google service that was created to allow any Cloud-Print-aware application (web, desktop, mobile) on any device in the network cloud to print to any printer. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
HTTP/2 NP System/Network Admin Native support for HTTP/2. This flow is used to test the new L4 objects created to support native HTTP/2.
HTTP2 System/Network Admin HTTP/2 is a replacement for how HTTP is expressed “on the wire.†It is not a ground-up rewrite of the protocol; HTTP methods, status codes and semantics will be the same, and it should be possible to use the same APIs as HTTP/1.x (possibly with some small additions) to represent the protocol.
IDENT System/Network Admin This application flow emulates a client talking to an IDENT server [RFC 1413].
IGD System/Network Admin Internet Gateway Device (IGD) Standardized Device Control Protocol is a NAT Port Mapping Protocol (NAT-PMP) and is supported by an increasing number of NAT routers. It is a common communications protocol of automatically configuring port forwarding. This implements IGD version 1.0, WANConnectionDevice:1 and WANIPConnection:1.
IPFIX System/Network Admin A protocol used to export IP flow information [RFC 5101, RFC 5102 and RFC 5103].
IPMI System/Network Admin Intelligent Platform Management Interface emulation.
LDAP System/Network Admin Lightweight Directory Access Protocol (LDAP) emulation [RFC 4150].
McAfeeNetflow System/Network Admin McAfee Network Security Platform Netflow is a protocol used by McAfee IPS to export relevant network traffic statistics. The stats can either be generic or have detailed protocol information (Netbios, HTTP, FTP, Telnet, SMTP).
Microsoft Azure Nov16 System/Network Admin Microsoft Azure is a cloud computing platform and infrastructure created by Microsoft for building, deploying, and managing applications and services through a global network of Microsoft-managed data centers. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Microsoft Update System/Network Admin Simulate a Microsoft Software Update for a PC
Multicast DNS (Apple Bonjour) System/Network Admin Multicast Domain Name System (mDNS) is used to resolve host names to IP addresses within small networks that do not include a local name server. It is a zero configuration service, utilizing essentially the same programming interfaces, packet formats and operating semantics as the unicast Domain Name System (DNS)
NTP System/Network Admin Network Time Protocol (NTP) [RFC 5905].
NTPv2 System/Network Admin Implementation of Network Time Protocol (Version 2) as described in RFC 1119.
Netflow System/Network Admin A protocol used for collecting IP traffic information
OpenFlow System/Network Admin OpenFlow is a communications protocol that gives access to the forwarding plane of a network switch or router over the network.
Port Control Protocol System/Network Admin This flow emulates the Port Control Protocol (PCP). PCP allows an IPv4 or IPv6 host to control how incoming IPv6 of IPv4 packets are translated and forwarded by a network address translator (NAT) or simple firewalls, and also allows a host to optimize its outgoing NAT keepalive messages.
Port Control Protocol v2 System/Network Admin This flow emulates the Port Control Protocol (PCP) version 2. PCP allows an IPv4 or IPv6 host to control how incoming IPv6 of IPv4 packets are translated and forwarded by a network address translator (NAT) or simple firewalls, and also allows a host to optimize its outgoing NAT keepalive messages.
Portmapper System/Network Admin This is the v2 version of the Port Mapper [RFC 1833] protocol. In general, the responses to client requests will automatically fill in fields to match up automatically. You can over ride those response values if you need.
RIPv1 System/Network Admin Routing Information Protocol version 1
RIPv2 System/Network Admin Routing Information Protocol version 2.
RPC BIND (Portmap) System/Network Admin The RPC BIND (Portmap) Protocol maps RPC program and version numbers to universal addresses, thus making dynamic binding of remote programs possible. [RFC 1833]
RPC MOUNT System/Network Admin The RPC MOUNT Protocol is a UNIX-based application that uses TCP/IP for transport. It is used to initiate client access to a server supporting the Network File System (NFS) application. It handles local operating system specifics such as path name format and user authentication. [RFC 1813]
Rusers System/Network Admin The rusers command produces the list of hosts or all machines on the local network.
SNMPV1 System/Network Admin SNMPV1 (Simple Network Management Protocol, version 1) [RFC 1157] is used to query and configure networked devices with minimal protocol overhead.
SNMPV1 Traps System/Network Admin SNMPV1 (Simple Network Management Protocol, version 1) [RFC 1157] is used to query and configure networked devices with minimal protocol overhead. SNMPV1 Traps use port 162 as opposed to the rest of the messages which use port 161.
SNMPv2c System/Network Admin SNMPv2c (Simple Network Management Protocol, version 2) [RFC 1213] is used to query and configure networked devices with minimal protocol overhead.
SNMPv2c Traps and Informs System/Network Admin SNMPv2c (Simple Network Management Protocol, version 2) [RFC 1213] is used to query and configure networked devices with minimal protocol overhead. SNMPv2c Traps use port 162 as opposed to the rest of the messages which use port 161.
SSDP System/Network Admin SSDP is a text-based protocol based on HTTPU. It uses the User Datagram Protocol (UDP) as the underlying transport protocol. Services are announced by the hosting system with multicast addressing to a specifically designated IP multicast address at UDP port number 1900.
STUN2 System/Network Admin Emulates the STUN version 2 protocol, the latest update to Session Traversal Utilities for NAT.
Sun RPC System/Network Admin The Remote Procedure Call (RPC) system developed by Sun Microsystems for use with NIS and NFS.
Syslog System/Network Admin The BSD Syslog Protocol (RFC 3164) is used for the transmission of event notification messages across networks.
TeamViewer System/Network Admin TeamViewer is a proprietary computer software package for remote control, desktop sharing, online meetings, web conferencing and file transfer between computers.
Time System/Network Admin This application flow emulates a Time session. Note that Time (RFC 868) is distinct from other clock-synchronizing protocols, such as NTP.
WebSocket System/Network Admin The WebSocket Protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to communications from that code. The security model used for this is the origin-based security model commonly used by web browsers. The protocol consists of an opening handshake followed by basic message framing, layered over TCP. The goal of this technology is to provide a mechanism for browser-based applications that need two-way communication with servers that does not rely on opening multiple HTTP connections (e.g., using XMLHttpRequest or IFRAMEs and long polling).
iSCSI System/Network Admin This application flow emulates the iSCSI protocol using ext2/3 filesystems. Currently, no other filesystem types are supported.
GSM MAP Telephony/Cable TV Mobile application part (MAP) is the protocol that is used to allow the GSM network nodes within the Network Switching Subsystem (NSS) to communicate with each other to provide services, such as roaming capability, text messaging (SMS), and subscriber authentication. MAP is transported and encapsulated with the SS7 protocols MTP, SCCP, and TCAP.
H.225 Telephony/Cable TV H.225 is a part of the H.323 standard for streaming AV protocols, usually used to establish a session between two endpoints referred to as a "caller" (the client) and a "callee" (the server). The Call Identifier and Conference ID fields are written as 16 byte GUIDs, eg, "00112233-4455-6677-8899-aabbccddeeff," and unless otherwise specified, the Call Identifier will be equal to the Conference ID. The H.245 Connect Port will determine which port H.245 services are running on the callee.
H.225 RAS Telephony/Cable TV H.225 RAS provides gatekeeper discovery, endpoint registration, endpoint location, admission control and access tokens between H.323 endpoints and gatekeepers. Both terminals and gateways are considered H.323 endpoints.
H.245 Telephony/Cable TV This application flow emulates an H.245 session set up, part of the H.323 suite of protocols. Note that there is no well-known port for H.245; instead, leave it unselected to pick up the port specified by a companion H.225 flow (otherwise, 0 will indicate a random server port).
H.248 Telephony/Cable TV The H248 protocol defines the interaction between Media Gateway Controllers and Media Gateways in order to support multimedia streams across networks.
MMS MM1 Telephony/Cable TV Multimedia Messaging Service MM1 Protocol version 1.0
S102 Telephony/Cable TV This protocol emulates the stage 3 of the Evolved Packet System S102 interface between the MME and the 1x CS IWS which relays the 1xCS signalling messages documented in 3GPP TS 23.216 [2] and 3GPP TS 23.272 [4]. 1x CS signalling messages are those messages that are defined for A21 interface as described in 3GPP2 A.S0008-D [3] and 3GPP2 A.S0009-D [6]. The S102 interface messages are based on A21 messages. This protocol is used to support UEs that do not transmit and receive on both the LTE and 1x radio interfaces simultaneously.
SMPP Telephony/Cable TV This flow emulates SMS text messaging using the SMPP protocol.
TR-069 Telephony/Cable TV This application flow emulates the TR-069 CWMP v1.1 protocol
TS 3GPP LI Telephony/Cable TV 3GPP Handover interface for Lawful Interception (LI) This protocol emulate CALEA Lawful Intercept Tpkt traffic. This includes the Mediation Device to Collection Function UMTS IRI and CC data as described in TS 133 108 V11.4.0 (2012-10). Note: This protocol usually runs on flows that have the "L7 Transport" parameter set to "TPKT".
Chargen Testing and Measurement Chargen sends a repeating pattern of bytes to the connected client [RFC 864]. The "Chargen Pattern" field may be used to configure a custom pattern.
Custom Application Testing and Measurement This is for creating custom user-defined protocols and applications.
Daytime Testing and Measurement The Daytime protocol provides an ASCII string of the current time in a format determind by the server [RFC 867]. Note that Daytime is distinct from other clock-synchronizing protocols, such as NTP.
Discard Testing and Measurement Discard is a diagnostic protocol used by clients to send data which is discarded by the server. [RFC 863]
Echo Testing and Measurement The echo service is a diagnostic service in which the server replies to the client with the same data that the client sent. [RFC 862]
OWAMP Control Testing and Measurement One-Way Active Measurement Control Protocol [RCF 4656].
OWAMP Test Testing and Measurement One-Way Active Measurement Test Protocol [RFC 4656].
Quote of the Day Testing and Measurement Quote of the Day protocol is a useful debugging and measurement tool. The service simply sends a short message without regard to the input. [RFC 865]
SNMPv3 Testing and Measurement Simple Network Management Protocol Version 3 (SNMPv3) is an Internet-standard protocol for collecting and organizing information about managed devices on IP networks and for modifying that information to change device behavior. Version 3 adds cryptographic security. This protocol simulation uses the User-based Security Model (USM) security model. Note that one can set the engine name, user name and authentication parameters in Wireshark under the Protocol Preferences for SNMP. This allows Wireshark to decode the encrypted PDU.
TWAMP Control Testing and Measurement Two-Way Active Measurement Protocol ( RFC 5357 ) provides a common protocol for measuring two-way metrics between network devices. TWAMP consists of two inter-related protocols: TWAMP-Control and TWAMP-Test. TWAMP-Control is used to initiate, start, and stop test sessions, whereas TWAMP-Test is used to exchange test packets between two TWAMP entities.
TWAMP Test Testing and Measurement Two-Way Active Measurement Protocol ( RFC 5357 ) provides a common protocol for measuring two-way metrics between network devices. TWAMP consists of two inter-related protocols: TWAMP-Control and TWAMP-Test. TWAMP-Test is used to exchange test packets between two TWAMP entities, whereas TWAMP-Control is used to initiate, start, and stop test sessions.
050 plus Voice/Video/Media 050 plus is an IP phone application for smartphones which allows you to make audio calls from your Smartphone via a special phone number starting with 050, so you can make and receive calls to mobiles and landlines.
Amazon Video Voice/Video/Media Emulates the use of Amazon Video as of March 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Ares Voice/Video/Media This flow emulates an Ares client communicating with its p2p network. It uses v2.1.8 by default.
BBC iPlayer Voice/Video/Media An HHTP-based protocol simulation of BBC iPlayer traffic.
BBC iPlayer Radio Voice/Video/Media An HHTP-based protocol simulation of BBC iPlayer Radio traffic.
Bearer Independent Call Control Voice/Video/Media BICC is an ISDN signaling protocol based on ITU Q.1901.
Dailymotion Aug17 Voice/Video/Media The use of the Dailymotion website as of August 2017. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Facetime Voice/Video/Media FaceTime is a Video Telephony and a Voice over IP (VOIP) software application and related protocols, developed by Apple Inc. for supported mobile devices running iOS and Macintosh computers running Mac OS X 10.6.6 onwards.
Fring Voice/Video/Media This is the Fring VOIP and Video Chat protocol for mobile devices.
GoToMeeting Oct16 Voice/Video/Media GoToMeeting is a web-hosted service created and marketed by the Online Services division of Citrix Systems. It is an online meeting, desktop sharing, and video conferencing software that enables the user to meet with other computer users, customers, clients or colleagues via the Internet in real time. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
HBO Now Oct16 Voice/Video/Media HBO Now video streaming. This emulation includes the HTTP streaming used for the video. The HTTP and HTTPS used for login/logout, advertise placement, movie selection and selected playback control is also included. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
HTTP Live Streaming Voice/Video/Media HLS - an HTTP-based media streaming communications protocol implemented by Apple Inc. as part of their QuickTime X and iPhone software systems. See http://tools.ietf.org/html/draft-pantos-http-live-streaming-07 or later versions for protocol details.
Hulu Desktop Voice/Video/Media Hulu video streaming to a desktop. This emulation includes the RTMPE streaming used for the video. The HTTP and HTTPS used for login/logout, advertise placement, movie selection and selected playback control is also included. Note that the host and flows needed for RTMPE will be dynamically created. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
IAX2 Voice/Video/Media The Inter-Asterisk eXchange protocol, version 2 (IAX2, RFC 5456) is an application-layer control and media protocol for creating, modifying, and terminating multimedia sessions over Internet Protocol (IP) networks.
JSEP Voice/Video/Media WebRTC is an open framework for the web that enables Real Time Communications in the browser. It includes the fundamental building blocks for high quality communications on the web such as network, audio and video components used in voice and video chat applications. The Javascript Session Establishment Protocol (JSEP) is the mechanism for allowing a Javascript application to fully control the signaling plane of a multimedia session via the interface specified in the W3C RTCPeerConnection API.
Kodi Sep17 Voice/Video/Media Kodi is a free and open-source media player that allows users to play and view digital media files from local and network storage media and the Internet. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Lync Audio/Video Voice/Video/Media Emulation of a Lync audio video session between two peers.
MGCP Voice/Video/Media The Media Gateway Control Protocol (MGCP) is a text-based Application Layer protocol used for call setup and call control between the media gateway and the media gateway controller (MGC).
MPEG-TS Voice/Video/Media This protocol emulates an MPEG transport stream running over UDP. MPEG-TS is a standard container format defined in ISO/IEC 13818-1, ITU-T Recommendation H.222.0
MSNP Voice/Video/Media The Microsoft Notification Protocol (MSNP version 21) is used by entities that communicate over the MSN Messenger network. The MSN Messenger network is used to transfer data regarding presence and instant messaging. The Microsoft's Windows Live Messenger application uses MSNP.
MSRP Voice/Video/Media MSRP (Message Session Relay Protocol) is a protocol for transmitting a series of related instant messages in the context of a communications session. An application instantiates the session with the Session Description Protocol (SDP) over Session Initiation Protocol (SIP) or other rendezvous methods.
Microsoft Smooth Streaming Voice/Video/Media The IIS Smooth Streaming Transport Protocol provides a means of delivering media from servers to clients in a way that can be cached by standard HTTP cache proxies in the communication chain. Allowing standard HTTP cache proxies to respond to requests on behalf of the server increases the number of clients that can be served by a single server.
Netflix Jul17 Voice/Video/Media Netflix is a subscription based provider of streaming media and video-on-demand. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Netflix Streaming Voice/Video/Media Emulate Netflix streaming via Silverlight or various hardware devices.
Niconico Nov13 Voice/Video/Media This flow simulates the use of the Niconico website (formerly known as Nico Nico Douga) as of November 2013. It supports logging in and out, playing video files and posting comments about the files as well as uploading video. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
Pandora Voice/Video/Media Pandora Internet Radio (also known as Pandora Radio or simply Pandora) is an automated music recommendation service and 'custodian' of the Music Genome Project. The service plays musical selections of a certain genre based on the user's artist selection. The user then provides positive or negative feedback for songs chosen by the service, which are taken into account when Pandora selects future songs.
Pandora iPhone Voice/Video/Media Pandora (iPhone). This app simulates Pandora Internet Radio running on an Apple iPhone. It is a music streaming and automated music recommendation service. This simulation includes the following actions: 'Start Pandora App', 'Change Tracks', 'Thumbs Up', 'Pause', 'Unpause', 'Skip Track', 'Select Options Screen', 'Bookmark Selection', 'Select Station Menu', 'Select Shuffle', 'Return from Shuffle', 'Turn on Shuffle', 'Show Lyrics', 'Thumbs Down', 'Hit Stations Button', 'Hit Feed Button'. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the superflow to disable this feature.
RTCP Voice/Video/Media The RTP Control Protocol (RTCP) [RFC 3550] provides statistics for an accompanying RTP flow. The functions of this protocol are providing statistics, lost packet counts, jitter, and latency.
RTMP Chunk Voice/Video/Media Real Time Messaging Chunk Stream. This is an underlying protocol that is used by RTMP.
RTMP Over TCP Voice/Video/Media Real Time Messaging Protocol. This is an Adobe protocol used primarily for video and audio streams, i.e. flash.
RTP Voice/Video/Media The Realtime Transfer Protocol (RTP) [RFC 3550] is used primarily as a carrier stream for VoIP sessions, though it does have other multimedia streaming uses.
RTSP Voice/Video/Media The Real Time Streaming Protocol (RTSP) is an application-layer protocol used to control the delivery of continuous data in real time. Data sources can be real-time or stored. RTSP is typically used to manage the delivery of audio and video streams over the Internet, via the Real Time Protocol (RTP). RTSP is described in detail by RFC 2326. This implementation emulates session establishment and teardown, stream parameter management and capability negotiation.
SCCP Voice/Video/Media A skinny protocol used for office telephone operations.
SIP Voice/Video/Media The Session Initiation Protocol (SIP) [RFC 3261] is an application-layer control (signaling) protocol for creating, modifying, and terminating multimedia sessions such as Internet telephone calls and multimedia distribution.
SaavnMusic Feb16 Voice/Video/Media Saavn, LLC is a digital distributor of English, Bollywood and regional Indian music in over 200 countries. It offers free music search and streaming supported by display advertisements. This app emulates the use of the Saavn Music website as of February 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Skype Voice/Video/Media This is a simulation of the Skype protocol.
Skype UDP Helper Voice/Video/Media This is a simulation of the Skype protocol.
Skype for Business Nov17 Voice/Video/Media Skype for Business is a unified communications platform targeted to businesses. Its main features include instant messaging, voice over IP, voicemail, file transfers, video conferencing, web conferencing and email. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Skype for Web Jul17 Voice/Video/Media Skype for Web is a audio and video chat application that can be run in a Web browser. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
SkypeV5 Voice/Video/Media This is a simulation of the Skype protocol, version 5.x.
Slingbox Streaming Voice/Video/Media This simulates streaming from a Slingbox hardware device.
Spotify Voice/Video/Media Spotify is a Swedish commercial music streaming, podcast and video service that provides digital rights management-protected content from record labels and media companies.
StandardMedia Mar16 Voice/Video/Media Standard Media is a media website with the head office located in Kenya, that provides local news and from around the world, from different areas of interest. This app emulates the use of the Standard Media website as of March 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Tango Voice/Video/Media Tango VoIP and Video Chat Protocol. Tango allows sending text messages, making voice calls and video calls to anyone around the world, provided they also use Tango.
TvAnts Voice/Video/Media TvAnts (Live streaming over P2P). A protocol for streaming video and audio broadcasts using peer to peer networking. TvAnts has been renamed to CCAnts (see www.ccants.com).
Twitch.tv Voice/Video/Media Emulates the use of Twitch.tv as of February 2016. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
VLC HTTP Voice/Video/Media VLC is the common name for the VLC media player. It is an open-source media player and streaming media server which can stream many different types of audio and video files as well as other file types over many different protocols. In this simulation files are streamed over HTTP.
WebEx Dec17 Voice/Video/Media WebEx audio/video meeting with content sharing and chat. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
YouTube Sep16 Voice/Video/Media YouTube is an American video-sharing website headquartered in San Bruno, California, United States that operates as one of Google's subsidiaries. The site allows users to upload, view, rate, share and comment on videos. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.
Zalo May17 Voice/Video/Media Zalo is an application for mobile devices that allows its users to send and receive messages including photos, videos, and contact information. This protocol uses dynamically created flows to simulate the various internal actions performed by a modern Web browser. Because these dynamic flows may be large in number and may contain a large amount of generated data, profile creation and test initialization may require a considerable amount of time. The "Max. Request/Response Pairs per Action" and "Max. Generated File Size" flow parameters can be used to control the number and size of the interactions performed by the actions. DNS resolution is always performed for each host. Delete the DNS host from the Super Flow to disable this feature.