---
title: "What is idv-prod1.apple.com? What breaks if you block it · Kilobat"
url: "https://kilobat.app/hosts/idv-prod1-apple-com"
description: "idv-prod1.apple.com, smp-device-content.apple.com and idv.cdn-apple.com are used by ID Verifier on iPhone. A Mac isn't expected to use them."
---

# What is idv-prod1.apple.com?

`idv-prod1.apple.com`, `smp-device-content.apple.com` and `idv.cdn-apple.com` are Apple hosts for ID Verifier on iPhone.

Run by Apple · Ports: 443 TCP · Checked: 7 November 2026

## Short answer

Apple's hosts for ID Verifier on iPhone, which accepts mobile IDs. Apple lists them for iOS.

Safe to block

A Mac doesn't need them. Blocking them stops an iPhone from accepting mobile IDs.

Matches

`idv-prod1.apple.com` `smp-device-content.apple.com` `idv.cdn-apple.com`

A name with `*.` covers every name under it: `*.push.apple.com` matches `1-courier.push.apple.com`.

## What it serves

Apple says that an iPhone must reach the ID Verifier hosts for an ID Verifier-enabled app to accept mobile IDs.

Apple lists all three for iOS, on port 443 TCP, with the description “ID Verifier on iPhone”. It marks all three as supporting proxies.

The list adds `humb.apple.com` to this group. See [`humb.apple.com`](https://kilobat.app/hosts/humb-apple-com).

`idv.cdn-apple.com` sits under `cdn-apple.com`, which has its own page: [`*.cdn-apple.com`](https://kilobat.app/hosts/cdn-apple-com). The exact name takes priority over that wildcard.

## What breaks if you block it

Safe to block

A Mac doesn't need them. Blocking them stops an iPhone from accepting mobile IDs.

What breaks if you block it

- ID Verifier on iPhone can't accept mobile IDs.

With Kilobat Pro and the network filter, you can block a host for every app or for one app: in Connections, select a connection and choose Block. Apple’s own services are never blocked by Kilobat’s [Protection](https://kilobat.app/docs/blocking#protection) lists.

## Notes

Apple says that the device starts these connections, and that Apple services fail any connection that uses HTTPS interception (SSL inspection). Exempt the host from inspection.

## Apple’s rules for its hosts

Apple’s list, [Use Apple products on enterprise networks](https://support.apple.com/en-us/101555), says that devices open these connections, not Apple’s servers. Apple services fail any connection that uses HTTPS interception, so a proxy that inspects TLS should leave Apple’s hosts alone.

If a firewall allows hosts by name, allowing `*.apple.com` covers most Apple services, Apple says. A firewall that works only with addresses can allow `17.0.0.0/8` for IPv4, and `2403:300::/32`, `2620:149::/32` and `2a01:b740::/32` for IPv6.

To see which app on your Mac opened a connection to this host, use Kilobat’s Connections tab, or the [agent network log](https://kilobat.app/docs/agents#agent-network-log) for AI agents.

## Sources

- [Apple Support: Use Apple products on enterprise networks](https://support.apple.com/en-us/101555)

Checked on 7 November 2026.

## Related

- [humb.apple.com](https://kilobat.app/hosts/humb-apple-com): An Apple host in the Device setup list, also named for Tap to Pay on iPhone and ID Verifier on iPhone. Apple gives no description in the setup list.
- [*.cdn-apple.com](https://kilobat.app/hosts/cdn-apple-com): An Apple content delivery domain. Apple lists it for iCloud services; update and sign-in hosts sit under it too.
