# DNS rebinding: definition and example

URL: https://mcpservercybersecurity.com/glossary/dns-rebinding/
Updated: 2026-11-16

DNS rebinding is a technique in which a domain name first resolves to a public address and later to a local one, letting a remote web page reach a service bound to the user's machine. A local MCP server reachable over HTTP is a target. The specification's defense is for servers to validate the Origin header and bind to localhost.

## Example

The Inspector's 2.12.0 release notes say its production web server now validates the Host header and answers 403 for hosts outside an allow-list, which closes a DNS rebinding route to the API token and stored OAuth tokens.

## Sources

- [MCP Inspector 2.12.0 release notes](https://github.com/modelcontextprotocol/inspector/releases/tag/2.12.0) (github.com), read 2026-11-16

## Related pages

- [Localhost binding](/glossary/localhost-binding/)
- [SSRF](/glossary/ssrf/)
- [MCP transport](/glossary/mcp-transport/)
- [Securing a Python MCP Server: Host Checks and Deployment](/guides/securing-a-python-mcp-server/)
- [All glossary terms](/glossary/)
- [Command injection](/glossary/command-injection/)
- [Dynamic Client Registration](/glossary/dynamic-client-registration/)
- [Guides](/guides/)
