ENUM (IETF RFC 6116) maps an E.164 number to internet URIs using DNS. The number's digits are reversed, dot-separated and suffixed with e164.arpa to form a domain; NAPTR records at that name carry regexp rules that rewrite the number into SIP, tel or other URIs, letting a routing engine resolve a phone number to a reachable service.
What ENUM solves
ENUM (E.164 Number to URI Mapping) bridges the telephone numbering plan and the internet's naming system. A caller or application holds an E.164 number, but a VoIP or IMS network needs a URI — a SIP address, a tel URI, an email or web endpoint — to actually reach the destination. ENUM, defined in IETF RFC 6116 (which obsoleted RFC 3761), uses the existing DNS to publish, per number, the set of URIs and services that number resolves to. Instead of a bespoke database and protocol, ENUM reuses DNS's global, cached, delegated infrastructure to answer 'given this phone number, what internet endpoints serve it, and in what preference order?'
From E.164 to a domain name
The transformation from number to queryable domain is mechanical and defined by RFC 6116. Take the full E.164 number, remove all non-digit characters (including the '+'), reverse the digit order, place a dot between every digit, and append the domain suffix 'e164.arpa'. The result is a fully qualified domain name that DNS can resolve. Reversing the digits mirrors the way DNS delegates from the most significant label rightward, so a country's number range can be delegated as a DNS zone the same way an IP reverse zone is. The apex domain e164.arpa is the IETF-designated tree for public ENUM.
E.164 number : +44 20 7946 0123
Digits only : 442079460123
Reverse : 321064972044
Dot-separate : 3.2.1.0.6.4.9.7.0.2.4.4
Append apex : 3.2.1.0.6.4.9.7.0.2.4.4.e164.arpa
→ DNS query for NAPTR records at that nameNAPTR records and regexp rewrite
The data ENUM returns lives in NAPTR (Naming Authority Pointer) resource records. Each NAPTR carries an Order and Preference that rank the alternatives, Flags (typically 'u' meaning the output is a terminal URI), a Service field naming the enumservice (for example E2U+sip, E2U+tel, E2U+email), and a Regexp that rewrites the queried number into the target URI. A resolver evaluates the regexp — a POSIX substitution over the original E.164 number — to produce the final URI, then a routing engine tries the results in Order/Preference sequence. This lets one number publish several reachable endpoints with a defined fallback order, all as ordinary DNS data.
$ORIGIN 3.2.1.0.6.4.9.7.0.2.4.4.e164.arpa.
IN NAPTR 10 100 "u" "E2U+sip" "!^.*$!sip:user@sip.example.net!" .
IN NAPTR 20 100 "u" "E2U+tel" "!^.*$!tel:+442079460123!" .
IN NAPTR 30 100 "u" "E2U+email" "!^.*$!mailto:user@example.net!" .
Fields: Order Pref Flags Service Regexp ReplacementPublic (user) versus private (infrastructure) ENUM
ENUM is deployed in two very different modes. Public or 'user' ENUM publishes mappings in the globally delegated e164.arpa tree, opt-in per number holder, so anyone can resolve a number to the endpoints its owner chose to advertise — this saw limited real-world uptake because of trust, privacy and business-model concerns. Private, 'carrier' or 'infrastructure' ENUM runs the identical technical mechanism inside a carrier's or IPX's own DNS, not under public e164.arpa, and is not visible to the internet. Infrastructure ENUM is where ENUM actually earns its keep: carriers use it internally to route numbers to SIP peers, resolve ported numbers and interconnect VoIP without exposing subscriber data.
| Aspect | Public (user) ENUM | Private (infrastructure) ENUM |
|---|---|---|
| DNS tree | Public e164.arpa | Operator/IPX-internal DNS |
| Who provisions | The number holder (opt-in) | The carrier / interconnect |
| Visibility | Globally resolvable | Private, not internet-visible |
| Primary use | User-published endpoints | Carrier VoIP/SIP routing, porting |
| Adoption | Limited | Widespread inside carriers/IPX |
ENUM in VoIP and SIP routing
In a SIP or IMS network ENUM is the number-to-URI resolver that sits in front of routing. When a call must leave the numbering-plan world and enter the SIP world, the routing engine performs an ENUM query on the destination E.164 number and, on a hit, routes to the returned SIP URI — often another carrier's session border controller — instead of breaking out to the PSTN. This keeps IP-originated calls on-net and IP end-to-end where possible, lowering cost and preserving media quality. Combined with number portability data, infrastructure ENUM lets a carrier resolve a dialed number to the correct serving network's SIP ingress even after the number has been ported.
Frequently asked
What is ENUM?
ENUM (E.164 Number to URI Mapping), defined in IETF RFC 6116, uses DNS to map a telephone number to internet URIs such as SIP or tel addresses. It reuses DNS's global, delegated infrastructure so a routing engine can resolve a phone number to the endpoints and services that number reaches.
How is an E.164 number turned into an ENUM domain?
Remove all non-digit characters including the '+', reverse the digit order, put a dot between every digit, and append 'e164.arpa'. For example +442079460123 becomes 3.2.1.0.6.4.9.7.0.2.4.4.e164.arpa. Reversing the digits aligns the number with DNS's most-significant-label-rightward delegation.
What is a NAPTR record in ENUM?
A NAPTR (Naming Authority Pointer) record holds each mapping: an Order and Preference to rank alternatives, Flags (usually 'u' for a terminal URI), a Service field naming the enumservice (E2U+sip, E2U+tel), and a Regexp that rewrites the number into the target URI. Results are tried in Order/Preference sequence.
What is the difference between public and private ENUM?
Public (user) ENUM publishes mappings in the globally delegated e164.arpa tree, opt-in per number holder, and saw limited uptake. Private (infrastructure/carrier) ENUM runs the same mechanism inside a carrier's or IPX's own DNS, invisible to the internet, and is widely used for internal VoIP/SIP routing and porting.
How does ENUM help route VoIP calls?
A SIP or IMS routing engine queries ENUM on the destination E.164 number and, on a hit, routes to the returned SIP URI — often another carrier's SBC — keeping the call IP end-to-end instead of breaking out to the PSTN. With portability data, infrastructure ENUM resolves a number to the correct serving network even after porting.
Which RFC defines ENUM?
IETF RFC 6116 is the current Dynamic Delegation Discovery System (DDDS) application for E.164-to-URI mapping; it obsoleted the earlier RFC 3761. Together with the DDDS framework and the NAPTR record type, RFC 6116 specifies the e164.arpa domain construction and the regexp rewrite that produces the target URIs.
Source specifications
The published standards this page is grounded in. Opens in a new tab.