iOS/Safari has historically enforced some certificate requirements more strictly and earlier than other platforms — notably, Apple set the industry's current 398-day maximum validity policy, and iOS devices reject certificates exceeding whatever the current Apple-set maximum is, even if other platforms haven't yet caught up to enforcing the same limit.
What to check if it's iOS-specific
Confirm your certificate's validity period doesn't exceed Apple's current maximum, and that it uses an algorithm and key length Apple's requirements currently accept — checking Apple's published certificate transparency and trust requirements directly is worth doing if you're seeing iOS-specific issues that don't reproduce on other platforms.
What iOS's stricter certificate policies mean for site owners specifically
Apple has historically enforced somewhat stricter certificate requirements on iOS than some other platforms, including specific maximum validity period limits that predated similar industry-wide requirements — a certificate technically valid elsewhere can occasionally still trigger a warning specifically on iOS if it doesn't meet Apple's particular requirements.
How to test whether an iOS-specific warning reflects a genuine configuration issue
Testing the same domain from a non-iOS device and comparing results distinguishes a genuine, cross-platform certificate misconfiguration from an iOS-specific requirement your certificate might not currently meet — if only iOS shows the warning, checking your certificate against Apple's specific, documented requirements is the next step.
What Apple's specific maximum validity period requirement historically meant for certificate issuance
Apple's early adoption of a shorter maximum certificate validity requirement, before it became a broader industry standard covered in our SSL History category, meant some certificates valid elsewhere could specifically fail on Apple devices during the period before other platforms caught up to the same requirement.
How to check Safari's specific certificate details view for more diagnostic information
Tapping the certificate warning in Safari and selecting to view certificate details shows the same underlying certificate information covered throughout this site — issuer, validity dates, SAN entries — giving you the specific detail needed to diagnose exactly what's triggering the iOS-specific warning.
A final note on staying ahead of platform-specific requirements
Given how quickly Apple's own certificate requirements have historically become broader industry standards, keeping your certificate configuration current against whatever the strictest major platform currently requires is a reasonable general practice that tends to preempt platform-specific warnings before they appear.
What Apple's Certificate Transparency enforcement timeline specifically involved
Apple enforced Certificate Transparency requirements on iOS and macOS somewhat ahead of some other platforms, meaning a certificate lacking proper CT log inclusion could trigger a warning specifically on Apple devices before other platforms began similarly strict enforcement — one of several examples of Apple's historically proactive certificate policy stance.
How to specifically test your certificate against Apple's documented requirements
Apple publishes specific technical requirements for certificates trusted on its platforms — reviewing your certificate against this documentation directly, rather than guessing, confirms whether a specific iOS-only warning reflects a genuine gap against Apple's particular requirements.
A quick closing checklist
A quick closing checklist covers testing the same domain from a non-Apple device for comparison, checking your certificate against Apple's specific documented requirements, and keeping your configuration current against whichever major platform currently has the strictest standards.
How Apple's App Transport Security adds a further layer beyond Safari's own browser warnings
Beyond Safari's visible warnings, Apple's App Transport Security framework enforces its own, sometimes stricter TLS requirements for apps specifically, meaning an app built for iOS can encounter connectivity issues around certificate requirements even when Safari itself shows no problem with the same server.