whatportis.com
suggest an edit →

Port 179Border Gateway Protocol

BGP (Border Gateway Protocol) is a standardized exterior gateway protocol designed to exchange routing information between autonomous systems (ASes) on the Internet. It forms the backbone of routing decisions across the global Internet, helping network operators determine the most efficient paths for data. Due to its importance, BGP plays a crucial role in maintaining overall Internet connectivity and stability..

inNetwork ServicesSystem
transport
tcp

single transport

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
4/10

caution

lookups
11,132

rank 378 of 993 · top 38%

Technical Details

what runs on :179

Overview

Border Gateway Protocol (BGP) is the protocol used to exchange routing information between different autonomous systems (ASes) on the Internet. It is classified as a path vector protocol and is defined in various RFCs, notably RFC 4271. BGP makes routing decisions based on network policies, path attributes, and rule sets.

Functionality

BGP facilitates inter-domain routing by enabling routers in different administrative domains to advertise, learn, and select the best routes to destination networks. It distinguishes itself from Interior Gateway Protocols (IGPs) like OSPF or EIGRP by scale and policy control rather than convergence speed. BGP operates over TCP, typically on port 179, providing reliable transit for routing updates.

Types and Features

There are two primary forms of BGP: external BGP (eBGP), used between different ASes, and internal BGP (iBGP), used within the same AS. BGP uses path attributes such as AS_PATH, NEXT_HOP, and LOCAL_PREF to determine route selection. It supports advanced features like route reflectors, confederations, multipath, and route-maps for granular control over routing behavior.

Security Information

exposure of :179

risk score

4/ 10caution

worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.

network services averages 3.9 across 604 ports — this one sits 0.1 above.

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

every listening transport is another surface to filter at the edge

security overview

Common Vulnerabilities

  • Route Hijacking: Malicious ASes can advertise incorrect IP prefix routes, hijacking traffic.
  • Route Leaks: Misconfigured policies can inadvertently expose internal routes externally.
  • Session Hijacking: Without protection, BGP sessions may be hijacked via TCP interception.
  • Denial of Service: Attackers can disrupt BGP sessions by overwhelming routers with bogus routes or exploiting TCP vulnerabilities.

Common Mitigations

  • Prefix Filtering: Limit accepted routes based on known, validated prefixes to prevent hijack and leak.
  • Use of TTL Security Hack (GTSM): Protect against off-path attacks by restricting TTL values.
  • TCP MD5 Signatures (RFC 2385): Authenticate BGP sessions to reduce the chance of session hijacking.
  • Resource Public Key Infrastructure (RPKI): Cryptographically verify the origin of route announcements.
  • Peer Authentication and Access Controls: Limit BGP peering to trusted ASes and secure router management interfaces.
  • Monitoring and Logging: Continuously monitor BGP sessions and routing anomalies for rapid response.

Related Ports

all 604 in network services →

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

portservicerisk
:9080Groove RPCcaution
:6543Jetnetcaution
:5938TeamViewercaution
:8291Winbox MikroTik Admincaution
:3233WhiskerControl Protocolcaution
:3268Microsoft Global Catalog (GC)caution
:135Microsoft EPMAPcaution
:3128Tatsoft Default HTTP Proxycaution

risk mix of the 8 listed

  • caution100%

0 of 8 encrypted