Skip to main content
All Engineering Labs
ReviewGraduate

Port & Protocol Lookup

Search a deterministic reference covering every port and range in the pinned public checklist, with notes for common infrastructure services, plus the sourced network requirements for Intune, Autopilot, Apple push notifications and Entra Connect.

Around 2 mins No account required Graduate level
Interactive utility

Run Port Lookup

Inputs stay in this browser and results are not saved.

Search the port and protocol reference

Matches port numbers, ranges, service names, protocols, aliases and technology terms.

Start a search or browse

Common references

22TCP

SSH

Encrypted remote shell, command execution and file transfer.

Typical use

Linux administration, automation, tunnels, SFTP/SCP and Git access.

Traffic direction

Client to server

Security considerations

Disable password authentication where practical, protect private keys and restrict administrative access by source network.

53TCP + UDP

DNS

Domain-name queries, responses and zone-transfer traffic.

Typical use

UDP handles most queries; TCP is required for zone transfers and responses that do not fit the negotiated UDP size.

Traffic direction

Client to server

Security considerations

Restrict recursion and zone transfers, patch resolvers, and account for both transports in firewall and monitoring policy.

443TCP

HTTPS

Secure HTTP traffic protected by TLS.

Typical use

Web applications, APIs, reverse proxies, load balancers and encrypted browser traffic.

Traffic direction

Client to server

Security considerations

TLS version, cipher policy, certificate validity and application authorization remain separate security controls.

HTTPTransport Layer SecurityWeb Servers
3389TCP + UDP

RDP

Microsoft Remote Desktop interactive sessions; modern clients can use both TCP and UDP.

Typical use

Remote Windows administration, virtual desktops and published applications.

Traffic direction

Client to server

Security considerations

Do not expose directly to the internet. Use a gateway or VPN, Network Level Authentication, MFA and source restrictions.

Endpoint management

Network requirements for Intune, Windows, Apple and Entra Connect

Hosts and ports from Microsoft and Apple documentation, each linked to its source and checked on 9 Nov 2026. Apple's support.apple.com articles couldn't be retrieved, so Apple device rows cite Microsoft's Intune documentation and Apple's developer documentation. Vendors change these lists; recheck the linked page before a production change.

24 of 24 rows

The PowerShell output only covers rows defined by port or IP range: New-NetFirewallRule takes addresses, not host names. Rules for host names such as *.manage.microsoft.com belong on your proxy or perimeter firewall; they're listed as comments at the end.

TechnologyHosts or rangeProtocol / portsDirectionPurposeSource
Microsoft Intune
Managed devices
  • *.manage.microsoft.com
  • manage.microsoft.com
  • *.dm.microsoft.com
  • EnterpriseEnrollment.manage.microsoft.com
TCP 80, 443OutboundIntune client and host service (endpoint set 163, required).

SSL inspection isn't supported for *.manage.microsoft.com or *.dm.microsoft.com. If your firewall can't use domain names, Microsoft publishes the subnet list on the same page.

Microsoft Learn: Network endpoints for Microsoft Intune
Microsoft Intune
Managed Windows devices
  • mmcswdc01.blob.core.windows.net
  • mmcswdc02.blob.core.windows.net
  • swda01-mscdn.manage.microsoft.com
  • swda02-mscdn.manage.microsoft.com
  • swdb01-mscdn.manage.microsoft.com
  • swdb02-mscdn.manage.microsoft.com
  • swdc01-mscdn.manage.microsoft.com
  • swdc02-mscdn.manage.microsoft.com
  • swdd01-mscdn.manage.microsoft.com
  • swdd02-mscdn.manage.microsoft.com
  • swdin01-mscdn.manage.microsoft.com
  • swdin02-mscdn.manage.microsoft.com
TCP 80, 443OutboundWin32 app content (endpoint set 170, required).Microsoft Learn: Network endpoints for Microsoft Intune
Microsoft Intune
Managed Windows devices (tenant in North America)
  • imeswda-afd-primary.manage.microsoft.com
  • imeswda-afd-secondary.manage.microsoft.com
  • imeswda-afd-hotfix.manage.microsoft.com
TCP 443OutboundIntune management extension: Win32 apps, PowerShell scripts, remediations, custom compliance.

Allow HTTP partial responses. Use the row for your tenant location (Tenant administration > Tenant details).

Microsoft Learn: Network endpoints for Microsoft Intune
Microsoft Intune
Managed Windows devices (tenant in Europe)
  • imeswdb-afd-primary.manage.microsoft.com
  • imeswdb-afd-secondary.manage.microsoft.com
  • imeswdb-afd-hotfix.manage.microsoft.com
TCP 443OutboundIntune management extension: Win32 apps, PowerShell scripts, remediations, custom compliance.

Allow HTTP partial responses.

Microsoft Learn: Network endpoints for Microsoft Intune
Microsoft Intune
Managed Windows devices (tenant in Asia Pacific)
  • imeswdc-afd-primary.manage.microsoft.com
  • imeswdc-afd-secondary.manage.microsoft.com
  • imeswdc-afd-hotfix.manage.microsoft.com
