Search a deterministic reference covering every port and range in the pinned public checklist, with reviewed engineering detail for common infrastructure services.
Inputs stay in this browser and results are not saved.
Matches port numbers, ranges, service names, protocols, aliases and technology terms.
Start a search or browse
Encrypted remote shell, command execution and file transfer.
Linux administration, automation, tunnels, SFTP/SCP and Git access.
Client to server
Disable password authentication where practical, protect private keys and restrict administrative access by source network.
Domain-name queries, responses and zone-transfer traffic.
UDP handles most queries; TCP is required for zone transfers and responses that do not fit the negotiated UDP size.
Client to server
Restrict recursion and zone transfers, patch resolvers, and account for both transports in firewall and monitoring policy.
Secure HTTP traffic protected by TLS.
Web applications, APIs, reverse proxies, load balancers and encrypted browser traffic.
Client to server
TLS version, cipher policy, certificate validity and application authorization remain separate security controls.
Microsoft Remote Desktop interactive sessions; modern clients can use both TCP and UDP.
Remote Windows administration, virtual desktops and published applications.
Client to server
Do not expose directly to the internet. Use a gateway or VPN, Network Level Authentication, MFA and source restrictions.
Enter a port, service, protocol, alias, or common technology name such as 443, HTTPS, Kerberos, WinRM, LDAP, or Kubernetes.
Multi-port technologies return all curated records so firewall and dependency decisions are not reduced to one port.
Confirm whether each entry uses TCP, UDP, or both and review its usual traffic direction before changing policy.
Use the security notes and official reference links as inputs to a change review, then verify against the deployed product configuration.
Prepare the following information before starting. Use measured evidence where possible; defaults are examples and should not be treated as recommendations.
The lookup performs client-side matching against a version-controlled dataset. Reviewed KBY records provide operational detail for common infrastructure, while a generated non-indexable layer guarantees coverage of every port and range in the pinned reference revision. IANA assignments are used where available; no AI model or external lookup API is involved at runtime.
Search results are deterministic matches against a reviewed core plus a generated, version-controlled coverage snapshot with explicit transport fields.
An engineer searches for port 443 while validating a web-facing load balancer rule.
The lookup identifies HTTPS over TCP, explains its typical use and traffic direction, and highlights that certificate, TLS version, and cipher configuration require separate review.
No. It covers every port and range in the pinned public reference snapshot and validates registered assignments against IANA where available. IANA remains the authority for the continuously updated registry.
Technologies such as Kerberos, Active Directory, DNS, DHCP, SMB, and Kubernetes use multiple transports or endpoints. The lookup keeps those records distinct.
No. Port numbers are conventions. Confirm the owning process, configuration, traffic, and application protocol on the system itself.
Open the interactive utility without an account. Inputs and results are not saved.
Open toolA useful digest about twice a week with new error references, tools, integration notes and production lessons. No daily noise.