| Vendor | 29 |Category | 30 |Hosts | 31 |Ports | 32 |Protocol | 33 |OS | 34 |Description | 35 |Connections Initiated | 36 |Supports proxies | 37 |Must be exempt from SSL/HTTPS Inspection? | 38 |Documentation Link | 39 |Additional Info | 40 |
| Apple | 43 |Additional content | 44 |audiocontentdownload.apple.com | 45 |80, 443 | 46 |TCP | 47 |iOS, iPadOS, macOS | 48 |GarageBand downloadable content | 49 |Apple Endpoint <-> Device | 50 |— | 51 |Yes | 52 |https://support.apple.com/en-bh/HT210060 | 53 |54 | |
| Apple | 57 |Additional content | 58 |playgrounds-assets-cdn.apple.com | 59 |443 | 60 |TCP | 61 |iPadOS, macOS | 62 |Swift Playgrounds | 63 |Apple Endpoint <-> Device | 64 |— | 65 |Yes | 66 |https://support.apple.com/en-bh/HT210060 | 67 |68 | |
| Apple | 71 |Additional content | 72 |playgrounds-cdn.apple.com | 73 |443 | 74 |TCP | 75 |iPadOS, macOS | 76 |Swift Playgrounds | 77 |Apple Endpoint <-> Device | 78 |— | 79 |Yes | 80 |https://support.apple.com/en-bh/HT210060 | 81 |82 | |
| Apple | 85 |Additional content | 86 |devimages-cdn.apple.com | 87 |80, 443 | 88 |TCP | 89 |macOS only | 90 |Xcode downloadable components | 91 |Apple Endpoint <-> Device | 92 |— | 93 |Yes | 94 |https://support.apple.com/en-bh/HT210060 | 95 |96 | |
| Apple | 99 |Additional content | 100 |download.developer.apple.com | 101 |80, 443 | 102 |TCP | 103 |macOS only | 104 |Xcode downloadable components | 105 |Apple Endpoint <-> Device | 106 |— | 107 |Yes | 108 |https://support.apple.com/en-bh/HT210060 | 109 |110 | |
| Apple | 113 |Additional content | 114 |sylvan.apple.com | 115 |80, 443 | 116 |TCP | 117 |tvOS only | 118 |Apple TV screen savers | 119 |Apple Endpoint <-> Device | 120 |— | 121 |Yes | 122 |https://support.apple.com/en-bh/HT210060 | 123 |124 | |
| Apple | 127 |App features | 128 |*.appattest.apple.com | 129 |443 | 130 |TCP | 131 |iOS, iPadOS, macOS | 132 |App validation, Touch ID and Face ID authentication for websites | 133 |Apple Endpoint <-> Device | 134 |— | 135 |Yes | 136 |https://support.apple.com/en-bh/HT210060 | 137 |138 | |
| Apple | 141 |App features | 142 |api.apple-cloudkit.com | 143 |443 | 144 |TCP | 145 |macOS only | 146 |App notarization | 147 |Apple Endpoint <-> Device | 148 |— | 149 |Yes | 150 |https://support.apple.com/en-bh/HT210060 | 151 |152 | |
| Apple | 155 |App Store | 156 |.itunes.apple.com | 157 |443, 80 | 158 |TCP | 159 |iOS, iPadOS, tvOS, macOS | 160 |Store content such as apps, books, and music | 161 |Apple Endpoint <-> Device | 162 |Yes | 163 |Yes | 164 |https://support.apple.com/en-bh/HT210060 | 165 |166 | |
| Apple | 169 |App Store | 170 |*.apps.apple.com | 171 |443 | 172 |TCP | 173 |iOS, iPadOS, tvOS, macOS | 174 |Store content such as apps, books, and music | 175 |Apple Endpoint <-> Device | 176 |Yes | 177 |Yes | 178 |https://support.apple.com/en-bh/HT210060 | 179 |180 | |
| Apple | 183 |App Store | 184 |*.mzstatic.com | 185 |443 | 186 |TCP | 187 |iOS, iPadOS, tvOS, macOS | 188 |Store content such as apps, books, and music | 189 |Apple Endpoint <-> Device | 190 |— | 191 |Yes | 192 |https://support.apple.com/en-bh/HT210060 | 193 |194 | |
| Apple | 197 |App Store | 198 |itunes.apple.com | 199 |443, 80 | 200 |TCP | 201 |iOS, iPadOS, tvOS, macOS | 202 |— | 203 |Apple Endpoint <-> Device | 204 |Yes | 205 |Yes | 206 |https://support.apple.com/en-bh/HT210060 | 207 |208 | |
| Apple | 211 |App Store | 212 |ppq.apple.com | 213 |443 | 214 |TCP | 215 |iOS, iPadOS, tvOS, macOS | 216 |Enterprise App validation | 217 |Apple Endpoint <-> Device | 218 |— | 219 |Yes | 220 |https://support.apple.com/en-bh/HT210060 | 221 |222 | |
| Apple | 225 |Apple Business Essentials device management | 226 |*.apple-mapkit.com | 227 |443 | 228 |TCP | 229 |iOS, iPadOS | 230 |View the location of devices in Managed Lost Mode | 231 |Apple Endpoint <-> Device | 232 |— | 233 |Yes | 234 |https://support.apple.com/en-bh/HT210060 | 235 |236 | |
| Apple | 239 |Apple Business Essentials device management | 240 |axm-app.apple.com | 241 |443 | 242 |TCP | 243 |iOS, iPadOS, macOS | 244 |View and manage apps and devices | 245 |Apple Endpoint <-> Device | 246 |— | 247 |Yes | 248 |https://support.apple.com/en-bh/HT210060 | 249 |250 | |
| Apple | 253 |Apple Business Essentials device management | 254 |axm-adm-enroll.apple.com | 255 |443 | 256 |TCP | 257 |iOS, iPadOS, tvOS, macOS | 258 |DEP enrollment server | 259 |Apple Endpoint <-> Device | 260 |— | 261 |Yes | 262 |https://support.apple.com/en-bh/HT210060 | 263 |264 | |
| Apple | 267 |Apple Business Essentials device management | 268 |axm-adm-mdm.apple.com | 269 |443 | 270 |TCP | 271 |iOS, iPadOS, tvOS, macOS | 272 |MDM server | 273 |Apple Endpoint <-> Device | 274 |— | 275 |Yes | 276 |https://support.apple.com/en-bh/HT210060 | 277 |278 | |
| Apple | 281 |Apple Business Essentials device management | 282 |axm-adm-scep.apple.com | 283 |443 | 284 |TCP | 285 |iOS, iPadOS, tvOS, macOS | 286 |SCEP server | 287 |Apple Endpoint <-> Device | 288 |— | 289 |Yes | 290 |https://support.apple.com/en-bh/HT210060 | 291 |292 | |
| Apple | 295 |Apple Business Essentials device management | 296 |icons.axm-usercontent-apple.com | 297 |443 | 298 |TCP | 299 |macOS only | 300 |Custom Package icons | 301 |Apple Endpoint <-> Device | 302 |— | 303 |Yes | 304 |https://support.apple.com/en-bh/HT210060 | 305 |306 | |
| Apple | 309 |Apple Business Manager and Apple School Manager | 310 |upload.appleschoolcontent.com | 311 |22 | 312 |SSH | 313 |- | 314 |SFTP uploads | 315 |Apple Endpoint <-> Device | 316 |Yes | 317 |Yes | 318 |https://support.apple.com/en-bh/HT210060 | 319 |320 | |
| Apple | 323 |Apple Business Manager and Apple School Manager | 324 |*.business.apple.com | 325 |443, 80 | 326 |TCP | 327 |- | 328 |Apple Business Manager | 329 |Apple Endpoint <-> Device | 330 |— | 331 |Yes | 332 |https://support.apple.com/en-bh/HT210060 | 333 |334 | |
| Apple | 337 |Apple Business Manager and Apple School Manager | 338 |*.itunes.apple.com | 339 |443, 80 | 340 |TCP | 341 |- | 342 |Apps and Books | 343 |Apple Endpoint <-> Device | 344 |Yes | 345 |Yes | 346 |https://support.apple.com/en-bh/HT210060 | 347 |348 | |
| Apple | 351 |Apple Business Manager and Apple School Manager | 352 |*.mzstatic.com | 353 |443 | 354 |TCP | 355 |- | 356 |Apps and Books | 357 |Apple Endpoint <-> Device | 358 |— | 359 |Yes | 360 |https://support.apple.com/en-bh/HT210060 | 361 |362 | |
| Apple | 365 |Apple Business Manager and Apple School Manager | 366 |*.school.apple.com | 367 |443, 80 | 368 |TCP | 369 |- | 370 |Apple School Manager | 371 |Apple Endpoint <-> Device | 372 |— | 373 |Yes | 374 |https://support.apple.com/en-bh/HT210060 | 375 |376 | |
| Apple | 379 |Apple Business Manager and Apple School Manager | 380 |*.vertexsmb.com | 381 |443 | 382 |TCP | 383 |- | 384 |Validating tax-exempt status | 385 |Apple Endpoint <-> Device | 386 |— | 387 |Yes | 388 |https://support.apple.com/en-bh/HT210060 | 389 |390 | |
| Apple | 393 |Apple Business Manager and Apple School Manager | 394 |api.edu.apple.com | 395 |443 | 396 |TCP | 397 |- | 398 |Apps and Books (ASM) | 399 |Apple Endpoint <-> Device | 400 |— | 401 |Yes | 402 |https://support.apple.com/en-bh/HT210060 | 403 |404 | |
| Apple | 407 |Apple Business Manager and Apple School Manager | 408 |api.ent.apple.com | 409 |443 | 410 |TCP | 411 |- | 412 |Apps and Books (ABM) | 413 |Apple Endpoint <-> Device | 414 |— | 415 |Yes | 416 |https://support.apple.com/en-bh/HT210060 | 417 |418 | |
| Apple | 421 |Apple Business Manager and Apple School Manager | 422 |appleid.cdn-apple.com | 423 |443 | 424 |TCP | 425 |- | 426 |Login authentication | 427 |Apple Endpoint <-> Device | 428 |Yes | 429 |Yes | 430 |https://support.apple.com/en-bh/HT210060 | 431 |432 | |
| Apple | 435 |Apple Business Manager and Apple School Manager | 436 |idmsa.apple.com | 437 |443 | 438 |TCP | 439 |- | 440 |Login authentication | 441 |Apple Endpoint <-> Device | 442 |Yes | 443 |Yes | 444 |https://support.apple.com/en-bh/HT210060 | 445 |446 | |
| Apple | 449 |Apple Business Manager and Apple School Manager | 450 |statici.icloud.com | 451 |443 | 452 |TCP | 453 |- | 454 |Device icons | 455 |Apple Endpoint <-> Device | 456 |— | 457 |Yes | 458 |https://support.apple.com/en-bh/HT210060 | 459 |460 | |
| Apple | 463 |Apple Business Manager and Apple School Manager | 464 |www.apple.com | 465 |443 | 466 |TCP | 467 |- | 468 |Fonts for certain languages | 469 |Apple Endpoint <-> Device | 470 |— | 471 |Yes | 472 |https://support.apple.com/en-bh/HT210060 | 473 |474 | |
| Apple | 477 |Apple Business Manager and Apple School Manager - Managed Apple Apple IDs | 478 |ws-ee-maidsvc.icloud.com | 479 |443, 80 | 480 |TCP | 481 |iOS, iPadOS, macOS | 482 |User lookup service | 483 |Apple Endpoint <-> Device | 484 |— | 485 |Yes | 486 |https://support.apple.com/en-bh/HT210060 | 487 |488 | |
| Apple | 491 |Apple diagnostics | 492 |diagassets.apple.com | 493 |443 | 494 |TCP | 495 |iOS, iPadOS, tvOS, macOS | 496 |Used by Apple devices to help detect possible hardware issues | 497 |Apple Endpoint <-> Device | 498 |Yes | 499 |Yes | 500 |https://support.apple.com/en-bh/HT210060 | 501 |502 | |
| Apple | 505 |Apple ID | 506 |appleid.apple.com | 507 |443 | 508 |TCP | 509 |iOS, iPadOS, tvOS, macOS | 510 |Apple ID authentication in Settings and System Preferences | 511 |Apple Endpoint <-> Device | 512 |Yes | 513 |Yes | 514 |https://support.apple.com/en-bh/HT210060 | 515 |516 | |
| Apple | 519 |Apple ID | 520 |appleid.cdn-apple.com | 521 |443 | 522 |TCP | 523 |iOS, iPadOS, tvOS, macOS | 524 |Apple ID authentication in Settings and System Preferences | 525 |Apple Endpoint <-> Device | 526 |Yes | 527 |Yes | 528 |https://support.apple.com/en-bh/HT210060 | 529 |530 | |
| Apple | 533 |Apple ID | 534 |gsa.apple.com | 535 |443 | 536 |TCP | 537 |iOS, iPadOS, tvOS, macOS | 538 |Apple ID authentication | 539 |Apple Endpoint <-> Device | 540 |Yes | 541 |Yes | 542 |https://support.apple.com/en-bh/HT210060 | 543 |544 | |
| Apple | 547 |Apple ID | 548 |idmsa.apple.com | 549 |443 | 550 |TCP | 551 |iOS, iPadOS, tvOS, macOS | 552 |Apple ID authentication | 553 |Apple Endpoint <-> Device | 554 |Yes | 555 |Yes | 556 |https://support.apple.com/en-bh/HT210060 | 557 |558 | |
| Apple | 561 |Associated Domains | 562 |app-site-association.cdn-apple.com | 563 |443 | 564 |TCP, UDP | 565 |iOS, iPadOS, macOS | 566 |Associated domains for universal links | 567 |Apple Endpoint <-> Device | 568 |— | 569 |Yes | 570 |https://support.apple.com/en-bh/HT210060 | 571 |572 | |
| Apple | 575 |Associated Domains | 576 |app-site-association.networking.apple | 577 |443 | 578 |TCP, UDP | 579 |iOS, iPadOS, macOS | 580 |Associated domains for universal links | 581 |Apple Endpoint <-> Device | 582 |— | 583 |Yes | 584 |https://support.apple.com/en-bh/HT210060 | 585 |586 | |
| Apple | 589 |Beta updates | 590 |cssubmissions.apple.com | 591 |443 | 592 |TCP | 593 |iOS, iPadOS, tvOS, macOS | 594 |Used by Feedback Assistant to upload files | 595 |Apple Endpoint <-> Device | 596 |Yes | 597 |Yes | 598 |https://support.apple.com/en-bh/HT210060 | 599 |600 | |
| Apple | 603 |Beta updates | 604 |fba.apple.com | 605 |443 | 606 |TCP | 607 |iOS, iPadOS, tvOS, macOS | 608 |Used by Feedback Assistant to file and view feedback | 609 |Apple Endpoint <-> Device | 610 |Yes | 611 |Yes | 612 |https://support.apple.com/en-bh/HT210060 | 613 |614 | |
| Apple | 617 |Beta updates | 618 |bpapi.apple.com | 619 |443 | 620 |TCP | 621 |iOS, iPadOS, tvOS, watchOS, macOS | 622 |Beta update enrollment | 623 |Apple Endpoint <-> Device | 624 |Yes | 625 |Yes | 626 |https://support.apple.com/en-bh/HT210060 | 627 |628 | |
| Apple | 631 |Carrier updates | 632 |appldnld.apple.com | 633 |80 | 634 |TCP | 635 |iOS, iPadOS | 636 |Cellular carrier bundle updates | 637 |Apple Endpoint <-> Device | 638 |— | 639 |Yes | 640 |https://support.apple.com/en-bh/HT210060 | 641 |642 | |
| Apple | 645 |Carrier updates | 646 |appldnld.apple.com.edgesuite.net | 647 |80 | 648 |TCP | 649 |iOS, iPadOS | 650 |Cellular carrier bundle updates | 651 |Apple Endpoint <-> Device | 652 |— | 653 |Yes | 654 |https://support.apple.com/en-bh/HT210060 | 655 |656 | |
| Apple | 659 |Carrier updates | 660 |itunes.apple.com | 661 |443 | 662 |TCP | 663 |iOS, iPadOS | 664 |Carrier bundle update discovery | 665 |Apple Endpoint <-> Device | 666 |— | 667 |Yes | 668 |https://support.apple.com/en-bh/HT210060 | 669 |670 | |
| Apple | 673 |Carrier updates | 674 |itunes.com | 675 |80 | 676 |TCP | 677 |iOS, iPadOS | 678 |Carrier bundle update discovery | 679 |Apple Endpoint <-> Device | 680 |— | 681 |Yes | 682 |https://support.apple.com/en-bh/HT210060 | 683 |684 | |
| Apple | 687 |Carrier updates | 688 |updates-http.cdn-apple.com | 689 |80 | 690 |TCP | 691 |iOS, iPadOS | 692 |Cellular carrier bundle updates | 693 |Apple Endpoint <-> Device | 694 |— | 695 |Yes | 696 |https://support.apple.com/en-bh/HT210060 | 697 |698 | |
| Apple | 701 |Carrier updates | 702 |updates.cdn-apple.com | 703 |443 | 704 |TCP | 705 |iOS, iPadOS | 706 |Cellular carrier bundle updates | 707 |Apple Endpoint <-> Device | 708 |— | 709 |Yes | 710 |https://support.apple.com/en-bh/HT210060 | 711 |712 | |
| Apple | 715 |Certificate validation | 716 |certs.apple.com | 717 |80, 443 | 718 |TCP | 719 |iOS, iPadOS, tvOS, macOS | 720 |Certificate validation | 721 |Apple Endpoint <-> Device | 722 |— | 723 |Yes | 724 |https://support.apple.com/en-bh/HT210060 | 725 |726 | |
| Apple | 729 |Certificate validation | 730 |crl.apple.com | 731 |80 | 732 |TCP | 733 |iOS, iPadOS, tvOS, macOS | 734 |Certificate validation | 735 |Apple Endpoint <-> Device | 736 |— | 737 |Yes | 738 |https://support.apple.com/en-bh/HT210060 | 739 |740 | |
| Apple | 743 |Certificate validation | 744 |crl.entrust.net | 745 |80 | 746 |TCP | 747 |iOS, iPadOS, tvOS, macOS | 748 |Certificate validation | 749 |Apple Endpoint <-> Device | 750 |— | 751 |Yes | 752 |https://support.apple.com/en-bh/HT210060 | 753 |754 | |
| Apple | 757 |Certificate validation | 758 |crl3.digicert.com | 759 |80 | 760 |TCP | 761 |iOS, iPadOS, tvOS, macOS | 762 |Certificate validation | 763 |Apple Endpoint <-> Device | 764 |— | 765 |Yes | 766 |https://support.apple.com/en-bh/HT210060 | 767 |768 | |
| Apple | 771 |Certificate validation | 772 |crl4.digicert.com | 773 |80 | 774 |TCP | 775 |iOS, iPadOS, tvOS, macOS | 776 |Certificate validation | 777 |Apple Endpoint <-> Device | 778 |— | 779 |Yes | 780 |https://support.apple.com/en-bh/HT210060 | 781 |782 | |
| Apple | 785 |Certificate validation | 786 |ocsp.apple.com | 787 |80 | 788 |TCP | 789 |iOS, iPadOS, tvOS, macOS | 790 |Certificate validation | 791 |Apple Endpoint <-> Device | 792 |— | 793 |Yes | 794 |https://support.apple.com/en-bh/HT210060 | 795 |796 | |
| Apple | 799 |Certificate validation | 800 |ocsp.digicert.cn | 801 |80 | 802 |TCP | 803 |iOS, iPadOS, tvOS, macOS | 804 |Certificate validation in China | 805 |Apple Endpoint <-> Device | 806 |— | 807 |Yes | 808 |https://support.apple.com/en-bh/HT210060 | 809 |810 | |
| Apple | 813 |Certificate validation | 814 |ocsp.digicert.com | 815 |80 | 816 |TCP | 817 |iOS, iPadOS, tvOS, macOS | 818 |Certificate validation | 819 |Apple Endpoint <-> Device | 820 |— | 821 |Yes | 822 |https://support.apple.com/en-bh/HT210060 | 823 |824 | |
| Apple | 827 |Certificate validation | 828 |ocsp.entrust.net | 829 |80 | 830 |TCP | 831 |iOS, iPadOS, tvOS, macOS | 832 |Certificate validation | 833 |Apple Endpoint <-> Device | 834 |— | 835 |Yes | 836 |https://support.apple.com/en-bh/HT210060 | 837 |838 | |
| Apple | 841 |Certificate validation | 842 |ocsp2.apple.com | 843 |443 | 844 |TCP | 845 |iOS, iPadOS, tvOS, macOS | 846 |Certificate validation | 847 |Apple Endpoint <-> Device | 848 |— | 849 |Yes | 850 |https://support.apple.com/en-bh/HT210060 | 851 |852 | |
| Apple | 855 |Certificate validation | 856 |valid.apple.com | 857 |443 | 858 |TCP | 859 |iOS, iPadOS, tvOS, macOS | 860 |Certificate validation | 861 |Apple Endpoint <-> Device | 862 |Yes | 863 |Yes | 864 |https://support.apple.com/en-bh/HT210060 | 865 |866 | |
| Apple | 869 |Classroom and Schoolwork | 870 |cls-ingest.itunes.apple.com | 871 |443 | 872 |TCP | 873 |iPadOS only | 874 |Schoolwork handout service | 875 |Apple Endpoint <-> Device | 876 |— | 877 |Yes | 878 |https://support.apple.com/en-bh/HT210060 | 879 |880 | |
| Apple | 883 |Classroom and Schoolwork | 884 |cls-iosclient.itunes.apple.com | 885 |443 | 886 |TCP | 887 |iPadOS only | 888 |Schoolwork handout service | 889 |Apple Endpoint <-> Device | 890 |— | 891 |Yes | 892 |https://support.apple.com/en-bh/HT210060 | 893 |894 | |
| Apple | 897 |Classroom and Schoolwork | 898 |pg-bootstrap.itunes.apple.com | 899 |443 | 900 |TCP | 901 |iPadOS only | 902 |Schoolwork handout service | 903 |Apple Endpoint <-> Device | 904 |— | 905 |Yes | 906 |https://support.apple.com/en-bh/HT210060 | 907 |908 | |
| Apple | 911 |Classroom and Schoolwork | 912 |play.itunes.apple.com | 913 |443 | 914 |TCP | 915 |iPadOS, macOS | 916 |Classroom and Schoolwork device verification | 917 |Apple Endpoint <-> Device | 918 |— | 919 |Yes | 920 |https://support.apple.com/en-bh/HT210060 | 921 |922 | |
| Apple | 925 |Classroom and Schoolwork | 926 |s.mzstatic.com | 927 |443 | 928 |TCP | 929 |iPadOS, macOS | 930 |Classroom and Schoolwork device verification | 931 |Apple Endpoint <-> Device | 932 |— | 933 |Yes | 934 |https://support.apple.com/en-bh/HT210060 | 935 |936 | |
| Apple | 939 |Classroom and Schoolwork | 940 |ws-ee-maidsvc.icloud.com | 941 |443 | 942 |TCP | 943 |iPadOS, macOS | 944 |Classroom and Schoolwork class roster service | 945 |Apple Endpoint <-> Device | 946 |— | 947 |Yes | 948 |https://support.apple.com/en-bh/HT210060 | 949 |950 | |
| Apple | 953 |Classroom and Schoolwork | 954 |ws.school.apple.com | 955 |443 | 956 |TCP | 957 |iPadOS, macOS | 958 |Classroom and Schoolwork class roster service | 959 |Apple Endpoint <-> Device | 960 |— | 961 |Yes | 962 |https://support.apple.com/en-bh/HT210060 | 963 |964 | |
| Apple | 967 |Content caching - Client | 968 |lcdn-locator.apple.com | 969 |443 | 970 |TCP | 971 |iOS, iPadOS, tvOS, macOS | 972 |Content caching locator service | 973 |Apple Endpoint <-> Device | 974 |— | 975 |Yes | 976 |https://support.apple.com/en-bh/HT210060 | 977 |978 | |
| Apple | 981 |Content caching - Client | 982 |serverstatus.apple.com | 983 |443 | 984 |TCP | 985 |macOS only | 986 |Content caching client public IP determination | 987 |Apple Endpoint <-> Device | 988 |— | 989 |Yes | 990 |https://support.apple.com/en-bh/HT210060 | 991 |992 | |
| Apple | 995 |Content caching - Server | 996 |lcdn-registration.apple.com | 997 |443 | 998 |TCP | 999 |macOS only | 1000 |Server registration | 1001 |Apple Endpoint <-> Device | 1002 |Yes | 1003 |Yes | 1004 |https://support.apple.com/en-bh/HT210060 | 1005 |1006 | |
| Apple | 1009 |Content caching - Server | 1010 |suconfig.apple.com | 1011 |80 | 1012 |TCP | 1013 |macOS only | 1014 |Configuration | 1015 |Apple Endpoint <-> Device | 1016 |— | 1017 |Yes | 1018 |https://support.apple.com/en-bh/HT210060 | 1019 |1020 | |
| Apple | 1023 |Content caching - Server | 1024 |xp-cdn.apple.com | 1025 |443 | 1026 |TCP | 1027 |macOS only | 1028 |Reporting | 1029 |Apple Endpoint <-> Device | 1030 |Yes | 1031 |Yes | 1032 |https://support.apple.com/en-bh/HT210060 | 1033 |1034 | |
| Apple | 1037 |Device management | 1038 |setup.icloud.com | 1039 |443 | 1040 |TCP | 1041 |iOS, iPadOS | 1042 |Required to log in with a Managed Apple ID on Shared iPad | 1043 |Apple Endpoint <-> Device | 1044 |— | 1045 |Yes | 1046 |https://support.apple.com/en-bh/HT210060 | 1047 |1048 | |
| Apple | 1051 |Device management | 1052 |*.push.apple.com | 1053 |443, 80, 5223, 2197 | 1054 |TCP | 1055 |iOS, iPadOS, tvOS, macOS | 1056 |Push notifications | 1057 |Apple Endpoint <-> Device | 1058 |- | 1059 |Yes | 1060 |https://support.apple.com/en-bh/HT210060 | 1061 |https://support.apple.com/en-bh/HT210060#apns | 1062 |
| Apple | 1065 |Device management | 1066 |deviceenrollment.apple.com | 1067 |443 | 1068 |TCP | 1069 |iOS, iPadOS, tvOS, macOS | 1070 |DEP provisional enrollment | 1071 |Apple Endpoint <-> Device | 1072 |— | 1073 |Yes | 1074 |https://support.apple.com/en-bh/HT210060 | 1075 |1076 | |
| Apple | 1079 |Device management | 1080 |deviceservices-external.apple.com | 1081 |443 | 1082 |TCP | 1083 |iOS, iPadOS, tvOS, macOS | 1084 |— | 1085 |Apple Endpoint <-> Device | 1086 |— | 1087 |Yes | 1088 |https://support.apple.com/en-bh/HT210060 | 1089 |1090 | |
| Apple | 1093 |Device management | 1094 |gdmf.apple.com | 1095 |443 | 1096 |TCP | 1097 |iOS, iPadOS, tvOS, macOS | 1098 |Used by an MDM server to identify which software updates are available to devices that use managed software updates | 1099 |Apple Endpoint <-> Device | 1100 |Yes | 1101 |Yes | 1102 |https://support.apple.com/en-bh/HT210060 | 1103 |1104 | |
| Apple | 1107 |Device management | 1108 |identity.apple.com | 1109 |443 | 1110 |TCP | 1111 |iOS, iPadOS, tvOS, macOS | 1112 |APNs certificate request portal | 1113 |Apple Endpoint <-> Device | 1114 |Yes | 1115 |Yes | 1116 |https://support.apple.com/en-bh/HT210060 | 1117 |1118 | |
| Apple | 1121 |Device management | 1122 |iprofiles.apple.com | 1123 |443 | 1124 |TCP | 1125 |iOS, iPadOS, tvOS, macOS | 1126 |Hosts enrollment profiles used when devices enroll in Apple School Manager or Apple Business Manager through Device Enrollment | 1127 |Apple Endpoint <-> Device | 1128 |Yes | 1129 |Yes | 1130 |https://support.apple.com/en-bh/HT210060 | 1131 |1132 | |
| Apple | 1135 |Device management | 1136 |mdmenrollment.apple.com | 1137 |443 | 1138 |TCP | 1139 |iOS, iPadOS, tvOS, macOS | 1140 |MDM servers to upload enrollment profiles used by clients enrolling through Device Enrollment in Apple School Manager or Apple Business Manager, and to look up devices and accounts | 1141 |Apple Endpoint <-> Device | 1142 |Yes | 1143 |Yes | 1144 |https://support.apple.com/en-bh/HT210060 | 1145 |1146 | |
| Apple | 1149 |Device management | 1150 |vpp.itunes.apple.com | 1151 |443 | 1152 |TCP | 1153 |iOS, iPadOS, tvOS, macOS | 1154 |MDM servers to perform operations related to Apps and Books, like assigning or revoking licenses on a device | 1155 |Apple Endpoint <-> Device | 1156 |Yes | 1157 |Yes | 1158 |https://support.apple.com/en-bh/HT210060 | 1159 |1160 | |
| Apple | 1163 |Device setup | 1164 |sq-device.apple.com | 1165 |443 | 1166 |TCP | 1167 |iOS, iPadOS | 1168 |eSIM activation | 1169 |Apple Endpoint <-> Device | 1170 |— | 1171 |Yes | 1172 |https://support.apple.com/en-bh/HT210060 | 1173 |1174 | |
| Apple | 1177 |Device setup | 1178 |time-ios.apple.com | 1179 |123 | 1180 |UDP | 1181 |iOS, iPadOS, tvOS | 1182 |Used by devices to set their date and time | 1183 |Apple Endpoint <-> Device | 1184 |— | 1185 |Yes | 1186 |https://support.apple.com/en-bh/HT210060 | 1187 |1188 | |
| Apple | 1191 |Device setup | 1192 |albert.apple.com | 1193 |443 | 1194 |TCP | 1195 |iOS, iPadOS, tvOS, macOS | 1196 |Device activation | 1197 |Apple Endpoint <-> Device | 1198 |Yes | 1199 |Yes | 1200 |https://support.apple.com/en-bh/HT210060 | 1201 |1202 | |
| Apple | 1205 |Device setup | 1206 |captive.apple.com | 1207 |443, 80 | 1208 |TCP | 1209 |iOS, iPadOS, tvOS, macOS | 1210 |Internet connectivity validation for networks that use captive portals | 1211 |Apple Endpoint <-> Device | 1212 |Yes | 1213 |Yes | 1214 |https://support.apple.com/en-bh/HT210060 | 1215 |1216 | |
| Apple | 1219 |Device setup | 1220 |gs.apple.com | 1221 |443 | 1222 |TCP | 1223 |iOS, iPadOS, tvOS, macOS | 1224 |— | 1225 |Apple Endpoint <-> Device | 1226 |Yes | 1227 |Yes | 1228 |https://support.apple.com/en-bh/HT210060 | 1229 |1230 | |
| Apple | 1233 |Device setup | 1234 |humb.apple.com | 1235 |443 | 1236 |TCP | 1237 |iOS, iPadOS, tvOS, macOS | 1238 |— | 1239 |Apple Endpoint <-> Device | 1240 |Yes | 1241 |Yes | 1242 |https://support.apple.com/en-bh/HT210060 | 1243 |1244 | |
| Apple | 1247 |Device setup | 1248 |static.ips.apple.com | 1249 |443, 80 | 1250 |TCP | 1251 |iOS, iPadOS, tvOS, macOS | 1252 |— | 1253 |Apple Endpoint <-> Device | 1254 |Yes | 1255 |Yes | 1256 |https://support.apple.com/en-bh/HT210060 | 1257 |1258 | |
| Apple | 1261 |Device setup | 1262 |tbsc.apple.com | 1263 |443 | 1264 |TCP | 1265 |iOS, iPadOS, tvOS, macOS | 1266 |— | 1267 |Apple Endpoint <-> Device | 1268 |Yes | 1269 |Yes | 1270 |https://support.apple.com/en-bh/HT210060 | 1271 |1272 | |
| Apple | 1275 |Device setup | 1276 |time.apple.com | 1277 |123 | 1278 |UDP | 1279 |iOS, iPadOS, tvOS, macOS | 1280 |Used by devices to set their date and time | 1281 |Apple Endpoint <-> Device | 1282 |— | 1283 |Yes | 1284 |https://support.apple.com/en-bh/HT210060 | 1285 |1286 | |
| Apple | 1289 |Device setup | 1290 |time-macos.apple.com | 1291 |123 | 1292 |UDP | 1293 |macOS only | 1294 |Used by devices to set their date and time | 1295 |Apple Endpoint <-> Device | 1296 |— | 1297 |Yes | 1298 |https://support.apple.com/en-bh/HT210060 | 1299 |1300 | |
| Apple | 1303 |Domain Name System resolution | 1304 |doh.dns.apple.com | 1305 |443 | 1306 |TCP | 1307 |iOS, iPadOS, tvOS, macOS | 1308 |Used for DNS over HTTPS (DoH) | 1309 |Apple Endpoint <-> Device | 1310 |Yes | 1311 |Yes | 1312 |https://support.apple.com/en-bh/HT210060 | 1313 |1314 | |
| Apple | 1317 |iCloud | 1318 |mask-api.icloud.com | 1319 |443 | 1320 |TCP | 1321 |iOS, iPadOS, macOS | 1322 |iCloud Private Relay | 1323 |Apple Endpoint <-> Device | 1324 |Yes | 1325 |Yes | 1326 |https://support.apple.com/en-bh/HT210060 | 1327 |1328 | |
| Apple | 1331 |iCloud | 1332 |mask-h2.icloud.com | 1333 |443 | 1334 |TCP | 1335 |iOS, iPadOS, macOS | 1336 |iCloud Private Relay | 1337 |Apple Endpoint <-> Device | 1338 |— | 1339 |Yes | 1340 |https://support.apple.com/en-bh/HT210060 | 1341 |1342 | |
| Apple | 1345 |iCloud | 1346 |mask.icloud.com | 1347 |443 | 1348 |UDP | 1349 |iOS, iPadOS, macOS | 1350 |iCloud Private Relay | 1351 |Apple Endpoint <-> Device | 1352 |— | 1353 |Yes | 1354 |https://support.apple.com/en-bh/HT210060 | 1355 |1356 | |
| Apple | 1359 |iCloud | 1360 |*.apple-cloudkit.com | 1361 |443 | 1362 |TCP | 1363 |iOS, iPadOS, tvOS, macOS | 1364 |iCloud services | 1365 |Apple Endpoint <-> Device | 1366 |— | 1367 |Yes | 1368 |https://support.apple.com/en-bh/HT210060 | 1369 |1370 | |
| Apple | 1373 |iCloud | 1374 |*.apple-livephotoskit.com | 1375 |443 | 1376 |TCP | 1377 |iOS, iPadOS, tvOS, macOS | 1378 |iCloud services | 1379 |Apple Endpoint <-> Device | 1380 |— | 1381 |Yes | 1382 |https://support.apple.com/en-bh/HT210060 | 1383 |1384 | |
| Apple | 1387 |iCloud | 1388 |*.apzones.com | 1389 |443 | 1390 |TCP | 1391 |iOS, iPadOS, tvOS, macOS | 1392 |iCloud services in China | 1393 |Apple Endpoint <-> Device | 1394 |— | 1395 |Yes | 1396 |https://support.apple.com/en-bh/HT210060 | 1397 |1398 | |
| Apple | 1401 |iCloud | 1402 |*.cdn-apple.com | 1403 |443 | 1404 |TCP | 1405 |iOS, iPadOS, tvOS, macOS | 1406 |iCloud services | 1407 |Apple Endpoint <-> Device | 1408 |— | 1409 |Yes | 1410 |https://support.apple.com/en-bh/HT210060 | 1411 |1412 | |
| Apple | 1415 |iCloud | 1416 |*.gc.apple.com | 1417 |443 | 1418 |TCP | 1419 |iOS, iPadOS, tvOS, macOS | 1420 |iCloud services | 1421 |Apple Endpoint <-> Device | 1422 |— | 1423 |Yes | 1424 |https://support.apple.com/en-bh/HT210060 | 1425 |1426 | |
| Apple | 1429 |iCloud | 1430 |*.icloud-content.com | 1431 |443 | 1432 |TCP | 1433 |iOS, iPadOS, tvOS, macOS | 1434 |iCloud services | 1435 |Apple Endpoint <-> Device | 1436 |— | 1437 |Yes | 1438 |https://support.apple.com/en-bh/HT210060 | 1439 |1440 | |
| Apple | 1443 |iCloud | 1444 |*.icloud.apple.com | 1445 |443 | 1446 |TCP | 1447 |iOS, iPadOS, tvOS, macOS | 1448 |iCloud services | 1449 |Apple Endpoint <-> Device | 1450 |— | 1451 |Yes | 1452 |https://support.apple.com/en-bh/HT210060 | 1453 |1454 | |
| Apple | 1457 |iCloud | 1458 |*.icloud.com | 1459 |443 | 1460 |TCP | 1461 |iOS, iPadOS, tvOS, macOS | 1462 |iCloud services | 1463 |Apple Endpoint <-> Device | 1464 |— | 1465 |Yes | 1466 |https://support.apple.com/en-bh/HT210060 | 1467 |1468 | |
| Apple | 1471 |iCloud | 1472 |*.icloud.com.cn | 1473 |443 | 1474 |TCP | 1475 |iOS, iPadOS, tvOS, macOS | 1476 |iCloud services in China | 1477 |Apple Endpoint <-> Device | 1478 |— | 1479 |Yes | 1480 |https://support.apple.com/en-bh/HT210060 | 1481 |1482 | |
| Apple | 1485 |iCloud | 1486 |*.iwork.apple.com | 1487 |443 | 1488 |TCP | 1489 |iOS, iPadOS, tvOS, macOS | 1490 |iWork documents | 1491 |Apple Endpoint <-> Device | 1492 |— | 1493 |Yes | 1494 |https://support.apple.com/en-bh/HT210060 | 1495 |1496 | |
| Apple | 1499 |Siri and search | 1500 |*.smoot.apple.com | 1501 |443 | 1502 |TCP | 1503 |iOS, iPadOS, macOS | 1504 |Search services, including Siri, Spotlight, Lookup, Safari, News, Messages and Music | 1505 |Apple Endpoint <-> Device | 1506 |— | 1507 |Yes | 1508 |https://support.apple.com/en-bh/HT210060 | 1509 |1510 | |
| Apple | 1513 |Siri and search | 1514 |guzzoni.apple.com | 1515 |443 | 1516 |TCP | 1517 |iOS, iPadOS, macOS | 1518 |Siri and dictation requests | 1519 |Apple Endpoint <-> Device | 1520 |— | 1521 |Yes | 1522 |https://support.apple.com/en-bh/HT210060 | 1523 |1524 | |
| Apple | 1527 |Software updates | 1528 |updates-http.cdn-apple.com | 1529 |80 | 1530 |TCP | 1531 |iOS, iPadOS, tvOS, macOS | 1532 |Software update downloads | 1533 |Apple Endpoint <-> Device | 1534 |— | 1535 |Yes | 1536 |https://support.apple.com/en-bh/HT210060 | 1537 |1538 | |
| Apple | 1541 |Software updates | 1542 |updates.cdn-apple.com | 1543 |443 | 1544 |TCP | 1545 |iOS, iPadOS, tvOS, macOS | 1546 |Software update downloads | 1547 |Apple Endpoint <-> Device | 1548 |— | 1549 |Yes | 1550 |https://support.apple.com/en-bh/HT210060 | 1551 |1552 | |
| Apple | 1555 |Software updates | 1556 |xp.apple.com | 1557 |443 | 1558 |TCP | 1559 |iOS, iPadOS, tvOS, macOS | 1560 |— | 1561 |Apple Endpoint <-> Device | 1562 |Yes | 1563 |Yes | 1564 |https://support.apple.com/en-bh/HT210060 | 1565 |1566 | |
| Apple | 1569 |Software updates | 1570 |gdmf.apple.com | 1571 |443 | 1572 |TCP | 1573 |iOS, iPadOS, tvOS, watchOS, macOS | 1574 |Software update catalog | 1575 |Apple Endpoint <-> Device | 1576 |— | 1577 |Yes | 1578 |https://support.apple.com/en-bh/HT210060 | 1579 |1580 | |
| Apple | 1583 |Software updates | 1584 |gg.apple.com | 1585 |443, 80 | 1586 |TCP | 1587 |iOS, iPadOS, tvOS, watchOS, macOS | 1588 |iOS, iPadOS, tvOS, watchOS, and macOS updates | 1589 |Apple Endpoint <-> Device | 1590 |Yes | 1591 |Yes | 1592 |https://support.apple.com/en-bh/HT210060 | 1593 |1594 | |
| Apple | 1597 |Software updates | 1598 |gs.apple.com | 1599 |443, 80 | 1600 |TCP | 1601 |iOS, iPadOS, tvOS, watchOS, macOS | 1602 |iOS, iPadOS, tvOS, watchOS, and macOS updates | 1603 |Apple Endpoint <-> Device | 1604 |Yes | 1605 |Yes | 1606 |https://support.apple.com/en-bh/HT210060 | 1607 |1608 | |
| Apple | 1611 |Software updates | 1612 |mesu.apple.com | 1613 |443, 80 | 1614 |TCP | 1615 |iOS, iPadOS, tvOS, watchOS, macOS | 1616 |Hosts software update catalogs | 1617 |Apple Endpoint <-> Device | 1618 |— | 1619 |Yes | 1620 |https://support.apple.com/en-bh/HT210060 | 1621 |1622 | |
| Apple | 1625 |Software updates | 1626 |appldnld.apple.com | 1627 |80 | 1628 |TCP | 1629 |iOS, iPadOS, watchOS | 1630 |iOS, iPadOS, and watchOS updates | 1631 |Apple Endpoint <-> Device | 1632 |— | 1633 |Yes | 1634 |https://support.apple.com/en-bh/HT210060 | 1635 |1636 | |
| Apple | 1639 |Software updates | 1640 |ns.itunes.apple.com | 1641 |443 | 1642 |TCP | 1643 |iOS, iPadOS, watchOS | 1644 |— | 1645 |Apple Endpoint <-> Device | 1646 |Yes | 1647 |Yes | 1648 |https://support.apple.com/en-bh/HT210060 | 1649 |1650 | |
| Apple | 1653 |Software updates | 1654 |configuration.apple.com | 1655 |443 | 1656 |TCP | 1657 |macOS only | 1658 |Rosetta 2 updates | 1659 |Apple Endpoint <-> Device | 1660 |— | 1661 |Yes | 1662 |https://support.apple.com/en-bh/HT210060 | 1663 |1664 | |
| Apple | 1667 |Software updates | 1668 |ig.apple.com | 1669 |443 | 1670 |TCP | 1671 |macOS only | 1672 |macOS updates | 1673 |Apple Endpoint <-> Device | 1674 |Yes | 1675 |Yes | 1676 |https://support.apple.com/en-bh/HT210060 | 1677 |1678 | |
| Apple | 1681 |Software updates | 1682 |oscdn.apple.com | 1683 |443, 80 | 1684 |TCP | 1685 |macOS only | 1686 |macOS Recovery | 1687 |Apple Endpoint <-> Device | 1688 |— | 1689 |Yes | 1690 |https://support.apple.com/en-bh/HT210060 | 1691 |1692 | |
| Apple | 1695 |Software updates | 1696 |osrecovery.apple.com | 1697 |443, 80 | 1698 |TCP | 1699 |macOS only | 1700 |macOS Recovery | 1701 |Apple Endpoint <-> Device | 1702 |— | 1703 |Yes | 1704 |https://support.apple.com/en-bh/HT210060 | 1705 |1706 | |
| Apple | 1709 |Software updates | 1710 |skl.apple.com | 1711 |443 | 1712 |TCP | 1713 |macOS only | 1714 |macOS updates | 1715 |Apple Endpoint <-> Device | 1716 |— | 1717 |Yes | 1718 |https://support.apple.com/en-bh/HT210060 | 1719 |1720 | |
| Apple | 1723 |Software updates | 1724 |swcdn.apple.com | 1725 |443, 80 | 1726 |TCP | 1727 |macOS only | 1728 |macOS updates | 1729 |Apple Endpoint <-> Device | 1730 |— | 1731 |Yes | 1732 |https://support.apple.com/en-bh/HT210060 | 1733 |1734 | |
| Apple | 1737 |Software updates | 1738 |swdist.apple.com | 1739 |443 | 1740 |TCP | 1741 |macOS only | 1742 |macOS updates | 1743 |Apple Endpoint <-> Device | 1744 |— | 1745 |Yes | 1746 |https://support.apple.com/en-bh/HT210060 | 1747 |1748 | |
| Apple | 1751 |Software updates | 1752 |swdownload.apple.com | 1753 |443, 80 | 1754 |TCP | 1755 |macOS only | 1756 |macOS updates | 1757 |Apple Endpoint <-> Device | 1758 |Yes | 1759 |Yes | 1760 |https://support.apple.com/en-bh/HT210060 | 1761 |1762 | |
| Apple | 1765 |Software updates | 1766 |swscan.apple.com | 1767 |443 | 1768 |TCP | 1769 |macOS only | 1770 |macOS updates | 1771 |Apple Endpoint <-> Device | 1772 |— | 1773 |Yes | 1774 |https://support.apple.com/en-bh/HT210060 | 1775 |1776 | |
| Apple | 1779 |Tap to Pay on iPhone | 1780 |humb.apple.com | 1781 |443 | 1782 |TCP | 1783 |iOS only | 1784 |Tap to Pay on iPhone setup | 1785 |Apple Endpoint <-> Device | 1786 |Yes | 1787 |Yes | 1788 |https://support.apple.com/en-bh/HT210060 | 1789 |1790 | |
| Apple | 1793 |Tap to Pay on iPhone | 1794 |phonesubmissions.apple.com | 1795 |443 | 1796 |TCP | 1797 |iOS only | 1798 |Optional analytics sharing | 1799 |Apple Endpoint <-> Device | 1800 |Yes | 1801 |Yes | 1802 |https://support.apple.com/en-bh/HT210060 | 1803 |1804 | |
| Apple | 1807 |Tap to Pay on iPhone | 1808 |pos-device.apple.com | 1809 |443 | 1810 |TCP, UDP | 1811 |iOS only | 1812 |Tap to Pay on iPhone | 1813 |Apple Endpoint <-> Device | 1814 |Yes | 1815 |Yes | 1816 |https://support.apple.com/en-bh/HT210060 | 1817 |1818 | |
| Jamf | 1821 |Administrator Workstation Connections (outbound) | 1822 |client device | 1823 |548, 445 | 1824 |AFP/SMB | 1825 |iOS, iPadOS, macOS | 1826 |The Jamf Admin application can upload new software packages to AFP or SMB distribution points. | 1827 |Jamf Admin to distribution points | 1828 |Yes | 1829 |unclear | 1830 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 1831 |1832 | |
| Jamf | 1835 |Administrator Workstation Connections (outbound) | 1836 |client device | 1837 |8443, 443 | 1838 |HTTPS | 1839 |iOS, iPadOS, macOS | 1840 |Administrators perform management tasks by logging in to the Jamf Pro server using a web browser and the Jamf Pro apps (Jamf Admin). When the default settings are used, on-premise Jamf Pro servers use port 8443, and Jamf Cloud-hosted servers use port 443. | 1841 |Administrator workstations to the Jamf Pro server | 1842 |Yes | 1843 |unclear | 1844 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 1845 |1846 | |
| Jamf | 1849 |Jamf AD CS Connector Connections | 1850 |Jamf ADCS Server | 1851 |135 and 49152-65535 | 1852 |DCOM | 1853 |Windows | 1854 |The Jamf AD CS Connector uses Microsoft Distributed Component Object Model (DCOM) to communicate with AD CS. | 1855 |Jamf AD CS Connector to AD CS | 1856 |Yes | 1857 |unclear | 1858 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 1859 |1860 | |
| Jamf | 1863 |Jamf AD CS Connector Connections | 1864 |Jamf ADCS Server | 1865 |443 | 1866 |HTTPS | 1867 |Windows | 1868 |Jamf Pro sends certificate signing requests and retrieves completed certificates by opening a connection to the Jamf AD CS Connector, typically on TCP port 443. | 1869 |Jamf Pro to Jamf AD CS Connector | 1870 |Yes | 1871 |unclear | 1872 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 1873 |1874 | |
| Jamf | 1877 |Jamf AD CS Connector Connections | 1878 |Jamf ADCS Server | 1879 |8443, 443 | 1880 |HTTPS | 1881 |Windows | 1882 |If your organization uses in-house apps developed with the Jamf Certificate SDK, connections to the Jamf Pro server will be via HTTPS. When default settings are used, on-premise Jamf Pro servers use port 8443, and Jamf Cloud-hosted servers use port 443. | 1883 |Mobile device apps to the Jamf Pro server | 1884 |Yes | 1885 |unclear | 1886 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 1887 |1888 | |
| Jamf | 1891 |Jamf Infrastructure Manager - Healthcare Listener Connections | 1892 |JIM Server | 1893 |2575 | 1894 |HL7 | 1895 |Windows | 1896 |2575 is an assigned port that can be used for HL7 communications, but the Healthcare Listener can be configured to use any preferred port 1024 or greater. | 1897 |HL7 interface to Jamf Infrastructure Manager host | 1898 |Yes | 1899 |unclear | 1900 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 1901 |1902 | |
| Jamf | 1905 |Jamf Infrastructure Manager - Healthcare Listener Connections | 1906 |JIM Server | 1907 |8443, 443 | 1908 |HTTPS | 1909 |Windows | 1910 |The Healthcare Listener informs the Jamf Pro Management Server when an action is needed on a device. When the default settings are used, on-premise Jamf Pro servers use port 8443, and Jamf Cloud-hosted servers use port 443. | 1911 |Jamf Infrastructure Manager host to the Jamf Pro server | 1912 |Yes | 1913 |unclear | 1914 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 1915 |1916 | |
| Jamf | 1919 |Jamf Infrastructure Manager - LDAP Proxy Connections | 1920 |JIM Server | 1921 |8081 | 1922 |HTTP | 1923 |Windows | 1924 |The LDAP Proxy service can expose this port to enable Healthcheck endpoint for verification of LDAP Proxy Server status. The default port is 8081 but can be changed by your administrator. | 1925 |External service to Jamf Infrastructure Manager host | 1926 |Yes | 1927 |unclear | 1928 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 1929 |1930 | |
| Jamf | 1933 |Jamf Infrastructure Manager - LDAP Proxy Connections | 1934 |JIM Server | 1935 |8443, 443 | 1936 |HTTPS | 1937 |Windows | 1938 |Jamf Infrastructure Manager instances connect to the Jamf Pro server when they are enrolled and periodically thereafter to confirm their operating status and retrieve updated settings. When the default settings are used, on-premise Jamf Pro servers use port 8443, and Jamf Cloud-hosted servers use port 443. | 1939 |Jamf Infrastructure Manager host to the Jamf Pro server | 1940 |Yes | 1941 |unclear | 1942 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 1943 |1944 | |
| Jamf | 1947 |Jamf Infrastructure Manager - LDAP Proxy Connections | 1948 |JIM Server | 1949 |389, 636 | 1950 |LDAP or LDAPS | 1951 |Windows | 1952 |The LDAP Proxy service receives lookup requests from the Jamf Pro server and forwards them to the directory service you have configured in Jamf Pro's LDAP settings. LDAP typically runs on port 389. If you encrypt your LDAP communications (e.g., LDAP over SSL/LDAPS), port 636 is commonly used. Your directory services administrator can tell you which port is used in your environment. | 1953 |Jamf Infrastructure Manager/LDAP Proxy to LDAP server/Domain controller | 1954 |Yes | 1955 |unclear | 1956 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 1957 |1958 | |
| Jamf | 1961 |Jamf Infrastructure Manager - LDAP Proxy Connections | 1962 |JIM Server | 1963 |8389, 8636 | 1964 |LDAP or LDAPS | 1965 |Windows | 1966 |All Jamf Pro LDAP lookups are sent via the Jamf Pro server. Jamf Pro can be configured to send LDAP queries to a Jamf Infrastructure Manager LDAP Proxy instance rather than directly to an LDAP host. The port on which the LDAP Proxy will listen for these incoming requests is configured when enrolling with the Jamf Pro server. On Linux, the port chosen should be at least 1024 because lower-numbered ports are reserved for more privileged services and users. Port 8389 might be chosen if running on LDAP, or port 8636 if running on LDAPS. | 1967 |Jamf Pro server to the Jamf Infrastructure Manager host | 1968 |Yes | 1969 |unclear | 1970 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 1971 |1972 | |
| Jamf | 1975 |Jamf Pro server (inbound) | 1976 |[yourserver].jamfcloud.com or on-prem hostname | 1977 |80, 8080, 443 | 1978 |HTTP or HTTPS | 1979 |- | 1980 |Some advanced installations may include a load balancer or reverse proxy. In this case, the Jamf Pro server URL’s host name will resolve to the IP address of the proxy. If SSL is terminated at the proxy, traffic is forwarded to the Jamf Pro server over HTTP (typical ports are 80/8080). Or, traffic may be re-encrypted or passed using HTTPS (often over port 443. | 1981 |Load balancer or proxy to the Jamf Pro server | 1982 |Yes | 1983 |unclear | 1984 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 1985 |1986 | |
| Jamf | 1989 |Jamf Pro server (inbound) | 1990 |[yourserver].jamfcloud.com or on-prem hostname | 1991 |8443 or 443 | 1992 |HTTPS | 1993 |- | 1994 |Connections to the Jamf Pro web app use HTTPS. When default settings are used, on-premise Jamf Pro servers use port 8443, and Jamf Cloud-hosted servers use port 443. Note: HTTPS Interception (SSL Inspection) is not supported for connections to Jamf Pro. If client HTTPS traffic traverses a web proxy, you must disable HTTPS Interception for connections to Jamf Pro. |
1995 | Managed computers or mobile devices, administrator workstations, and other services to the Jamf Pro server | 1996 |Yes | 1997 |Yes | 1998 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 1999 |2000 | |
| Jamf | 2003 |Jamf Pro server (outbound) | 2004 |[yourserver].jamfcloud.com or on-prem hostname | 2005 |80 | 2006 |HTTP | 2007 |- | 2008 |App Store app information can be retrieved from the App Store. | 2009 |Jamf Pro server to Apple | 2010 |Yes | 2011 |unclear | 2012 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2013 |2014 | |
| Jamf | 2017 |Jamf Pro server (outbound) | 2018 |[yourserver].jamfcloud.com or on-prem hostname | 2019 |80, 443 | 2020 |HTTP or HTTPS | 2021 |- | 2022 |The Jamf Pro server connects to Pendo if Engage is enabled in Jamf Pro. Jamf Engage data is compressed to approximately 100KB and loads asynchronously. Data is securely transmitted via SSL and each transmission is less than 2KB. | 2023 |Jamf Pro server to *.jamfcloud.com | 2024 |Yes | 2025 |unclear | 2026 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2027 |2028 | |
| Jamf | 2031 |Jamf Pro server (outbound) | 2032 |[yourserver].jamfcloud.com or on-prem hostname | 2033 |80, 443 | 2034 |HTTP or HTTPS | 2035 |- | 2036 |The Jamf Pro server connects to Microsoft via the Microsoft Graph API if the connection between Jamf Pro and Microsoft Intune is configured. For more information, see the following documentation from Microsoft: Network endpoints for Microsoft Intune | 2037 |Jamf Pro server to the following domains: login.microsoftonline.com graph.microsoft.com *.manage.microsoft.com |
2038 | Yes | 2039 |unclear | 2040 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2041 |2042 | |
| Jamf | 2045 |Jamf Pro server (outbound) | 2046 |[yourserver].jamfcloud.com or on-prem hostname | 2047 |80, 443 | 2048 |HTTP or HTTPS | 2049 |- | 2050 |If you are deploying SCEP certificate configuration profiles with a dynamic challenge, or using Jamf Pro's SCEP proxy services, the Jamf Pro server connects to your SCEP Enrollment server to obtain an enrollment challenge password and/or retrieve generated certificates on behalf of managed devices. Note: In a clustered environment, requests related to the SCEP Proxy are handled by the web app that receives the request. Therefore, it is important that all web apps are able to communicate with the configured SCEP service. |
2051 | Jamf Pro server to SCEP Enrollment server | 2052 |Yes | 2053 |unclear | 2054 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2055 |2056 | |
| Jamf | 2059 |Jamf Pro server (outbound) | 2060 |[yourserver].jamfcloud.com or on-prem hostname | 2061 |443 | 2062 |HTTPS | 2063 |- | 2064 |The Jamf Pro server can integrate with Apple-hosted services such as Device Enrollment (formerly Device Enrollment Program), Volume Purchasing (formerly Volume Purchase Program), and Global Service Exchange (GSX). | 2065 |Jamf Pro server to Apple | 2066 |Yes | 2067 |unclear | 2068 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2069 |2070 | |
| Jamf | 2073 |Jamf Pro server (outbound) | 2074 |[yourserver].jamfcloud.com or on-prem hostname | 2075 |443 | 2076 |HTTPS | 2077 |- | 2078 |The Jamf Pro server can access hosted schema to populate Application & Custom Settings options. | 2079 |Jamf Pro server to prod-custom-setting-schemas.s3.amazonaws.com | 2080 |Yes | 2081 |unclear | 2082 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2083 |2084 | |
| Jamf | 2087 |Jamf Pro server (outbound) | 2088 |[yourserver].jamfcloud.com or on-prem hostname | 2089 |443 | 2090 |HTTPS | 2091 |- | 2092 |The Jamf Pro server can connect to Jamf-hosted utilities and services including: Retrieving information about newly released software and version updates from Jamf's patch reporting database, hosted at https://jamf-patch.jamfcloud.com/ Apple Push Notification certificate signing requests (CSR) Customer Experience Metrics information submitted to Jamf (optional) Jamf Push Proxy communication with Jamf Self Service for iOS Retrieving information from Jamf's hardware model name service, hosted at https://hw-model-names.services.jamfcloud.com (if configured) |
2093 | Jamf Pro server to *.jamfcloud.com and *.jamf.com | 2094 |Yes | 2095 |unclear | 2096 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2097 |2098 | |
| Jamf | 2101 |Jamf Pro server (outbound) | 2102 |[yourserver].jamfcloud.com or on-prem hostname | 2103 |443 | 2104 |HTTPS | 2105 |- | 2106 |The Jamf Pro server connects to Jamf-hosted services via the Cloud Services Connection. | 2107 |Jamf Pro server to the following domains: https://csa.services.jamfcloud.com https://ics.services.jamfcloud.com |
2108 | Yes | 2109 |unclear | 2110 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2111 |2112 | |
| Jamf | 2115 |Jamf Pro server (outbound) | 2116 |[yourserver].jamfcloud.com or on-prem hostname | 2117 |443 | 2118 |HTTPS | 2119 |- | 2120 |A cloud distribution point (Amazon S3 or CloudFront, Akamai, RackSpace, or Jamf Cloud Distribution Service) can be used to host your software packages for distribution to managed clients. The Jamf Pro server connects to these services to perform initial configuration, to upload packages added via the Jamf Pro web app or Jamf Admin, and as needed to request content access tokens and URL signatures. | 2121 |Jamf Pro server to cloud hosting provider | 2122 |Yes | 2123 |unclear | 2124 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2125 |2126 | |
| Jamf | 2129 |Jamf Pro server (outbound) | 2130 |[yourserver].jamfcloud.com or on-prem hostname | 2131 |443 | 2132 |HTTPS | 2133 |- | 2134 |Jamf Pro can be configured to send webhook notifications for a variety of events (device enrollment, inventory updates, etc.) to support workflow automation and data integrations. | 2135 |Jamf Pro server to event listener application server | 2136 |Yes | 2137 |unclear | 2138 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2139 |2140 | |
| Jamf | 2143 |Jamf Pro server (outbound) | 2144 |[yourserver].jamfcloud.com or on-prem hostname | 2145 |443 | 2146 |HTTPS | 2147 |- | 2148 |The Jamf Pro server connects to TeamViewer via TeamViewer API if connection between Jamf Pro and TeamViewer is configured. For more information, see TeamViewer Integration in the Jamf Pro Documentation | 2149 |- | 2150 |Yes | 2151 |unclear | 2152 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2153 |2154 | |
| Jamf | 2157 |Jamf Pro server (outbound) | 2158 |[yourserver].jamfcloud.com or on-prem hostname | 2159 |2195, 2196 | 2160 |HTTPS | 2161 |- | 2162 |Ports 2195/2196 are used only for legacy binary Apple Push Notification (APNs) service protocol until Jamf Pro deprecates the binary protocol or Apple no longer supports it. Notifications are sent to Apple on port 2195 and delivery feedback is solicited on port 2196. | 2163 |Jamf Pro server to Apple APNs 17/8 IP range | 2164 |Yes | 2165 |unclear | 2166 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2167 |2168 | |
| Jamf | 2171 |Jamf Pro server (outbound) | 2172 |[yourserver].jamfcloud.com or on-prem hostname | 2173 |443, 2197 | 2174 |HTTPS | 2175 |- | 2176 |The Jamf Pro server uses Apple Push Notification service (APNs) to prompt managed devices to check in for mobile device management (MDM). Port 443 is used by default for the HTTP/2 connections. Port 2197 can be used only in on-premise environments. Note: Allow outbound connections to and redirects from Apple's 17.0.0.0/8 block over TCP port 5223 / 443 from all client networks and on port 2197, where applicable, from Jamf Pro servers to ensure APNs will function correctly on your network. |
2177 | Jamf Pro server to Apple APNs 17/8 IP range | 2178 |Yes | 2179 |unclear | 2180 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2181 |2182 | |
| Jamf | 2185 |Jamf Pro server (outbound) | 2186 |[yourserver].jamfcloud.com or on-prem hostname | 2187 |389, 636 | 2188 |LDAP, Start TLS, or LDAPS | 2189 |- | 2190 |Directory service integration via LDAP (389), LDAP over TLS (Start TLS/389) or LDAP over SSL (LDAPS/636) can be used for user authentication, device assignment, and user information and group membership lookups. Note: All Jamf Pro server LDAP connections will originate from the Jamf Pro server. For information about LDAP Proxy connections, see the "Jamf Infrastructure Manager – LDAP Proxy Connections" section in this document. |
2191 | Jamf Pro server to LDAP/Domain controller | 2192 |Yes | 2193 |unclear | 2194 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2195 |2196 | |
| Jamf | 2199 |Jamf Pro server (outbound) | 2200 |[yourserver].jamfcloud.com or on-prem hostname | 2201 |11211 | 2202 |memcached | 2203 |- | 2204 |Memcached data access acceleration services can help reduce database load in multi-server Jamf Pro configurations. | 2205 |Jamf Pro servers to Memcached servers | 2206 |Yes | 2207 |unclear | 2208 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2209 |2210 | |
| Jamf | 2213 |Jamf Pro server (outbound) | 2214 |[yourserver].jamfcloud.com or on-prem hostname | 2215 |3306 | 2216 |MySQL | 2217 |- | 2218 |The Jamf Pro server connects to a MySQL database. | 2219 |Jamf Pro server to MySQL database | 2220 |Yes | 2221 |unclear | 2222 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2223 |2224 | |
| Jamf | 2227 |Jamf Pro server (outbound) | 2228 |[yourserver].jamfcloud.com or on-prem hostname | 2229 |25, 465, 587 | 2230 |SMTP | 2231 |- | 2232 |Email integration via an SMTP gateway can be used for administrative notifications, user messaging, and enrollment invitations. The SMTP port depends on the service provider and type of encryption supported. Note: To help keep data and communications as secure as possible, port 25 is blocked in Jamf Cloud. Jamf recommends using port 587 with TLS. |
2233 | Jamf Pro server to SMTP gateway host | 2234 |Yes | 2235 |unclear | 2236 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2237 |2238 | |
| Jamf | 2241 |Jamf Pro server (outbound) | 2242 |[yourserver].jamfcloud.com or on-prem hostname | 2243 |514 | 2244 |Syslog | 2245 |- | 2246 |Change Management logs can be written to log files and to a Syslog server. | 2247 |Jamf Pro server to Syslog server | 2248 |Yes | 2249 |unclear | 2250 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2251 |2252 | |
| Jamf | 2255 |Managed Computer and Mobile Device Connections (outbound) | 2256 |client device | 2257 |548 | 2258 |AFP | 2259 |iOS, iPadOS, macOS | 2260 |Software packages can be downloaded by Mac computers from an Apple File Protocol (AFP) server. | 2261 |Mac computers to AFP servers | 2262 |Yes | 2263 |unclear | 2264 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2265 |2266 | |
| Jamf | 2269 |Managed Computer and Mobile Device Connections (outbound) | 2270 |client device | 2271 |5223, 443 | 2272 |APNs | 2273 |iOS, iPadOS, macOS | 2274 |The Jamf Pro server will send a message to the Apple Push Notification service when it has an MDM profile or command awaiting delivery to an enrolled device. Mac computers and iOS devices maintain a persistent connection to APNs when connected to a network so they will receive new notifications quickly. End user devices connect to APNs using port 5223 by default, but will fail over to port 443 when connecting via Wi-Fi. | 2275 |Managed devices to APNs | 2276 |Yes | 2277 |unclear | 2278 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2279 |2280 | |
| Jamf | 2283 |Managed Computer and Mobile Device Connections (outbound) | 2284 |client device | 2285 |80, 443 | 2286 |HTTP and HTTPS | 2287 |iOS, iPadOS, macOS | 2288 |Mac computers can download software packages from an HTTP and HTTPS server such as Apple macOS Server, Apache, and Microsoft IIS. | 2289 |Managed computers to HTTP/HTTPS distribution point | 2290 |Yes | 2291 |unclear | 2292 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2293 |2294 | |
| Jamf | 2297 |Managed Computer and Mobile Device Connections (outbound) | 2298 |client device | 2299 |80, 443 | 2300 |HTTP and HTTPS | 2301 |iOS, iPadOS, macOS | 2302 |The Apple ecosystem relies on many Internet-based systems maintained by Apple and their content distribution network (CDN). Examples include Apple Software Update, the App Store, Device Enrollment (formerly Device Enrollment Program), Volume Purchasing (formerly Volume Purchase Program). | 2303 |Managed devices to Apple/CDN | 2304 |Yes | 2305 |unclear | 2306 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2307 |2308 | |
| Jamf | 2311 |Managed Computer and Mobile Device Connections (outbound) | 2312 |client device | 2313 |443 | 2314 |HTTPS | 2315 |iOS, iPadOS, macOS | 2316 |Mac computers can download software packages from a cloud distribution point (Amazon S3 or CloudFront, Akamai, RackSpace, or Jamf Cloud Distribution Service). | 2317 |Managed computers to a cloud distribution point | 2318 |Yes | 2319 |unclear | 2320 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2321 |2322 | |
| Jamf | 2325 |Managed Computer and Mobile Device Connections (outbound) | 2326 |client device | 2327 |443 | 2328 |HTTPS | 2329 |iOS, iPadOS, macOS | 2330 |iOS devices can download in-house apps and ebooks from the Jamf Cloud Distribution Service. | 2331 |Managed mobile devices to JCDS | 2332 |Yes | 2333 |unclear | 2334 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2335 |2336 | |
| Jamf | 2339 |Managed Computer and Mobile Device Connections (outbound) | 2340 |client device | 2341 |443 | 2342 |HTTPS | 2343 |iOS, iPadOS, macOS | 2344 |Managed computers send crash logging and some anonymized usage statistics to Jamf's Sentry server. For more information, see the Sentry Crash Logging and Usage Analytics Integrations article. | 2345 |Managed computers to sentry.pub.jamf.build | 2346 |Yes | 2347 |unclear | 2348 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2349 |2350 | |
| Jamf | 2353 |Managed Computer and Mobile Device Connections (outbound) | 2354 |client device | 2355 |8443, 443 | 2356 |HTTPS | 2357 |iOS, iPadOS, macOS | 2358 |Mac computers and iOS devices connect to the Jamf Pro server when: Prompted to enroll in mobile device management by Apple’s Device Enrollment (formerly Device Enrollment Program) Enrolling via user-initiated enrollment in a web browser Running the jamf agent (Mac computers only) Running Self Service Mobile for iOS Running Self Service for macOS Responding to an MDM push notification When the default settings are used, on-premise Jamf Pro servers use port 8443 and the Jamf Cloud managed-hosting option uses port 443. |
2359 | Managed devices to the Jamf Pro server | 2360 |Yes | 2361 |unclear | 2362 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2363 |2364 | |
| Jamf | 2367 |Managed Computer and Mobile Device Connections (outbound) | 2368 |client device | 2369 |445, 137–139 | 2370 |SMB | 2371 |iOS, iPadOS, macOS | 2372 |Software packages can be distributed to Mac computers using a Windows SMB (CIFS) distribution point. | 2373 |Managed computers to SMB servers | 2374 |Yes | 2375 |unclear | 2376 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2377 |2378 | |
| Jamf | 2381 |SCCM Plug-In Connections | 2382 |SCCM Proxy Service | 2383 |80, 443 | 2384 |HTTP/HTTPS | 2385 |Windows | 2386 |The SCCM Proxy Service will transmit updated device inventory information to the Microsoft Configuration Manager API. | 2387 |SCCM Plug-In host to SCCM server | 2388 |Yes | 2389 |unclear | 2390 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2391 |2392 | |
| Jamf | 2395 |SCCM Plug-In Connections | 2396 |SCCM Proxy Service | 2397 |8443, 443 | 2398 |HTTPS | 2399 |Windows | 2400 |The SCCM Proxy Service queries the Jamf Pro server via a REST API to obtain information about your managed devices. When the default settings are used, on-premise Jamf Pro servers use port 8443, and the Jamf Cloud-hosted servers use port 443. | 2401 |SCCM Plug-In host to the Jamf Pro server | 2402 |Yes | 2403 |unclear | 2404 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2405 |2406 | |
| Jamf | 2409 |Single Sign-On Connections (bidirectional) | 2410 |client device | 2411 |custom | 2412 |custom | 2413 |iOS, iPadOS, macOS | 2414 |To implement single sign-on in on-premise environments, two-way communication on TCP ports between the Identity Provider and Jamf Pro server is required. | 2415 |IdP <-> Device | 2416 |Yes | 2417 |unclear | 2418 |https://learn.jamf.com/bundle/technical-articles/page/Network_Ports_Used_by_Jamf_Pro.html | 2419 |2420 | |
| Microsoft | 2423 |Office Apps | 2424 |client device | 2425 |see documentation | 2426 |see documentation | 2427 |iOS, iPadOS, macOS | 2428 |This is a link to the macadmins.software website run by Paul Bowden @microsoft and the PDF he already has with the endpoints used by Office apps on macOS | 2429 |- | 2430 |- | 2431 |- | 2432 |https://macadmins.software/docs/Network_Traffic.pdf | 2433 |2434 | |
| Microsoft | 2437 |SSO Plug-in | 2438 |*.cdn-apple.com | 2439 |unclear | 2440 |unclear | 2441 |iOS, iPadOS, macOS | 2442 |For the SSO plug-in to function properly, Apple devices should be allowed to reach to both identity provider URLs and its own URLs without additional interception. This means that those URLs need to be excluded from network proxies, interception and other enterprise systems. | 2443 |device <-> host | 2444 |Unclear | 2445 |Yes | 2446 |https://learn.microsoft.com/en-us/azure/active-directory/develop/apple-sso-plugin#required-network-configuration | 2447 |2448 | |
| Microsoft | 2451 |SSO Plug-in | 2452 |*.networking.apple | 2453 |unclear | 2454 |unclear | 2455 |iOS, iPadOS, macOS | 2456 |For the SSO plug-in to function properly, Apple devices should be allowed to reach to both identity provider URLs and its own URLs without additional interception. This means that those URLs need to be excluded from network proxies, interception and other enterprise systems. | 2457 |device <-> host | 2458 |Unclear | 2459 |Yes | 2460 |https://learn.microsoft.com/en-us/azure/active-directory/develop/apple-sso-plugin#required-network-configuration | 2461 |2462 | |
| Microsoft | 2465 |SSO Plug-in | 2466 |login-us.microsoftonline.com | 2467 |unclear | 2468 |unclear | 2469 |iOS, iPadOS, macOS | 2470 |For the SSO plug-in to function properly, Apple devices should be allowed to reach to both identity provider URLs and its own URLs without additional interception. This means that those URLs need to be excluded from network proxies, interception and other enterprise systems. | 2471 |device <-> host | 2472 |Unclear | 2473 |Yes | 2474 |https://learn.microsoft.com/en-us/azure/active-directory/develop/apple-sso-plugin#required-network-configuration | 2475 |2476 | |
| Microsoft | 2479 |SSO Plug-in | 2480 |login.chinacloudapi.cn | 2481 |unclear | 2482 |unclear | 2483 |iOS, iPadOS, macOS | 2484 |For the SSO plug-in to function properly, Apple devices should be allowed to reach to both identity provider URLs and its own URLs without additional interception. This means that those URLs need to be excluded from network proxies, interception and other enterprise systems. | 2485 |device <-> host | 2486 |Unclear | 2487 |Yes | 2488 |https://learn.microsoft.com/en-us/azure/active-directory/develop/apple-sso-plugin#required-network-configuration | 2489 |2490 | |
| Microsoft | 2493 |SSO Plug-in | 2494 |login.microsoft.com | 2495 |unclear | 2496 |unclear | 2497 |iOS, iPadOS, macOS | 2498 |For the SSO plug-in to function properly, Apple devices should be allowed to reach to both identity provider URLs and its own URLs without additional interception. This means that those URLs need to be excluded from network proxies, interception and other enterprise systems. | 2499 |device <-> host | 2500 |Unclear | 2501 |Yes | 2502 |https://learn.microsoft.com/en-us/azure/active-directory/develop/apple-sso-plugin#required-network-configuration | 2503 |2504 | |
| Microsoft | 2507 |SSO Plug-in | 2508 |login.microsoftonline.com | 2509 |unclear | 2510 |unclear | 2511 |iOS, iPadOS, macOS | 2512 |For the SSO plug-in to function properly, Apple devices should be allowed to reach to both identity provider URLs and its own URLs without additional interception. This means that those URLs need to be excluded from network proxies, interception and other enterprise systems. | 2513 |device <-> host | 2514 |Unclear | 2515 |Yes | 2516 |https://learn.microsoft.com/en-us/azure/active-directory/develop/apple-sso-plugin#required-network-configuration | 2517 |2518 | |
| Microsoft | 2521 |SSO Plug-in | 2522 |login.microsoftonline.us | 2523 |unclear | 2524 |unclear | 2525 |iOS, iPadOS, macOS | 2526 |For the SSO plug-in to function properly, Apple devices should be allowed to reach to both identity provider URLs and its own URLs without additional interception. This means that those URLs need to be excluded from network proxies, interception and other enterprise systems. | 2527 |device <-> host | 2528 |Unclear | 2529 |Yes | 2530 |https://learn.microsoft.com/en-us/azure/active-directory/develop/apple-sso-plugin#required-network-configuration | 2531 |2532 | |
| Microsoft | 2535 |SSO Plug-in | 2536 |login.partner.microsoftonline.cn | 2537 |unclear | 2538 |unclear | 2539 |iOS, iPadOS, macOS | 2540 |For the SSO plug-in to function properly, Apple devices should be allowed to reach to both identity provider URLs and its own URLs without additional interception. This means that those URLs need to be excluded from network proxies, interception and other enterprise systems. | 2541 |device <-> host | 2542 |Unclear | 2543 |Yes | 2544 |https://learn.microsoft.com/en-us/azure/active-directory/develop/apple-sso-plugin#required-network-configuration | 2545 |2546 | |
| Microsoft | 2549 |SSO Plug-in | 2550 |sts.windows.net | 2551 |unclear | 2552 |unclear | 2553 |iOS, iPadOS, macOS | 2554 |For the SSO plug-in to function properly, Apple devices should be allowed to reach to both identity provider URLs and its own URLs without additional interception. This means that those URLs need to be excluded from network proxies, interception and other enterprise systems. | 2555 |device <-> host | 2556 |Unclear | 2557 |Yes | 2558 |https://learn.microsoft.com/en-us/azure/active-directory/develop/apple-sso-plugin#required-network-configuration | 2559 |2560 | |
| Microsoft | 2563 |Tenant Restrictions | 2564 |login.microsoft.com | 2565 |unclear | 2566 |unclear | 2567 |iOS, iPadOS, macOS | 2568 |Proxy configuration and requirements: The following configuration is required to enable tenant restrictions through your proxy infrastructure. This guidance is generic, so you should refer to your proxy vendor's documentation for specific implementation steps. Prerequisites: The proxy must be able to perform TLS interception, HTTP header insertion, and filter destinations using FQDNs/URLs. Clients must trust the certificate chain presented by the proxy for TLS communications. For example, if certificates from an internal public key infrastructure (PKI) are used, the internal issuing root certificate authority certificate must be trusted. Microsoft Entra ID P1 or P2 1 licenses are required for use of tenant restrictions. |
2569 | device <-> host | 2570 |Yes | 2571 |No | 2572 |https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/tenant-restrictions#urls-and-ip-addresses | 2573 |2574 | |
| Microsoft | 2577 |Tenant Restrictions | 2578 |login.microsoftonline.com | 2579 |unclear | 2580 |unclear | 2581 |iOS, iPadOS, macOS | 2582 |Proxy configuration and requirements: The following configuration is required to enable tenant restrictions through your proxy infrastructure. This guidance is generic, so you should refer to your proxy vendor's documentation for specific implementation steps. Prerequisites: The proxy must be able to perform TLS interception, HTTP header insertion, and filter destinations using FQDNs/URLs. Clients must trust the certificate chain presented by the proxy for TLS communications. For example, if certificates from an internal public key infrastructure (PKI) are used, the internal issuing root certificate authority certificate must be trusted. Microsoft Entra ID P1 or P2 1 licenses are required for use of tenant restrictions. |
2583 | device <-> host | 2584 |Yes | 2585 |No | 2586 |https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/tenant-restrictions#urls-and-ip-addresses | 2587 |2588 | |
| Microsoft | 2591 |Tenant Restrictions | 2592 |login.windows.net | 2593 |unclear | 2594 |unclear | 2595 |iOS, iPadOS, macOS | 2596 |Proxy configuration and requirements: The following configuration is required to enable tenant restrictions through your proxy infrastructure. This guidance is generic, so you should refer to your proxy vendor's documentation for specific implementation steps. Prerequisites: The proxy must be able to perform TLS interception, HTTP header insertion, and filter destinations using FQDNs/URLs. Clients must trust the certificate chain presented by the proxy for TLS communications. For example, if certificates from an internal public key infrastructure (PKI) are used, the internal issuing root certificate authority certificate must be trusted. Microsoft Entra ID P1 or P2 1 licenses are required for use of tenant restrictions. |
2597 | device <-> host | 2598 |Yes | 2599 |No | 2600 |https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/tenant-restrictions#urls-and-ip-addresses | 2601 |