# Network & DNS

> Egress from an agent's own IPv6 address, graph-first name resolution, encrypted DNS for a phone or laptop, and the signed zones behind every identity.

*Source: https://www.whisper.security/docs/network*

---
A Whisper identity is a routable address, so it has a place of its own on the wire. This
chapter covers what that address sends and what answers for it.

```bash
whisper run curl -s https://rdap.whisper.online/egress-ip
{"ip":"2a04:2a01:b69a:6717:e3b0:51ff:3bf7:f478"}
```

That echo needs no key, and the address it reports is the one the far end saw.
[Egress](/docs/network/egress) is where you set that up: a routed tunnel, a bound proxy,
or an HTTPS relay for a runtime that holds no sockets.

The [resolver](/docs/network/resolver) is the other half. Every name your agents look up
is checked against the Whisper graph before it is answered, and your account decides what
happens to the names the graph has no opinion about. A phone or a laptop can sit behind
the same resolver without running an agent at all, which is what
[Devices](/docs/network/devices) is for.

Underneath both sits the signed zone work: the forward and reverse records that make an
address checkable by a stranger, and the apex you can delegate to put identities under
your own name. That is [Authoritative DNS](/docs/network/authoritative).

If you have not minted an identity yet, start at
[Create an Identity](/docs/identity/create); the address it hands back is what every page
in this chapter operates on.