Result for 06145096461A7429127A2EA6EF2D101B08CB6F0E

Query result

Key Value
FileName./usr/sbin/kres-cache-gc
FileSize23388
MD58F957BD16957978B3D91E88FADFE7C48
SHA-106145096461A7429127A2EA6EF2D101B08CB6F0E
SHA-256E8D0C268BF2FEE9DF0944F101BC5BB77C6F3C449FAED166F252985E637A2D2E7
SSDEEP384:eINj+/ihhBZwjtpn1fKRDYboY9iWAZNbtuT9P+zuolSjca6+iCa9d9BDVVtcv5z2:vd+/ihhBZIzn1fKRDYMgiWAZNbtuT9Pa
TLSHT11DB2E803FB50CE53C5E9CF30591F4A0192BF896D83DAA223B17D8AD4774AA0D5CE7598
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
FileSize282032
MD5D790946DDF8AD00ABE6E0B0D9FE1D31C
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-1FBC747A7AF0A9BEDC7C514412CFCD1CEC6F55D40
SHA-2563F93A472DC16128BFFFBB1EF775511D4C9DCA9016B5BF1714C22E30B9CC875F2