---
id: "cache-poisoning"
kind: "glossary-term"
title: "cache poisoning"
language: "en"
category: "Security and abuse"
updated: "2026-10-04T14:01:23Z"
canonical: "https://tldlog.com/glossary/cache-poisoning/"
translations:
  es: "https://tldlog.com/es/glosario/envenenamiento-cache/"
  de: "https://tldlog.com/de/glossar/cache-poisoning/"
  fr: "https://tldlog.com/fr/glossaire/empoisonnement-cache/"
  it: "https://tldlog.com/it/glossario/avvelenamento-cache/"
  pt-BR: "https://tldlog.com/pt/glossario/envenenamento-cache/"
  ru: "https://tldlog.com/ru/glossariy/otravlenie-kesha/"
  zh-Hans: "https://tldlog.com/zh/cihui/huancun-toudu/"
---

# cache poisoning

An attack that slips false answers into a resolver's memory, so users asking for a real domain are sent to a wrong address. Dan Kaminsky showed in 2008 how practical it was. Random source ports made it much harder, and DNSSEC lets resolvers detect forged answers.

## related terms

- [resolver](https://tldlog.com/glossary/resolver/)
- [DNSSEC](https://tldlog.com/glossary/dnssec/)
- [pharming](https://tldlog.com/glossary/pharming/)
- [DNS hijacking](https://tldlog.com/glossary/dns-hijacking/)
- [TTL](https://tldlog.com/glossary/ttl/)