TLS Inspector

TLS Inspector is and will continue to be made entirely by humans, not AI. Our contribution rules explicitly forbids using AI for code or documentation.

It's time for your TLS Inspector 2025 Wrapped!

- This year you inspected an unknown number of hosts.
- You encountered an unknown number of expired certificates.
- Your most frequent CA was unknown.

We don't collect telemetry. We don't track you. Your privacy matters.

Thank you for your understanding and for using TLS Inspector.

Work continues on the next big update.

While I aimed to remove as many barriers as possible to make providing feedback easy, this has unfortunately allowed too many abusive and now threatening messages to come my way.

You can always send me a message here, or open up an issue on our GitHub, links to both will remain in the app.

After due consideration I've come to the conclusion that the ability to submit feedback directly from TLS Inspector must be removed.

Listening to legitimate feedback about the app has always been a guiding principle for me, but the feedback I've received recently has gone from creepy to abusive.

I'm hard at work on the next major update to TLS Inspector. However, this does mean that I won't be releasing an update to support Liquid Glass or any other iOS 26 feature in the near future.

I'm sorry or you're welcome.

Happy Pride 🏳️‍🌈🏳️‍⚧️🩷

It's our 9th release-day-anniversary today! We're looking forward to what's next and the big milestone next year.

Thanks for using TLS Inspector 🔐❤️

TLS Inspector 2.8.3 is available now. It includes a fix for how HTTP headers are collected during inspection.

I'm hard at work on the big 3.0 update and hope to be able to share a testable copy with you all soon.

TLS Inspector 2.8.2 is out now!

We've got some major improvements planned for later in the year, but for today we're just keeping things running smoothly with some bug fixes.