faqs.org - Internet FAQ Archives

RFC 3490 - Internationalizing Domain Names in Applications (IDNA)


Or Display the document by number




Network Working Group                                       P. Faltstrom
Request for Comments: 3490                                         Cisco
Category: Standards Track                                     P. Hoffman
                                                              IMC & VPNC
                                                             A. Costello
                                                             UC Berkeley
                                                              March 2003

         Internationalizing Domain Names in Applications (IDNA)

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2003).  All Rights Reserved.

Abstract

   Until now, there has been no standard method for domain names to use
   characters outside the ASCII repertoire.  This document defines
   internationalized domain names (IDNs) and a mechanism called
   Internationalizing Domain Names in Applications (IDNA) for handling
   them in a standard fashion.  IDNs use characters drawn from a large
   repertoire (Unicode), but IDNA allows the non-ASCII characters to be
   represented using only the ASCII characters already allowed in so-
   called host names today.  This backward-compatible representation is
   required in existing protocols like DNS, so that IDNs can be
   introduced with no changes to the existing infrastructure.  IDNA is
   only meant for processing domain names, not free text.

Table of Contents

   1. Introduction..................................................  2
      1.1 Problem Statement.........................................  3
      1.2 Limitations of IDNA.......................................  3
      1.3 Brief overview for application developers.................  4
   2. Terminology...................................................  5
   3. Requirements and applicability................................  7
      3.1 Requirements..............................................  7
      3.2 Applicability.............................................  8
         3.2.1. DNS resource records................................  8

         3.2.2. Non-domain-name data types stored in domain names...  9
   4. Conversion operations.........................................  9
      4.1 ToASCII................................................... 10
      4.2 ToUnicode................................................. 11
   5. ACE prefix.................................................... 12
   6. Implications for typical applications using DNS............... 13
      6.1 Entry and display in applications......................... 14
      6.2 Applications and resolver libraries....................... 15
      6.3 DNS servers............................................... 15
      6.4 Avoiding exposing users to the raw ACE encoding........... 16
      6.5  DNSSEC authentication of IDN domain names................ 16
   7. Name server considerations.................................... 17
   8. Root server considerations.................................... 17
   9. References.................................................... 18
      9.1 Normative References...................................... 18
      9.2 Informative References.................................... 18
   10. Security Considerations...................................... 19
   11. IANA Considerations.......................................... 20
   12. Authors' Addresses........................................... 21
   13. Full Copyright Statement..................................... 22

1. Introduction

   IDNA works by allowing applications to use certain ASCII name labels
   (beginning with a special prefix) to represent non-ASCII name labels.
   Lower-layer protocols need not be aware of this; therefore IDNA does
   not depend on changes to any infrastructure.  In particular, IDNA
   does not depend on any changes to DNS servers, resolvers, or protocol
   elements, because the ASCII name service provided by the existing DNS
   is entirely sufficient for IDNA.

   This document does not require any applications to conform to IDNA,
   but applications can elect to use IDNA in order to support IDN while
   maintaining interoperability with existing infrastructure.  If an
   application wants to use non-ASCII characters in domain names, IDNA
   is the only currently-defined option.  Adding IDNA support to an
   existing application entails changes to the application only, and
   leaves room for flexibility in the user interface.

   A great deal of the discussion of IDN solutions has focused on
   transition issues and how IDN will work in a world where not all of
   the components have been updated.  Proposals that were not chosen by
   the IDN Working Group would depend on user applications, resolvers,
   and DNS servers being updated in order for a user to use an
   internationalized domain name.  Rather than rely on widespread
   updating of all components, IDNA depends on updates to user
   applications only; no changes are needed to the DNS protocol or any
   DNS servers or the resolvers on user's computers.

1.1 Problem Statement

   The IDNA specification solves the problem of extending the repertoire
   of characters that can be used in domain names to include the Unicode
   repertoire (with some restrictions).

   IDNA does not extend the service offered by DNS to the applications.
   Instead, the applications (and, by implication, the users) continue
   to see an exact-match lookup service.  Either there is a single
   exactly-matching name or there is no match.  This model has served
   the existing applications well, but it requires, with or without
   internationalized domain names, that users know the exact spelling of
   the domain names that the users type into applications such as web
   browsers and mail user agents.  The introduction of the larger
   repertoire of characters potentially makes the set of misspellings
   larger, especially given that in some cases the same appearance, for
   example on a business card, might visually match several Unicode code
   points or several sequences of code points.

   IDNA allows the graceful introduction of IDNs not only by avoiding
   upgrades to existing infrastructure (such as DNS servers and mail
   transport agents), but also by allowing some rudimentary use of IDNs
   in applications by using the ASCII representation of the non-ASCII
   name labels.  While such names are very user-unfriendly to read and
   type, and hence are not suitable for user input, they allow (for
   instance) replying to email and clicking on URLs even though the
   domain name displayed is incomprehensible to the user.  In order to
   allow user-friendly input and output of the IDNs, the applications
   need to be modified to conform to this specification.

   IDNA uses the Unicode character repertoire, which avoids the
   significant delays that would be inherent in waiting for a different
   and specific character set be defined for IDN purposes by some other
   standards developing organization.

1.2 Limitations of IDNA

   The IDNA protocol does not solve all linguistic issues with users
   inputting names in different scripts.  Many important language-based
   and script-based mappings are not covered in IDNA and need to be
   handled outside the protocol.  For example, names that are entered in
   a mix of traditional and simplified Chinese characters will not be
   mapped to a single canonical name.  Another example is Scandinavian
   names that are entered with U+00F6 (LATIN SMALL LETTER O WITH
   DIAERESIS) will not be mapped to U+00F8 (LATIN SMALL LETTER O WITH
   STROKE).

   An example of an important issue that is not considered in detail in
   IDNA is how to provide a high probability that a user who is entering
   a domain name based on visual information (such as from a business
   card or billboard) or aural information (such as from a telephone or
   radio) would correctly enter the IDN.  Similar issues exist for ASCII
   domain names, for example the possible visual confusion between the
   letter 'O' and the digit zero, but the introduction of the larger
   repertoire of characters creates more opportunities of similar
   looking and similar sounding names.  Note that this is a complex
   issue relating to languages, input methods on computers, and so on.
   Furthermore, the kind of matching and searching necessary for a high
   probability of success would not fit the role of the DNS and its
   exact matching function.

1.3 Brief overview for application developers

   Applications can use IDNA to support internationalized domain names
   anywhere that ASCII domain names are already supported, including DNS
   master files and resolver interfaces.  (Applications can also define
   protocols and interfaces that support IDNs directly using non-ASCII
   representations.  IDNA does not prescribe any particular
   representation for new protocols, but it still defines which names
   are valid and how they are compared.)

   The IDNA protocol is contained completely within applications.  It is
   not a client-server or peer-to-peer protocol: everything is done
   inside the application itself.  When used with a DNS resolver
   library, IDNA is inserted as a "shim" between the application and the
   resolver library.  When used for writing names into a DNS zone, IDNA
   is used just before the name is committed to the zone.

   There are two operations described in section 4 of this document:

   -  The ToASCII operation is used before sending an IDN to something
      that expects ASCII names (such as a resolver) or writing an IDN
      into a place that expects ASCII names (such as a DNS master file).

   -  The ToUnicode operation is used when displaying names to users,
      for example names obtained from a DNS zone.

   It is important to note that the ToASCII operation can fail.  If it
   fails when processing a domain name, that domain name cannot be used
   as an internationalized domain name and the application has to have
   some method of dealing with this failure.

   IDNA requires that implementations process input strings with
   Nameprep [NAMEPREP], which is a profile of Stringprep [STRINGPREP],
   and then with Punycode [PUNYCODE].  Implementations of IDNA MUST

   fully implement Nameprep and Punycode; neither Nameprep nor Punycode
   are optional.

