Skip to content
QKQuickKit日本語
TCP/IPLOCALRuns in your browser

IP Protocol Numbers

Searchable reference of IP protocol numbers — the IPv4 Protocol field and IPv6 Next Header field — with IPv6 extension-header flagging.

This tool handles input and primary processing in your browser and is designed not to send the input to QuickKit’s server.

IP protocol number reference table

NumberHexKeywordProtocol nameReferenceIPv6 ext. header
00x00HOPOPTIPv6 Hop-by-Hop OptionRFC 8200yes
10x01ICMPInternet Control Message ProtocolRFC 792no
20x02IGMPInternet Group Management ProtocolRFC 1112no
30x03GGPGateway-to-Gateway ProtocolRFC 823no
40x04IPv4IPv4 encapsulationRFC 2003no
50x05STInternet Stream ProtocolRFC 1819no
60x06TCPTransmission Control ProtocolRFC 9293no
80x08EGPExterior Gateway ProtocolRFC 888no
90x09IGPany private interior gateway (e.g. Cisco IGRP)IANAno
170x11UDPUser Datagram ProtocolRFC 768no
270x1BRDPReliable Data ProtocolRFC 908no
330x21DCCPDatagram Congestion Control ProtocolRFC 4340no
410x29IPv6IPv6 encapsulationRFC 2473no
430x2BIPv6-RouteRouting Header for IPv6RFC 8200yes
440x2CIPv6-FragFragment Header for IPv6RFC 8200yes
460x2ERSVPResource Reservation ProtocolRFC 2205, RFC 3209no
470x2FGREGeneric Routing EncapsulationRFC 2784no
500x32ESPEncapsulating Security PayloadRFC 4303yes
510x33AHAuthentication HeaderRFC 4302yes
580x3AIPv6-ICMPICMP for IPv6RFC 4443no
590x3BIPv6-NoNxtNo Next Header for IPv6RFC 8200no — ends the header chain
600x3CIPv6-OptsDestination Options for IPv6RFC 8200yes
880x58EIGRPEnhanced Interior Gateway Routing ProtocolRFC 7868no
890x59OSPFIGPOpen Shortest Path FirstRFC 2328, RFC 5340no
940x5EIPIPIP-within-IP Encapsulation ProtocolIANAno
970x61ETHERIPEthernet-within-IP EncapsulationRFC 3378no
980x62ENCAPEncapsulation HeaderRFC 1241no
1030x67PIMProtocol Independent MulticastRFC 7761no
1080x6CIPCompIP Payload Compression ProtocolRFC 3173no
1120x70VRRPVirtual Router Redundancy ProtocolRFC 9568no
1150x73L2TPLayer Two Tunneling Protocol version 3RFC 3931no
1240x7CISIS over IPv4IS-IS over IPv4IANAno
1320x84SCTPStream Control Transmission ProtocolRFC 9260no
1330x85FCFibre ChannelRFC 6172no
1350x87Mobility HeaderIPv6 Mobility HeaderRFC 6275yes
1360x88UDPLiteLightweight User Datagram ProtocolRFC 3828no
1370x89MPLS-in-IPMPLS-in-IPRFC 4023no
1380x8AmanetMANET ProtocolsRFC 5498no
1390x8BHIPHost Identity ProtocolRFC 7401yes
1400x8CShim6Shim6 ProtocolRFC 5533yes
1410x8DWESPWrapped Encapsulating Security PayloadRFC 5840no
1420x8EROHCRobust Header CompressionRFC 5858no
1430x8FEthernetEthernet (SRv6 / segment routing)RFC 8986no
1440x90AGGFRAGAGGFRAG encapsulation payload for ESPRFC 9347no
1450x91NSHNetwork Service HeaderRFC 9491no
1460x92HomaHomaIANAno
1470x93BIT-EMUBit-stream EmulationRFC 9801yes
2530xFDUse for experimentation and testingRFC 3692yes
2540xFEUse for experimentation and testingRFC 3692yes
2550xFFReservedReservedIANAno
How it works

Reference for the 8-bit value in the IPv4 header "Protocol" field and the IPv6 header "Next Header" field, from the IANA Assigned Internet Protocol Numbers registry (registry last updated 2026-03-09; verified 2026-09-15). This table is a curated subset of the values operators meet often; only entries verified as correct are included, and an absent value may still be assigned. Number and keyword follow the registry; the protocol name is a curated display label. Search by decimal number, by 0x-style hex, or by a word in the keyword or name. In IPv6 the same field is the Next Header field. The IPv6 extension header column mirrors the IPv6 Extension Header attribute of that registry — 0, 43, 44, 50, 51, 60, 135, 139, 140, 147 and the experimental values 253 and 254 are marked there. Value 59 means "no next header": it ends the header chain and is not marked as an extension header, so it is shown separately. Protocol numbers 253 and 254 are reserved for experimentation and testing (RFC 3692); 255 is reserved. The Reference column is a curated protocol reference: the current protocol-specification RFC where a clear one exists (for example RFC 9568 for VRRP, RFC 9260 for SCTP), otherwise the RFCs the registry cites, and IANA when the assignment is backed only by an IANA contact or submission. The full table works without JavaScript; search and the lookup panel need JavaScript.