Result for 0B5A9CABFE9E781A54176B891EE6D1C3C9EADB36

Query result

Key Value
FileName./usr/sbin/kresc
FileSize9776
MD59472EAFEDA69DAAE3A17D66844945E68
SHA-10B5A9CABFE9E781A54176B891EE6D1C3C9EADB36
SHA-2564D55D3B26229D5BA15D5277DE7F112CDAF2BA53D7638F8CD46781DACF73B6DB3
SSDEEP192:TxPeQwaIjBUdNDWu/yd+OUJPS09t75Zz5u9vtBb9I1l:TxPel6NT/ygCO7TiBb9Ij
TLSHT1B412A3D9A5536A33E8CD1E3C44170E28D730C38BAFD71B13656876501E9AA9C8D2EF9C
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