2. Terminology

   The key words "MUST", "SHALL", "REQUIRED", "SHOULD", "RECOMMENDED",
   and "MAY" in this document are to be interpreted as described in BCP
   14, RFC 2119 [RFC2119].

   A code point is an integer value associated with a character in a
   coded character set.

   Unicode [UNICODE] is a coded character set containing tens of
   thousands of characters.  A single Unicode code point is denoted by
   "U+" followed by four to six hexadecimal digits, while a range of
   Unicode code points is denoted by two hexadecimal numbers separated
   by "..", with no prefixes.

   ASCII means US-ASCII [USASCII], a coded character set containing 128
   characters associated with code points in the range 0..7F.  Unicode
   is an extension of ASCII: it includes all the ASCII characters and
   associates them with the same code points.

   The term "LDH code points" is defined in this document to mean the
   code points associated with ASCII letters, digits, and the hyphen-
   minus; that is, U+002D, 30..39, 41..5A, and 61..7A. "LDH" is an
   abbreviation for "letters, digits, hyphen".

   [STD13] talks about "domain names" and "host names", but many people
   use the terms interchangeably.  Further, because [STD13] was not
   terribly clear, many people who are sure they know the exact
   definitions of each of these terms disagree on the definitions.  In
   this document the term "domain name" is used in general.  This
   document explicitly cites [STD3] whenever referring to the host name
   syntax restrictions defined therein.

   A label is an individual part of a domain name.  Labels are usually
   shown separated by dots; for example, the domain name
   "www.example.com" is composed of three labels: "www", "example", and
   "com".  (The zero-length root label described in [STD13], which can
   be explicit as in "www.example.com." or implicit as in
   "www.example.com", is not considered a label in this specification.)
   IDNA extends the set of usable characters in labels that are text.
   For the rest of this document, the term "label" is shorthand for
   "text label", and "every label" means "every text label".

   An "internationalized label" is a label to which the ToASCII
   operation (see section 4) can be applied without failing (with the
   UseSTD3ASCIIRules flag unset).  This implies that every ASCII label
   that satisfies the [STD13] length restriction is an internationalized
   label.  Therefore the term "internationalized label" is a
   generalization, embracing both old ASCII labels and new non-ASCII
   labels.  Although most Unicode characters can appear in
   internationalized labels, ToASCII will fail for some input strings,
   and such strings are not valid internationalized labels.

   An "internationalized domain name" (IDN) is a domain name in which
   every label is an internationalized label.  This implies that every
   ASCII domain name is an IDN (which implies that it is possible for a
   name to be an IDN without it containing any non-ASCII characters).
   This document does not attempt to define an "internationalized host
   name".  Just as has been the case with ASCII names, some DNS zone
   administrators may impose restrictions, beyond those imposed by DNS
   or IDNA, on the characters or strings that may be registered as
   labels in their zones.  Such restrictions have no impact on the
   syntax or semantics of DNS protocol messages; a query for a name that
   matches no records will yield the same response regardless of the
   reason why it is not in the zone.  Clients issuing queries or
   interpreting responses cannot be assumed to have any knowledge of
   zone-specific restrictions or conventions.

   In IDNA, equivalence of labels is defined in terms of the ToASCII
   operation, which constructs an ASCII form for a given label, whether
   or not the label was already an ASCII label.  Labels are defined to
   be equivalent if and only if their ASCII forms produced by ToASCII
   match using a case-insensitive ASCII comparison.  ASCII labels
   already have a notion of equivalence: upper case and lower case are
   considered equivalent.  The IDNA notion of equivalence is an
   extension of that older notion.  Equivalent labels in IDNA are
   treated as alternate forms of the same label, just as "foo" and "Foo"
   are treated as alternate forms of the same label.

   To allow internationalized labels to be handled by existing
   applications, IDNA uses an "ACE label" (ACE stands for ASCII
   Compatible Encoding).  An ACE label is an internationalized label
   that can be rendered in ASCII and is equivalent to an
   internationalized label that cannot be rendered in ASCII.  Given any
   internationalized label that cannot be rendered in ASCII, the ToASCII
   operation will convert it to an equivalent ACE label (whereas an
   ASCII label will be left unaltered by ToASCII).  ACE labels are
   unsuitable for display to users.  The ToUnicode operation will
   convert any label to an equivalent non-ACE label.  In fact, an ACE
   label is formally defined to be any label that the ToUnicode
   operation would alter (whereas non-ACE labels are left unaltered by

   ToUnicode).  Every ACE label begins with the ACE prefix specified in
   section 5.  The ToASCII and ToUnicode operations are specified in
   section 4.

   The "ACE prefix" is defined in this document to be a string of ASCII
   characters that appears at the beginning of every ACE label.  It is
   specified in section 5.

   A "domain name slot" is defined in this document to be a protocol
   element or a function argument or a return value (and so on)
   explicitly designated for carrying a domain name.  Examples of domain
   name slots include: the QNAME field of a DNS query; the name argument
   of the gethostbyname() library function; the part of an email address
   following the at-sign (@) in the From: field of an email message
   header; and the host portion of the URI in the src attribute of an
   HTML <IMG> tag.  General text that just happens to contain a domain
   name is not a domain name slot; for example, a domain name appearing
   in the plain text body of an email message is not occupying a domain
   name slot.

   An "IDN-aware domain name slot" is defined in this document to be a
   domain name slot explicitly designated for carrying an
   internationalized domain name as defined in this document.  The
   designation may be static (for example, in the specification of the
   protocol or interface) or dynamic (for example, as a result of
   negotiation in an interactive session).

   An "IDN-unaware domain name slot" is defined in this document to be
   any domain name slot that is not an IDN-aware domain name slot.
   Obviously, this includes any domain name slot whose specification
   predates IDNA.

3. Requirements and applicability

3.1 Requirements

   IDNA conformance means adherence to the following four requirements:

   1) Whenever dots are used as label separators, the following
      characters MUST be recognized as dots: U+002E (full stop), U+3002
      (ideographic full stop), U+FF0E (fullwidth full stop), U+FF61
      (halfwidth ideographic full stop).

   2) Whenever a domain name is put into an IDN-unaware domain name slot
      (see section 2), it MUST contain only ASCII characters.  Given an
      internationalized domain name (IDN), an equivalent domain name
      satisfying this requirement can be obtained by applying the

      ToASCII operation (see section 4) to each label and, if dots are
      used as label separators, changing all the label separators to
      U+002E.

   3) ACE labels obtained from domain name slots SHOULD be hidden from
      users when it is known that the environment can handle the non-ACE
      form, except when the ACE form is explicitly requested.  When it
      is not known whether or not the environment can handle the non-ACE
      form, the application MAY use the non-ACE form (which might fail,
      such as by not being displayed properly), or it MAY use the ACE
      form (which will look unintelligle to the user).  Given an
      internationalized domain name, an equivalent domain name
      containing no ACE labels can be obtained by applying the ToUnicode
      operation (see section 4) to each label.  When requirements 2 and
      3 both apply, requirement 2 takes precedence.

   4) Whenever two labels are compared, they MUST be considered to match
      if and only if they are equivalent, that is, their ASCII forms
      (obtained by applying ToASCII) match using a case-insensitive
      ASCII comparison.  Whenever two names are compared, they MUST be
      considered to match if and only if their corresponding labels
      match, regardless of whether the names use the same forms of label
      separators.

3.2 Applicability

   IDNA is applicable to all domain names in all domain name slots
   except where it is explicitly excluded.

   This implies that IDNA is applicable to many protocols that predate
   IDNA.  Note that IDNs occupying domain name slots in those protocols
   MUST be in ASCII form (see section 3.1, requirement 2).

3.2.1. DNS resource records

   IDNA does not apply to domain names in the NAME and RDATA fields of
   DNS resource records whose CLASS is not IN.  This exclusion applies
   to every non-IN class, present and future, except where future
   standards override this exclusion by explicitly inviting the use of
   IDNA.

   There are currently no other exclusions on the applicability of IDNA
   to DNS resource records; it depends entirely on the CLASS, and not on
   the TYPE.  This will remain true, even as new types are defined,
   unless there is a compelling reason for a new type to complicate
   matters by imposing type-specific rules.

3.2.2. Non-domain-name data types stored in domain names

   Although IDNA enables the representation of non-ASCII characters in
   domain names, that does not imply that IDNA enables the
   representation of non-ASCII characters in other data types that are
   stored in domain names.  For example, an email address local part is
   sometimes stored in a domain label (hostmaster@example.com would be
   represented as hostmaster.example.com in the RDATA field of an SOA
   record).  IDNA does not update the existing email standards, which
   allow only ASCII characters in local parts.  Therefore, unless the
   email standards are revised to invite the use of IDNA for local
   parts, a domain label that holds the local part of an email address
   SHOULD NOT begin with the ACE prefix, and even if it does, it is to
   be interpreted literally as a local part that happens to begin with
   the ACE prefix.

