Result for 05DA6F021DE8897BF907B7EE240AD30A88AA7E1D

Query result

Key Value
FileName./usr/lib/mips64el-linux-gnuabi64/knot-resolver/kres_modules/nsid.so
FileSize10928
MD5341FEBD1A0B132F5572A1CDC73DDAEE8
SHA-105DA6F021DE8897BF907B7EE240AD30A88AA7E1D
SHA-256F591F4E36E5B1AF84B42EDB0706BB050ADC207533C4F7E6F250D4E33DFBCF6E7
SSDEEP96:cG0/KBWB2KSBwqyqtUcF+91+/OkSexeuZhoY9MFxlRuQAqAtw2js:n0/K8MdUccrASexeuZiYCFxlRzA
TLSHT1C232A5EAFF45AEBBC0AC4731C85B437937349D07A68107336A4CAAF01C4778C1E91889
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize302540
MD5400935B06E914DAA5C4372E83E1A1913
PackageDescriptioncaching, DNSSEC-validating DNS resolver The Knot Resolver is a caching full resolver implementation written in C and LuaJIT, including both a resolver library and a daemon. Modular architecture of the library keeps the core tiny and efficient, and provides a state-machine like API for extensions. There are three built-in modules - iterator, cache, validator, and many external. . The Lua modules, switchable and shareable cache, and fast FFI bindings makes it great to tap into resolution process, or be used for your recursive DNS service. It's the OpenResty of DNS. . The server adopts a different scaling strategy than the rest of the DNS recursors - no threading, shared-nothing architecture (except MVCC cache that may be shared). You can start and stop additional nodes depending on the contention without downtime.
PackageMaintainerknot-resolver packagers <knot-resolver@packages.debian.org>
PackageNameknot-resolver
PackageSectionnet
PackageVersion5.4.2-1
SHA-1F8B50362DEBD60FAEB4823E007CD3C069A167778
SHA-256FF1DE63F70F27985B389A379EDB000E1407CE08BEA70FA7501A4870544E43E55