Huntbook by Predefender

part-5

Network Services and Ports

Author: Roger C.B. Johnsen

A port suggests a service; it does not prove one. Prefer application identification, process telemetry, certificates, DNS, and packet content over port labels alone.

High-value service reference

PortServiceHunt for
20-21/TCPFTPClear-text credentials, external uploads, and unapproved use.
22/TCPSSH/SFTPNew sources, unusual accounts, reverse tunnels, long sessions.
23/TCPTelnetClear-text remote access; require explicit ownership.
25,465,587/TCPSMTPDirect-to-internet mail and high-volume egress.
53/UDP,TCPDNSUnapproved resolvers, long labels, rare types, tunneling.
67-68/UDPDHCPRogue offers and altered gateway or DNS options.
80/TCPHTTPClear-text payloads, direct-IP requests, downloads.
88/UDP,TCPKerberosAbnormal ticket volume, downgrade, unusual hosts.
123/UDPNTPUnapproved sources, amplification, clock changes.
135/TCPMS RPCRemote administration; follow negotiated dynamic ports.
137-139NetBIOSLegacy discovery, poisoning exposure, cross-segment use.
161-162/UDPSNMPDefault communities, scanning, unexpected writes.
389,636/TCPLDAP(S)Reconnaissance, clear-text binds, unusual query volume.
443/TCP,UDPHTTPS/QUICSNI/certificate anomalies, rare destinations, periodicity.
445/TCPSMBAdmin shares, remote execution, fan-out, file transfer.
500,4500/UDPIKE/IPsecUnapproved VPN peers and endpoint tunnels.
1433/TCPMS SQLExposure, discovery bursts, unusual clients.
2049/TCP,UDPNFSUnexpected mounts and sensitive exports.
3268,3269/TCPAD Global CatalogDirectory discovery from unusual hosts.
3389/TCP,UDPRDPNew pairs, exposure, off-hours use, identity anomalies.
5353,5355/UDPmDNS/LLMNRCross-segment leakage and poisoning exposure.
5985,5986/TCPWinRMCorrelate caller, account, process, and target scope.
6379/TCPRedisUnauthenticated exposure and unexpected clients.
8080,8443/TCPAlternate webShadow consoles, proxies, and tunneling.

Fast triage

  1. Determine direction, result, duration, bytes, and listener versus connector.
  2. Resolve the owning process, user, workload, and device role.
  3. Compare historical prevalence; first-seen pairs often outperform rare ports.
  4. Inspect protocol metadata and look for fan-out, periodicity, and abnormal transfer.

Use the live IANA port registry for authoritative assignments.

Revision

Revised DateComment
2025-03-16Article added
2026-07-22Replaced static OS list with hunting-oriented reference