TCP 443OutboundIntune management extension: Win32 apps, PowerShell scripts, remediations, custom compliance.

Allow HTTP partial responses.

Microsoft Learn: Network endpoints for Microsoft Intune
Intune for macOS
Managed Macs
  • macsidecar.manage.microsoft.com
  • macsidecareu.manage.microsoft.com
  • macsidecarap.manage.microsoft.com
TCP 443OutboundmacOS app and script deployment CDN: macsidecar (North America), macsidecareu (Europe), macsidecarap (Asia Pacific).

Only the host for your tenant's region is needed.

Microsoft Learn: Network endpoints for Microsoft Intune
Microsoft Entra ID
Managed devices
  • login.microsoftonline.com
  • graph.windows.net
TCP 80, 443OutboundAuthentication and identity (endpoint set 56, required).Microsoft Learn: Network endpoints for Microsoft Intune
Microsoft Entra ID
Managed devices
  • enterpriseregistration.windows.net
  • certauth.enterpriseregistration.windows.net
TCP 80, 443OutboundIdentity supporting services and CDNs (endpoint set 59, required).Microsoft Learn: Network endpoints for Microsoft Intune
Windows Push Notification Services
Managed Windows devices
  • *.notify.windows.com
  • *.wns.windows.com
  • sinwns1011421.wns.windows.com
  • sin.notify.windows.com
TCP 443OutboundPush notifications for Intune device actions and immediate check-ins (endpoint set 171).

Microsoft says WNS may not work through proxies; a direct connection is recommended. Allow by FQDN rather than IP range.

Microsoft Learn: Network endpoints for Microsoft Intune
Windows Push Notification Services
Windows devices receiving notifications
  • *.wns.windows.com
  • login.microsoftonline.com
  • login.live.com
TCP 443OutboundWNS client endpoints (ClientDNS) and the identity service hosts WNS lists.Microsoft Learn: Allowing Windows Notification traffic through enterprise firewalls
Delivery Optimization
Windows devices
  • *.do.dsp.mp.microsoft.com
  • *.dl.delivery.mp.microsoft.com
TCP 80, 443OutboundDelivery Optimization cloud service and metadata (endpoint set 172).

Proxies must allow byte-range requests.

Microsoft Learn: Network endpoints for Microsoft Intune
Delivery Optimization
Windows devices (peers on your network)
Any (port-based)TCP 7680Inbound and outboundPeer-to-peer content sharing between devices.

Only needed when peering is used. The service stops listening on 7680 when it's idle.

Microsoft Learn: Configure Delivery Optimization (ports)
Delivery Optimization
Windows devices
Any (port-based)UDP 3544Inbound and outboundTeredo NAT traversal to reach peers across NATs. Required for download mode Group (2) or Internet (3).Microsoft Learn: Configure Delivery Optimization (ports)
Windows Autopilot
Devices running Autopilot
  • *.windowsupdate.com
  • *.dl.delivery.mp.microsoft.com
  • *.prod.do.dsp.mp.microsoft.com
  • *.delivery.mp.microsoft.com
  • *.update.microsoft.com
  • tsfe.trafficshaping.dsp.mp.microsoft.com
  • adl.windows.com
TCP 80, 443OutboundWindows Update during Autopilot (endpoint set 164).Microsoft Learn: Network endpoints for Microsoft Intune
Windows Autopilot
Devices running Autopilot
  • time.windows.com
UDP 123OutboundNTP time sync (endpoint set 165).Microsoft Learn: Network endpoints for Microsoft Intune
Windows Autopilot
Devices running Autopilot
  • clientconfig.passport.net
  • windowsphone.com
  • *.s-microsoft.com
  • c.s-microsoft.com
TCP 443OutboundWNS dependencies for Autopilot (endpoint set 169).Microsoft Learn: Network endpoints for Microsoft Intune
Windows Autopilot
Devices running Autopilot
  • ekop.intel.com
  • ekcert.spserv.microsoft.com
  • ftpm.amd.com
TCP 443OutboundThird-party deployment dependencies, including TPM attestation (endpoint set 173).Microsoft Learn: Network endpoints for Microsoft Intune
Apple Push Notification service
Apple devices on all client networks
  • 17.0.0.0/8
TCP 5223, 443OutboundDevices' persistent connection to APNs, which Apple MDM push notifications depend on. Microsoft lists 5223 and 443 to Apple's 17.0.0.0/8 block from all client networks, including redirects.

Apple's archived TN2265 describes 443 as the fallback when a device can't reach APNs on 5223. Apple's current network articles on support.apple.com couldn't be retrieved for this dataset; check them before changing production rules.

Microsoft Learn: Manually configure Jamf Pro integration with Intune (network ports)Apple Developer (archived): TN2265 Troubleshooting Push Notifications
Apple Push Notification service
Push provider servers (an on-premises MDM or app server; not needed on devices)
  • api.push.apple.com
  • api.sandbox.push.apple.com
TCP 443, 2197OutboundHTTP/2 provider API. Port 2197 can replace 443 so you can allow APNs without allowing all HTTPS.

Devices don't connect to these hosts; servers that send notifications do. Intune is cloud-only and needs no on-premises servers, so an Intune-only estate doesn't need this row.

