Certificate Health Check

Check your iPhone signing setup before you waste time.

Upload a .mobileprovision profile for a browser-side check. Add your .p12 and password only if you want a full certificate check.

Profile-only check works locally .p12 check is optional Temporary full check

READY

Upload files to check them Start with a mobileprovision profile. Add .p12 + password for the full certificate check.

Mobileprovision profile

Drop your .mobileprovision here or tap to browse Checks expiry, UDID list, app identifier, and profile details.

Optional device UDID

Optional .p12 certificate

Drop your .p12 here for the full check Requires the certificate password. Files are checked temporarily and deleted.

Certificate password

Profile-only checks run in your browser. The full `.p12` check uses a temporary server check because browsers cannot reliably inspect password-protected PKCS#12 files.

Need ready certificate files for your device?

Get CertDrop for $8

What this catches

Expired or soon-expiring provisioning profiles.
A device UDID missing from the profile.
A `.p12` password that does not open the certificate.
A `.p12` certificate that does not match the uploaded provisioning profile.
App identifiers and team details useful for install troubleshooting.

If your device has a blacklist-related signing issue or a difficult install history, mention it during checkout so CertDrop can prepare the compatible setup where available.

How to read the health-check result

The provisioning profile identifies the development team, permitted app identifier, registered devices, capabilities, and expiry date. If you provide a UDID, the checker can confirm whether that exact device is included. A missing device entry means an app signed with that profile will not be installable on that iPhone or iPad.

The optional full check opens the password-protected .p12 and compares its signing certificate with the uploaded profile. A password failure means the file could not be opened with the supplied password. A certificate mismatch means the two files should not be used together, even if each file is otherwise valid.

What the checker cannot guarantee

A passing result confirms that the inspected certificate and profile information is internally consistent. It cannot guarantee that every IPA is compatible, that an app has valid entitlements, or that iOS will accept an installation previously affected by another signing identity. Use the IPA compatibility checker for app metadata and the signing error guide when iOS displays a specific message.

Profile-only checks run inside the browser. Password-protected certificate checks require the temporary full-check process described above, and uploaded full-check files are deleted after processing.