4. Conversion operations

   An application converts a domain name put into an IDN-unaware slot or
   displayed to a user.  This section specifies the steps to perform in
   the conversion, and the ToASCII and ToUnicode operations.

   The input to ToASCII or ToUnicode is a single label that is a
   sequence of Unicode code points (remember that all ASCII code points
   are also Unicode code points).  If a domain name is represented using
   a character set other than Unicode or US-ASCII, it will first need to
   be transcoded to Unicode.

   Starting from a whole domain name, the steps that an application
   takes to do the conversions are:

   1) Decide whether the domain name is a "stored string" or a "query
      string" as described in [STRINGPREP].  If this conversion follows
      the "queries" rule from [STRINGPREP], set the flag called
      "AllowUnassigned".

   2) Split the domain name into individual labels as described in
      section 3.1.  The labels do not include the separator.

   3) For each label, decide whether or not to enforce the restrictions
      on ASCII characters in host names [STD3].  (Applications already
      faced this choice before the introduction of IDNA, and can
      continue to make the decision the same way they always have; IDNA
      makes no new recommendations regarding this choice.)  If the
      restrictions are to be enforced, set the flag called
      "UseSTD3ASCIIRules" for that label.

   4) Process each label with either the ToASCII or the ToUnicode
      operation as appropriate.  Typically, you use the ToASCII
      operation if you are about to put the name into an IDN-unaware
      slot, and you use the ToUnicode operation if you are displaying
      the name to a user; section 3.1 gives greater detail on the
      applicable requirements.

   5) If ToASCII was applied in step 4 and dots are used as label
      separators, change all the label separators to U+002E (full stop).

   The following two subsections define the ToASCII and ToUnicode
   operations that are used in step 4.

   This description of the protocol uses specific procedure names, names
   of flags, and so on, in order to facilitate the specification of the
   protocol.  These names, as well as the actual steps of the
   procedures, are not required of an implementation.  In fact, any
   implementation which has the same external behavior as specified in
   this document conforms to this specification.

4.1 ToASCII

   The ToASCII operation takes a sequence of Unicode code points that
   make up one label and transforms it into a sequence of code points in
   the ASCII range (0..7F).  If ToASCII succeeds, the original sequence
   and the resulting sequence are equivalent labels.

   It is important to note that the ToASCII operation can fail.  ToASCII
   fails if any step of it fails.  If any step of the ToASCII operation
   fails on any label in a domain name, that domain name MUST NOT be
   used as an internationalized domain name.  The method for dealing
   with this failure is application-specific.

   The inputs to ToASCII are a sequence of code points, the
   AllowUnassigned flag, and the UseSTD3ASCIIRules flag.  The output of
   ToASCII is either a sequence of ASCII code points or a failure
   condition.

   ToASCII never alters a sequence of code points that are all in the
   ASCII range to begin with (although it could fail).  Applying the
   ToASCII operation multiple times has exactly the same effect as
   applying it just once.

   ToASCII consists of the following steps:

   1. If the sequence contains any code points outside the ASCII range
      (0..7F) then proceed to step 2, otherwise skip to step 3.

   2. Perform the steps specified in [NAMEPREP] and fail if there is an
      error.  The AllowUnassigned flag is used in [NAMEPREP].

   3. If the UseSTD3ASCIIRules flag is set, then perform these checks:

     (a) Verify the absence of non-LDH ASCII code points; that is, the
         absence of 0..2C, 2E..2F, 3A..40, 5B..60, and 7B..7F.

     (b) Verify the absence of leading and trailing hyphen-minus; that
         is, the absence of U+002D at the beginning and end of the
         sequence.

   4. If the sequence contains any code points outside the ASCII range
      (0..7F) then proceed to step 5, otherwise skip to step 8.

   5. Verify that the sequence does NOT begin with the ACE prefix.

   6. Encode the sequence using the encoding algorithm in [PUNYCODE] and
      fail if there is an error.

   7. Prepend the ACE prefix.

   8. Verify that the number of code points is in the range 1 to 63
      inclusive.

4.2 ToUnicode

   The ToUnicode operation takes a sequence of Unicode code points that
   make up one label and returns a sequence of Unicode code points.  If
   the input sequence is a label in ACE form, then the result is an
   equivalent internationalized label that is not in ACE form, otherwise
   the original sequence is returned unaltered.

   ToUnicode never fails.  If any step fails, then the original input
   sequence is returned immediately in that step.

   The ToUnicode output never contains more code points than its input.
   Note that the number of octets needed to represent a sequence of code
   points depends on the particular character encoding used.

   The inputs to ToUnicode are a sequence of code points, the
   AllowUnassigned flag, and the UseSTD3ASCIIRules flag.  The output of
   ToUnicode is always a sequence of Unicode code points.

   1. If all code points in the sequence are in the ASCII range (0..7F)
      then skip to step 3.

   2. Perform the steps specified in [NAMEPREP] and fail if there is an
      error.  (If step 3 of ToASCII is also performed here, it will not
      affect the overall behavior of ToUnicode, but it is not
      necessary.)  The AllowUnassigned flag is used in [NAMEPREP].

   3. Verify that the sequence begins with the ACE prefix, and save a
      copy of the sequence.

   4. Remove the ACE prefix.

   5. Decode the sequence using the decoding algorithm in [PUNYCODE] and
      fail if there is an error.  Save a copy of the result of this
      step.

   6. Apply ToASCII.

   7. Verify that the result of step 6 matches the saved copy from step
      3, using a case-insensitive ASCII comparison.

   8. Return the saved copy from step 5.

5. ACE prefix

   The ACE prefix, used in the conversion operations (section 4), is two
   alphanumeric ASCII characters followed by two hyphen-minuses.  It
   cannot be any of the prefixes already used in earlier documents,
   which includes the following: "bl--", "bq--", "dq--", "lq--", "mq--",
   "ra--", "wq--" and "zq--".  The ToASCII and ToUnicode operations MUST
   recognize the ACE prefix in a case-insensitive manner.

   The ACE prefix for IDNA is "xn--" or any capitalization thereof.

   This means that an ACE label might be "xn--de-jg4avhby1noc0d", where
   "de-jg4avhby1noc0d" is the part of the ACE label that is generated by
   the encoding steps in [PUNYCODE].

   While all ACE labels begin with the ACE prefix, not all labels
   beginning with the ACE prefix are necessarily ACE labels.  Non-ACE
   labels that begin with the ACE prefix will confuse users and SHOULD
   NOT be allowed in DNS zones.

6. Implications for typical applications using DNS

   In IDNA, applications perform the processing needed to input
   internationalized domain names from users, display internationalized
   domain names to users, and process the inputs and outputs from DNS
   and other protocols that carry domain names.

   The components and interfaces between them can be represented
   pictorially as:

                    +------+
                    | User |
                    +------+
                       ^
                       | Input and display: local interface methods
                       | (pen, keyboard, glowing phosphorus, ...)
   +-------------------|-------------------------------+
   |                   v                               |
   |          +-----------------------------+          |
   |          |        Application          |          |
   |          |   (ToASCII and ToUnicode    |          |
   |          |      operations may be      |          |
   |          |        called here)         |          |
   |          +-----------------------------+          |
   |                   ^        ^                      | End system
   |                   |        |                      |
   | Call to resolver: |        | Application-specific |
   |              ACE  |        | protocol:            |
   |                   v        | ACE unless the       |
   |           +----------+     | protocol is updated  |
   |           | Resolver |     | to handle other      |
   |           +----------+     | encodings            |
   |                 ^          |                      |
   +-----------------|----------|----------------------+
       DNS protocol: |          |
                 ACE |          |
                     v          v
          +-------------+    +---------------------+
          | DNS servers |    | Application servers |
          +-------------+    +---------------------+

   The box labeled "Application" is where the application splits a
   domain name into labels, sets the appropriate flags, and performs the
   ToASCII and ToUnicode operations.  This is described in section 4.

