Result for 0BEBB0E3D7C85ED979FE7872BCC3EB83E7C1EC94

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabihf/knot-resolver/kres_modules/nsid.so
FileSize5608
MD5587D0E42DA8C9B96CAE46D3309D51DAE
SHA-10BEBB0E3D7C85ED979FE7872BCC3EB83E7C1EC94
SHA-2561195F754B93CD4789E74C6BF2EAD19829A761F82AA15866FFDBC02E253C90085
SSDEEP96:fZ4CBWBAwdxxG38FmQ75E99pJSie5V6jxJ:R4C8SwdX1ma5ERJ
TLSHT19BC1634BF6931C96DC55D67CC9AB4710BB20E84067576B235AD034E83E436F8ACE3949
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
FileSize265240
MD54384330B59CE2DCE0A104A4ED70BA512
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.3.1-1
SHA-1676F6821CD638E876FE7BA2C37FFCE1C4C9AD43A
SHA-25688BC5517FF9E7729D6C6605D1EC100BD21635C6B76F4FE770F5C30A50743A1A8