CentralNic Reseller Homepage
CentralNic Reseller Homepage

.bank

API commands

Please find in the following a set of the most commonly used standard API commands in order to register, modify, renew, and transfer a domain name.

Domain Registration

(API Command reference » AddDomain)
  • Registrant completes application on .bank website
  • fTLD issues registration token to registrant.
  • The registrant/registrar can register the domain name on RRPProxy with the fTLD-Token: X-ALLOCATION-TOKEN = [fTLD Registration Token]
Exception
command = AddDomain
domain = yourdomain.bank
ownercontact0 = (CONTACT)
admincontact0 = (CONTACT)
techcontact0 = (CONTACT)
billingcontact0 = (CONTACT)
nameserver0 = (NAMESERVER)
nameserver1 = (NAMESERVER)
X-ALLOCATION-TOKEN = (TEXT)

DomainPinLock is required as multi factor authentication and will be set on AddDomain. It is NOT possible to deactivate DomainPinlock. Instead of SMS, E-Mail authentication will be used, the token will be sent to the registrant's email address.

Domain Modification

(API Command reference » ModifyDomain)

Changes to the domain can only be performed, when a valid token is provided through the DomainPinLock security feature!

Exception
command       = ModifyDomain
domain        = yourdomain.bank
ownercontact0 = (CONTACT)
token = (TEXT)

Domain Renewal

(API Command reference » RenewDomain)
Command
command    = RenewDomain
domain     = yourdomain.bank
period     = (INT)
expiration = (INT)

General Re-verification Renewal Process Draft to Registrants (Template for Registrars to modify) As part of the fTLD Security Requirements that support the value of trust-based .bank domains, a re-verification of these domains must be completed at least every two years or at the time of a renewal, whichever comes first. Please find further information here. Re-verification of Registrants and their domain names will be triggered under the following circumstances:

  • Domain Renewals: If it has been more than 20 months since a full verification, another full verification will be performed. If it has been 20 months or less since a full verification and no information has changed, the renewal will be processed immediately.
  • Organization Name Change: A full verification is performed.
  • Domain Transfer: If it has been 20 month or less since a full verification and no information has changed, the associated renewal will be processed immediately. If it has been more than 20 months since a full verification, another full verification will be performed.
  • Bi-annual for domains registered for longer than two years: A full verification of the information will be performed even if the information is exactly the same.

If you anticipate any of the above events for your .bank domains this year, please ensure the information in your account is current so that any re-verification that is needed can proceed as smoothly as possible. This information includes both your Registrant Contact and Organization details, as well as the telephone number and address.

Please note that information about the Government Regulatory Authority and ID, and HR and Manager contact information is now required by fTLD as this assists Symantec in completing the verification process in a timely manner. Please contact us if you have any updates for this information or if you did not initially provide that information so that it can be included on the re-verification order.

You should also alert your HR department and others to anticipate and quickly respond to Symantec’s request for confirmation of employment and authority so any needed re-verification can be completed as quickly and smoothly as possible. If Symantec is unable to reach someone to complete the verification, they will leave a security code on their voicemail. It’s important to understand this detail and that the person can provide the security code when they return Symantec’s call to complete the verification.

We look forward to supporting you during this process so please don’t hesitate to contact us as needed.

Domain Deletion

(API Command reference » DeleteDomain)
Exception
command = DeleteDomain
domain  = yourdomain.bank
token = (TEXT)

Domain Transfer

(API Command reference » TransferDomain)
Command
command = TransferDomain
domain = yourdomain.bank
action = REQUEST
auth = (TEXT)

Transfer procedure

  • The transfer is submitted to the registry and the losing registrar is automatically notified by them.
  • The losing registrar sends an email to the owner (and optionally admin) contact, informing about the transfer; this may include options to approve and/or deny the transfer. If neither explicitly approved nor denied, the transfer will be automatically finalized after 5 days.

Transfer notes

  • A .bank domain transfer must be initiated with a so-called authorisation code, (auth-code) which can be obtained from the current registrar through the owner/admin contact of the domain.
  • Ensure that your respective domain does not have a lock-status (clientTransferProhibited and/or serverTransferProhibited). This can be seen in WHOIS.
  • If the domain has a client-side transfer lock, the owner can ask the current registrar to have the lock removed.

These procedures only apply for domain transfers between registrars. For internal transfers between resellers, please consult our documentation about internal transfers/usertransfers.

Auth-Codes

The format for auth info requires a minimum length of 8 characters and a maximum length of 32 characters.

Additionally, auth info must contain at least one of each of the following three character types:

  • Alphabetic character:a-z;
  • A-Z Numeric character : 0-9
  • Special characters: !;<=$%?&@[()]*^+-,'-{.|/}:~

Domain Restore

(API Command reference » RestoreDomain)
Command
command = RestoreDomain
domain  = yourdomain.bank

Domain Extensions

X-ALLOCATION-TOKENProvide a token that has to be issued by the registry for the registration of a premium domain name.

