Result for 00C32FBC83F723AF1831C0A327122840A2905F07

Query result

Key Value
FileName./usr/lib/knot-resolver/hints.so
FileSize42984
MD5D009E433476E0AF97F24B655BB94BEC6
SHA-100C32FBC83F723AF1831C0A327122840A2905F07
SHA-25694E1343476B66271602B08FB02927118CD96BF63672FE11D028A50F4508B4881
SSDEEP768:sshSfZr4Gc69JZOPoI58HytWd/4D5GbkhHcNciJj9YVrDi:nuDZOA1HrdGikh8cA5
TLSHT1A013F882FB4DDF26D0DF4F30C91FC25B2A693C66E684D322B598AB95671A7C50BC3409
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
FileSize241192
MD5C703996FA019D6121A4E116DD613EAB9
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
SHA-13335DD63BD4F71719F29D816DCA70034A8A9B580
SHA-256E825FE27175B0C755A7D7607FE5DD0A1EF1B1E86E17EB1F5E61E1E600641A8DB