API archive entry · source-reported

Mozilla tls scanner

Mozilla observatory tls scanner

Provider / source website

From the publisher

README & documentation

Source preview

Read the project’s overview, installation instructions and usage examples. The original README is the source of truth.

[](https://whatsdeployed.io/s-LVL) [](https://circleci.com/gh/mozilla/tls-observatory/tree/master) The Mozilla TLS Observatory is a suite of tools for analysis and inspection on Transport Layer Security (TLS) services. The components of TLS Observatory include: Want the WebUI? Check out Mozilla's Observatory ! You can use the TLS Observatory to compare your site against the mozilla guidelines. It requires Golang 1.15+ to be installed: Then get the binary: And scan using our hosted service: The analysis at the end tell you what need to be changed to reach the old, intermediate or modern level. We recommend to target the intermediate level by default, and modern if you don't care about old clients. A docker container also exists that contains the CLI, API, Scanner and Runner. Fetch is from docker pull mozilla/tls-observatory. You can use the Kubernetes configuration provided in https://github.com/mozilla/tls-observatory/tree/master/kubernetes , or alternatively, you can do the following: You can use the mozilla/tls-observatory docker container for development: However,…

mozilla/tls-observatory on GitHub A short preview, not the full document.

Read the full README ↗ · Preview checked 2026-10-29T05:39:46.687Z

Inside the original README — Document outline
  1. Mozilla TLS Observatory
  2. Getting started
  3. Using the tlsobs client from Docker
  4. Developing
  5. Create the database
  6. Starting the API and Scanner
  7. Run a scan locally
  8. Configuration
  9. tlsobs-api
  10. tlsobs-scanner
  11. tlsobs-runner
  12. API Endpoints

Headings are captured from the source. Links open the publisher’s document, not a locally hosted copy.

Links from the README

References supplied by the publisher, not independently verified endorsements. Check the destination before downloading files or entering credentials.

Documentation belongs to its respective authors. A listing is not a grant of reuse or training rights. Confirm the document’s own terms at the source.

Where these facts came from

AltAPIs imported it from public-apis/public-apis. The source link and dates remain visible for independent inspection.

What is reported

  • Name, category, and short description
  • Authentication label
  • HTTPS and CORS labels
  • Provider/source URL

What is not established

  • Current uptime or availability
  • Pricing, quotas, and rate limits
  • Security, compliance, or licensing posture
  • SDK quality or endpoint completeness

Record checkpoints

  1. First observed: Sep 14, 2026
  2. Last directory-field change: Sep 14, 2026
  3. Current source observation: Nov 1, 2026

Submit a source-backed correction

Source reference

public-apis/public-apis

This page separates source-reported facts from questions that need live provider verification.