Domain Restrictions

  • Registrant organization must be in banking sector
  • Domainname must be in touch with organization
    • Qualified Registrants Registrant Eligibility Policy
    • The following for-profit and not-for-profit businesses or organizations are initially eligible to register domain names in .bank:
      • 3.1 State, regional and provincial banks that are chartered and supervised by a government regulatory authority;
      • 3.2 Savings associations that are charted and supervised by a government regulatory authority;
      • 3.3 National banks that are chartered and supervised by a government regulatory authority;
      • 3.4 Associations whose members are primarily comprised of entities identified above in 3.1, 3.2 or 3.3;
      • 3.5 Groups of associations whose members are primarily comprised of associations identified above in 3.4;
      • 3.6 Service providers that are principally owned by or predominantly supporting regulated entities identified above in 3.1, 3.2 or 3.3. (if approved by the Registry Operator Board); and
      • 3.7 Government regulators of chartered and supervised banks or savings associations or organizations whose members are primarily comprised of such government regulators (if approved by the Registry Operator Board).
  • Bank holding companies are not eligible as they do not fit the definition of a bank nor do they provide banking services. If the bank holding company believes they need to be listed in the registration, they can for example be listed as the admin contact. Please do not submit any requests in this format as they will be rejected.
  • DomainPinLock is required as multi factor authentication and will be set on AddDomain. It is NOT possible to deactivate DomainPinlock. Instead of SMS, E-Mail authentication will be used, the token will be sent to the registrant's email address. Changes to the domain can only be performed, when a valid token is provided!
  • .bank domains must use .bank nameservers (e.g. ns1.bankname.bank)
  • DNSSEC required
  • Domain-based Message Authentication, Reporting and Conformance (DMARC) required
  • encryption required for web access, mail exchange and file transfer
  • full list of .bank security requirements
  • possibility to add domains without nameservers

Please carefully review the .bank Registrant Eligibility Policy and Security Requirements before submitting requests to avoid inconveniences for all involved in the registration process and most importantly your customer. If the eligible banking entity provides these types of services itself along with its banking services then the registration is permissible. If however these services are provided by separate legal entities that are not eligible for domains in .bank (e.g. mortgage broker, equipment leasing company, investment firm), then the registration is not permissible.

.bank reserved names can be checked on the registry website.

  • As noted in the Name Selection and Name Allocation Policies (see https://www.register.bank/policies), fTLD reserves the right to both amend the Reserved Names List and to allocate these names in the future under one or more of the identified allocation mechanisms.
    Names that appear on the Reserved Names List (i.e., Common Community Names and Generic Names) are not available for registration. Pursuant to the Reserved Names Challenge Policy you may submit a formal complaint to fTLD to request the removal of a name from reservation; such requests or challenges should be submitted using the fTLD-Reserved-Names-Challenge-Policy-BANK form and sent to complaint@ftld.com.
    In the Reserved Names Challenge Policy, please review section 4.0, Evidence in Relation to an Allocation Request or Proposal Challenge, to learn about the documentary evidence that is required of a third-party (“Requestor”) seeking to challenge the reservation of a certain name. To verify a Requestor’s rights or legitimate interests to a reserved name, fTLD requires documentation to show the domain name(s) corresponds to their trademark, trade name or service mark as described in the Name Selection Policy. The documentation to verify a Requestor’s rights to a mark is described in the fTLD-Reserved-Names-Challenge-Policy-BANK form.

Supported IDN Scripts

The following IDN scripts are supported by .bank.
Provide the LANGUAGE TAG corresponding to your desired IDN within the AddDomain command as X-IDN-LANGUAGE extension.

AfrikaansAFR
AlbanianALB
ArabicARA
AragoneseARG
ArmenianARM
AssameseASM
AsturianAST
AvestanAVE
AwadhiAWA
AzerbaijaniAZE
BalineseBAN
BaluchiBAL
BasaBAS
BashkirBAK
BasqueBAQ
BelarusianBEL
BengaliBEN
BhojpuriBHO
BosnianBOS
BulgarianBUL
BurmeseBUR
CaribCAR
CatalanCAT
ChechenCHE
ChineseCHI
ChuvashCHV
CopticCOP
CorsicanCOS
CroatianSCR
CzechCZE
DanishDAN
DivehiDIV
DogriDOI
DutchDUT
EnglishENG
EstonianEST
FaroeseFAO
FijianFIJ
FinnishFIN
FrenchFRE
FrisianFRI
GaelicGLA
GeorgianGEO
GermanGER
GondiGON
GreekGRE
GujaratiGUJ
HebrewHEB
HindiHIN
HungarianHUN
IcelandicICE
IndicINC
IndonesianIND
IngushINH
IrishGLE
ItalianITA
JapaneseJPN
JavaneseJAV
KashmiriKAS
KazakhKAZ
KhmerKHM
KirghizKIR
KoreanKOR
KurdishKUR
LaoLAO
LatvianLAV
LithuanianLIT
LuxembourgischLTZ
MacedonianMAC
MalayMAY
MalayalamMAL
MalteseMLT
MaoriMAO
MoldavianMOL
MongolianMON
NepaliNEP
NorwegianNOR
OriyaORI
OssetianOSS
PanjabiPAN
PersianPER
PolishPOL
PortuguesePOR
PushtoPUS
RajasthaniRAJ
RomanianRUM
RussianRUS
SamoanSMO
SanskritSAN
SardinianSRD
SerbianSCC
SindhiSND
SinhaleseSIN
SlovakSLO
SlovenianSLV
SomaliSOM
SpanishSPA
SwahiliSWA
SwedishSWE
SyriacSYR
TajikTGK
TamilTAM
TeluguTEL
ThaiTHA
TibetanTIB
TurkishTUR
UkrainianUKR
UrduURD
UzbekUZB
VietnameseVIE
WelshWEL
YiddishYID

Get more information of "IDN tables", which represent permitted code points (letters) allowed for Internationalised Domain Name registrations in particular registries on IANA Repository of IDN Practices.

We reallydomains
-