Result for 210ECFDD945D9847F215FDF6CCF9D34EBD02F59D

Query result

Key Value
FileName./usr/lib/x86_64-linux-gnu/knot-resolver/kres_modules/policy.lua
FileSize29326
MD52E93A0370807D91D4F3EFEF3F7CC01E2
SHA-1210ECFDD945D9847F215FDF6CCF9D34EBD02F59D
SHA-256A46DFBE699C4D8D2183FED2DAA82FAC372410BD18E5DEA0B9323F940DBC95AEE
SSDEEP768:A/9rCLjGY9KQVk9FiXI/RM4eSYzPIJCfjaO9rxT7RBnxQoynR:4rO1GzRM4eSY+2aOd7POoyR
TLSHT1E6D2E85E707FD19AA6F260E8D81F0622FDDEFD79524E266184C802B0618127FC1B7D79
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
FileSize270644
MD5EE3A9BD3089EE98FB3DA96A9F2A43F06
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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameknot-resolver
PackageSectionnet
PackageVersion5.2.1-1
SHA-1C04CEC76C3D1DE2C0BB85AF4FE13B631D944AB48
SHA-256BEE2B2E09353585415C108CEDD692589C3EEB5CD1D8ABC6E872AE463BC738D03