Port 1718H.323 Multicast Gatekeeper Discovery

H.323 multicast gatekeeper discovery uses this port to locate a gatekeeper on an H.323 network.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
2/10

safe

lookups
0

rank 994 of 1,908 · top 52%

also known as h323gatedisc, H.323 gatekeeper discovery, H.225 RAS discovery

Technical Details

what runs on :1718

H.323 gatekeeper discovery uses H.225 RAS Gatekeeper Request (GRQ) messages, normally sent over UDP to the H.323 multicast address 224.0.1.41 on port 1718. A gatekeeper responds with Gatekeeper Confirm (GCF) or Gatekeeper Reject (GRJ), after which the endpoint uses UDP port 1719 for RAS exchanges and commonly TCP port 1720 for H.225 call signaling. Messages use ASN.1 PER encoding and are not encrypted by default; although IANA lists both TCP and UDP, multicast discovery is ordinarily a UDP operation.

Security Information

exposure of :1718

risk score

2/ 10safe

routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.

network services averages 3.2 across 842 ports — this one sits 1.2 below.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

This port is intended for local H.323 network discovery, not direct Internet exposure. Unrestricted access can disclose gatekeeper and endpoint information or permit spoofed discovery responses, while legacy H.323 implementations may have additional protocol vulnerabilities; restrict it to trusted voice-network segments and filter multicast and unsolicited WAN traffic.

the 8 most looked-up other ports in network services — 842 ports carry that label.

risk mix of the 8 listed

  • caution100%

0 of 8 encrypted