Find research datasets worth reusing

DoH-Gen-F-AABBC

<p><strong>Please refer to the original data article for further data description:</strong> <a href="https://doi.org/10.1016/j.dib.2022.108310">Jeřábek & Hynek et al., Collection of datasets with DNS over HTTPS traffic In: Data in Brief Journal</a> ,DOI:<a href="https://doi.org/10.1016/j.dib.2022.108310">10.1016/j.dib.2022.108310</a></p> <p><strong>Dataset of DNS over HTTPS traffic  from Firefox </strong><em>(AdGuard, AhaDNS, BlahDNS, BraveDNS, CloudFlare)</em><br> The dataset contains DoH and HTTPS traffic that was captured in a virtualized environment (Docker) and generated automatically by Firefox browser with enabled DoH towards 5 different DoH servers (AdGuard, AhaDNS, BlahDNS, BraveDNS, CloudFlare) and a web page loads towards a sample of web pages taken from Majestic Million dataset. The data are provided in the form of PCAP files. However, we also provided TLS enriched flow data that are generated with opensource [ipfixprobe](https://github.com/CESNET/ipfixprobe) flow exporter. Other than TLS related information is not relevant since the dataset comprises only encrypted TLS traffic. The TLS enriched flow data are provided in the form of CSV files with the following columns:</p> <table> <thead> <tr> <th>Column Name</th> <th>Column Description</th> </tr> </thead> <tbody> <tr> <td>DST_IP</td> <td>Destination IP address</td> </tr> <tr> <td>SRC_IP</td> <td>Source IP address</td> </tr> <tr> <td>BYTES</td> <td>The number of transmitted bytes from Source to Destination</td> </tr> <tr> <td>BYTES_REV</td> <td>The number of transmitted bytes from Destination to Source</td> </tr> <tr> <td>TIME_FIRST</td> <td>Timestamp of the first packet in the flow in format YYYY-MM-DDTHH-MM-SS</td> </tr> <tr> <td>TIME_LAST</td> <td>Timestamp of the last packet in the flow in format YYYY-MM-DDTHH-MM-SS</td> </tr> <tr> <td>PACKETS</td> <td>The number of packets transmitted from Source to Destination</td> </tr> <tr> <td>PACKETS_REV</td> <td>The number of packets transmitted from Destination to Source</td> </tr> <tr> <td>DST_PORT</td> <td>Destination port</td> </tr> <tr> <td>SRC_PORT</td> <td>Source port</td> </tr> <tr> <td>PROTOCOL</td> <td>The number of transport protocol</td> </tr> <tr> <td>TCP_FLAGS</td> <td>Logic OR across all TCP flags in the packets transmitted from Source to Destination</td> </tr> <tr> <td>TCP_FLAGS_REV</td> <td>Logic OR across all TCP flags in the packets transmitted from Destination to Source</td> </tr> <tr> <td>TLS_ALPN</td> <td>The Value of Application Protocol Negotiation Extension sent from Server</td> </tr> <tr> <td>TLS_JA3</td> <td>The JA3 fingerprint</td> </tr> <tr> <td>TLS_SNI</td> <td>The value of Server Name Indication Extension sent by Client</td> </tr> </tbody> </table> <p>The DoH resolvers in the dataset can be identified by IP addresses written in <strong><em>doh_resolver_ip.csv </em></strong>file.</p> <p>The main part of the dataset is located in <strong>DoH-Gen-F-AABBC</strong><strong><em>.tar.gz </em></strong>and has the following structure:</p> <p> </p> <pre><code>. └─── data | - Main directory with data └── generated | - Directory with generated captures ├── pcap | - Generated PCAPs │ └── firefox └── tls-flow-csv | - Generated CSV flow data └── firefox</code></pre> <p> </p> <p><strong>Total stats of generated data:</strong></p> <table> <thead> <tr> <th>Name</th> <th>Value</th> </tr> </thead> <tbody> <tr> <td>Total Data Size</td> <td>40.2 GB</td> </tr> <tr> <td>Total files</td> <td>10</td> </tr> <tr> <td>DoH extracted tls flows</td> <td>~57 K</td> </tr> <tr> <td>Non-DoH extracted tls flows</td> <td>~327 K</td> </tr> </tbody> </table> <p><strong>DoH Server information</strong></p> <table> <thead> <tr> <th>Name</th> <th>Provider</th> <th>DoH query url</th> </tr> </thead> <tbody> <tr> <td>AdGuard</td> <td><a href="https://adguard-dns.com">https://adguard-dns.com</a></td> <td><a href="https://dns.adguard.com/dns-query">https://dns.adguard.com/dns-query</a></td> </tr> <tr> <td>AhaDNS</td> <td><a href="https://ahadns.com">https://ahadns.com</a></td> <td><a href="https://doh.it.ahadns.net/dns-query">https://doh.it.ahadns.net/dns-query</a></td> </tr> <tr> <td>BlahDNS</td> <td><a href="https://blahdns.com">https://blahdns.com</a></td> <td><a href="https://doh-de.blahdns.com/dns-query">https://doh-de.blahdns.com/dns-query</a></td> </tr> <tr> <td>BraveDNS</td> <td><a href="https://brave.com">https://brave.com</a></td> <td><a href="https://basic.bravedns.com">https://basic.bravedns.com</a></td> </tr> <tr> <td>CloudFlare</td> <td><a href="https://www.cloudflare.com">https://www.cloudflare.com</a></td> <td><a href="https://cloudflare-dns.com/dns-query">https://cloudflare-dns.com/dns-query</a></td> </tr> </tbody> </table> <p>Please cite the original article:</p> <pre><code>@article{Jerabek2022, title = {Collection of datasets with DNS over HTTPS traffic}, journal = {Data in Brief}, volume = {42}, pages = {108310}, year = {2022}, issn = {2352-3409}, doi = {https://doi.org/10.1016/j.dib.2022.108310}, url = {https://www.sciencedirect.com/science/article/pii/S2352340922005121}, author = {Kamil Jeřábek and Karel Hynek and Tomáš Čejka and Ondřej Ryšavý} }</code></pre>

DoH-Gen-C-AABBCC

<p>Dataset of DNS over HTTPS traffic (AdGuard, AhaDNS, BlahDNS, BraveDNS, Comcast, CZNIC)</p> <p>The dataset contains DoH and HTTPS traffic that was captured in controlled environment and generated automatically by Chrome browser with enabled DoH towards 6 different DoH servers (AdGuard, AhaDNS, BlahDNS, BraveDNS, Comcast, CZNIC) and a web page loads towards a sample of web pages taken from Majestic Million dataset. The data are provided in the form of PCAP files. However, we also provided TLS enriched flow data that are generated with opensource <a href="https://github.com/CESNET/ipfixprobe">ipfixprobe</a> flow exporter. Other than TLS related information is not relevant since the dataset comprises only encrypted TLS traffic. The TLS enriched flow data are provided in the form of CSV files with the following columns:</p> <table> <thead> <tr> <th>Column Name</th> <th>Column Description</th> </tr> </thead> <tbody> <tr> <td>DST_IP</td> <td>Destination IP address</td> </tr> <tr> <td>SRC_IP</td> <td>Source IP address</td> </tr> <tr> <td>BYTES</td> <td>The number of transmitted bytes from Source to Destination</td> </tr> <tr> <td>BYTES_REV</td> <td>The number of transmitted bytes from Destination to Source</td> </tr> <tr> <td>TIME_FIRST</td> <td>Timestamp of the first packet in the flow in format YYYY-MM-DDTHH-MM-SS</td> </tr> <tr> <td>TIME_LAST</td> <td>Timestamp of the last packet in the flow in format YYYY-MM-DDTHH-MM-SS</td> </tr> <tr> <td>PACKETS</td> <td>The number of packets transmitted from Source to Destination</td> </tr> <tr> <td>PACKETS_REV</td> <td>The number of packets transmitted from Destination to Source</td> </tr> <tr> <td>DST_PORT</td> <td>Destination port</td> </tr> <tr> <td>SRC_PORT</td> <td>Source port</td> </tr> <tr> <td>PROTOCOL</td> <td>The number of transport protocol</td> </tr> <tr> <td>TCP_FLAGS</td> <td>Logic OR across all TCP flags in the packets transmitted from Source to Destination</td> </tr> <tr> <td>TCP_FLAGS_REV</td> <td>Logic OR across all TCP flags in the packets transmitted from Destination to Source</td> </tr> <tr> <td>TLS_ALPN</td> <td>The Value of Application Protocol Negotiation Extension sent from Server</td> </tr> <tr> <td>TLS_JA3</td> <td>The JA3 fingerprint</td> </tr> <tr> <td>TLS_SNI</td> <td>The value of Server Name Indication Extension sent by Client</td> </tr> </tbody> </table> <p>The DoH resolvers in the dataset can be identified by IP addresses written in <strong><em>doh_resolver_ip.csv </em></strong>file.</p> <p>The main part of the dataset is located in <strong><em>DoH-Gen-C-AABBCC.tar.gz </em></strong>and has the following structure:</p> <pre><code>. └─── data | - Main directory with data └── generated | - Directory with generated captures ├── pcap | - Generated PCAPs │ └── chrome └── tls-flow-csv | - Generated CSV flow data └── chrome</code></pre> <p> </p> <p><strong>Total stats of generated data:</strong></p> <table> <thead> <tr> <th>Name</th> <th>Value</th> </tr> </thead> <tbody> <tr> <td>Total Data Size</td> <td>39.9 GB</td> </tr> <tr> <td>Total files</td> <td>12</td> </tr> <tr> <td>DoH extracted tls flows</td> <td>~35 K</td> </tr> <tr> <td>Non-DoH extracted tls flows</td> <td>~247 K</td> </tr> </tbody> </table> <p> </p> <p><strong>DoH Server information</strong></p> <p> </p> <table> <thead> <tr> <th>Name</th> <th>Provider</th> <th>DoH query url</th> </tr> </thead> <tbody> <tr> <td>AdGuard</td> <td><a href="https://adguard-dns.com">https://adguard-dns.com</a></td> <td><a href="https://dns.adguard.com/dns-query">https://dns.adguard.com/dns-query</a></td> </tr> <tr> <td>AhaDNS</td> <td><a href="https://ahadns.com">https://ahadns.com</a></td> <td><a href="https://doh.it.ahadns.net/dns-query">https://doh.it.ahadns.net/dns-query</a></td> </tr> <tr> <td>BlahDNS</td> <td><a href="https://blahdns.com">https://blahdns.com</a></td> <td><a href="https://doh-de.blahdns.com/dns-query">https://doh-de.blahdns.com/dns-query</a></td> </tr> <tr> <td>BraveDNS</td> <td><a href="https://brave.com">https://brave.com</a></td> <td><a href="https://basic.bravedns.com">https://basic.bravedns.com</a></td> </tr> <tr> <td>Comcast</td> <td><a href="https://corporate.comcast.com">https://corporate.comcast.com</a></td> <td><a href="https://doh.xfinity.com/dns-query">https://doh.xfinity.com/dns-query</a></td> </tr> <tr> <td>CZNIC</td> <td><a href="https://www.nic.cz">https://www.nic.cz</a></td> <td><a href="https://odvr.nic.cz/doh">https://odvr.nic.cz/doh</a></td> </tr> </tbody> </table> <p> </p>

DoH-Gen-F-FGHOQS

<p><strong>Please refer to the original data article for further data description:</strong> <a href="https://doi.org/10.1016/j.dib.2022.108310">Jeřábek & Hynek et al., Collection of datasets with DNS over HTTPS traffic In: Data in Brief Journal</a> ,DOI:<a href="https://doi.org/10.1016/j.dib.2022.108310">10.1016/j.dib.2022.108310</a></p> <p><strong>Dataset of DNS over HTTPS traffic from Firefox </strong><em>(FFMuc, Google, Hostux, OpenDNS Quad9, Switch)</em><br> The dataset contains DoH and HTTPS traffic that was captured in a virtualized environment (Docker) and generated automatically by Firefox browser with enabled DoH towards 6 different DoH servers (FFMuc, Google, Hostux, OpenDNS Quad9, Switch) and a web page loads towards a sample of web pages taken from Majestic Million dataset. The data are provided in the form of PCAP files. However, we also provided TLS enriched flow data that are generated with opensource <a href="https://github.com/CESNET/ipfixprobe">ipfixprobe</a> flow exporter. Other than TLS related information is not relevant since the dataset comprises only encrypted TLS traffic. The TLS enriched flow data are provided in the form of CSV files with the following columns:</p> <table> <thead> <tr> <th>Column Name</th> <th>Column Description</th> </tr> </thead> <tbody> <tr> <td>DST_IP</td> <td>Destination IP address</td> </tr> <tr> <td>SRC_IP</td> <td>Source IP address</td> </tr> <tr> <td>BYTES</td> <td>The number of transmitted bytes from Source to Destination</td> </tr> <tr> <td>BYTES_REV</td> <td>The number of transmitted bytes from Destination to Source</td> </tr> <tr> <td>TIME_FIRST</td> <td>Timestamp of the first packet in the flow in format YYYY-MM-DDTHH-MM-SS</td> </tr> <tr> <td>TIME_LAST</td> <td>Timestamp of the last packet in the flow in format YYYY-MM-DDTHH-MM-SS</td> </tr> <tr> <td>PACKETS</td> <td>The number of packets transmitted from Source to Destination</td> </tr> <tr> <td>PACKETS_REV</td> <td>The number of packets transmitted from Destination to Source</td> </tr> <tr> <td>DST_PORT</td> <td>Destination port</td> </tr> <tr> <td>SRC_PORT</td> <td>Source port</td> </tr> <tr> <td>PROTOCOL</td> <td>The number of transport protocol</td> </tr> <tr> <td>TCP_FLAGS</td> <td>Logic OR across all TCP flags in the packets transmitted from Source to Destination</td> </tr> <tr> <td>TCP_FLAGS_REV</td> <td>Logic OR across all TCP flags in the packets transmitted from Destination to Source</td> </tr> <tr> <td>TLS_ALPN</td> <td>The Value of Application Protocol Negotiation Extension sent from Server</td> </tr> <tr> <td>TLS_JA3</td> <td>The JA3 fingerprint</td> </tr> <tr> <td>TLS_SNI</td> <td>The value of Server Name Indication Extension sent by Client</td> </tr> </tbody> </table> <p>The DoH resolvers in the dataset can be identified by IP addresses written in <strong><em>doh_resolver_ip.csv </em></strong>file.</p> <p>The main part of the dataset is located in <strong><em>DoH-Gen-F-FGHOQS.tar.gz </em></strong>and has the following structure:</p> <p> </p> <pre><code>. └─── data | - Main directory with data └── generated | - Directory with generated captures ├── pcap | - Generated PCAPs │ └── firefox └── tls-flow-csv | - Generated CSV flow data └── firefox</code></pre> <p> </p> <p><strong>Total stats of generated data:</strong></p> <table> <thead> <tr> <th>Name</th> <th>Value</th> </tr> </thead> <tbody> <tr> <td>Total Data Size</td> <td>46.7 GB</td> </tr> <tr> <td>Total files</td> <td>12</td> </tr> <tr> <td>DoH extracted tls flows</td> <td>~98 K</td> </tr> <tr> <td>Non-DoH extracted tls flows</td> <td>~353 K</td> </tr> </tbody> </table> <p><strong>DoH Server information</strong></p> <table> <thead> <tr> <th>Name</th> <th>Provider</th> <th>DoH query url</th> </tr> </thead> <tbody> <tr> <td>FFMuc</td> <td><a href="https://ffmuc.net">https://ffmuc.net</a></td> <td><a href="https://doh.ffmuc.net/dns-query">https://doh.ffmuc.net/dns-query</a></td> </tr> <tr> <td>Google</td> <td><a href="https://google.com">https://google.com</a></td> <td><a href="https://dns.google/dns-query">https://dns.google/dns-query</a></td> </tr> <tr> <td>Hostux</td> <td><a href="https://dns.hostux.net/en/">https://dns.hostux.net/en/</a></td> <td><a href="https://dns.hostux.net/dns-query">https://dns.hostux.net/dns-query</a></td> </tr> <tr> <td>OpenDNS</td> <td><a href="https://www.opendns.com">https://www.opendns.com</a></td> <td><a href="https://doh.opendns.com/dns-query">https://doh.opendns.com/dns-query</a></td> </tr> <tr> <td>Quad9</td> <td><a href="https://www.quad9.net">https://www.quad9.net</a></td> <td><a href="https://dns.quad9.net/dns-query">https://dns.quad9.net/dns-query</a></td> </tr> <tr> <td>Switch</td> <td><a href="https://www.switch.ch">https://www.switch.ch</a></td> <td><a href="https://dns.switch.ch/dns-query">https://dns.switch.ch/dns-query</a></td> </tr> </tbody> </table> <p> </p> <p>Please cite the original article:</p> <pre><code>@article{Jerabek2022, title = {Collection of datasets with DNS over HTTPS traffic}, journal = {Data in Brief}, volume = {42}, pages = {108310}, year = {2022}, issn = {2352-3409}, doi = {https://doi.org/10.1016/j.dib.2022.108310}, url = {https://www.sciencedirect.com/science/article/pii/S2352340922005121}, author = {Kamil Jeřábek and Karel Hynek and Tomáš Čejka and Ondřej Ryšavý} }</code></pre>

DoH-Gen-F-CCDDD

<p><strong>Dataset of DNS over HTTPS traffic from Firefox </strong><em>(Comcast, CZNIC, DNSForge, DSNSB, DOHli)</em><br> The dataset contains DoH and HTTPS traffic that was captured in a virtualized environment (Docker) and generated automatically by Firefox browser with enabled DoH towards 5 different DoH servers (Comcast, CZNIC, DNSForge, DSNSB, DOHli) and a web page loads towards a sample of web pages taken from Majestic Million dataset. The data are provided in the form of PCAP files. However, we also provided TLS enriched flow data that are generated with opensource [ipfixprobe](https://github.com/CESNET/ipfixprobe) flow exporter. Other than TLS related information is not relevant since the dataset comprises only encrypted TLS traffic. The TLS enriched flow data are provided in the form of CSV files with the following columns:</p> <table> <thead> <tr> <th>Column Name</th> <th>Column Description</th> </tr> </thead> <tbody> <tr> <td>DST_IP</td> <td>Destination IP address</td> </tr> <tr> <td>SRC_IP</td> <td>Source IP address</td> </tr> <tr> <td>BYTES</td> <td>The number of transmitted bytes from Source to Destination</td> </tr> <tr> <td>BYTES_REV</td> <td>The number of transmitted bytes from Destination to Source</td> </tr> <tr> <td>TIME_FIRST</td> <td>Timestamp of the first packet in the flow in format YYYY-MM-DDTHH-MM-SS</td> </tr> <tr> <td>TIME_LAST</td> <td>Timestamp of the last packet in the flow in format YYYY-MM-DDTHH-MM-SS</td> </tr> <tr> <td>PACKETS</td> <td>The number of packets transmitted from Source to Destination</td> </tr> <tr> <td>PACKETS_REV</td> <td>The number of packets transmitted from Destination to Source</td> </tr> <tr> <td>DST_PORT</td> <td>Destination port</td> </tr> <tr> <td>SRC_PORT</td> <td>Source port</td> </tr> <tr> <td>PROTOCOL</td> <td>The number of transport protocol</td> </tr> <tr> <td>TCP_FLAGS</td> <td>Logic OR across all TCP flags in the packets transmitted from Source to Destination</td> </tr> <tr> <td>TCP_FLAGS_REV</td> <td>Logic OR across all TCP flags in the packets transmitted from Destination to Source</td> </tr> <tr> <td>TLS_ALPN</td> <td>The Value of Application Protocol Negotiation Extension sent from Server</td> </tr> <tr> <td>TLS_JA3</td> <td>The JA3 fingerprint</td> </tr> <tr> <td>TLS_SNI</td> <td>The value of Server Name Indication Extension sent by Client</td> </tr> </tbody> </table> <p>The DoH resolvers in the dataset can be identified by IP addresses written in <strong><em>doh_resolver_ip.csv </em></strong>file.</p> <p>The main part of the dataset is located in <strong><em>DoH-Gen-F-CCDDD.tar.gz </em></strong>and has the following structure:</p> <p> </p> <pre><code>. └─── data | - Main directory with data └── generated | - Directory with generated captures ├── pcap | - Generated PCAPs │ └── firefox └── tls-flow-csv | - Generated CSV flow data └── firefox</code></pre> <p> </p> <p><strong>Total stats of generated data:</strong></p> <table> <thead> <tr> <th>Name</th> <th>Value</th> </tr> </thead> <tbody> <tr> <td>Total Data Size</td> <td>40.2 GB</td> </tr> <tr> <td>Total files</td> <td>10</td> </tr> <tr> <td>DoH extracted tls flows</td> <td>~100 K</td> </tr> <tr> <td>Non-DoH extracted tls flows</td> <td>~315 K</td> </tr> </tbody> </table> <p><strong>DoH Server information</strong></p> <table> <thead> <tr> <th>Name</th> <th>Provider</th> <th>DoH query url</th> </tr> </thead> <tbody> <tr> <td>Comcast</td> <td><a href="https://corporate.comcast.com">https://corporate.comcast.com</a></td> <td><a href="https://doh.xfinity.com/dns-query">https://doh.xfinity.com/dns-query</a></td> </tr> <tr> <td>CZNIC</td> <td><a href="https://www.nic.cz">https://www.nic.cz</a></td> <td><a href="https://odvr.nic.cz/doh">https://odvr.nic.cz/doh</a></td> </tr> <tr> <td>DNSForge</td> <td><a href="https://dnsforge.de">https://dnsforge.de</a></td> <td><a href="https://dnsforge.de/dns-query">https://dnsforge.de/dns-query</a></td> </tr> <tr> <td>DNSSB</td> <td><a href="https://dns.sb/doh/">https://dns.sb/doh/</a></td> <td><a href="https://doh.dns.sb/dns-query">https://doh.dns.sb/dns-query</a></td> </tr> <tr> <td>DOHli</td> <td><a href="https://doh.li">https://doh.li</a></td> <td><a href="https://doh.li/dns-query">https://doh.li/dns-query</a></td> </tr> </tbody> </table> <p> </p>

DoH-Gen-C-DDD

<p><strong>NOTICE:</strong> The data file 0_chrome_dohli.pcap is corrupted and is not used in our articles that work with this dataset.</p> <p>Dataset of DNS over HTTPS traffic from Chrome Browser <em>(DNSForge, DSNSB, DOHli)</em></p> <p>The dataset contains DoH and HTTPS traffic that was captured in controlled environment and generated automatically by Chrome browser with enabled DoH towards 3 different DoH servers (DNSForge, DSNSB, DOHli) and a web page loads towards a sample of web pages taken from Majestic Million dataset. The data are provided in the form of PCAP files. However, we also provided TLS enriched flow data that are generated with opensource <a href="https://github.com/CESNET/ipfixprobe">ipfixprobe</a> flow exporter. Other than TLS related information is not relevant since the dataset comprises only encrypted TLS traffic. The TLS enriched flow data are provided in the form of CSV files with the following columns:</p> <table> <tbody><tr> <th>Column Name</th> <th>Column Description</th> </tr> </tbody><tbody> <tr> <td>DST_IP</td> <td>Destination IP address</td> </tr> <tr> <td>SRC_IP</td> <td>Source IP address</td> </tr> <tr> <td>BYTES</td> <td>The number of transmitted bytes from Source to Destination</td> </tr> <tr> <td>BYTES_REV</td> <td>The number of transmitted bytes from Destination to Source</td> </tr> <tr> <td>TIME_FIRST</td> <td>Timestamp of the first packet in the flow in format YYYY-MM-DDTHH-MM-SS</td> </tr> <tr> <td>TIME_LAST</td> <td>Timestamp of the last packet in the flow in format YYYY-MM-DDTHH-MM-SS</td> </tr> <tr> <td>PACKETS</td> <td>The number of packets transmitted from Source to Destination</td> </tr> <tr> <td>PACKETS_REV</td> <td>The number of packets transmitted from Destination to Source</td> </tr> <tr> <td>DST_PORT</td> <td>Destination port</td> </tr> <tr> <td>SRC_PORT</td> <td>Source port</td> </tr> <tr> <td>PROTOCOL</td> <td>The number of transport protocol</td> </tr> <tr> <td>TCP_FLAGS</td> <td>Logic OR across all TCP flags in the packets transmitted from Source to Destination</td> </tr> <tr> <td>TCP_FLAGS_REV</td> <td>Logic OR across all TCP flags in the packets transmitted from Destination to Source</td> </tr> <tr> <td>TLS_ALPN</td> <td>The Value of Application Protocol Negotiation Extension sent from Server</td> </tr> <tr> <td>TLS_JA3</td> <td>The JA3 fingerprint</td> </tr> <tr> <td>TLS_SNI</td> <td>The value of Server Name Indication Extension sent by Client</td> </tr> </tbody> </table> <p>The DoH resolvers in the dataset can be identified by IP addresses written in <strong><em>doh_resolver_ip.csv </em></strong>file.</p> <p>The main part of the dataset is located in <strong><em>DoH-Gen-C-DDD.tar.gz </em></strong>and has the following structure:</p> <pre><code>. └─── data | - Main directory with data └── generated | - Directory with generated captures ├── pcap | - Generated PCAPs │ └── chrome └── tls-flow-csv | - Generated CSV flow data └── chrome</code></pre> <p><strong>Total stats of generated data:</strong></p> <table> <tbody><tr> <th>Name</th> <th>Value</th> </tr> </tbody><tbody> <tr> <td>Total Data Size</td> <td>34.5 GB</td> </tr> <tr> <td>Total files</td> <td>6</td> </tr> <tr> <td>DoH extracted tls flows</td> <td>~15 K</td> </tr> <tr> <td>Non-DoH extracted tls flows</td> <td>~103 K</td> </tr> </tbody> </table> <p> </p> <p><strong>DoH Server information</strong></p> <p> </p> <table> <tbody><tr> <th>Name</th> <th>Provider</th> <th>DoH query url</th> </tr> </tbody><tbody> <tr> <td>DNSForge</td> <td><a href="https://dnsforge.de">https://dnsforge.de</a></td> <td><a href="https://dnsforge.de/dns-query">https://dnsforge.de/dns-query</a></td> </tr> <tr> <td>DNSSB</td> <td><a href="https://dns.sb/doh/">https://dns.sb/doh/</a></td> <td><a href="https://doh.dns.sb/dns-query">https://doh.dns.sb/dns-query</a></td> </tr> <tr> <td>DOHli</td> <td><a href="https://doh.li">https://doh.li</a></td> <td><a href="https://doh.li/dns-query">https://doh.li/dns-query</a></td> </tr> </tbody> </table> <p> </p> <p> </p> <p> </p>

opencc-zeroJan 2022View details →

FIG. 5. — Gryllobencain patrickmuelleri n. gen., n in A 100-million-year-old ensiferan with unusual mouthparts and comments on the evolution of raptorial appendages within Polyneoptera

FIG. 5. — Gryllobencain patrickmuelleri n. gen., n. sp., BUB 3073: A, overview in dorsal view; B, close-up in anterior head area with ocelli; C, overview in ventral view; D, close-up on distal part of thorax appendage 1. In A and C background was desaturated to enhance contrast. Abbreviations: an, antenna; ce, cercus; cl, claw of thorax appendage; f1-3, femur of thorax appendage 1-3; mp, maxillary palp; oc, ocelli; ta1, tarsus of thorax appendage 1; ti1-3, tibia of thorax appendage 1-3. Scale bars: A, C, 0.5 mm; B, D, 0.1 mm.

opencc-zeroJan 2022View details →

FIG. 6. — Gryllobencain patrickmuelleri n. gen., n in A 100-million-year-old ensiferan with unusual mouthparts and comments on the evolution of raptorial appendages within Polyneoptera

FIG. 6. — Gryllobencain patrickmuelleri n. gen., n. sp., BUB 3072: A, overview in dorsal view; B, close-up on cercus; C, overview in ventral view; D, close-up on head. Abbreviations: an, antenna; ce, cercus; f1, 3, femur of thorax appendage 1, 3; hc, head capsule; mp, maxillary palp; ti1, 3, tibia of thorax appendage 1, 3. Scale bars: A, C, 1 mm; B, D, 0.5 mm.

FIG. 7. — A in Integrative taxonomic studies on Rinacapritermes Amina & Rajmohana, n. gen. (Blattodea: Isoptera: Termitidae) with two new species from India

FIG. 7. — A, pronotum of Rinacapritermes silvius Amina & Rajmohana, n. gen., n. sp. soldier; B, pronotum of Indocapritermes aruni Chhotani, 1997 soldier C, mandible of Rinacapritermes abundans Amina & Rajmohana, n. gen., n. sp. soldier D, mandible of Indocapritermes aruni soldier. Scale bars: 0.2 mm.

FIG. 4 in Integrative taxonomic studies on Rinacapritermes Amina & Rajmohana, n. gen. (Blattodea: Isoptera: Termitidae) with two new species from India

FIG. 4. — Maximum likelihood tree based on 663 bp of mitochondrial COI gene (*represents the bootstrap values above 50%).

FIG. 2 in Integrative taxonomic studies on Rinacapritermes Amina & Rajmohana, n. gen. (Blattodea: Isoptera: Termitidae) with two new species from India

FIG. 2. — Rinacapritermes abundans Amina & Rajmohana, n. gen., n. sp.: A, soldier body dorsal view; B, soldier head dorsal view; C, soldier head profile; D, soldier's labrum; E, soldier's Postmentum; F, worker left and right mandible. Scale bars: A, 0.5 mm; B, F, 0.3 mm; C, 0.2 mm; D, E, 0.1 mm.

FIG. 1 in Integrative taxonomic studies on Rinacapritermes Amina & Rajmohana, n. gen. (Blattodea: Isoptera: Termitidae) with two new species from India

FIG. 1. — Rinacapritermes silvius Amina & Rajmohana, n. gen., n. sp.: A, soldier body dorsal view; B, soldier head dorsal view; C, soldier head profile; D, soldier's labrum; E, soldier's postmentum; F, worker left and right mandible. Scale bars: A, B, 0.5 mm; C, F, 0.3 mm; D, 0.1 mm; E, 0.2 mm.

FIG. 3 in Integrative taxonomic studies on Rinacapritermes Amina & Rajmohana, n. gen. (Blattodea: Isoptera: Termitidae) with two new species from India

FIG. 3. — Digestive tube of Rinacapritermes silvius Amina & Rajmohana, n. gen., n. sp. worker: A, dorsal view; B, left lateral view; C, right lateral view; D, ventral view; E, worker's enteric valve armature. Scale bars: A-D, 0.5 mm; E, 20 μm.

FIG. 6 in Integrative taxonomic studies on Rinacapritermes Amina & Rajmohana, n. gen. (Blattodea: Isoptera: Termitidae) with two new species from India

FIG. 6. — Labrum of genera under Pericapritermes-group; A, Dicuspiditermes incola (Wasmann, 1893); B, Homallotermes pilosus (Mathur & Thapa, 1962); C, Indocapritermes aruni Chhotani, 1997; D, Krishnacapritermes maitii Chhotani, 1997; E, Labiocapritermes distortus (Silvestri, 1922); F, Pericapritermes dunensis (Roonwal & Sen-Sarma, 1960); G, Procapritermes keralai (Chhotani & Ferry, 1995); H, Pseudocapritermes fletcheri (Holmgren & Holmgren, 1917). Scale bars: A-C, 0.3 mm; D, E, H, 0.2 mm; F, G, 0.1 mm.

Figs 257–264. Maghreba gen. nov., live specimens. 257–259. M in Revisions of Holocnemus and Crossopriza: the spotted-leg clade of Smeringopinae (Araneae, Pholcidae)

Figs 257–264. Maghreba gen. nov., live specimens. 257–259. M. gharbija gen. et sp. nov., male and female from Morocco, E of Ghazoua. 260–262. M. aurouxi (Barrientos, 2019) gen. nov., male and female from Morocco, SE of Zebzat. 263–264. M. djabalija gen. et sp. nov., male and female with eggsac from Morocco, NE of Tizi n'Test.

Fig. 9 in Pyrgotid Flies Assigned To Apyrgota. Iii. Species Of Afropyrgota Gen. N. And Tylotrypes (Diptera, Pyrgotidae)

Fig. 9. Afropyrgota, ♀ abdominal sternites, macerated, ventral view: 1 — A. copelandi sp. n.; 2 — A. marshalli; 3 — A. uzungwa sp. n. Рис. 9. Afropyrgota, ♀ брюшные стерниты ♀, мацерированные, вид снизу: 1 — A. copelandi sp. n.; 2 — A. marshalli; 3 — A. uzungwa sp. n.

Fig. 10 in Pyrgotid Flies Assigned To Apyrgota. Iii. Species Of Afropyrgota Gen. N. And Tylotrypes (Diptera, Pyrgotidae)

Fig. 10. Tylotrypes: 1–3 — T. fuscipes (Wulp) (1 — holotype Ơ, RMNH, habitus left; 2 — non-type ♀, Taiwan, CMNH, habitus left; 3 — same, mid femur, anterior); 4–12 — T. immsi Bezzi (4 — holotype, ♀, India, BMNH, habitus left; 5 — same, face, anterior; 6 — non-type ♀, Nepal, CNC, macerated oviscape, left; 7–8 — aculeus, ventral and lateral; 9 — same, spermatheca; 10 — non-type Ơ, macerated epandrium and hypandrium, right; 11, 12 — phallus glans, lateral and ventral); 13 — T. longa (Shi), holotype ♀, China, IZAS, habitus left (photo L.-h. Wang, modified); 14, 15 — T. sp., ♀, Thailand, ZSSM (14 — habitus left, 15 — head, anterolateral view). fo — femoral organ; mvl — medioventral lobe; opc — ovipositor callus; phg — phallic guide. Рис. 10. Tylotrypes: 1–3 — T. fuscipes (Wulp) (1 — голотип Ơ, RMNH, общий вид слева; 2 — нетиповая ♀, Тайвань, CMNH, общий вид слева; 3 — то же, среднее бедро, спереди); 4–12 — T. immsi Bezzi (4 — голотип ♀, Индия, BMNH, общий вид слева; 5 — то же, лицо, спереди; 6 — нетиповая ♀, Непал, CNC, мацерированый основной членик яйцеклада, вид слева; 7, 8 — акулеус, вид снизу и вид сбоку; 9 — то же, сперматека; 10 — нетиповой Ơ, мацерированые эпандрий и гипандрий вид справа; 11–12 — гланс фаллюса, вид сбоку и вид снизу); 13 — T. longa (Shi), голотип ♀, Китай, IZAS, общий вид слева (фото Л.-Х. Ваня, с изменениями); 14, 15 — T. sp., ♀, Таиланд, ZSSM (14 — общий вид слева, 15 — голова, вид спереди и сбоку). fo — феморальный орган; mvl — медиовентральная лопасть; opc — мозоль основного членика яйцеклада; phg — направляющая лопасть.

Fig. 7 in Pyrgotid Flies Assigned To Apyrgota. Iii. Species Of Afropyrgota Gen. N. And Tylotrypes (Diptera, Pyrgotidae)

Fig. 7. Afropyrgota uzungwa sp. n., ♀: 1 — holotype, lateral view; 2, 3 — head (2 — left, 3 — anterior); 4 — mesonotum dorsal; 5 — wing; 6 — fore leg, posterior; 7 — mid leg, anterior; 8 — hind leg, anterior and abdomen, ventrolateral. Scale bar 5 mm. Рис. 7. Afropyrgota uzungwa sp. n., ♀: 1 — голотип, вид сбоку; 2–4 — голова (2 — вид слева, 3 — anterior); 4 — среднеспинка сверху; 5 — крыло; 6 — передняя нога, вид сзади; 7 — средняя нога, вид спереди; 8 — задняя нога, вид спереди и брюшко, вид снизу и сбоку. Масштабная линейка 5 мм.

Fig. 6 in Pyrgotid Flies Assigned To Apyrgota. Iii. Species Of Afropyrgota Gen. N. And Tylotrypes (Diptera, Pyrgotidae)

Fig. 6. Afropyrgota ota sp. n., ♀: 1 — holotype, lateral view; 2–4 — head (2 — left, 3 — anterior, 4 — dorsal view); 5 — wing; 6 — mid leg, anterior; 7 — prosternum, anteroventral; 8 — paratype abdomen, lateral view. Рис. 6. Afropyrgota ota sp. n., ♀: 1 — голотип, вид сбоку; 2–4 — голова (2 — вид слева, 3 — спереди, 4 — сверху); 5 — крыло паратипа; 6 — средняя нога, спереди; 7 — простернум, спереди и снизу; 8 — брюшко паратипа, вид сбоку.

Fig. 5 in Pyrgotid Flies Assigned To Apyrgota. Iii. Species Of Afropyrgota Gen. N. And Tylotrypes (Diptera, Pyrgotidae)

Fig. 5. Afropyrgota marshalli, holotype Ơ: 1 — lateral view; 2 — labels, 3 — wing; 4 — mesonotum, dorsal view; 5 — epandrium, right view. Рис. 5. Afropyrgota marshalli, голотип Ơ: 1 — вид сбоку; 2 — этикетки, 3 — крыло; 4 — среднеспинка, вид сверху; 5 — эпандрий, вид справа.

Fig. 4 in Pyrgotid Flies Assigned To Apyrgota. Iii. Species Of Afropyrgota Gen. N. And Tylotrypes (Diptera, Pyrgotidae)

Fig. 4. Afropyrgota marshalli, ♀: 1 — lateral view; 2–4 — head (2 — left, 3 — anterior, 4 — dorsal view); 5 — mesonotum, dorsal view; 6 — wing; 7 — mid femur, anterior view; 8 — oviscape, ventrolateral; 9 — same, lateroventral lobe; 10 — aculeus; 11 — spermathecae. Fig. 4. Afropyrgota marshalli, ♀: 1 — вид сбоку; 2–4 — голова (2 — вид слева, 3 — спереди, 4 — сверху); 5 — среднеспинка, вид сверху; 6 — крыло; 7 — среднее бедро, вид спереди; 8 — основной членик яйцеклада, вид снизу и сбоку; 9 — то же, латеровентральная лопасть; 10 — акулеус; 11 — сперматеки.