Index of IANA Protocol Registries
Navigation Menu
Search code, repositories, users, issues, pull requests..., provide feedback.
We read every piece of feedback, and take your input very seriously.
Saved searches
Use saved searches to filter your results more quickly.
To see all available qualifiers, see our documentation .
- Notifications
IANA assigned port numbers
kapetan/service-names-port-numbers
Folders and files, repository files navigation, service-names-port-numbers.
A simple json list with IANA assigned port numbers. See IANAs Service Name and Transport Protocol Port Number Registry for more details.
In the above example ports is an array containg objects with following format.
Note that not all properties are necessarily present on each entry.
- JavaScript 100.0%
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
1.9 Standards Assignments
- 2 contributors
This protocol uses standard Internet Assigned Numbers Authority (IANA) port assignments for HTTP and Secure Sockets Layer (SSL) . These standard port assignments use IANA-assigned ports, as listed in the following table.
Additional resources
- Acronyms and Terms
- Courses and Learning
- ICANN for Beginners
- What ICANN Does
- Effect on the Internet
- What's Going On Now
- How to Participate
- Terms & Conditions
- NextGen@ICANN Program
- President's Corner
- ICANN Management Organization Chart
- IANA DNSSEC Root Information
- TLD DNSSEC Report
- Root Deployment
- Deployment Graph
- Key Ceremony
- Presentations
- Related Sites
- GNSO Improvements
- Travel Support
- WHOIS Policy Review Team Recommendations - Implementation
- Subscribe and Follow
- Media Assets
- Leader Bios
- About ICANN
- Strategic Initiatives
- Additional Resources
- Board Activities and Meetings
- Reconsideration
- Updating the IRP
- Standards of Practice
- Respectful Communication
- Empowered Community Administration
- Empowered Community Administration Mailing List
- Empowered Community Correspondence
- Document Disclosure
- Getting Started
- Nominating Committee
- Technical Liaison Group
- Accountability & Transparency
- Registration Directory Service
- Security, Stability, and Resiliency
- Competition, Consumer Trust & Consumer Choice
- CCT Metrics
- Expected Standards of Behavior
- Employee Practices and Resources
- Enhancing ICANN Accountability – Work Stream 2 Implementation
- Current Bylaws
- Board Code of Conduct
- Board Conflicts of Interest Policy
- Board Statements of Interest
- Lobbying Disclosures & Contribution Reports
- Summary of Conflicts of Interest and Ethics Practices Review
- Evolving ICANN’s MSM
- Call for Public Input: Draft Process to Develop the Proposal (8 April-8 May 2014
- Process to Develop the Proposal and Next Steps
- AOC Tracking
- Partnership Memorandums of Understanding
- Annual Reports
- Financial Reports
- Policies, Guidelines and Procedures
- ICANN Strategic Plan for FY26-30
- Strategic Outlook Trends Program
- ICANN Strategic Plan for FY16-20
- Quarterly Reports
- 2023 ICANN CEO Search Committee
- Technical Experts Group (TEG)
- Past NomComs
- Customer Standing Committee
- Root Zone Evaluation Review Committee (RZERC)
- Civil Society
- Complaints Report
- Domain Name System Abuse
- Approach & Process
- gTLD Registry Compliance
- Accredited Registrar Compliance
- General Questions
- Complaint Submission & Learn More
- Performance Reports
- 2024 Global Amendment to the RAA
- 2023 Global Amendment to the RAA
- Registrar Library
- News & Communications
- Registrar Application
- Registrar Application Instructions
- Registrar Training
- Annual Registrar Compliance Certificate
- Bulk Transfers
- Data Retention Waiver
- Purchasing an ICANN-Accredited Registrar
- Registrar Data Escrow Program
- Registrar Mergers
- Registrar Name Changes
- Registrar Primary Contact Updates
- Registry-Registrar Agreement (RRA) Termination
- Renewing an Existing Accreditation
- Terminating an Accreditation
- Transferring (Assigning) an ICANN Accreditation
- Privacy and Proxy Service Providers
- Policy Statement
- Billing Frequently Asked Questions (FAQ) for Registrars
- Consensus Policies
- Contact List
- Domain Name Holder FAQs
- Inter-Registrar Transfer Information
- Operations Handbook for Registrars
- GDD Accounts and Services Team
- gTLD Lifecycle
- Naming Services portal
- Registration Data Access Protocol (RDAP)
- Registrar Data Escrow Reporting FAQ
- Registrar Data Escrow Agent Transition Resources
- Registrar Data Escrow Agent Change FAQ
- Registrar FAQs
- Security Response Waiver (SRW) Requests for Registrars
- Data Directory Services Privacy Law Conflicts
- Whois-Related Policies and Provisions
- Registration Data Policy Implementation Resources
- RSEP Implementation Notes
- Preliminary Determination of Competition Issues
- Reconciliation
- RSEP Announcements Archive
- ICANN News & Media
- ICANN Public Comment Page
- ICANN Public Meetings Calendar
- 2024 Global Amendment to the Base New gTLD Registry Agreement
- 2023 Global Amendment to the Base New gTLD Registry Agreement
- 2017 Global Amendment to the Base New gTLD Registry Agreement
- Proof of Concept Reports
- Terminated Registry Agreements
- Data Protection and Privacy
- Continuity Archive
- Form 6166 - U.S. Tax Residency Certification (TRC)
- Framework for Registry Operators to Respond to Security Threats
- Operations Handbook for Registry Operators
- gTLDs JSON Report
- List of Top-Level Domains
- Monthly Registry Reports
- New gTLD Program
- New gTLD Program Case Studies
- New gTLD Registry Operator CSV Report
- Registry FAQs
- Registry Listing Page
- Registry System Testing (RST)
- Service Level Agreement (SLA) Monitoring System API Specification
- Completed Direct Change of Control
- Registry Operator Change of Control
- Continued Operations Instrument (COI)
- Centralized Zone Data Service (CZDS)
- Community gTLD Change Requests
- Cross-Ownership Notification Service
- ICANN-Approved Registry Data Escrow Agents
- Registry Data Escrow Agent Change Requests
- Registry Data Escrow Agreement Amendments
- Registry Data Escrow Agent Application
- IDN Table Update and Publish
- Material Subcontracting Arrangement (MSA) Change
- New gTLD RA Renewals
- Registry Agreement Termination Service
- Registry Operator Name Change
- Fast Track RSEP Process and Standard Authorization Language
- RSEP Process Workflow
- Technical Evaluation Panel
- EBERO Temporary Transition Process
- EBERO Transition Process - Communicate
- EBERO Transition Process - DNS
- EBERO Transition Process - Data Escrow
- EBERO Transition Process - RDDS
- EBERO Transition Process - SRS
- Prospective Registry Evaluation Matrix
- Registry Transition Process with Proposed Successor - Check Support
- Registry Transition Process with Proposed Successor - Communicate
- Registry Transition Process with Proposed Successor - Evaluate
- Registry Transition Process with Proposed Successor
- Registry Transition Process with Request for Proposals - Check Support
- Registry Transition Process with Request for Proposals - Communicate
- Registry Transition Process with Request for Proposals - Evaluate
- Registry Transition Process with Request for Proposals - RFP
- Registry Transition Process with Request for Proposals
- Removal of Cross-Ownership Restrictions
- Two-Character Archive
- Country & Territory Names
- RRA Amendment Procedure
- RRA Amendment with Temporary Specification
- INGO Claims Notification
- TMCH Requirements
- Security Response Waiver (SRW) Requests for Registry Operators
- About Domain Names
- ICANN Policies
- Using Domain Name Registration Data
- Keeping Registration Data Accurate
- Access and the Evolution of the WHOIS System
- Domain Name Industry
- Registering Domain Names
- Contact Information and WDRP
- Securely Managing Your Domain Name
- Transferring Domain Names
- Renewing Domain Names
- Rights and Responsibilities
- Spam, Phishing, and Website Content
- Trademark Infringement
- GDS Metrics
- IS-SSR Team Blogs
- Security Terminology
- Document Archive
- Background Materials
- Root Zone Database
- ICANN and ISO
- Generation Panel Update
- Maximal Starting Repertoire
- Proposals for Root Zone Label Generation Ruleset
- IDN Variant TLD Implementation
- LGR Toolset
- IDN ccTLD Fast Track
- IDN Implementation Guidelines
- Second-Level LGR Reference
- Announcements and Blogs Posts
- Make your systems UA-ready
- Universal Acceptance Steering Group (UASG)
- UA Training
- UA Readiness Evaluations
- Policy Mission
- Policy Staff Goals
- IPv6 Allocation
- ASN Allocation
- Post Exhaustion IPv4 Allocation
- New RIRs Criteria
- Review Procedures
- Policy Updates
- Operational Design Phase (ODP)
- Implementation
- Root Zone KSK Rollover
- Tech Day Archive
- Report Security Issues
- Certificate Authority
- Registry Liaison
- Dispute Resolution
- Policy Document
- Provider Approval Process
- Principal Documents
- Proceedings
- Historical Documents
- FAQ: IT Professionals
- FAQ: Registries
- Guide for IT Professionals
- Recommendations for New ccTLDs
- Report a Problem
- Registrar Problems
- Whois Data Correction
- Independent Review Process
- Request for Reconsideration
ICANN Locations
Headquarters, los angeles, california, usa.
12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536, USA
Phone: +1 310 301 5800 Fax: +1 310 823 8649
REGIONAL OFFICES
Istanbul, türkiye.
Hakki Yeten Cad. Selenium Plaza No:10/C K:10 34349 Istanbul, Türkiye
Tel: +32 2 894 7409
South Beach Tower 38 Beach Road, Unit 04-11 Singapore 189767
Phone: +65 6816 1288
Montevideo, Uruguay
La Casa de Internet de Latinoamérica y el Caribe Rambla República de México 6125 11400 Montevideo, Uruguay
Phone: +598 2604 2222 ext 5701 Fax: +598 2604 2222 ext 4112
Brussels, Belgium
6 Rond-Point Schuman B-1040 Brussels, Belgium
Phone: +32 2 894 7414
ENGAGEMENT CENTERS
Beijing, china.
5th Floor, No. 1 Building, Software Park Chinese Academy of Sciences 4 South 4th Street Zhongguancun, Haidian District, Beijing, China
Geneva, Switzerland
Chemin des Mines 2 1202 Genève, Switzerland
Phone: +41 22 592 12 51
Nairobi, Kenya
Regus Center 17th Floor JKUAT Towers, Kenyatta Avenue PO BOX 15168-00400 Nairobi, Kenya
Phone: +254 (0)20 5157029 Fax: +254 (0)20 5157001
Washington, D.C., USA
1901 L Street NW, Suite 300 Washington, DC 20036, USA
Phone: +1 202 570 7240 Fax: +1 202 789 0104
If you require assistance or have a question, please visit Global Support
A note about our terms of service:
We have updated our electronic terms of service to provide greater transparency and align with laws applicable to us. Learn more .
This site uses cookies to deliver an efficient user experience and to help us see how the site is used. Learn more . OK
Time Zone Database
The Time Zone Database (often called tz or zoneinfo ) contains code and data that represent the history of local time for many representative locations around the globe. It is updated periodically to reflect changes made by political bodies to time zone boundaries, UTC offsets, and daylight-saving rules. Its management procedure is documented in BCP 175: Procedures for Maintaining the Time Zone Database .
Latest version
Mailing lists.
- Announcements: A low-volume announcement mailing list used for announcing updates to the Time Zone Database. Subscribe/Unsubscribe Archive
- Submissions and Discussion: A higher volume discussion list used for discussing proposals for updates to the Database. Contributions to this list may be emailed to [email protected] . Subscribe/Unsubscribe Archive
Distribution
We provide access to the Time Zone Database via three methods:
- HTTP: https://www.iana.org/time-zones
- FTP: ftp://ftp.iana.org/tz/
- Rsync: rsync://rsync.iana.org/tz/
TZ Coordinator
The IESG-designated TZ Coordinators are Paul Eggert (primary) and Tim Parenti (secondary).
Further information
IMAGES
VIDEO
COMMENTS
User Ports are assigned by IANA using the "IETF Review" process, the "IESG Approval" process, or the "Expert Review" process, as per . Dynamic Ports are not assigned. The registration procedures for service names and port numbers are described in . Assigned ports both System and User ports SHOULD NOT be used without or prior to IANA registration.
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.
RFC 6335 Service Name and Port Number Procedures August 2011 1.Introduction For many years, the assignment of new service names and port number values for use with the Transmission Control Protocol (TCP) [] and the User Datagram Protocol (UDP) [] has had less than clear guidelines.New transport protocols have been added -- the Stream Control Transmission Protocol (SCTP) [] and the Datagram ...
This document updates IANA's procedures by obsoleting the previous UDP and TCP port assignment procedures defined in Sections 8 and 9.1 of the IANA Allocation Guidelines, and it updates the IANA service name and port assignment procedures for UDP-Lite, the Datagram Congestion Control Protocol (DCCP), and the Stream Control Transmission Protocol ...
This is the dataset of IANA service names and their assigned ports and transport protocols - along with related metadata. port_number: The ports assigned to that service. This can be individual ports, or a range. contact: the name of the individual or organisation who serves as the contact person for the assignment. registration_date.
Library and Microservice (GraphQL API) against the IANA Service Names And Port Numbers Registry - rm3l/service-names-port-numbers ... (IANA, Nmap Services, ...) and allows to lookup service names from port numbers, or vice-versa. This library is an in-memory database that allows to lookup IANA records based upon certain filters (e.g., service ...
RFC 5531 The range 0x00000001 - 0x1fffffff is reserved to be assigned by IANA. New assignments will start from decimal 400000. Up to 100 numbers: First Come First Served. 101-1000 numbers: Specification Required. (Expert: Spencer Shepler) More than 1000 numbers: IESG Approval. Transport Semantics (r_nc_semantics) RFC 1833 Standards Action
This is a list of TCP and UDP port numbers used by protocols for operation of network applications. The Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP) only need one port for duplex, bidirectional traffic.They usually use port numbers that match the services of the corresponding TCP or UDP implementation, if they exist. The Internet Assigned Numbers Authority (IANA) is ...
A simple json list with IANA assigned port numbers. See IANAs Service Name and Transport Protocol Port Number Registry for more details. npm install service-names-port-numbers Usage. var ports = require ('service-names-port-numbers') (); In the above example ports is an array containg objects with following format.
This document defines the procedures that the Internet Assigned Numbers Authority (IANA) uses when handling registration and other requests related to the transport protocol port number and service name registry and updates RFC2782 to clarify what a service name is and how it is registered. This document defines the procedures that the Internet Assigned Numbers Authority (IANA) uses when ...
3. Port Number Types. TCP, UDP, SCTP and DCCP use 16-bit namespaces for their port number registries. The port registries for all these transport protocols are subdivided into three ranges of numbers, and Section 6 (Port Number Space Requests) describes the IANA procedures for each range in detail: . the Well Known Ports, i.e., the System Ports, from 0-1023 (assigned by IANA)
1.9 Standards Assignments. This protocol uses standard Internet Assigned Numbers Authority (IANA) port assignments for HTTP and Secure Sockets Layer (SSL). These standard port assignments use IANA-assigned ports, as listed in the following table. This protocol uses standard Internet Assigned Numbers Authority (IANA) port assignments for HTTP ...
ID 725 Known Mappings UDP Port 2948 TCP Port 2948 IP Protocol - IP Version IPv4 Support Yes IPv6 Support Yes Application Group wap-group Category browsing
The format of the SRV RR Here is the format of the SRV RR, whose DNS type code is 33: _Service._Proto.Name TTL Class SRV Priority Weight Port Target (There is an example near the end of this document.) Service The symbolic name of the desired service, as defined in Assigned Numbers [STD 2] or locally.
Service names are assigned on a first-come, first-served process, as documented in . 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 .
This document defines the procedures that the Internet Assigned Numbers Authority (IANA) uses when handling assignment and other requests related to the Service Name and Transport Protocol Port Number Registry. It also discusses the rationale and principles behind these procedures and how they facilitate the long-term sustainability of the registry.
1901 L Street NW, Suite 300. Washington, DC 20036, USA. Phone: +1 202 570 7240. Fax: +1 202 789 0104. If you require assistance or have a question, please visit Global Support.
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.
The Time Zone Database (often called tz or zoneinfo) contains code and data that represent the history of local time for many representative locations around the globe. It is updated periodically to reflect changes made by political bodies to time zone boundaries, UTC offsets, and daylight-saving rules. Its management procedure is documented in ...