Result for 193630EF7721E33B7C8DD42BF798A7EB09FC0479

Query result

Key Value
FileName./usr/lib/i386-linux-gnu/knot-resolver/kres_modules/hints.so
FileSize17908
MD5439ADDA0D3EB03828FC2762A1D74788D
SHA-1193630EF7721E33B7C8DD42BF798A7EB09FC0479
SHA-256BA7934D78BD412909E03B095B3110A829FBCEE731EE41C25BCAA256545EDC3F4
SSDEEP384:yEFfucf3nggTjNltlCHoJg3drOeUeLD1BdhAuYdZzpbZpBHLpuu3d:Vf3nfTRlHCceBD1BdOuYdZzpbZpBHLpN
TLSHT19782084AB9D2C8B2E971B97841CF473CA07058354ED3D6637D963F7824633A0EA29739
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
FileSize298128
MD5020739677BD6A0B7A1D34DAD606F3846
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-1AD171F32D808AA5647397ECE84DC009DB3C8ABF4
SHA-25695A7BA63AE47898D38FD5F646B376510F856512717A5685D8DAAA2EA224FEB16