Reference & Lookup Data · Integration
SSL Labs
Add SSL Labs to your product for your customers, and give your AI agents governed access to it.
SSL Labs grades how a hostname is actually serving TLS, and an embedded SSL Labs integration is how that grade appears next to the person who can change it. An assessment covers the certificate and its chain, the protocol versions and cipher suites the endpoint negotiates, and the known weaknesses it is exposed to, ending in a letter grade with the reasons behind it. Two things shape the build, and neither is an OAuth flow. There is no customer account to connect, so what is configured per tenant is the list of hostnames your product may submit. And a full assessment takes minutes rather than milliseconds, so results are polled until ready and then cached, and a repeated request should reuse the cached assessment instead of starting another. fastn paces requests deliberately so a portfolio-wide run does not look like abuse.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Assess a hostname on request and show the grade beside the certificate and protocol findings that produced it.
Watch certificate expiry across the hostnames a customer has registered, so a renewal is chased before it lapses.
Re-assess on a schedule and keep the history, so a customer can show a weak cipher suite was genuinely removed.
Restrict which hostnames each tenant may submit, and reuse a cached assessment rather than queuing a duplicate.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent assesses a hostname and explains which protocol or cipher choice is holding the grade down.
An agent compares an assessment with the one before it and reports what changed in the chain.
An agent checks certificate expiry across a customer's hostnames as one step of a wider review, with each call logged.
Example prompt
Assess this hostname's TLS setup, tell me the grade and list what to change to move it up.
Set up SSL Labs in 4 steps
- 01Enable the SSL Labs connector in your fastn dashboard.
- 02Register your product's SSL Labs API access, then configure which hostnames each tenant may submit, since there is no customer account to authorise.
- 03Choose the assessment and result-read actions your product uses, and set how long a cached assessment counts as current.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the SSL Labs integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an SSL Labs integration without building it. Your customers connect their own SSL Labs account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an SSL Labs update is not your on-call problem.
- One integration serves your product and your agents. The same governed SSL Labs connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
Mozilla Observatory
MxToolbox
APIVoidOften used alongside
Tools the same teams tend to run next to SSL Labs, across other categories.
Salesforce
HubSpot
Notion
SnowflakeSSL Labs integration FAQ
How do I add an SSL Labs integration to my product?
Enable the SSL Labs connector in your fastn dashboard, then let each customer authenticate their own SSL Labs account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no SSL Labs client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own SSL Labs account?
Yes. Every connection is scoped to the individual customer, so each authorises their own SSL Labs account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this SSL Labs integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent assesses a hostname and explains which protocol or cipher choice is holding the grade down.
Who maintains the SSL Labs integration?
fastn does. When SSL Labs changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does an SSL Labs lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should SSL Labs results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. SSL Labs is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the SSL Labs integration?
A common starting point: assess a hostname on request and show the grade beside the certificate and protocol findings that produced it. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the SSL Labs integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding SSL Labs does not change your per-connector cost. You can start free with 3 connected accounts.
Add SSL Labs to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.