• AI Domains
  • Pricing
  • Membership

    • .properties

    Generic top-level domainsIDNDNSSEC

    Overview

    • .properties refers to two related things documented in the provided sources:
      • A generic top-level domain (gTLD) string delegated in ICANN's New gTLD Program and operated by Donuts (Big Pass, LLC).
      • A widely used file extension in Java-related technologies for storing application configuration parameters and localization resource bundles (property files).

    History

    • gTLD

      • The .properties string was applied for during ICANN's New gTLD Program and is listed as active.
      • Registry operator / manager: Donuts (Big Pass, LLC).
      • A Registry Agreement with ICANN was signed on December 5, 2013.
      • .properties was delegated to the DNS Root Zone on 4 February 2014.

    • File format

      • The .properties file format is commonly used in Java for application configuration and resource bundles.
      • Before Java 9, .properties files were traditionally encoded in ISO-8859-1 (Latin-1); non-Latin-1 characters required Unicode escape sequences (\uHHHH) or conversion tools such as native2ascii or po2prop.
      • Java 1.5 introduced an XML Properties format (which is UTF-8 encoded by default).
      • In Java 9 and later, the default encoding for property resource bundles was changed to UTF-8 (with fallback to ISO-8859-1 on invalid sequences).

    Usage and Audience

    • As a gTLD

      • The .properties gTLD is categorized under "Real Estate" in the ICANNWiki listing. The registry is Donuts (Big Pass, LLC).

    • As a file format (Java and beyond)

      • Purpose: store configurable parameters as key/value string pairs and to provide localized strings via property resource bundles.
      • Common characteristics:
        • Each line typically stores a single property, with key/value separated by =, :, or whitespace.
        • Comments begin with # or ! as the first non-blank character.
        • Backslash (\) is used for escaping and for continuing values across lines.
        • Unicode escapes (\uHHHH) are used for non-Latin-1 characters in legacy encodings; modern Java supports UTF-8 for resource bundles.
      • Editing and tooling: any text editor can edit .properties files (Notepad, Emacs, Vim, etc.). Third-party editors and IDE plugins provide additional features such as validation, key synchronization, and encoding conversion.
      • Non-Java and ecosystem uses: several other projects and ecosystems use .properties files or compatible formats, including Apache Flex (UTF-8 encoded in that context), Apache mod_jk (uriworkermap.properties), Perl (Config::Properties), SAP (SAPUI5/OpenUI5 localization), and packages in Node.js and PHP ecosystems.

    Notable Cases or Examples

    • File-format related tools and projects mentioned in the sources:
      • native2ascii (JDK tool) and po2prop (Translate Toolkit) for converting non-Latin-1 text to .properties-escaped format.
      • Java XML Properties format (introduced in Java 1.5) as an alternative that uses UTF-8.
      • Libraries and utilities: Jackson Properties module (mapping properties to Java objects), various Eclipse plugins (MultiProperties, Properties Editor), Java Properties Editor application, JLokalize, and other open-source editors and converters.
      • Specific product/framework usage: SAPUI5/OpenUI5 uses .properties for localization; Apache Flex uses UTF-8 encoded .properties files; mod_jk has its own interpretations for certain characters in .properties-formatted config files.

    Operator

    Binky Moon, LLC

    Whois

    % IANA WHOIS server
% for more information on IANA, visit http://www.iana.org
% This query returned 1 object

domain:       PROPERTIES

organisation: Binky Moon, LLC
address:      c/o Identity Digital Limited
address:      10500 NE 8th Street, Suite 750
address:      Bellevue WA 98004
address:      United States of America (the)

contact:      administrative
name:         Vice President, Engineering
organisation: Identity Digital Limited
address:      10500 NE 8th Street, Suite 750
address:      Bellevue WA 98004
address:      United States of America (the)
phone:        +1.425.298.2200
fax-no:       +1.425.671.0020
e-mail:       tldadmin@identity.digital

contact:      technical
name:         Senior Director, DNS Infrastructure Group
organisation: Identity Digital Limited
address:      10500 NE 8th Street, Suite 750
address:      Bellevue WA 98004
address:      United States of America (the)
phone:        +1.425.298.2200
fax-no:       +1.425.671.0020
e-mail:       tldtech@identity.digital

nserver:      V0N0.NIC.PROPERTIES 2a01:8840:16:0:0:0:0:46 65.22.20.46
nserver:      V0N1.NIC.PROPERTIES 2a01:8840:17:0:0:0:0:46 65.22.21.46
nserver:      V0N2.NIC.PROPERTIES 2a01:8840:18:0:0:0:0:46 65.22.22.46
nserver:      V0N3.NIC.PROPERTIES 161.232.10.46 2a01:8840:f4:0:0:0:0:46
nserver:      V2N0.NIC.PROPERTIES 2a01:8840:19:0:0:0:0:46 65.22.23.46
nserver:      V2N1.NIC.PROPERTIES 161.232.11.46 2a01:8840:f5:0:0:0:0:46
ds-rdata:     24565 8 2 519c0cae03f6f4a6679f85ed1376f04a6702406f0731734618f608895306e4f5

whois:        whois.nic.properties

status:       ACTIVE
remarks:      Registration information: https://www.identity.digital/

created:      2014-01-30
changed:      2023-09-13
source:       IANA

    Registrars