Result for 01872933A2EB6FA55FC897CF77359E586FB717D6

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabihf/knot-resolver/kres_modules/nsid.so
FileSize5608
MD5EF71D50B118053566739B9BAB670B543
SHA-101872933A2EB6FA55FC897CF77359E586FB717D6
SHA-2560C95C002D1C21FBC7F30F45FE64AC29AFF55CD7C99F217301B937BDD1E6C9397
SSDEEP96:Hv9YBWBABoA6KSYeOqL9sCpKe56skcbCWJ:P68SiiiOqLqZT
TLSHT176C1844FF2D70C93C4554778496B4719E730DD4836534B237AB4AA902E8B7B8FCB2A09
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
FileSize293500
MD51BC48E36E0ECC17F233D4DBD1CDF7C34
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.1-2
SHA-10004F72B2AAFA43742C8F7DD0D717B615AC79A1F
SHA-25679AA3C374DCB97C8E0A6FADE39F8332B841887746808C71E428C6E9A285F3DF0