EPP (Extensible Provisioning Protocol)
EPP (Extensible Provisioning Protocol) is the protocol registrars use to talk to registries: every registration, renewal, transfer, and nameserver change on a gTLD domain is an EPP command, standardized by the IETF in RFC 5730 and its companions. Investors rarely touch EPP directly, but they see its fingerprints everywhere — most visibly in domain status codes.
EPP status codes
The statuses on a WHOIS/RDAP record are EPP statuses. Client-prefixed codes (clientTransferProhibited, clientHold) are set by the registrar; server-prefixed codes (serverTransferProhibited, serverHold) are set by the registry and outrank them. Lifecycle statuses like redemptionPeriod and pendingDelete tell you exactly where an expired name sits.
The "EPP code" you are asked for during transfers
Confusingly, registrars often call the transfer authorization code the "EPP code." It is a per-domain password used within an EPP transfer request — not the protocol itself. If a transfer form asks for your EPP code, it wants the auth code from your current registrar.
Frequently Asked Questions
What is an EPP status code?
A standardized flag on a domain's registry record describing its state: locks like clientTransferProhibited, holds like serverHold, and lifecycle stages like redemptionPeriod or pendingDelete. Any RDAP or WHOIS lookup lists them.
Is the EPP code the same as the auth code?
Yes — EPP code, auth code, authorization code, and transfer key all name the same per-domain secret you obtain from the current registrar to approve an outbound transfer.