iOS Certificate Checker
P12 & Profile Check
Expiry, Apple trust chains and revocation. One clear result.
Expiry, trust and revocation are assessed separately. Results do not guarantee installation on a device.
How to check an iOS certificate
CertScope checks iOS signing certificates and provisioning profiles online. Inspect each result separately: a certificate that has not expired is not necessarily usable.
- Select a certificate or profile
Use the separate P12 and profile buttons. Select one file or both, up to 16 MB per file.
- Enter the password and check
If your P12 is password protected, enter its password. After upload, the server performs an independent verification.
- Review status and matching
Review expiry, Apple trust and revocation separately. When both files are uploaded, check whether their certificates match.
Certificate checker FAQ
Can I check just a P12? Do I need an Apple account?
Yes. Upload a P12 or PFX to inspect certificate information, validity, private-key matching, Apple trust and online revocation results. No Apple account sign-in is required. Enter the correct password if the P12 is protected.
Why upload P12 and mobileprovision together?
A P12 usually contains a certificate and private key. A mobileprovision file (also accepted with an MB extension) describes app provisioning. When both are uploaded, certificate SHA-256 fingerprints are compared. Matching team names do not prove that certificates match.
How are Enterprise and Ad Hoc distinguished?
A matching provisioning profile with a verified Apple signature provides stronger evidence of distribution type. With only a P12, some labels are estimates. The Ad Hoc label for an exact 365-day validity period is a site-specific heuristic, not an Apple determination.
What do expired, revoked and unknown mean?
Expired means the certificate is outside its validity period. Revoked means a verified revocation response was received. Failed queries or unverified OCSP responses are shown as unknown, which does not mean not revoked. Consider expiry, trust and revocation together. Results do not guarantee device installation.
Are original files, private keys or passwords uploaded or stored?
Clicking Upload & check sends the original P12 / mobileprovision files and the password needed for verification to the server. Files may contain private keys or device information. Normal files that meet the archive rules are stored. Expired P12 files meeting historical Apple-chain and private-key matching requirements are archived separately. Confirmed revoked files are not stored. Passwords are not written to disk.
Why did Apple trust or revocation checks fail?
Expired certificates, an incomplete chain, a non-Apple issuer or a network error may affect the result. Check the files and password, provide a matching profile and review each check separately. An unknown result alone does not establish that a certificate is valid.
Reference: Apple: Ad Hoc provisioning profiles. CertScope is an independent tool, not an official Apple service.
Visits are estimated by IP without visitor cookies. Visit and submission records retain source IPs for authenticated administrators for 90 days. Analytics do not contain file contents or passwords. Visitors sharing a public IP are counted together.