General
- Extension
- .net
- Type
- Classic extension
- Meaning
- Networks and internet services
- Registry
- VeriSign Global Registry Services
- Registry website
- www.verisigninc.com
- Registered since
- 1 January 1985
- ICANN agreement
- since 1 July 2017
Properties
- DNSSEC signed
- yes
- Name servers
- 13 (13 with IPv6)
- WHOIS server
- whois.verisign-grs.com
- RDAP server
- rdap.verisign.com/net/v1
- At 1blu
- available to order directly
Registration conditions
- IDN
- Umlauts and other characters are possible. Every IDN registration needs a language tag; the characters of a label must not mix different scripts.
- Who may register?
- In principle anyone, unless the registry sets additional conditions (e.g. for industry, regional or brand extensions).
- Length
- At most 63 characters per label (for IDNs the ACE form counts). This follows the DNS standard RFC 1035, which the ICANN registry agreement requires. The registry does not state its own minimum length.
- Characters
- a–z, 0–9 and hyphen. No hyphen at the beginning or end, and in positions 3 and 4 only for IDNs (ACE form starting with xn--).
- Registrant data
- Name, street, city, state/province and postal code where applicable, country, phone and e-mail of the registrant; an organisation is optional. Personal data is redacted in public lookups where data protection law requires it.
- Term
- 1 to 10 years per registration or renewal (ICANN Registry Agreement).
- Transfer
- With an auth code (auth info) under the ICANN Transfer Policy. A lock period applies after a new registration or transfer.
- After expiry
- Restore possible during the Redemption Grace Period (ICANN rules).
- Disputes
- ICANN Uniform Domain-Name Dispute-Resolution Policy (UDRP).
The registry's current rules are binding: www.verisigninc.com.
Sources: Verisign: IDN registration rules · ICANN Transfer Policy · ICANN UDRP · ICANN: .net Registry Agreement · Verisign: About IDN registrations · ICANN Registration Data Policy · IANA Root Zone Database: .net · As of 28 October 2026