App Transport Security Explained: What NSAllowsArbitraryLoads Really Does

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

App Transport Security Explained: What NSAllowsArbitraryLoads Really Does

Short answer: NSAllowsArbitraryLoads set to true in your Info.plist turns off App Transport Security for your entire app — every network connection your app makes is allowed to use plain HTTP and outdated TLS, to any server, forever. It's one boolean, it usually gets added to fix one stubborn request during development, and it's one of the highest-signal findings in an iOS security review. PreShipIt's project upload scan flags it as a high-severity finding for exactly that reason.

What ATS enforces when it's on

App Transport Security has been iOS's default networking policy since iOS 9. With no NSAppTransportSecurity key in your Info.plist at all, connections made through URLSession must meet a baseline:

That's a sensible floor: it means a user on café Wi-Fi can't have your app's API traffic read or rewritten by whoever controls the network. ATS doesn't make your app secure by itself — it removes one whole class of network attack by default.

What the one boolean changes

NSAllowsArbitraryLoads is the master override. Set it to true and the baseline above stops applying app-wide: HTTP loads succeed, weak TLS configurations succeed, and nothing in the OS will warn you or your users. Two details people get wrong:

Apple's documentation is blunt about the intent: arbitrary loads are a last resort, and ATS exceptions are expected to be justified when your app goes through App Review.

The exceptions that are actually scoped

ATS has a per-domain mechanism designed for the real-world case — one third-party server you don't control that can't do modern TLS yet. Under NSExceptionDomains, each domain gets its own dictionary:

Key What it relaxes
NSExceptionAllowsInsecureHTTPLoads Allows plain HTTP to this domain only
NSExceptionMinimumTLSVersion Lowers the TLS floor for this domain (e.g. to TLS 1.0/1.1)
NSExceptionRequiresForwardSecrecy Set to false to allow non-forward-secrecy ciphers for this domain
NSIncludesSubdomains Applies the exception to subdomains too — use sparingly

An exception written this way is auditable: anyone reviewing the plist can see exactly which domain got special treatment and how much. A global disable tells a reviewer nothing except that nobody scoped the problem.

How to check your app right now

# print the ATS dictionary from your built app or project plist
plutil -p YourApp/Info.plist | grep -A 10 NSAppTransportSecurity

# or search the whole project, including generated plists
grep -r "NSAllowsArbitraryLoads" --include="*.plist" .

Three outcomes:

  1. No NSAppTransportSecurity key at all — full default policy. This is the goal.
  2. Per-domain exceptions only — acceptable if each domain genuinely needs it. Review them once a year; vendors fix their TLS eventually, and stale exceptions are pure attack surface.
  3. NSAllowsArbitraryLoads = true — fix it: delete the key, run the app, and let ATS blockers tell you which specific connection actually needed help. Then scope an exception to that domain alone, or better, fix the server.

The related check: cleartext URLs in code

Even with ATS on, hardcoded http:// URLs in Swift files and plists are worth grepping for — they're the requests that will fail loudly the day you remove the global override, and they're how the override got justified in the first place. Our upload scan checks both: the ATS keys in your plists, and cleartext URLs across your .swift, .plist, and .json files (ignoring localhost and schema/namespace URLs, which are harmless).

The one-line version: if your plist has the boolean, your app has no transport security policy — it has a permission slip. Upload your project and we'll read the plist (and the rest of the project) for you, or run the plutil command above and read it yourself.

Related: How to Check Your Site's Security Headers — the server-side counterpart: what your API should be sending back once the connection itself is encrypted.

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report