6.1 Entry and display in applications

   Applications can accept domain names using any character set or sets
   desired by the application developer, and can display domain names in
   any charset.  That is, the IDNA protocol does not affect the
   interface between users and applications.

   An IDNA-aware application can accept and display internationalized
   domain names in two formats: the internationalized character set(s)
   supported by the application, and as an ACE label.  ACE labels that
   are displayed or input MUST always include the ACE prefix.
   Applications MAY allow input and display of ACE labels, but are not
   encouraged to do so except as an interface for special purposes,
   possibly for debugging, or to cope with display limitations as
   described in section 6.4..  ACE encoding is opaque and ugly, and
   should thus only be exposed to users who absolutely need it.  Because
   name labels encoded as ACE name labels can be rendered either as the
   encoded ASCII characters or the proper decoded characters, the
   application MAY have an option for the user to select the preferred
   method of display; if it does, rendering the ACE SHOULD NOT be the
   default.

   Domain names are often stored and transported in many places.  For
   example, they are part of documents such as mail messages and web
   pages.  They are transported in many parts of many protocols, such as
   both the control commands and the RFC 2822 body parts of SMTP, and
   the headers and the body content in HTTP.  It is important to
   remember that domain names appear both in domain name slots and in
   the content that is passed over protocols.

   In protocols and document formats that define how to handle
   specification or negotiation of charsets, labels can be encoded in
   any charset allowed by the protocol or document format.  If a
   protocol or document format only allows one charset, the labels MUST
   be given in that charset.

   In any place where a protocol or document format allows transmission
   of the characters in internationalized labels, internationalized
   labels SHOULD be transmitted using whatever character encoding and
   escape mechanism that the protocol or document format uses at that
   place.

   All protocols that use domain name slots already have the capacity
   for handling domain names in the ASCII charset.  Thus, ACE labels
   (internationalized labels that have been processed with the ToASCII
   operation) can inherently be handled by those protocols.

6.2 Applications and resolver libraries

   Applications normally use functions in the operating system when they
   resolve DNS queries.  Those functions in the operating system are
   often called "the resolver library", and the applications communicate
   with the resolver libraries through a programming interface (API).

   Because these resolver libraries today expect only domain names in
   ASCII, applications MUST prepare labels that are passed to the
   resolver library using the ToASCII operation.  Labels received from
   the resolver library contain only ASCII characters; internationalized
   labels that cannot be represented directly in ASCII use the ACE form.
   ACE labels always include the ACE prefix.

   An operating system might have a set of libraries for performing the
   ToASCII operation.  The input to such a library might be in one or
   more charsets that are used in applications (UTF-8 and UTF-16 are
   likely candidates for almost any operating system, and script-
   specific charsets are likely for localized operating systems).

   IDNA-aware applications MUST be able to work with both non-
   internationalized labels (those that conform to [STD13] and [STD3])
   and internationalized labels.

   It is expected that new versions of the resolver libraries in the
   future will be able to accept domain names in other charsets than
   ASCII, and application developers might one day pass not only domain
   names in Unicode, but also in local script to a new API for the
   resolver libraries in the operating system.  Thus the ToASCII and
   ToUnicode operations might be performed inside these new versions of
   the resolver libraries.

   Domain names passed to resolvers or put into the question section of
   DNS requests follow the rules for "queries" from [STRINGPREP].

6.3 DNS servers

   Domain names stored in zones follow the rules for "stored strings"
   from [STRINGPREP].

   For internationalized labels that cannot be represented directly in
   ASCII, DNS servers MUST use the ACE form produced by the ToASCII
   operation.  All IDNs served by DNS servers MUST contain only ASCII
   characters.

   If a signaling system which makes negotiation possible between old
   and new DNS clients and servers is standardized in the future, the
   encoding of the query in the DNS protocol itself can be changed from

   ACE to something else, such as UTF-8.  The question whether or not
   this should be used is, however, a separate problem and is not
   discussed in this memo.

6.4 Avoiding exposing users to the raw ACE encoding

   Any application that might show the user a domain name obtained from
   a domain name slot, such as from gethostbyaddr or part of a mail
   header, will need to be updated if it is to prevent users from seeing
   the ACE.

   If an application decodes an ACE name using ToUnicode but cannot show
   all of the characters in the decoded name, such as if the name
   contains characters that the output system cannot display, the
   application SHOULD show the name in ACE format (which always includes
   the ACE prefix) instead of displaying the name with the replacement
   character (U+FFFD).  This is to make it easier for the user to
   transfer the name correctly to other programs.  Programs that by
   default show the ACE form when they cannot show all the characters in
   a name label SHOULD also have a mechanism to show the name that is
   produced by the ToUnicode operation with as many characters as
   possible and replacement characters in the positions where characters
   cannot be displayed.

   The ToUnicode operation does not alter labels that are not valid ACE
   labels, even if they begin with the ACE prefix.  After ToUnicode has
   been applied, if a label still begins with the ACE prefix, then it is
   not a valid ACE label, and is not equivalent to any of the
   intermediate Unicode strings constructed by ToUnicode.

6.5  DNSSEC authentication of IDN domain names

   DNS Security [RFC2535] is a method for supplying cryptographic
   verification information along with DNS messages.  Public Key
   Cryptography is used in conjunction with digital signatures to
   provide a means for a requester of domain information to authenticate
   the source of the data.  This ensures that it can be traced back to a
   trusted source, either directly, or via a chain of trust linking the
   source of the information to the top of the DNS hierarchy.

   IDNA specifies that all internationalized domain names served by DNS
   servers that cannot be represented directly in ASCII must use the ACE
   form produced by the ToASCII operation.  This operation must be
   performed prior to a zone being signed by the private key for that
   zone.  Because of this ordering, it is important to recognize that
   DNSSEC authenticates the ASCII domain name, not the Unicode form or

   the mapping between the Unicode form and the ASCII form.  In the
   presence of DNSSEC, this is the name that MUST be signed in the zone
   and MUST be validated against.

   One consequence of this for sites deploying IDNA in the presence of
   DNSSEC is that any special purpose proxies or forwarders used to
   transform user input into IDNs must be earlier in the resolution flow
   than DNSSEC authenticating nameservers for DNSSEC to work.

7. Name server considerations

   Existing DNS servers do not know the IDNA rules for handling non-
   ASCII forms of IDNs, and therefore need to be shielded from them.
   All existing channels through which names can enter a DNS server
   database (for example, master files [STD13] and DNS update messages
   [RFC2136]) are IDN-unaware because they predate IDNA, and therefore
   requirement 2 of section 3.1 of this document provides the needed
   shielding, by ensuring that internationalized domain names entering
   DNS server databases through such channels have already been
   converted to their equivalent ASCII forms.

   It is imperative that there be only one ASCII encoding for a
   particular domain name.  Because of the design of the ToASCII and
   ToUnicode operations, there are no ACE labels that decode to ASCII
   labels, and therefore name servers cannot contain multiple ASCII
   encodings of the same domain name.

   [RFC2181] explicitly allows domain labels to contain octets beyond
   the ASCII range (0..7F), and this document does not change that.
   Note, however, that there is no defined interpretation of octets
   80..FF as characters.  If labels containing these octets are returned
   to applications, unpredictable behavior could result.  The ASCII form
   defined by ToASCII is the only standard representation for
   internationalized labels in the current DNS protocol.

8. Root server considerations

   IDNs are likely to be somewhat longer than current domain names, so
   the bandwidth needed by the root servers is likely to go up by a
   small amount.  Also, queries and responses for IDNs will probably be
   somewhat longer than typical queries today, so more queries and
   responses may be forced to go to TCP instead of UDP.

9. References

9.1 Normative References

   [RFC2119]    Bradner, S., "Key words for use in RFCs to Indicate
                Requirement Levels", BCP 14, RFC 2119, March 1997.

   [STRINGPREP] Hoffman, P. and M. Blanchet, "Preparation of
                Internationalized Strings ("stringprep")", RFC 3454,
                December 2002.

   [NAMEPREP]   Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep
                Profile for Internationalized Domain Names (IDN)", RFC
                3491, March 2003.

   [PUNYCODE]   Costello, A., "Punycode: A Bootstring encoding of
                Unicode for use with Internationalized Domain Names in
                Applications (IDNA)", RFC 3492, March 2003.

   [STD3]       Braden, R., "Requirements for Internet Hosts --
                Communication Layers", STD 3, RFC 1122, and
                "Requirements for Internet Hosts -- Application and
                Support", STD 3, RFC 1123, October 1989.

   [STD13]      Mockapetris, P., "Domain names - concepts and
                facilities", STD 13, RFC 1034 and "Domain names -
                implementation and specification", STD 13, RFC 1035,
                November 1987.

