Result for 10A65CC18AAA5876E757E806500166BE15EAC21B

Query result

Key Value
FileName./usr/lib/libkres.so.9
FileSize190544
MD5253D2F79458275352636D5E332C6A2CF
SHA-110A65CC18AAA5876E757E806500166BE15EAC21B
SHA-25614B3E0BE4397A0161A3512D828BFB38B6BEE1CF56028DBD0C18BB89E1728C6FA
SSDEEP3072:8ZJKusxlqQv2zyMQ6qZu4JhYzY4pQKS+unbhCU2Nn/lJ7:YPYhv2zHqt46KduVCT/
TLSHT149143B2EB6B2A47CD0CAC07417CF86B1A9B0B4B52617383F3BC6A6742D50D91760D72B
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
FileSize249808
MD572C4157C1E8739E7A6E9A5F8FAF2F44A
PackageDescriptioncaching, DNSSEC-validating DNS resolver The Knot DNS 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
PackageVersion3.2.1-3~bpo9+1
SHA-19AF1D0C4E1AC77999151AB76AD2090BAE890A345
SHA-256AE35CA205859C7D144C1CD3B1DBBC8FCB5A5A6290143F446B3726ECE85F5FB3F