Apple Developer: Sending notification requests to APNs
Microsoft Entra Connect
Microsoft Entra Connect server
Any (port-based)TCP 443OutboundSynchronise with Microsoft Entra ID.Microsoft Learn: Hybrid identity required ports and protocols
Microsoft Entra Connect
Microsoft Entra Connect server
Any (port-based)TCP 80OutboundDownload certificate revocation lists to verify TLS certificates.Microsoft Learn: Hybrid identity required ports and protocols
Microsoft Entra Connect
Microsoft Entra Connect server to domain controllers
Any (port-based)TCP 53, 88, 135, 389, 445, 636, 3268OutboundDNS, Kerberos, MS-RPC, LDAP, SMB (Seamless SSO and password writeback), LDAP over TLS, and Global Catalog (Seamless SSO).

Initial configuration and password synchronisation also use random high RPC ports 49152-65535.

Microsoft Learn: Hybrid identity required ports and protocols
Microsoft Entra Connect
Microsoft Entra Connect server to domain controllers
Any (port-based)UDP 53, 88, 389OutboundDNS, Kerberos and LDAP over UDP.Microsoft Learn: Hybrid identity required ports and protocols
Microsoft Entra Connect
Server running the Microsoft Entra Connect Health agent
Any (port-based)TCP 443OutboundSend health data to Microsoft Entra ID. The latest agent versions only need 443.

Older agents prefer TCP 5671 (Azure Service Bus) and fall back to 443.

Microsoft Learn: Hybrid identity required ports and protocols

All curated port pages

Purpose and audience

Who this Lab is for

Designed for

  • Systems Engineers
  • SREs and DevOps Engineers
  • Network and IT Administrators

Use it when

  • Reviewing firewall rules or load-balancer exposure
  • Triaging an unfamiliar listening port
  • Planning infrastructure dependencies and network policy
How to use it

A complete run, step by step

1

Search by number or name

Enter a port, service, protocol, alias, or common technology name such as 443, HTTPS, Kerberos, WinRM, LDAP, or Kubernetes.

2

Review every matching entry

Multi-port technologies return all curated records so firewall and dependency decisions are not reduced to one port.

3

Check transport and direction

Confirm whether each entry uses TCP, UDP, or both and review its usual traffic direction before changing policy.

4

Validate the operational context

Use the security notes and official reference links as inputs to a change review, then verify against the deployed product configuration.

Input guide

What you will need

Prepare the following information before starting. Use measured evidence where possible; defaults are examples and should not be treated as recommendations.

Results and methodology

What the result tells you

Your report includes

  • TCP, UDP, SCTP and DCCP transport identification where listed
  • All relevant entries for multi-port services
  • Operational notes for common infrastructure
  • Complete port and range coverage from the pinned reference snapshot
  • Endpoint management network requirements, filterable by vendor and technology, copyable as CSV or New-NetFirewallRule commands

Notes on how this lab calculates its results

The lookup performs client-side matching against a version-controlled dataset. Curated 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. Endpoint management rows come from Microsoft Learn and Apple Developer pages, each linked from its row with the date it was checked; Apple's support.apple.com articles could not be retrieved, so Apple device rows cite Microsoft's Intune documentation and Apple's developer documentation. No AI model or external lookup API is involved at runtime.

Deterministic calculation · high confidence · v2026.08.2

Search results are deterministic matches against a curated core plus a generated, version-controlled coverage snapshot with explicit transport fields. Endpoint management rows each cite the Microsoft or Apple page they came from.

Model assumptions

  • • Port assignments describe common defaults rather than proof of a live service.
  • • Endpoint management rows reflect the vendor pages on the date they were checked; vendors change these lists, so recheck the linked page before a production change.
  • • The exhaustive coverage layer is pinned to a specific public-list revision rather than claiming to mirror the continuously updated IANA registry.
  • • Reference-only entries identify documented conventions and require confirmation against current vendor documentation.
  • • Product-specific overrides and network topology must be checked before changing firewall policy.
Worked example

Reviewing HTTPS exposure

Situation

An engineer searches for port 443 while validating a web-facing load balancer rule.

Result

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.

Important limitations

Use the result with engineering judgement

  • The exhaustive checklist is a pinned snapshot and is not a substitute for the continuously updated IANA registry.
  • Applications can be configured to listen on non-standard ports.
  • A known port does not prove which process or protocol is actually using a live socket.
  • Reference-only records require confirmation against current vendor documentation before firewall changes.
Frequently asked questions

Questions before you begin

Is this the complete IANA port registry?

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.

Why can one service return several ports?

Technologies such as Kerberos, Active Directory, DNS, DHCP, SMB, and Kubernetes use multiple transports or endpoints. The lookup keeps those records distinct.

Does finding a port confirm the service running on a host?

No. Port numbers are conventions. Confirm the owning process, configuration, traffic, and application protocol on the system itself.

Ready to run Port Lookup?

Open the interactive utility without an account. Inputs and results are not saved.

Open tool
The KBY Brief

Get practical engineering references

A short email about twice a week with new runbooks, configuration traps and fixes from KBY Technologies.