mediumsmall-res.png

dotAIRPORT – Domain Names for Airports

Trust, Safety, Intuitive Visibility

dotAIRPORT, LLC will submit an application for the domain extension  ‘.airport’ to ICANN in 2020 (see newgtlds.icann.org). Internet domain names like www.chicago.airport, www.ord.airport or www.ohare.airport will become available to the global airport community.

dotAIRPORT, LLC is designed to be an airport industry stakeholder-group funded, owned & governed, public-benefit, non-profit effort to secure the domain extension ‘.airport’. All domain registrants will be authenticated by relevant national airport associations or authorities. ‘.airport’ domains will serve as trust label to airport visitors aiding the Internet user to more easily & intuitively identify genuine, authoritative, official airport websites; thus creating trust, safety and visibility: an intuitive link between airports and their guests.

The aim is that all airports will use the same syntax for their web addresses (URLs): Their name, city and/or their IATA code with the new domain suffix .airport!

  • www.lax.airport

  • www.dulles.airport

  • www.ohare.airport

  • www.heathrow.airport

  • www.dubai.airport

Airports would automatically own all relevant domains (up to 10 domains per airport at no cost): 

  • www.ohare.airport

  • www.chicago.airport

  • www.ord.airport

The Internet user would be enabled to easily identify authentic, "real" airport website among other results in search engines like Google. Search engines would receive a clear signal about the authenticity of a website, as all registrants in the .airport namespace would be authenticated by airport organizations and only official airports authorities are eligible to register .airport domain names. In a few cases several airports share one city name (and usually one metropolitan IATA code):

  • NYC = New York City = JFK & EWR & LGA

  • BER = Berlin = TXL & SFX

  • LON = London = LGW & LTN & LHR & STN

  • MOW = Moscow = SVO & DME & VKO

  • PAR = Paris = CDG & ORY

In many cases these airports are already collaborating; and have a joined website (e.g. berlin-airport.de for BER or parisaeroport.fr for PAR). In the other cases there will be shared splash page for city.airport by dotAIRPORT, LLC. In the few cases the airport organizations of one city won't agree to a solution the .airport registry will (free of charge of course) set up a neutral website which offers the Internet user links to the offcial web presence of the involved airports. Obviously without the explicit agreement of the other affected parties Luton would not be eligible to register london.airport. The .airport namespace will be managed - to make sure the needs of the airports but especially the travelers are met.


Currently there is no "system" in airport web addresses:

  • flysfo.com (should be sfo.airport, sanfrancisco.airport)

  • lawa.org (unrecognizable, should be lax.airport, losangeles.airport

  • dohahamadairport.com (recognizable but long. Should be doha.airport, doh.airport, qatar.airport, hamad.airport)

  • flydenver.com (similar to flysfo.com - but doesn't use the IATA code "den". Should be denver.airport, den.airport)



For more information please send an email to alexander.schubert@dotairport.org or call +1(202)684 6806