Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
450
datasets available to search
ShareScore release 0.9.0
Dataset results
450 results for “hook”
Sealing. Circular sealing in terracotta with a three line inscription; above a discus. On the reverse a hooked device, possibly an elephant goad
<p>Sealing. Circular sealing in terracotta with a three line inscription; above a discus. On the reverse a hooked device, possibly an elephant goad. British Museum 2005,0814.10.</p>
NW Coast Halibut Hook
A Halibut hook from the traditional Northwest coastel people of North America's Alaskan region. Source: Objaverse 1.0 / Sketchfab
Wmid-2b4e88 - post medieval dress hook
An incomplete copper alloy single sharp hooked clasp (dress hook), of Early Post Medieval dating (AD 1500 to AD 1600). Around 75% of the dress hook is present, with the sharp hook missing. The openwork plate is depicting an equal armed cross with a central pellet, within a linear circle, four circular holes are present in each quarter. The edge is beaded and engrailed. A sub rectangular attachment loop is present. The single sharp pointed hook is missing. The back is undecorated. For more information, please visit the online database record available at: https://finds.org.uk/database/artefacts/record/id/1071527 Source: Objaverse 1.0 / Sketchfab
Low Poly Pirate Hook
Free Pirate Hook! Terms of Use: Free to use/dowload, but please do offer credit to the source author Please do not use this for anything inapropiate or out of line, Source: Objaverse 1.0 / Sketchfab
Wmid-d46a92 - Post Medieval dress hook
An incomplete copper alloy dress hook, of Early Post Medieval dating (AD 1600 to AD 1700). This is the hook section of such fasteners, with its rectangular blunt hook truncated. The central area of the plate has a raised foliate design with a central quartered berry and four leaves in cross formation with four small circular berries in the angles. This design is within a broadly lozengiform line border formed of four lines with scrolled ends; at the middle corners these form a pair of projecting rounded knops at either side. There are two pierced lobes flanking the start of the hook, one either side of a billeted transverse band. At the opposite end to the hook is a third pierced lobe with projecting scrolled terminals to either side, giving a fleur-de-lis terminal. For more information, please visit the online database record available at: https://finds.org.uk/database/artefacts/record/id/1072771 Source: Objaverse 1.0 / Sketchfab
Figs 61–66 in Sem Study Of Hooks In The Acanthocephala With Emphasis On Structural-Functional Relationships
Figs 61–66. SEM of proboscis and hooks
Figs 67–72 in Sem Study Of Hooks In The Acanthocephala With Emphasis On Structural-Functional Relationships
Figs 67–72. SEM of proboscis and hooks
Figs 37–42 in Sem Study Of Hooks In The Acanthocephala With Emphasis On Structural-Functional Relationships
Figs 37–42. SEM of proboscis and hooks
Figs 43–48 in Sem Study Of Hooks In The Acanthocephala With Emphasis On Structural-Functional Relationships
Figs 43–48. SEM of proboscis and hooks
Figs 19–24 in Sem Study Of Hooks In The Acanthocephala With Emphasis On Structural-Functional Relationships
Figs 19–24. SEM of proboscis and hooks of Acanthocephalaus parallelcemenglanda-
Figs 85–90 in Sem Study Of Hooks In The Acanthocephala With Emphasis On Structural-Functional Relationships
Figs 85–90. Proboscis and hooks of Neo-
Figs 13–18 in Sem Study Of Hooks In The Acanthocephala With Emphasis On Structural-Functional Relationships
Figs 13–18. SEM of proboscis and hooks
Figs 115–120 in Sem Study Of Hooks In The Acanthocephala With Emphasis On Structural-Functional Relationships
Figs 115–120. Proboscis and hooks of Rhadinorhynchus hiansi (cont.) (figs
Dataset for paper Spotting the Hook: Leveraging Domain Data for Advanced Phishing Detection
<p>The dataset contains DNS records, IP-related features, WHOIS/RDAP information, information from TLS certificate fields, and GeoIP information for 432,572 benign domains from Cisco Umbrella and 68,353 phishing domains from PhishTank and OpenPhish services. The ground truth for the phishing dataset was double-check with the VirusTotal (VT) service. Domain names not considered as phishing by VT have been removed. The data was collected between March and November 2023.The final assessment of the data was conducted in December 2023.</p> <p>The dataset is useful for statistical analysis of domain data or feature extraction for training machine learning-based classifiers, e.g. for phishing detection. </p> <h1>Data Files</h1> <p>The data is located in two individual files:</p> <ul> <li><strong>benign.json</strong> - data for 432,572 benign domains, and</li> <li><strong>phishing.json</strong> - data for 68,353 phishing domains.</li> </ul> <h1>Data Structure</h1> <div> <p>Both files contain a JSON array of records generated using mongoexport. The following table documents the structure of a record. Please note that:</p> <ul> <li>some fields may be missing (they should be interpreted as nulls), </li> <li>extra fields may be present (they should be ignored), </li> <li>due to a processing error, the common_name field of the certificate objects always contains trailing symbols: <code>‘></code> .</li> </ul> </div> <table> <tbody> <tr> <td> <div> <div> <p><strong>Field name </strong></p> </div> </div> </td> <td> <div> <div> <p><strong>Field type </strong></p> </div> </div> </td> <td> <div> <div> <p><strong>Nullable </strong></p> </div> </div> </td> <td> <div> <div> <p><strong>Description </strong></p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>domain_name </p> </div> </div> </td> <td> <div> <div> <p>String </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>The evaluated domain name </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>url </p> </div> </div> </td> <td> <div> <div> <p>String </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>The source URL for the domain name </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>evaluated_on </p> </div> </div> </td> <td> <div> <div> <p>Date </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>Date of last collection attempt </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>source </p> </div> </div> </td> <td> <div> <div> <p>String </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>An identifier of the source </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>sourced_on </p> </div> </div> </td> <td> <div> <div> <p>Date </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>Date of ingestion of the domain name </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>dns </p> </div> </div> </td> <td> <div> <div> <p>Object </p> </div> </div> </td> <td> <div> <div> <p>Yes </p> </div> </div> </td> <td> <div> <div> <p>Data from DNS scan </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>rdap </p> </div> </div> </td> <td> <div> <div> <p>Object </p> </div> </div> </td> <td> <div> <div> <p>Yes </p> </div> </div> </td> <td> <div> <div> <p>Data from RDAP or WHOIS </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>tls </p> </div> </div> </td> <td> <div> <div> <p>Object </p> </div> </div> </td> <td> <div> <div> <p>Yes </p> </div> </div> </td> <td> <div> <div> <p>Data from TLS handshake </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>ip_data </p> </div> </div> </td> <td> <div> <div> <p>Array of Objects </p> </div> </div> </td> <td> <div> <div> <p>Yes </p> </div> </div> </td> <td> <div> <div> <p>Array of data objects capturing the IP addresses related to the domain name </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p><strong>DNS data (dns field) </strong></p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>A </p> </div> </div> </td> <td> <div> <div> <p>Array of Strings </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>Array of IPv4 addresses </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>AAAA </p> </div> </div> </td> <td> <div> <div> <p>Array of Strings </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>Array of IPv6 addresses </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>TXT </p> </div> </div> </td> <td> <div> <div> <p>Array of Strings </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>Array of raw TXT values </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>CNAME </p> </div> </div> </td> <td> <div> <div> <p>Object </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>The CNAME target and related IPs </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>MX </p> </div> </div> </td> <td> <div> <div> <p>Array of Objects </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>Array of objects with the MX target hostname, priority and related IPs </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>NS </p> </div> </div> </td> <td> <div> <div> <p>Array of Objects </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>Array of objects with the NS target hostname and related IPs </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>SOA </p> </div> </div> </td> <td> <div> <div> <p>Object </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>All the SOA fields, present if found at the target domain name </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>zone_SOA </p> </div> </div> </td> <td> <div> <div> <p>Object </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>The SOA fields of the target’s zone (closest point of delegation), present if found and not a record in the target domain directly </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>dnssec </p> </div> </div> </td> <td> <div> <div> <p>Object </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>Flags describing the DNSSEC validation result for each record type </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>ttls </p> </div> </div> </td> <td> <div> <div> <p>Object </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>The TTL values for each record type </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>remarks </p> </div> </div> </td> <td> <div> <div> <p>Object </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>The zone domain name and DNSSEC flags </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p><strong>RDAP data (rdap field) </strong></p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>copyright_notice </p> </div> </div> </td> <td> <div> <div> <p>String </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>RDAP/WHOIS data usage copyright notice </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>dnssec </p> </div> </div> </td> <td> <div> <div> <p>Bool </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>DNSSEC presence flag </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>entitites </p> </div> </div> </td> <td> <div> <div> <p>Object </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>An object with various arrays representing the found related entity types (e.g. abuse, admin, registrant). The arrays contain objects describing the individual entities. </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>expiration_date </p> </div> </div> </td> <td> <div> <div> <p>Date </p> </div> </div> </td> <td> <div> <div> <p>Yes </p> </div> </div> </td> <td> <div> <div> <p>The current date of expiration </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>handle </p> </div> </div> </td> <td> <div> <div> <p>String </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>RDAP handle </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>last_changed_date </p> </div> </div> </td> <td> <div> <div> <p>Date </p> </div> </div> </td> <td> <div> <div> <p>Yes </p> </div> </div> </td> <td> <div> <div> <p>The date when the domain was last changed </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>name </p> </div> </div> </td> <td> <div> <div> <p>String </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>The target domain name for which the data in this object are stored </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>nameservers </p> </div> </div> </td> <td> <div> <div> <p>Array of Strings </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>Nameserver hostnames provided by RDAP or WHOIS </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>registration_date </p> </div> </div> </td> <td> <div> <div> <p>Date </p> </div> </div> </td> <td> <div> <div> <p>Yes </p> </div> </div> </td> <td> <div> <div> <p>First registration date </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>status </p> </div> </div> </td> <td> <div> <div> <p>Array of Strings </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>The state of the registered object [TODO] </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>terms_of_service_url </p> </div> </div> </td> <td> <div> <div> <p>String </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>URL of the RDAP usage ToS </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>url </p> </div> </div> </td> <td> <div> <div> <p>String </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>URL of the RDAP entity </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>whois_server </p> </div> </div> </td> <td> <div> <div> <p>String </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>WHOIS server address </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p><strong>TLS data (tls field) </strong></p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>cipher </p> </div> </div> </td> <td> <div> <div> <p>String </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>TLS cipher suite description according to [TODO] </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>protocol </p> </div> </div> </td> <td> <div> <div> <p>String </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>One of “TLS”, ”TLSv1.2”, ”TLSv1.3” </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>certificates </p> </div> </div> </td> <td> <div> <div> <p>Array of Objects </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>Array of objects representing the certificate chain, the first element is the root certificate </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p><strong>IP data (elements in the ip_data array) </strong></p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>ip </p> </div> </div> </td> <td> <div> <div> <p>String </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>The IP address </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>from_record </p> </div> </div> </td> <td> <div> <div> <p>String </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>The type of the DNS record the address was captured from </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>remarks </p> </div> </div> </td> <td> <div> <div> <p>Object </p> </div> </div> </td> <td> <div> <div> <p>No </p> </div> </div> </td> <td> <div> <div> <p>Ping round-trip time, “is alive” flag and rdap/geo/asn evaluation dates </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>rdap </p> </div> </div> </td> <td> <div> <div> <p>Object </p> </div> </div> </td> <td> <div> <div> <p>Yes </p> </div> </div> </td> <td> <div> <div> <p>RDAP data, similar to DNS RDAP, see the JSON Schema for details </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>geo </p> </div> </div> </td> <td> <div> <div> <p>Object </p> </div> </div> </td> <td> <div> <div> <p>Yes </p> </div> </div> </td> <td> <div> <div> <p>Geolocation data from the GeoLite2 City database (e.g. latitude, longitude, city, country, etc.) </p> </div> </div> </td> </tr> <tr> <td> <div> <div> <p>asn </p> </div> </div> </td> <td> <div> <div> <p>Object </p> </div> </div> </td> <td> <div> <div> <p>Yes </p> </div> </div> </td> <td> <div> <div> <p>Autonomous system data from the GeoLite2 ASN database (ASN, organization, network) </p> </div> </div> </td> </tr> </tbody> </table> <h1>Acknowledgements</h1> <p>We would like to thank the OpenPhish Team for grating permission to use and publish their dataset. We also thank VirusTotal for providing us access to the API for research purposes. The research has been supported by the <strong>Flow-based Encrypted Traffic Analysis</strong> project, no. VJ02010024, granted by the Ministry of the Interior of the Czech Republic and the <strong>Smart Information Technology for a Resilient Society </strong>project, no. FIT-S-23-8209, granted by Brno University of Technology.</p>
FIgS. 26–29. Urodacus butleri, n. sp., paratype ♂ (WAM T85141). 26. Dextral hemispermatophore, dorsal aspect. 27–29. Detail of capsule lamellae, dorsal, ental, and ventral aspects. Abbreviations: Al, anterior lobe; C, capsule; Cp, conical process; DTR, distal transverse ridge; L, lamella; Lh, lamellar hook; Lhp, lamellar hook process; IBL, internobasal lobe; T, trunk. Scale bars = 0.5 mm.
FIgS. 26–29. Urodacus butleri, n. sp., paratype ♂ (WAM T85141). 26. Dextral hemispermatophore, dorsal aspect. 27–29. Detail of capsule lamellae, dorsal, ental, and ventral aspects. Abbreviations: Al, anterior lobe; C, capsule; Cp, conical process; DTR, distal transverse ridge; L, lamella; Lh, lamellar hook; Lhp, lamellar hook process; IBL, internobasal lobe; T, trunk. Scale bars = 0.5 mm.
A possible formation channel for blue hook stars in globular cluster - II. Effects of metallicity, mass ratio, tidal enhancement efficiency and helium abundance
<p>MESA inlists and run_star_extras associated with <a href="https://ui.adsabs.harvard.edu/?#abs/2016MNRAS.463.3449L">Lei et al. (2016)</a>. MESA version 7211.</p> <p>Publication DOI: <a href="https://doi.org/10.1093/mnras/stw2242">10.1093/mnras/stw2242</a></p>
Fig. 6 in Large onychites (cephalopod hooks) from the Upper Jurassic of the Boreal Realm
Fig. 6. Morphological terms for mega−onychites, based on Engeser (1987).
Image 4 in New floral distribution records of Aquilegia nivalis (Baker) Falc. ex B.D. Jacks and Doronicum falconeri C.B. Clarke ex Hook. f. from the Valley of Flowers National Park, Uttarakhand, India
Image 4. Herbarium of Doronicum falconeri
Image 2 in New floral distribution records of Aquilegia nivalis (Baker) Falc. ex B.D. Jacks and Doronicum falconeri C.B. Clarke ex Hook. f. from the Valley of Flowers National Park, Uttarakhand, India
Image 2. Aquilegia nivalis
A generalized Hooke's law to study the transport properties of rocks
<p>The nonlinear characteristics of the rock transport properties as a function of stress (permeability and electrical conductivity in this study) is closely related to the geometry of the pore space, which consists of stiff pores, cracks and fractures. We consider two behaviors of the pore space, one linear and the other exponential, related to the stiff pores and fractures, respectively, where a generalized Hooke's law describes the relation between stress and strain. Using this theory, we derive relations between porosity, transport properties and effective stress (confining minus pore pressure), which are validated by experimental data of four tight sandstones collected from the Shaximiao Formation of Sichuan Basin, southwest China. The agreement is good. At low effective stresses, the closure of cracks is the main mechanism affecting the transport properties, whose behavior is similar in terms of their parameters. Subsequently, experimental data of six tight sandstones from the Yanchang Formation, collected from the Ordos Basin, west China, are employed to confirm the previous results, indicating that the fluid and electrical current follow the same path in the pore space. In addition, we find that the effect of metallic minerals on the electrical conductivity is more significant than that of clay.</p>
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.