9.2 Informative References

   [RFC2535]    Eastlake, D., "Domain Name System Security Extensions",
                RFC 2535, March 1999.

   [RFC2181]    Elz, R. and R. Bush, "Clarifications to the DNS
                Specification", RFC 2181, July 1997.

   [UAX9]       Unicode Standard Annex #9, The Bidirectional Algorithm,
                <http://www.unicode.org/unicode/reports/tr9/>.

   [UNICODE]    The Unicode Consortium. The Unicode Standard, Version
                3.2.0 is defined by The Unicode Standard, Version 3.0
                (Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5),
                as amended by the Unicode Standard Annex #27: Unicode
                3.1 (http://www.unicode.org/reports/tr27/) and by the
                Unicode Standard Annex #28: Unicode 3.2
                (http://www.unicode.org/reports/tr28/).

   [USASCII]    Cerf, V., "ASCII format for Network Interchange", RFC
                20, October 1969.

10. Security Considerations

   Security on the Internet partly relies on the DNS.  Thus, any change
   to the characteristics of the DNS can change the security of much of
   the Internet.

   This memo describes an algorithm which encodes characters that are
   not valid according to STD3 and STD13 into octet values that are
   valid.  No security issues such as string length increases or new
   allowed values are introduced by the encoding process or the use of
   these encoded values, apart from those introduced by the ACE encoding
   itself.

   Domain names are used by users to identify and connect to Internet
   servers.  The security of the Internet is compromised if a user
   entering a single internationalized name is connected to different
   servers based on different interpretations of the internationalized
   domain name.

   When systems use local character sets other than ASCII and Unicode,
   this specification leaves the the problem of transcoding between the
   local character set and Unicode up to the application.  If different
   applications (or different versions of one application) implement
   different transcoding rules, they could interpret the same name
   differently and contact different servers.  This problem is not
   solved by security protocols like TLS that do not take local
   character sets into account.

   Because this document normatively refers to [NAMEPREP], [PUNYCODE],
   and [STRINGPREP], it includes the security considerations from those
   documents as well.

   If or when this specification is updated to use a more recent Unicode
   normalization table, the new normalization table will need to be
   compared with the old to spot backwards incompatible changes.  If
   there are such changes, they will need to be handled somehow, or
   there will be security as well as operational implications.  Methods
   to handle the conflicts could include keeping the old normalization,
   or taking care of the conflicting characters by operational means, or
   some other method.

   Implementations MUST NOT use more recent normalization tables than
   the one referenced from this document, even though more recent tables
   may be provided by operating systems.  If an application is unsure of
   which version of the normalization tables are in the operating

   system, the application needs to include the normalization tables
   itself.  Using normalization tables other than the one referenced
   from this specification could have security and operational
   implications.

   To help prevent confusion between characters that are visually
   similar, it is suggested that implementations provide visual
   indications where a domain name contains multiple scripts.  Such
   mechanisms can also be used to show when a name contains a mixture of
   simplified and traditional Chinese characters, or to distinguish zero
   and one from O and l.  DNS zone adminstrators may impose restrictions
   (subject to the limitations in section 2) that try to minimize
   homographs.

   Domain names (or portions of them) are sometimes compared against a
   set of privileged or anti-privileged domains.  In such situations it
   is especially important that the comparisons be done properly, as
   specified in section 3.1 requirement 4.  For labels already in ASCII
   form, the proper comparison reduces to the same case-insensitive
   ASCII comparison that has always been used for ASCII labels.

   The introduction of IDNA means that any existing labels that start
   with the ACE prefix and would be altered by ToUnicode will
   automatically be ACE labels, and will be considered equivalent to
   non-ASCII labels, whether or not that was the intent of the zone
   adminstrator or registrant.

11. IANA Considerations

   IANA has assigned the ACE prefix in consultation with the IESG.

12. Authors' Addresses

   Patrik Faltstrom
   Cisco Systems
   Arstaangsvagen 31 J
   S-117 43 Stockholm  Sweden

   EMail: paf@cisco.com

   Paul Hoffman
   Internet Mail Consortium and VPN Consortium
   127 Segre Place
   Santa Cruz, CA  95060  USA

   EMail: phoffman@imc.org

   Adam M. Costello
   University of California, Berkeley

   URL: http://www.nicemice.net/amc/

13. Full Copyright Statement

   Copyright (C) The Internet Society (2003).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.

 

User Contributions:

1
Samir emerson hurtado alvradi
Como puedo cancelar mis facturasi mo me
An entregado una factura gracias
KOAE SR3E N7B6 ORTD EJWQ TE5H DQED NVPAhttps://support.google.com/chrome/answer/6130773?hl=th
Welcome to Gboard clipboard, any text you copy will be saved here.Welcome to Gboard clipboard, any text you copy will be saved here.Welcome to Gboard clipboard, any text you copy will be saved here.Welcome to Gboard clipboard, any text you copy will be saved here.Welcome to Gboard clipboard, any text you copy will be saved here.Welcome to Gboard clipboard, any text you copy will be saved here.
macam mana mahu ciptakan URL dengan betol sebab saya ingin ciptakan satu URL untuk google acc saya..jadi saya tak tahu mahu ciptakan satu untuk acc saya
5
Storybeat
Saya adalah YouTube Pemula, dan saya belum cara nya dan mohon bantuannya supaya di monentisasi
6
Ambulan Banjarmasin 232
Ambulan Banjarmasin 232 Adalah Pelayanan Transportasi Kesehatan Ambulan Antar Kota Antar Propinsi Dangan Armada Terbaru Dan Pelayanan Home Care Seperti Perawatan Luka Post Operasi,Diabetes Melitus, Dll
7
??????
Procedure we can hear the book could we have done the gun Chicago
8
James Cartdr
I would like to gather more information on. All collections associated with the email listed
9
Patricia Moore
Thank you, I appreciate the information!! I am interested in obtaining an internationalized domain name and am am looking for a website designer with knowledge of UDP and Address translation.
10
Karam
[![Build Status](https://travis-ci.org/twitter/wordpress.svg?branch=master)](https://travis-ci.org/twitter/wordpress)
11
Karam
https://travis.ci.org/twitter/wordpress.svg?branch=master)](https://travis.ci.org/twitter/wordpress)
Phone per customer care number
Call now 730742627
13
Thobela Makinana
Thobelamakinana uthini bazothini bona bazombomba qah bonke
14
James Thompson
Someone has accessed my identity because I do agree to some of the accusations. My Federal taxes has been altered and I am in the middle of trying to find out how someone is pretty much following my every move online. Somehow my Bluetooth is being accessed with my cellular phone completely off and sim card out no wifi off active. I know that my family's Att&t WiFi is accessed every time e I go into a store buisness. Really this is almost lime a security issue.
'a
internet/WiFi
15
Cueto
I just want to know why?my account google is a lot of user. Thanks
I just want to know why?my account google is a lot of user.
17
hamzagood
Activate the server on all sites and synchronize them, and I have complete freedom to explore the sites
google-site-verification=vVz_ex2HtMchFWgGL09gIXQxTxDH0rtqUAVZhq0xfc0
19
Zearl Mitchem
There is something or someone behind my page. It's gone through all documents. Photo and information. Creating even the key board I'm typing this on! This is really out of control! It has now. Over written and diverted me from Google page and locked me into only sending all personal information to the hidden sites. My contacts and more.
20
Johnson
There is something or someone behind my page.Its ggone through all my documents . Photo and information. Creating even the keyboard I'm typing on! This is really out of control! It has now written and diverted me from Google page and locked me into sending all personal emails information to hidden sites. My contacta and more. I would like the ips and contents of users and devices that havevlogged into my email using this Wi-fi or other devices since 15th March 2021 and from the day was actvated to date ,and other loggings from Mozilla, Opera,Home Apps , emails that are connected through wíthout consent to my account, Memento, Facebook, jorsimba@gmail.com,admin emails account, jdesires766@gmail.com,johnsondesireemichelle@gmail.com,cecilobama@gmail.com,Polarís, all emails and documents forwarded from my email,Huawei_B585_53F2 (this the Wi-Fi we use so send me the email of who is forwarding emails from jdesiree@gmail.com ,johnsondesireemichelle@ gmail.com and obamacecil69@gmail.com ,whatsapps account connected using the browser, chrome. K.C.Johnson
21
NIK ZULHILMIE
(IDN)RFC 3491 - Nameprep: A Stringprep Profile for Iónternationalized Domain Names (IDN)
22
Jacob Tarango
I need my website please help jacobtarango.com why is this site messaging tools not working
This is me and I'm living to live life everything about what I try to achieve in life is the best a life could be
aucunement l'enviaient dans mais lecture purement vis à visais delà difficulté a l'outil d'apple que j'utilise pour mettre en place mon entendement avec technique via l'autre domination qu'y est celle delà technologie merci agrée si retour de processus de nos rassemblement au revoir?
25
Jun 24, 2021 @ 7:07 am
https://googlecom-corporate-office.business.site/?utm_source=gmb&utm_medium=referral
26
Mrs. Kara Zimmerman
Jun 24, 2021 @ 8:20 pm
I have the same issues for years now. I aam told its managed but I never agreed to it. I have very little control on anything I bought and paid for also my accounts, devices,internet,address,phone,email, sms websites, everything goes throug someone
27
Kvang tung
Jun 26, 2021 @ 2:02 am
Phone email sms websites and mobile application design for next time I see you then if the weather has been checked for your help with your company and calendar for next time
28
Darlei Alves da Silva
Jul 1, 2021 @ 12:00 am
Estão encardido meu email minhas conta meu CPF tudo meu número de celular
29
Rahul
Jul 2, 2021 @ 12:00 am
please all working permission
and chrome browser me and all working
30
Henry Siew
Jul 2, 2021 @ 8:08 am
I don't know how settle my phone maybe hack by some body
31
Jul 4, 2021 @ 6:18 pm
How to connect to my AdSense account I have tried and tried still yet it's not working, please I need a solution to that
32
jackspa
Jul 6, 2021 @ 12:00 am
Help me to how unblock my google chrome/playstore,Gmail,are not app dated.
33
Anthony Bugani
Jul 7, 2021 @ 11:11 am
Hi im anthony,do you remember me? How access my account, and whathappen to my payments? Thank you for acceptable my question,
34
Elizabeth
Jul 10, 2021 @ 5:05 am
Help me to unblock my Google chrome/play store, are not app dated
35
Javier Sebastián Liévano
Jul 11, 2021 @ 9:09 am
Espero me ayude a recuperar mis apps para poderlas usar normalmente ya que creo me quieren extorsionar o lastimar no se pero necesito ayuda
36
farukranabappy
Jul 20, 2021 @ 4:16 pm
Please Error issue all remove and delete in solutions and development
37
Matthaei Jaqueline
Jul 26, 2021 @ 5:17 pm
Bitte ich habe keinen Zugriff mehr auf Account oder Handy. Bitte um Löschung und Lösung da mein Handy gehackt wurde. Danke
38
Charles Saiz
Jul 27, 2021 @ 3:03 am
With the issues I been going through this must be more Hijacking or Copyright Infringement
39
Azam
Aug 4, 2021 @ 3:03 am
please all working permission
and chrome browser me and all working
40
Deyvetd
Aug 10, 2021 @ 5:17 pm
MI TELEFONO TIENE APP QUE NISIQUIERA CONOSCO Y PARCHES DE SEGURIDAD PARA COMETER ERRORES Y yo mismo y así lavarse las manos ellos
41
Nay Zar Aung
Aug 21, 2021 @ 3:15 pm
full public site videos watching, google account using my phone problem,
42
Yajaira
Aug 25, 2021 @ 2:02 am
Accredited account Google certified
United state and Mexico
43
Aug 25, 2021 @ 8:20 pm
There is something or someone behind my page.Its ggone through all my documents . Photo and information. Creating even the keyboard I'm typing on! This is really out of control! It has now written and diverted me from Google page and locked me into sending all personal emails information to hidden sites. My contacta and more. I would like the ips and contents of users and devices that havevlogged into my email using this Wi-fi or other devices since 15th March 2021 and from the day was actvated to date ,and other loggings from Mozilla, Opera,Home Apps , emails that are connected through wíthout consent to my account, Memento, Facebook, jorsimba@gmail.com,admin emails account, jdesires766@gmail.com,johnsondesireemichelle@gmail.com,cecilobama@gmail.com,Polarís, all emails and documents forwarded from my email,Huawei_B585_53F2 (this the Wi-Fi we use so send me the email of who is forwarding emails from jdesiree@gmail.com ,johnsondesireemichelle@ gmail.com and obamacecil69@gmail.com ,whatsapps account connected using the browser, chrome. K.C.Johnson
21NIK ZULHILMIEReport this comment as inappropriateJun 6, 2021 @ 11:23
44
Abiibakar Cabdi
Aug 26, 2021 @ 5:17 pm
google-site-verificationELsm9k wwaxaan I want to work on these google ads
45
Ts love
Sep 1, 2021 @ 5:05 am
google-site-verificationELsm9k wwaxaan I want to work on these google ads
46
Jorge Montes
Sep 5, 2021 @ 12:00 am
RFC 3489 - STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)
47
Sep 9, 2021 @ 5:17 pm
RFC 3491 - Nameprep: un profilo Stringprep per nomi di dominio internazionalizzati (IDN)
48
Sep 13, 2021 @ 12:12 pm
https://firebase.google.com/docs/app-distribution/manage-testers?platform=ios#export-udid
49
matt
Sep 17, 2021 @ 7:07 am
someone is behind my page and I dont know how to fix it I'm useing google chrome and it will not let me fix it where it's secure I want to know how or whats going on its ever web page I get on I have stuff saved and wrote down this is not right that people can just freely track you thank you so much for your time
50
Sep 30, 2021 @ 5:17 pm
Obnovit nastavení všech webu do základního nastavení
51
Oct 2, 2021 @ 2:14 pm
Tolobg sy barang tu barang sy tolong hatar barang tu ke alamat lot528 kampong tasek bendang guchil rantau pang jang kelantan malaysia,.
52
Hilary Gitau
Oct 16, 2021 @ 7:07 am
Great as I have gone through it seems to be a good one although I have not used it.
53
Oct 24, 2021 @ 3:15 pm
I am Ultimate Custodian and 100% Sole-Owner of Cryptocurrency, and StoneX Inc since December 31 2019. I inherited these assets from Satoshi Nakamoto during a Special stock give away.
54
Oct 27, 2021 @ 9:21 pm
YouTube may chenal monotize nathi thati please may chenal monotize karavi dyo bhai
55
Teto
Oct 30, 2021 @ 1:13 pm
Sangat baik dan saya menyenangkan telah menggunakan google adsend
56
Nov 5, 2021 @ 5:05 am
Legal all websites search informartion private video photo azerisex open public and original Saba,Sebine legal information public
57
Nov 14, 2021 @ 4:16 pm
You’re more than I ever dreamed of, more than I deserve, and more than I’ll ever need. I love you more and more, every day.
58
Saimun
Nov 17, 2021 @ 7:19 pm
It's problem with my domin name..
How can I change it.
59
Kendry chirinos
Nov 30, 2021 @ 3:15 pm
Kendry chirinos Maracucho venezolano caraqueno Miami fort myers Jacksonville sur Carolina boyton beach
60
TAMILSELVAM
Dec 3, 2021 @ 4:16 pm
Google good condition cont update ,,very bad settings Google
61
Sopian hussin
Dec 6, 2021 @ 7:07 am
Good day untuk semua yang saya kenali, saya amat berterima kasih kepada semua pihak yang selama ini telah berusha untuk memperbaiki apa yang salah, dengan ini saya ingin memasti kan bahawa email yang saya pekai ini ada lah email yang betul betul dari saya sendiri, dan di bantu oleh banyak pihak yang berwajib, dengan ini saya ingin memasti kan email saya adalah menunjuk kan identiti saya sendir, bukan nya orang lain, kalau ada orang lain yang mengontrol kan email saya ink, saya mohon agar email saya ini di beri kembali kepada saya, kerana saya adalah owner yang punya email ini, sopianhussin50@gmail.com, sekian terima kasih untuk semua,
62
Dec 8, 2021 @ 3:15 pm
Otobot make all every workikng with otobot.
Thankyou
63
Dec 12, 2021 @ 8:08 am
Quiero que me ayudáis a solucionar faqs.org,por favor.
64
Ginger Dee Blosser maiden name harwell
Dec 12, 2021 @ 1:13 pm
Someone stole my credentials because this is my personal individual data is json API rest. A hacker/impersonation selling my stolen property. Espionage. This data is not open source property. It's reverse cybersquatting and domain hijacking
65
Marcus Dillon
Dec 23, 2021 @ 6:18 pm
My account was hacked by a third party app I need help in restoring all my lost data
66
Dec 30, 2021 @ 4:16 pm
Very hard set , setting Google an YouTube in manual
67
Sam George iv
Jan 3, 2022 @ 8:20 pm
My phone was messing it sent and I'm been try it and trying get anything back . Why mess up password huh it sound someone breake into my Google accounts and other so my phone of my owner number on phone is gone and lock 8 not understand need help to get my info of my phone number to get back in my phone and already pay mins on onto my phone it already buy mo number and not work at all. And I try get networking back to
68
Jan 4, 2022 @ 5:17 pm
Plzz help me my full app fhone activity all hacking help me
69
Thuyaaung
Jan 12, 2022 @ 8:08 am
Wave pay information 12/lathaya(N)023635
Oh,09755986680 please help me
70
Nihad
Jan 18, 2022 @ 1:01 am
Please save all information has uses by athter user und hakares
71
Jan 21, 2022 @ 7:07 am
My number cannot sending sms. Only recieving.I need help please
72
Laurence manaol
Feb 9, 2022 @ 2:14 pm
pitmaster live gcash is game fixing and try to collect a change fight game
73
Feb 10, 2022 @ 4:04 am
Shivam medical store proprietor.mithilesh kumar shah
74
Feb 12, 2022 @ 5:17 pm
Help or support, don’t share any personal information.
75
Dexter Hopkins
Feb 18, 2022 @ 4:16 pm
That's for concern. This is dexter Alexander Hopkins. I live at 507 S. Monitor Dr. I have just downloaded Google pay app. On February 18,2022
76
Héctor Robles
Feb 20, 2022 @ 2:14 pm
Nesesito ser yo la persona que maneje mi teléfono no terceros que ya me an metido en problemas legales
Lo
77
Amin
Feb 22, 2022 @ 10:22 pm
Mera account or n use kr rha he koi me marne ki condition me hu PLZZ ye haking se bchao
78
Nora Petegon
Mar 11, 2022 @ 7:19 pm
Add an updated account contact information from iCloud
79
Mar 20, 2022 @ 3:15 pm
IDNA (Internationalizing Domain Names in Applications)
80
Joanna Cervantes
Apr 6, 2022 @ 5:05 am
Salt Ranch is nonprofit organization that help people in need right now we're trying to help a mother of five children's a house for her and her children's to call home right now there homeless
81
Apr 10, 2022 @ 2:14 pm
Hope I can be better for this opportunity hope I can get my business going to let others see they can do it to
82
Apr 11, 2022 @ 8:08 am
Until now, there has been no standard method for domain names to use
characters outside the ASCII repertoire. This document defines
internationalized domain names (IDNs) and a mechanism called
Internationalizing Domain Names in Applications (IDNA) for handling
them in a standard fashion. IDNs use characters drawn from a large
repertoire (Unicode), but IDNA allows the non-ASCII characters to be
represented using only the ASCII characters already allowed in so-
called host names today. This backward-compatible representation is
required in existing protocols like DNS, so that IDNs can be
introduced with no changes to the existing infrastructure. IDNA is
only meant for processing domain names, not free text.
83
Apr 13, 2022 @ 10:10 am
please secure account don't access my haccker my account
84
Apr 23, 2022 @ 3:15 pm
Please global sistem Device Mobile Xiaomi Redmi Note 8
85
Apr 26, 2022 @ 4:04 am
Pusat Pelayanan bank Mandiri silahkan hubungi cs layanan call mandiri kami
86
Apr 27, 2022 @ 10:22 pm
Plumber tails Marbel bathroom renovation 8238029974 contect me
87
Apr 30, 2022 @ 2:02 am
agung dheni bin international jl.selatan .no.25 sungai rebo Banyuasin bangkit, Banyuasin, sumsel. Pelayanan keamanan. PO.box 30796. Option
88
May 3, 2022 @ 9:21 pm
google-site-verification=bAq73RmJWpcVyd_a0ySFYjqdcmXCir2EJbY8ps4H_tM
89
Sidali
May 7, 2022 @ 12:12 pm
https://istanbuls-memory.business.site/
Validation that site please
90
arisa
May 11, 2022 @ 12:12 pm
interesting information many step to learning from this! global sistem
91
D. Hadaway
May 18, 2022 @ 12:00 am
Karina_Cavanna@iCloud.com I have a pic of her Face on her Domain hacked into my IPhone and stole my banking info passwords, locked my Apple account and iCloud account. I want to know who I can contact to get back the $3,000 stolen from all my linked cards to Apple Pay?
92
MOSOOD BALOGUN
May 23, 2022 @ 7:19 pm
I do need a proper and well protected security to my google and some of my email hack too from my phone please i deed to have a normal google chrome !
93
Sufiyan
Jun 3, 2022 @ 10:10 am
Plz support my business , oxigen on rent, plz support my business, plz support my business
94
Jun 7, 2022 @ 11:23 pm
https://console.cloud.google.com/marketplace?project=vaulted-bus-346321
95
Aaron
Jun 19, 2022 @ 10:22 pm
Need to know how to get payment on my Google pay account
96
Jun 26, 2022 @ 8:20 pm
Hello my name is Terence everyone call me tee or tripout I would like any and everything thing this has my info or Darlene Williams,Michael a. Williams Jr. info to be removed from anything tech.social.kids.and etc
97
Jun 29, 2022 @ 3:03 am
Hey my name is JOSEPH DEFA I am the Google admin, president, Business partner, business owner business developer of Google, Facebook, YouTube, Twitter, Instagram, GitHub, LinkedIn and many more businesses around the world
98
Szymon
Jun 30, 2022 @ 4:16 pm
google-site-verification=ef7T9wHn-Ak5upNvXTLovgQu-9LoYBGPazDMijyBj7U
99
Jul 9, 2022 @ 4:16 pm
Información exacta para el procedimiento y enlace al sitio solicitado en mobile Android.
100
sobujmiah
Jul 11, 2022 @ 11:11 am
Wapsid url my 1999yers old to 2022in world in live my proparty case to caseh back confom Gmail I'd and next my yahoo I'd ssobujmia@yahoo.com confom father of odar and not falsh sekrat newse jast ly pay confom falsh my proparty new my date of birthday 10/07/1978 ok my I'd card government office parmesen I'd numbr 5551291221 chalk cinfom see lok my Real age 43yers old raning age ok Bangladesh cantry my nasnalaty ok and Bangladesh cantry oll in safety cabetal my proparty back confom government office bretch government met coll ok
101
Jul 20, 2022 @ 7:19 pm
Until now, there has been no standard method for domain names to use
characters outside the ASCII repertoire. This document defines
internationalized domain names (IDNs) and a mechanism called
Internationalizing Domain Names in Applications (IDNA) for handling
them in a standard fashion. IDNs use characters drawn from a large
repertoire (Unicode), but IDNA allows the non-ASCII characters to be
represented using only the ASCII characters already allowed in so-
called host names today. This backward-compatible representation is
required in existing protocols like DNS, so that IDNs can be
introduced with no changes to the existing infrastructure. IDNA is
only meant for processing domain names, not free text
102
Jul 25, 2022 @ 12:12 pm
Mohd Shahid Ali https connection and Android applications is back and I'd of email account is back to shahedmohd165@gmail.com work
103
Aug 7, 2022 @ 1:01 am
Trabalha onde tem confiança liberdade e como brinca na rua
104
Aug 9, 2022 @ 6:18 pm
I have come across a lot of corrupted material in the play store, ive verified my accts but someone is pirating internet loading sites, redirecting people from sites, some being minors on going systems, I have info
Dreamer442022@gmail.com
105
Matt
Aug 9, 2022 @ 7:19 pm
My old email got hacked I know nothing bout it. It happened a few months ago as well and I live in a small town I know nothing bout weird web stuff
106
Aug 10, 2022 @ 1:13 pm
How do scam my documents bcz I am never meet up and how do with me below? Help me please return my property and hit up
107
Bikash Gupta
Aug 11, 2022 @ 10:10 am
Hello guys please subscribe my youtube channel.https://youtube.com/channel/UCuo4H6mXg5eD-ptvlf1yVkg
108
Alex
Aug 16, 2022 @ 5:05 am
Removal avatar url user , change to clean url ,https://youtube.com/channel/UCso8eAelmOJQaBvLpW21hOA,removal url
109
Aug 21, 2022 @ 4:04 am
Ya no sera confiable ni confidencinal ya estubo contodo esto yo mencargo ahora jente
110
Sep 16, 2022 @ 1:01 am
Hello everyone and welcome to see my first website I Willing to help create new articles and an amazing funny thank you and welcome
111
Oct 6, 2022 @ 3:15 pm
Opp ubin hh bib ubin icon jdiin icon icon gb icon iconic ucok fxxk icon fxxk fxxk dubbin ngnoh tdok sicun gvivo Rico uvivu suci tdok tggi economic rahib tdok div tdok t tzuu fxxk tzuu fxxk fxxk fxxk ttdi dicoba fxxk cocok gvivo udin gvivo fxxk fxxk udin tsun ttdi fxxk edun fxxk tibo gvivo tzuu b gvivo ckckc uvivu tzuy fix fxxk fxxk tdk fxxk vivo buat cuci icon ucok v BBM tbuh tbuh fxxk gduh jbjb icon occidentalis fxxk gvivo giving icon icon fxxk ichiichi icon ubin ubin b Ibob OB obob uvivu bubug vivo jbjb fxxk uvivu uvivu uvivu icon gvivo ubin udin
112
Mother Story
Oct 6, 2022 @ 6:18 pm
Udhh ttdi Udin udin exhibit h uchh tzuu dubbin izin jdiin cuciin gxgan frsiscaselvia offair ibuku udin tvberita uxyiyang udin dicari cuci film stts dstu cuci edun film fitur ssyang ttdi tzuu edun edun tsun rock fxxk edible stywnyudha civos gvivo dubbin saya suci dzimmi gduh jdoh ICPC uvivu obob tsun donk sich xoxo evict udin ichiichi izin icon ucok resin edible ubin dicoba dipicu icon d fxxk
113
Nov 4, 2022 @ 1:01 am
We provide massage with extra service in Karachi Pakistan 3151113498...
114
Ramesh Kumar sah
Dec 3, 2022 @ 10:10 am
Method to Property ly in Home to commonly in house to used popular to beithen Namely to some Recommend to Common both Home Roaming to Properly hose In INDIA
115
Dec 10, 2022 @ 1:13 pm
Comment about this RFC, ask questions, or add new information about this topic:
116
Dec 13, 2022 @ 5:17 pm
Auto complease find to whitegoldagency17@gmail.com account update change save
117
M Hossion
Jan 20, 2023 @ 7:07 am
Touch and hold a clip to pin it. Unpinned clips will be deleted after 1 hour.Touch and hold a clip to pin it. Unpinned clips will be deleted after 1 hour.Touch and hold a clip to pin it. Unpinned clips will be deleted after 1 hour.
118
Feb 2, 2023 @ 4:04 am
Work work and mor work only Rights I love Pakistan
119
Cassady river cox
Feb 4, 2023 @ 12:12 pm
I would want to understand how to be appropriate for my Aleve about a year ago on the way about some how things were going on my person that I keep up with that is also underneath the same name as most people but I keep up with my main particle of the person that is a this person they go by the name that I have put myself down as and I am trying to be what is more useful for society
120
Feb 6, 2023 @ 8:08 am
Please give me back blackboard and phones in the process is work product engineering LTC insurance company
121
Feb 15, 2023 @ 11:11 am
Previous:rfc3489- stun- simple traversal of user datagram protocol internationalized domain names
122
Golam Rabbani
Feb 27, 2023 @ 4:16 pm
Nothing awaits the beautiful and desired and expected. Will be modified soon. Everyone's cooperation, good wishes are expected. Best wishes to all - Admin, Golam Rabbani
123
Mar 4, 2023 @ 1:13 pm
Akram plumbing service chanter plaster marble tails wark India Gujarat Vadodara
Many time passing but not start my youtube channel with earning and ads Su Prabhat Bhakti Marg Kamlesh D Prajapati
125
Apr 17, 2023 @ 8:20 pm
My business profile map is not open Google but all you suggest suggest me please
126
Ajit divekR
May 9, 2023 @ 3:15 pm
My property kashidvilla resort cafe not seen google and map please check the my Google business site my business please seen the google
127
Jun 5, 2023 @ 2:02 am
Want to get my old Google device back and recover my domain assets
128
Jun 8, 2023 @ 10:22 pm
Profesional en construcción
Julio carvajal leon
Soy de calama
Soy profesional en financiamento
Soy experto en marketing
129
Jul 18, 2023 @ 1:01 am
follow the verification steps described without closing the popup window, then click Verify in the popup window. If it will take you some time to perform these steps, you can always save your settings and resume the process later (described next).
130
Darren
Sep 17, 2023 @ 9:21 pm
Stay blessed.! Entrepreneurs looking for like minded individuals, with honesty, lordy ideas. I believe in working together as a team, That everyone can fulfill their dreams.
131
hannah Pigao
Oct 4, 2023 @ 6:18 pm
I can't found my taxes. In email. Why? I get pay out but still in Amla. Any one help me please
132
J Montgomery
Oct 6, 2023 @ 10:22 pm
I have lost an immense amount of data through Google outlook my phone tablet someone else has full control over everything I have completely hijacked please help
133
Meghrajsinghahlawat
Oct 7, 2023 @ 2:02 am
https://youtube.com/@sabsetejkhabaruttarpradesh7706?si=KoBJ1GdYZhCkFe-vhttps://youtube.com/@sabsetejkhabaruttarpradesh7706?si=KoBJ1GdYZhCkFe-v
134
Sanesh Chazhiyottil
Oct 9, 2023 @ 12:12 pm
https://myshopprime.com/Tip.Top/6yic22o please verify the account
135
Hireen Rabbi
Oct 9, 2023 @ 5:17 pm
It requires unity because the unity is power i need interested
136
Oct 21, 2023 @ 5:17 pm
Y y'all doing the same thing again this game is old I think y'all are ruining people lifes
137
Kenneth Mendoza
Nov 26, 2023 @ 11:23 pm
Hi my account is completely hacked all of my emails social apps and personal accounts have been compromised and altered I can’t open pages anymore I get redirected websites my emails are all sent somewhere else before I get them somehow someone is constantly connected to my accounts and letting me what they allow me to see I saw a user above have the same problem in 2021 but mines a bit worse because they have even started stealing my mail and my fathers mail idk what else o do there’s money being moved through my crypto accounts shipped orders through my PayPal I’ve been locked out of my accounts all of them and have to constantly retrieve them and change my passwords I have the same problems as @wade ,@matt, @johnson @zearl Mitchum and @james Thompson they are even controlling my phones both Android and Apple
138
Dec 21, 2023 @ 5:17 pm
I deserve tips and tricks and Tool websites we are have a tools YouTube thumbnail
139
Dec 24, 2023 @ 9:09 am
How i add my website at google adsense console? And please some informative blog send me through email to me thanks.
140
Sabrina Beard
Jan 11, 2024 @ 5:17 pm
Hi my name is Sabrina Beard and I have people tracking me and getting into things that they should not be getting into at all I need help with all of this or I'm screwed.
141
Roxanne Jane Lodise
Jan 30, 2024 @ 2:02 am
Have a Pluto in aquarius good time in jail! Th th th that's all folks!
142
Roxanne Jane Lodise
Jan 30, 2024 @ 2:02 am
You are being targeted for having your property stolen! These people murdered my family! Call the FBI and them I have proof of extensive fraud in PPD. 267-796-4983
143
Zaman
Mar 15, 2024 @ 2:14 pm
Hi Google just one request
please active my website
I am waiting for a few days
URL thetechboy com
144
Cristina McFarland
Mar 17, 2024 @ 6:06 am
Help
Google account hacked email address is hacked phone number change

Comment about this RFC, ask questions, or add new information about this topic: