Internet Assigned Numbers Authority

Service Name and Transport Protocol Port Number Registry

Last Updated
2024-03-18
Expert(s)
TCP/UDP: Joe Touch; Eliot Lear, Kumiko Ono, Wes Eddy, Brian Trammell, 
Jana Iyengar, and Michael Scharf
SCTP: Michael Tuexen
DCCP: Eddie Kohler and Yoshifumi Nishida
Reference
[RFC6335]
Note
Service names and port numbers are used to distinguish between different
services that run over transport protocols such as TCP, UDP, DCCP, and
SCTP.

Service names are assigned on a first-come, first-served process, as
documented in [RFC6335].

Port numbers are assigned in various ways, based on three ranges: System
Ports (0-1023), User Ports (1024-49151), and the Dynamic and/or Private
Ports (49152-65535); the different uses of these ranges are described in
[RFC6335]. According to Section 8.1.2 of [RFC6335], System Ports are 
assigned by the "IETF Review" or "IESG Approval" procedures described in 
[RFC8126]. User Ports are assigned by IANA using the "IETF Review" process, 
the "IESG Approval" process, or the "Expert Review" process, as per 
[RFC6335]. Dynamic Ports are not assigned.

The registration procedures for service names and port numbers are
described in [RFC6335].

Assigned ports both System and User ports SHOULD NOT be used without
or prior to IANA registration.

************************************************************************
* PLEASE NOTE THE FOLLOWING:                                           *
*                                                                      *
* ASSIGNMENT OF A PORT NUMBER DOES NOT IN ANY WAY IMPLY AN             *
* ENDORSEMENT OF AN APPLICATION OR PRODUCT, AND THE FACT THAT NETWORK  *
* TRAFFIC IS FLOWING TO OR FROM A REGISTERED PORT DOES NOT MEAN THAT   *
* IT IS "GOOD" TRAFFIC, NOR THAT IT NECESSARILY CORRESPONDS TO THE     *
* ASSIGNED SERVICE. FIREWALL AND SYSTEM ADMINISTRATORS SHOULD          *
* CHOOSE HOW TO CONFIGURE THEIR SYSTEMS BASED ON THEIR KNOWLEDGE OF    *
* THE TRAFFIC IN QUESTION, NOT WHETHER THERE IS A PORT NUMBER          *
* REGISTERED OR NOT.                                                   *
************************************************************************

Request an Assignment
  [https://www.iana.org/protocols/apply]

Available Formats

CSV

XML

HTML

Plain text
Service Name Port Number Transport Protocol Description Assignee Contact Registration Date Modification Date Reference Service Code Unauthorized Use Reported Assignment Notes
http-alt 8008 tcp HTTP Alternate [James_Gettys] [James_Gettys]
http-alt 8008 udp HTTP Alternate [James_Gettys] [James_Gettys]
http-alt 8080 tcp HTTP Alternate (see port 80) [Stephen_Casner] [Stephen_Casner]
http-alt 8080 udp HTTP Alternate (see port 80) [Stephen_Casner] [Stephen_Casner]
websnp 8084 tcp Snarl Network Protocol over HTTP [full_phat_products] [Chris_Peel_2] 2019-08-08
radan-http 8088 tcp Radan HTTP [Steve_Hay] [Steve_Hay] 2008-06-13
radan-http 8088 udp Radan HTTP [Steve_Hay] [Steve_Hay] 2008-06-13
privoxy 8118 tcp Privoxy HTTP proxy [Andreas_Oesterhelt] [Andreas_Oesterhelt] 2002-06
privoxy 8118 udp Privoxy HTTP proxy [Andreas_Oesterhelt] [Andreas_Oesterhelt] 2002-06
synapse-nhttps 8243 tcp Synapse Non Blocking HTTPS [Ruwan_Linton] [Ruwan_Linton] 2008-07-10
synapse-nhttps 8243 udp Synapse Non Blocking HTTPS [Ruwan_Linton] [Ruwan_Linton] 2008-07-10
synapse-nhttp 8280 tcp Synapse Non Blocking HTTP [Ruwan_Linton] [Ruwan_Linton] 2008-06-05
synapse-nhttp 8280 udp Synapse Non Blocking HTTP [Ruwan_Linton] [Ruwan_Linton] 2008-06-05
pcsync-https 8443 tcp PCsync HTTPS
pcsync-https 8443 udp PCsync HTTPS
pcsync-http 8444 tcp PCsync HTTP [Katy_Lynn_McCullough] [Katy_Lynn_McCullough]
pcsync-http 8444 udp PCsync HTTP [Katy_Lynn_McCullough] [Katy_Lynn_McCullough]
openremote-ctrl 8688 tcp OpenRemote Controller HTTP/REST [OpenRemote_Inc] [Juha_Lindfors] 2012-12-18
ultraseek-http 8765 tcp Ultraseek HTTP [Walter_Underwood] [Walter_Underwood]
ultraseek-http 8765 udp Ultraseek HTTP [Walter_Underwood] [Walter_Underwood]
manyone-http 8910 tcp manyone-http [Matt_King] [Matt_King] 2002-04
manyone-http 8910 udp manyone-http [Matt_King] [Matt_King] 2002-04
http-wmap 8990 tcp webmail HTTP service [Chris_Newman] [Chris_Newman] 2007-12-03
http-wmap 8990 udp webmail HTTP service [Chris_Newman] [Chris_Newman] 2007-12-03
https-wmap 8991 tcp webmail HTTPS service [Chris_Newman] [Chris_Newman] 2007-12-03
https-wmap 8991 udp webmail HTTPS service [Chris_Newman] [Chris_Newman] 2007-12-03
armcenterhttp 9294 tcp ARMCenter http Service [Eric_Thiebaut_George] [Eric_Thiebaut_George] 2006-04
armcenterhttp 9294 udp ARMCenter http Service [Eric_Thiebaut_George] [Eric_Thiebaut_George] 2006-04
armcenterhttps 9295 tcp ARMCenter https Service [Eric_Thiebaut_George] [Eric_Thiebaut_George] 2006-04
armcenterhttps 9295 udp ARMCenter https Service [Eric_Thiebaut_George] [Eric_Thiebaut_George] 2006-04
tungsten-https 9443 tcp WSO2 Tungsten HTTPS [Afkham_Azeez] [Afkham_Azeez] 2006-06
tungsten-https 9443 udp WSO2 Tungsten HTTPS [Afkham_Azeez] [Afkham_Azeez] 2006-06
wso2esb-console 9444 tcp WSO2 ESB Administration Console HTTPS [Ruwan_Linton] [Ruwan_Linton] 2008-08-20
wso2esb-console 9444 udp WSO2 ESB Administration Console HTTPS [Ruwan_Linton] [Ruwan_Linton] 2008-08-20
tungsten-http 9762 tcp WSO2 Tungsten HTTP [Afkham_Azeez] [Afkham_Azeez] 2006-06
tungsten-http 9762 udp WSO2 Tungsten HTTP [Afkham_Azeez] [Afkham_Azeez] 2006-06
nsesrvr 9988 tcp Software Essentials Secure HTTP server [Narayanan_Raju] [Narayanan_Raju] 2009-02-05
bveapi 10880 tcp BVEssentials HTTP API [Tri_Tech_Computers_Ltd] [James_Emerton] 2012-11-19
bveapi 10880 udp BVEssentials HTTP API [Tri_Tech_Computers_Ltd] [James_Emerton] 2012-11-19
hkp 11371 tcp OpenPGP HTTP Keyserver [David_Shaw] [David_Shaw] 2003-05
hkp 11371 udp OpenPGP HTTP Keyserver [David_Shaw] [David_Shaw] 2003-05
amt-soap-http 16992 tcp Intel(R) AMT SOAP/HTTP [David_T_Hines] [David_T_Hines] 2005-02
amt-soap-http 16992 udp Intel(R) AMT SOAP/HTTP [David_T_Hines] [David_T_Hines] 2005-02
amt-soap-https 16993 tcp Intel(R) AMT SOAP/HTTPS [David_T_Hines] [David_T_Hines] 2005-02
amt-soap-https 16993 udp Intel(R) AMT SOAP/HTTPS [David_T_Hines] [David_T_Hines] 2005-02
commtact-http 20002 tcp Commtact HTTP [Tomas_Svoboda] [Tomas_Svoboda] 2004-12
commtact-http 20002 udp Commtact HTTP [Tomas_Svoboda] [Tomas_Svoboda] 2004-12
commtact-https 20003 tcp Commtact HTTPS [Tomas_Svoboda] [Tomas_Svoboda] 2004-12
commtact-https 20003 udp Commtact HTTPS [Tomas_Svoboda] [Tomas_Svoboda] 2004-12
tcc-http 24680 tcp TCC User HTTP Service [Brian_Kennedy] [Brian_Kennedy] 2006-08
tcc-http 24680 udp TCC User HTTP Service [Brian_Kennedy] [Brian_Kennedy] 2006-08
kopek-httphead 27504 tcp Kopek HTTP Head Port [Sten_H_Danielsen] [Sten_H_Danielsen] 2002-07
kopek-httphead 27504 udp Kopek HTTP Head Port [Sten_H_Danielsen] [Sten_H_Danielsen] 2002-07
pmwebapi 44323 tcp HTTP binding for Performance Co-Pilot client API [Performance_Co-Pilot_PCP_Project] [Ken_McDonell_2] 2013-10-09
bidib tcp Model Railway Control via netBiDiB [BiDiB_Tools_e.V.] [Andreas_Bergmaier] 2022-12-26 Defined TXT keys: bidib,node,interface,uid,prod,user - http://bidib.org/transport/bidib_net_e.html
bootstrap tcp Bootstrap service discovery [Pedro_Garcia] [Pedro_Garcia] 2023-03-20 Defined TXT keys: "url": if present, indicates a connection url (i.e. wss://example.com/bootstrap, or https://example.com/bootstrap) to be used by the device for bootstrapping; "namespace": identifies the underlying application-level protocol (should be unique for the application protocol, typically a UUID or a URN)
bootstrap udp Bootstrap service discovery [Pedro_Garcia] [Pedro_Garcia] 2023-03-20 Defined TXT keys: "url": if present, indicates a connection url (i.e. wss://example.com/bootstrap, or https://example.com/bootstrap) to be used by the device for bootstrapping; "namespace": identifies the underlying application-level protocol (should be unique for the application protocol, typically a UUID or a URN)
caldav tcp Calendaring Extensions to WebDAV (CalDAV) - non-TLS [IESG] [IETF_Chair] 2012-02-17 [RFC6764] This is an extension of the http service. Defined TXT keys: path=<context path>
caldavs tcp Calendaring Extensions to WebDAV (CalDAV) - over TLS [IESG] [IETF_Chair] 2012-02-17 [RFC6764] This is an extension of the https service. Defined TXT keys: path=<context path>
canon-chmp tcp Canon HTTP Management Protocol [Canon_Inc_3] [Tomoyuki_Hansaki] 2014-09-03 2015-03-16 Defined TXT keys: txtvers, mpath
carddav tcp vCard Extensions to WebDAV (CardDAV) - non-TLS [IESG] [IETF_Chair] 2012-02-17 [RFC6352] This is an extension of the http service. Defined TXT keys: path=<context path>
carddavs tcp vCard Extensions to WebDAV (CardDAV) - over TLS [IESG] [IETF_Chair] 2012-02-17 [RFC6352] This is an extension of the https service. Defined TXT keys: path=<context path>
clique udp Clique Link-Local Multicast Chat Room [Telepathy_project] [Telepathy_project] Defined TXT keys: see http://telepathy.freedesktop.org/xmpp/clique
dell-soss-ds-w tcp Spotlight on SQL Server Diagnostic Server HTTP [Dell_2] [Rob_Griffin_3] 2013-10-03 Defined TXT keys: None
ditrios Ditrios SOA Framework Protocol [Mark_Schmatz] [Mark_Schmatz] Defined TXT keys: http://www.ditrios.org/index.php?link=tutorial/index#zeroconf
ebreg ebXML Registry [Matthew_MacKenzie] [Matthew_MacKenzie] Defined TXT keys: HttpBinding=</path/to/registry/http/binding>
googexpeditions tcp Service related to Google Expeditions which is a technology for enabling multi-participant virtual fieldtrip experiences over a local wireless network. See http://g.co/expeditions for more details [Google_Inc] [Jason_Schiller] 2015-07-31 Defined TXT keys: None
googexpeditions udp Service related to Google Expeditions which is a technology for enabling multi-participant virtual fieldtrip experiences over a local wireless network. See http://g.co/expeditions for more details [Google_Inc] [Jason_Schiller] 2015-07-31 Defined TXT keys: None
gucam-http tcp Image Data Transfer API for Wi-Fi Camera Devices over HTTP [Ripplex_Inc] [Hiroshi_Matsuda] 2013-03-04 Defined TXT keys: device-name=<name of camera device>
https tcp HTTP over SSL/TLS [Tim_Berners_Lee] [Tim_Berners_Lee] Web browsers like Safari and Internet Explorer (with the Bonjour for Windows plugin) DO NOT browse for DNS-SD service type "_https._tcp" in addition to browsing for "_http._tcp". This is a conscious decision to reduce proliferation of service types, to help keep DNS-SD efficient on the network. Today, if a user types http://www.mybank.com/ into their web browser, the web server automatically redirects the user to https://www.mybank.com/. Rather than having an entirely different DNS-SD service type for https, we recommend using the same redirection mechanism: advertise a plain "http" service, which consists of nothing except an HTTP redirection to the desired "https" URL. Work is currently being done on adding mechanisms to HTTP and TLS to allow the server to tell the client that it needs to activate TLS on the current connection before proceeding. If this becomes widely adopted, it further justifies the decision to not create a separate DNS-SD service type "_https._tcp", because security becomes just another one of the things that is negotiated on a per-connection basis (like content-type negotiation today) rather than being an entirely separate thing.
meshcop udp Thread Mesh Commissioning [Thread_Group_Inc] [Esko_Dijk] 2020-11-20 Defined TXT keys: Thread 1.1 Specification, Section 8.4.1.1.2. https://www.threadgroup.org/ThreadSpec
meshcop-e udp Thread Mesh Commissioning Ephemeral-key [Thread_Group_Inc] [Esko_Dijk] 2024-01-22 Defined TXT keys: TXT records keys, if any, will be defined in Section 8.12 of the Thread Specification. https://www.threadgroup.org/ThreadSpec
mist tcp A Medical Interoperability Service Type, used to identify medical devices providing network interfaces. [Jon_Griffeth] [Jon_Griffeth] 2017-01-12 Defined TXT keys: https://www.praesentia.com/medkit/mist-service-type (dn dt md mf pr sn vn)
objective Means for clients to locate servers in an Objective (http://www.objective.com) instance. [Marc_Bailey] [Marc_Bailey] Defined TXT keys: txtvers='1' type={'production'|'standby'|'test'|'demo'} protocol={['SOAP'],['CORBA']} transport=['iiop']|['http']
ola tcp Web Interface for the Open Lighting Architecture Software [Open_Lighting_Project] [Simon_Newton_2] 2013-12-09 2014-02-25 Subtypes: _www-http Defined TXT keys: None
owhttpd OWFS (1-wire file system) web server [Paul_H_Alfille] [Paul_H_Alfille] Defined TXT keys: txtvers
pgpkey-http PGP Keyserver using HTTP/1.1 [Jeroen_Massar_3] [Jeroen_Massar_3] Defined TXT keys: path=<path on the server where the HKP applications reside> normally: "path=/pks/"
pgpkey-https PGP Keyserver using HTTPS [Jeroen_Massar_3] [Jeroen_Massar_3] Defined TXT keys: path=<path on the server where the HKP applications reside> normally: "path=/pks/"
presence Peer-to-peer messaging / Link-Local Messaging [XMPP_Registrar] [XMPP_Registrar] Defined TXT keys: See http://www.xmpp.org/registrar/linklocal.html Note: Registration updated May 2007. Was formerly listed as "iChat AV" (Apple's IM client for Mac OS X) with TXT keys: txtvers, port.p2pj, phsh, vc, 1st, AIM, msg, status, last When first shipped in Mac OS X 10.2, iChat's peer-to-peer messaging protocol was created to solve the problem of serverless messaging between peers on the same link. However, there is nothing inherent in the protocol that limits it to being only link-local; it was simply an artifact of iChat in Mac OS X 10.2 using link-local Multicast DNS to discover peers. With the advent of Wide-Area DNS-SD, it is also possible to use iChat's peer-to-peer messaging between machines on different links.
qttp QuickTime Transfer Protocol [Stuart_Cheshire] [Stuart_Cheshire] Defined TXT keys: u=<username> p=<password> path=<path to document> (Same as for _http._tcp)
recipe-sharing tcp Recipe Sharing Protocol [Daniel_G_Taylor] [Daniel_G_Taylor] 2007-11 Defined TXT keys: [http://www.recipemanager.org/rsp/rsp10draft.html#dnssd]
senteo-http Senteo Assessment Software Protocol [Michael_Boyle] [Michael_Boyle] Defined TXT keys: None
slimhttp SliMP3 Server Web Interface [Dean_Blackketter_2] [Dean_Blackketter_2] Defined TXT keys: None
smartenergy Smart Energy Profile [Robby_Simpson] [Robby_Simpson] Defined TXT keys: See http://www.zigbee.org/SmartEnergy
snif-cln tcp End-to-end TLS Relay Client Connection [VESvault_Corp] [Jim_Zubov] 2021-12-15 [https://snif.host/relay-proto#snif-cln] Defined TXT keys: None
snif-fifo tcp End-to-end TLS Relay Cluster [VESvault_Corp] [Jim_Zubov] 2021-12-15 [https://snif.host/relay-proto#snif-fifo] Defined TXT keys: None
snif-srv tcp End-to-end TLS Relay Service Connection [VESvault_Corp] [Jim_Zubov] 2021-12-29 [https://snif.host/relay-proto#snif-srv] Defined TXT keys: None
sparql SPARQL Protocol and RDF Query Language [Alex_Tucker] [Alex_Tucker] Defined TXT keys: txtvers=1 path=<relative or absolute URL of endpoint> protovers=<number> [if not specified then default is 1.0, corresponding to SPARQL version] binding=<HTTP | SOAP> [if not specified then default is HTTP] vocabs=<space separated list of URIs> [RDF vocabularies or OWL ontologies used by the endpoint] metadata=<URL> [to fetch RDF/XML description of SPARQL service]
spx-hmp tcp SpinetiX HMP [SpinetiX_S_A] [Diego_Santa_Cruz] 2011-10-18 Defined TXT keys: txtvers=1 cport= the port for the content HTTP server (secondary HTTP server used for content publishing) mode= the mode in which the HMP device is currently operating, one of "normal", "safe" or "recovery" serial= serial number of the HMP device firmware= firmware version string (e.g., 2.1.0-0.1.7844) model= model string (e.g., HMP100)
sztp tcp This service name is used to construct the SRV service label "_sztp" for discovering SZTP bootstrap servers. [IESG] [IETF_Chair] 2019-01-17 [RFC8572] This protocol uses HTTPS as a substrate.
timezone tcp Time Zone Data Distribution Service - non-TLS [IESG] [IETF_Chair] 2015-08-03 [RFC7808] This is an extension of the http service. Defined TXT keys: path=<context path> (as per Section 6 of [RFC6763]).
timezones tcp Time Zone Data Distribution Service - over TLS [IESG] [IETF_Chair] 2015-08-03 [RFC7808] This is an extension of the https service. Defined TXT keys: path=<context path> (as per Section 6 of [RFC6763]).
usp-agt-coap udp USP discovery [Broadband_Forum] [Broadband_Forum] 2017-01-12 [http://www.broadband-forum.org/assignments] Defined TXT keys: see www.broadband-forum.org/assignments
usp-agt-http tcp USP discovery [Broadband_Forum] [Broadband_Forum] 2017-01-12 [http://www.broadband-forum.org/assignments] Defined TXT keys: see www.broadband-forum.org/assignments
usp-agt-mqtt tcp USP discovery [Broadband_Forum] [Broadband_Forum] 2020-03-17 [http://www.broadband-forum.org/assignments] Defined TXT keys: see www.broadband-forum.org/assignments
usp-agt-stomp tcp USP discovery [Broadband_Forum] [Broadband_Forum] 2017-01-12 [http://www.broadband-forum.org/assignments] Defined TXT keys: see www.broadband-forum.org/assignments
usp-agt-ws tcp USP discovery [Broadband_Forum] [Broadband_Forum] 2017-09-28 [http://www.broadband-forum.org/assignments] Defined TXT keys: see www.broadband-forum.org/assignments
usp-ctr-coap udp USP discovery [Broadband_Forum] [Broadband_Forum] 2017-01-12 [http://www.broadband-forum.org/assignments] Defined TXT keys: see www.broadband-forum.org/assignments
usp-ctr-http tcp USP discovery [Broadband_Forum] [Broadband_Forum] 2017-01-12 [http://www.broadband-forum.org/assignments] Defined TXT keys: see www.broadband-forum.org/assignments
usp-ctr-mqtt tcp USP discovery [Broadband_Forum] [Broadband_Forum] 2020-03-17 [http://www.broadband-forum.org/assignments] Defined TXT keys: see www.broadband-forum.org/assignments
usp-ctr-stomp tcp USP discovery [Broadband_Forum] [Broadband_Forum] 2017-01-12 [http://www.broadband-forum.org/assignments] Defined TXT keys: see www.broadband-forum.org/assignments

Contact Information

ID Name Organization Contact URI Last Updated
[Afkham_Azeez] Afkham Azeez mailto:azeez&wso2.com 2006-06
[Alex_Tucker] Alex Tucker mailto:alex&floop.org.uk
[Andreas_Bergmaier] Andreas Bergmaier mailto:andreas.bergmaier&bidib.org 2022-01-04
[Andreas_Oesterhelt] Andreas Oesterhelt mailto:oes&privoxy.org 2002-06
[BiDiB_Tools_e.V.] BiDiB & Tools e.V. mailto:info&bidib.org 2022-12-26
[Brian_Kennedy] Brian Kennedy mailto:BrianK&targetedconvergence.com 2006-08
[Broadband_Forum] Broadband Forum mailto:help&broadband-forum.org 2020-03-17
[Canon_Inc_3] Canon Inc. mailto:fujii.ken-ichi149&canon.co.jp 2014-09-03
[Chris_Newman] Chris Newman mailto:chris.newman&oracle.com 2017-01-26
[Chris_Peel_2] Chris Peel mailto:chris.gsi&fullphat.net 2014-05-16
[Daniel_G_Taylor] Daniel G. Taylor mailto:dan&programmer-art.org 2007-11
[David_Shaw] David Shaw mailto:dshaw&jabberwocky.com 2003-05
[David_T_Hines] David T. Hines mailto:david.hines&intel.com 2005-02
[Dean_Blackketter_2] Dean Blackketter mailto:dean&slimdevices.com
[Dell_2] Dell mailto:rob.gri55in&gmail.com 2013-10-03
[Diego_Santa_Cruz] Diego Santa Cruz SpinetiX S.A. mailto:Diego.SantaCruz&spinetix.com 2011-10-18
[Eric_Thiebaut_George] Eric Thiebaut-George mailto:erict&aurema.com 2006-04
[Esko_Dijk] Esko Dijk Thread Group, Inc. mailto:esko.dijk&iotconsultancy.nl 2024-01-22
[full_phat_products] full phat products mailto:chris.gsi&fullphat.net 2019-08-08
[Google_Inc] Google Inc. mailto:numbers&google.com 2015-07-31
[Hiroshi_Matsuda] Hiroshi Matsuda Ripplex Inc. mailto:gucam&ripplex.com 2013-03-04
[IESG] IESG mailto:iesg&ietf.org
[IETF_Chair] IETF Chair IETF mailto:chair&ietf.org
[James_Emerton] James Emerton Tri Tech Computers Ltd. mailto:james&tri-tech.com 2012-11-19
[James_Gettys] James Gettys mailto:jg&w3.org
[Jason_Schiller] Jason Schiller Google Inc. mailto:jschiller&google.com 2015-07-31
[Jeroen_Massar_3] Jeroen Massar mailto:jeroen&unfix.org
[Jim_Zubov] Jim Zubov VESvault Corp mailto:jz&vesvault.com 2021-12-29
[Jon_Griffeth] Jon Griffeth mailto:griffeth&praesentia.com 2017-01-12
[Juha_Lindfors] Juha Lindfors OpenRemote, Inc. mailto:juha&openremote.org 2012-12-18
[Katy_Lynn_McCullough] Katy Lynn McCullough mailto:KatyM&laplink.com
[Ken_McDonell_2] Ken_McDonell mailto:kenj&internode.on.net 2013-10-09
[Marc_Bailey] Marc Bailey mailto:marc&objective.com
[Mark_Schmatz] Mark Schmatz mailto:ditrios&markschmatz.de
[Matt_King] Matt King mailto:m&manyone.net 2002-04
[Matthew_MacKenzie] Matthew MacKenzie mailto:mattm&adobe.com
[Michael_Boyle] Michael Boyle mailto:michaelboyle&smarttech.com
[Narayanan_Raju] Narayanan Raju mailto:narayanan.raju&hp.com 2009-02-05
[Open_Lighting_Project] Open Lighting Project mailto:simon&nomis52.net 2013-12-09
[OpenRemote_Inc] OpenRemote, Inc. mailto:juha&openremote.org 2012-12-18
[Paul_H_Alfille] Paul H Alfille mailto:paul.alfille&gmail.com
[Pedro_Garcia] Pedro Garcia mailto:pedro.garcia&puzzle-star.com 2023-03-20
[Performance_Co-Pilot_PCP_Project] Performance Co-Pilot (PCP) Project mailto:kenj&internode.on.net 2013-10-09
[Ripplex_Inc] Ripplex Inc. mailto:gucam&ripplex.com 2013-03-04
[Rob_Griffin_3] Rob Griffin Dell mailto:rob.gri55in&gmail.com 2013-10-03
[Robby_Simpson] Robby Simpson, PhD mailto:rsimpson&gmail.com
[Ruwan_Linton] Ruwan Linton mailto:ruwan&wso2.com 2008-08-20
[Simon_Newton_2] Simon Newton mailto:simon&nomis52.net 2013-12-09
[SpinetiX_S_A] SpinetiX S.A. mailto:Diego.SantaCruz&spinetix.com 2011-10-18
[Sten_H_Danielsen] Sten H. Danielsen mailto:shd&kopek.net 2002-07
[Stephen_Casner] Stephen Casner mailto:casner&precpt.com
[Steve_Hay] Steve Hay mailto:SteveHay&planit.com 2008-06-13
[Stuart_Cheshire] Stuart Cheshire mailto:cheshire&apple.com 2022-07-11
[Telepathy_project] Telepathy project mailto:telepathy&lists.freedesktop.org
[Thread_Group_Inc] Thread Group, Inc. mailto:help&threadgroup.org 2024-01-22
[Tim_Berners_Lee] Tim Berners-Lee mailto:timbl&w3.org
[Tomas_Svoboda] Tomas Svoboda mailto:svoboda&infima.cz 2004-12
[Tomoyuki_Hansaki] Tomoyuki Hansaki Canon Inc. mailto:hansaki.tomoyuki&canon.co.jp 2014-09-03
[Tri_Tech_Computers_Ltd] Tri Tech Computers Ltd. mailto:admins&tri-tech.com 2012-11-19
[VESvault_Corp] VESvault Corp mailto:info&vesvault.com 2021-12-29
[Walter_Underwood] Walter Underwood mailto:wunder&infoseek.com
[XMPP_Registrar] XMPP Registrar mailto:registrar&xmpp.org