• AI Domain Generator
  • Blog
  • Pricing
  • Membership
    1. Home
    3. Top-Level Domains
    5. .secure

    Search For .secure Domain

    Type
    Generic top-level domain
    Registry
    Amazon Registry
    Operator
    Amazon Registry Services, Inc.
    Launched
    Registration term
    1–10 years
    DNSSEC
    Supported
    IDN
    Supported

    About .secure domain

    .secure is a proposed generic top-level domain (gTLD) that was part of ICANN's New gTLD Program. The application was submitted by Artemis Internet, a subsidiary of the IT security firm NCC Group. The proposal was designed as a high-security domain extension with stringent operational requirements for registrants. The application process involved a contention set with another applicant, and the TLD has not been delegated by ICANN.

    Who can register .secure domain

    Registration for .secure domains would be restricted to entities that can demonstrate and maintain compliance with the registry's defined security standards. Prospective registrants would likely need to undergo a verification process to prove their identity and technical capability to operate a secure online presence. The registry operator would enforce policies to ensure all domains under .secure adhere to specific security protocols, potentially including mandatory use of security technologies like DNSSEC and HTTPS.

    How to register .secure domain

    As a proposed and non-delegated TLD, .secure domains are not currently available for registration through any commercial process. If the TLD were to be delegated in the future, allocation would be managed by the successful registry operator according to ICANN's established procedures for new gTLDs. This would likely involve an initial sunrise period for trademark holders, followed by a landrush and general availability phase. The specific steps for registration would be defined and published by the registry at that time.

    Typical uses of .secure domain

    If launched, the .secure extension would be intended for websites where security and trust are paramount. It would likely be adopted by financial institutions, e-commerce platforms, healthcare providers, and government services seeking to signal a verified, high-security online environment to users. The TLD's value proposition would be its enforced security standards, differentiating it from open extensions and aiming to create a namespace where visitors can have greater confidence in the authenticity and safety of the sites they visit.

    Tips for registering .secure domain

    • Registration would be contingent upon passing the registry's security compliance checks, not simply on payment.
    • Domains would likely be subject to ongoing audits to ensure continued adherence to the required security protocols.
    • The registry would probably enforce specific technical requirements, such as mandatory encryption and domain name system security extensions.
    • Given its proposed security focus, WHOIS privacy services might be limited or unavailable to ensure registrant accountability.

    Frequently asked questions about .secure domain

    Who operates .secure domain?The registry for .secure domains is Amazon Registry, administered by Amazon Registry Services, Inc..
    Who can register a .secure domain?

    Eligibility would be based on the ability to meet and maintain the registry's security standards. Registrants would need to verify their identity and demonstrate the technical infrastructure to support a secure website, such as implementing specific encryption protocols. The registry would likely have the right to suspend domains found to be non-compliant with its security policies after registration.

    Can I transfer a .secure domain between registrars?

    Inter-registrar transfers would be possible but would require the gaining registrar to also be accredited by the .secure registry and capable of supporting its security requirements. The transfer process would likely include a re-verification of the registrant's eligibility and compliance status to ensure security standards are maintained. Standard ICANN transfer policies would apply, but may be supplemented by additional registry-specific procedures.

    What security standards would a .secure domain require?

    While the final specifications were never published for the proposed TLD, the application suggested requirements like mandatory DNSSEC, enforced use of HTTPS with strong certificates, and email security measures. Registrants would likely need to submit to vulnerability scans and comply with a defined security framework. The registry operator would set the exact technical and operational standards that all domain holders must follow.

    How would trademark holders be protected during the launch?

    If the TLD launched, it would be required to follow ICANN's rights protection mechanisms. This includes a Sunrise Period allowing verified trademark owners to register their marks before general availability. The registry would also be obligated to implement the Uniform Rapid Suspension (URS) and Uniform Domain-Name Dispute-Resolution Policy (UDRP) to address cybersquatting.

    Could an individual register a .secure domain for a personal blog?

    It is unlikely, as the proposed model emphasized high-security use cases for organizations. The compliance costs and technical requirements would probably be prohibitive for most personal sites. The registry would assess each application against its security criteria, and a personal blog would likely not meet the intended use case or justify the operational overhead.