.AIRPORT
The AI-Powered Intuitive Link To Airports
Trust, Safety, Visibility
Empowering The Airport Experience Through Innovation
.airport: A Public-Benefit, AI-Powered Global Standard for Airport Domain Names
.airport Project Overview
We are creating .airport as the new global domain standard for airports.
From launch, .airport will AI-identify, register and operate the relevant domains for approximately 4,000 commercial passenger airports globally:
In the next ICANN new gTLD round, we will apply for .airport. Activation is targeted for 2028.
Until claimed by an airport, each domain will lead through a registry-operated .airport gateway page to the official airport website.
A simulated .airport gateway page for Amsterdam Schiphol is available at:
Only verified airports can claim .airport domains, and only those matching their own identifiers.
Because the domains are active from launch, .airport creates user utility from day one, even before airports claim or promote them.
Establishing .airport as the Global Airport-Domain Standard
We are establishing .airport as the primary public domain structure for commercial airports globally, with IATA-code .airport domains as the standard passenger-link format across aviation systems.
.airport creates three routes into the airport website: traveller intuition, aviation-system distribution and airport-controlled domain adoption.
1. Traveller intuition
From launch, the matching .airport domains for all approximately 4,000 commercial passenger airports are active. The traveller uses the airport identifier most relevant to the journey. Unique identifiers lead to the airport website; shared identifiers like LON or London keep the traveller one click away through a neutral gateway.
Until claimed by an airport, each domain will lead through a registry-operated gateway page to the official airport website, see an example here: www.dotairport.org/ams
The gateway pages introduce .airport directly to airport management, digital, marketing, IT and government teams and give every airport a clear route to claim and activate its .airport domains. We intend to appoint SITA, IATA or a comparable airport-industry organization as .airport’s distribution and verification partner, driving global airport outreach, validation and activation.
2. Aviation-system distribution
IATA-code .airport domains provide the standardized link into aviation-distribution systems and the digital passenger journey.
Three-letter IATA airport codes already structure the passenger journey: booking records, itineraries, flight confirmations, boarding passes, baggage tags, airline communications, OTAs, GDSs and travel platforms.
All three-letter .airport domains are reserved for current and future IATA airport codes. AMS maps to www.ams.airport, which will lead to www.schiphol.nl. View the simulated AMS gateway page: www.dotairport.org/ams
The rollout is built to place IATA-code .airport domains inside PNRs, e-tickets, flight confirmations, itineraries, boarding passes, airline communications and travel-platform workflows through aviation-distribution partners including SITA, IATA, Amadeus, Sabre and Travelport.
At these trusted passenger touchpoints, the .airport link prompts the traveller to visit the airport website even without a prior intention to look for airport information, creating new qualified traffic for the airport.
3. Airport-controlled domain adoption
After claim, the airport decides whether to use its .airport package through a gateway page, direct forwarding, campaigns or as a primary public domain. The remaining .airport domains and the existing legacy domain continue leading to the same airport website.
Together, these routes establish .airport as the global standard for trusted airport domains leading to airport websites.
The Utility .airport Creates for Travellers, the Aviation Industry and Airports
For global brands, the internet has settled into a familiar pattern: BMW.com, Apple.com and Ford.com lead to the official brand websites.
.airport brings that brand.com predictability to airports.
The aviation industry and travellers rely on structured airport identifiers - IATA codes, abbreviations, airport & city names - across booking records, itineraries, boarding passes, passenger communications and the wider travel journey.
Yet airport web addresses follow no comparable structure.
In the EU/EEA alone, roughly one third of commercial passenger airports do not use a dedicated airport domain. They use shared domains instead: Aena airports under aena.es/..., Finavia airports under finavia.fi/..., Swedavia airports under swedavia.com/..., Avinor airports under avinor.no/..., and Paris Charles de Gaulle / Orly under parisaeroport.fr.
The same pattern exists outside the EU/EEA, in countries like Thailand, Malaysia, Brazil, Saudi Arabia and other major aviation markets.
Other airports have dedicated domains, but no common system: frankfurt-airport.com, dfwairport.com, flychicago.com/ohare, skg-airport.gr, baden-airpark.de and ost.aero.
Unpredictable Placement of Airport Identifiers in Current Official Airport Web Addresses:
Even among the world's largest airports, their web addresses have evolved into a fragmented patchwork with no common structure.
The problem is twofold
First, the identifier chosen by the airport is unpredictable: IATA code, abbreviation, airport or city name.
Second, the web-address structure is unpredictable: .com or country-code domain, subdomain, or longer URL under a shared domain.
.airport absorbs that complexity into one predictable domain structure:
www.identifier.airport
Examples include: www.madrid.airport, www.helsinki.airport, www.cdg.airport, www.schiphol.airport, www.bkk.airport, www.ohare.airport, www.midway.airport, www.oslo.airport, www.frankfurt.airport, www.dfw.airport and www.heathrow.airport.
Not one identifier per airport - one structure for every valid airport identifier:
AMS, Schiphol, Amsterdam → www.ams.airport, www.schiphol.airport, www.amsterdam.airport
.airport establishes one public structure for commercial airports globally. Adoption starts where demand is strongest: airports without a dedicated domain, followed by airports that want a clearer public address. Over time, we expect every commercial airport globally to use a .airport domain as its primary public domain.
IATA codes, abbreviations, airport & city names operate within the same structure, enabling airlines, airports, travel platforms and passengers to rely on the identifier most relevant to them while reaching the same official airport website.
.airport domains for shared identifiers like LON or London lead to neutral gateway pages, keeping the traveller one click away from the relevant airport website.
A Commercial Model with Global Public Utility
.airport is an EU-led commercial initiative establishing trusted global airport-domain infrastructure for commercial aviation.
Its public-benefit utility is delivered through complete neutral inclusion and free use by passengers and the aviation industry. Its operations are financed through paid airport participation.