Skip to content
devtls

Scans & history

Start a scan from a domain’s row or its detail page. The scan is queued, then running, then success or failed; the page follows it as it goes. Most scans take a few seconds. A failed scan means devtls couldn’t complete it — the host didn’t resolve, nothing answered, or the TLS handshake broke — and the reason is shown.

To keep the scanner from being used as a probe, each organization can start about 10 scans a minute. Past that, devtls answers 429 with a Retry-After header.

devtls re-scans every domain on its own, so history fills in without you:

Plan Every
Free week
Pro, Team, Founder day

Scheduled scans count toward your monthly allowance like any other.

A deep scan also asks SSL Labs for its grade and shows it beside devtls’s. It’s slower — SSL Labs runs its own full test — and it never changes devtls’s score. Use it as a second opinion, especially when a legacy protocol is reported as not tested. Deep scans need a paid plan.

By default devtls records the cipher suite your server chooses. Enumeration walks every suite the server would accept for each TLS version up to 1.2, which catches a weak suite still allowed as a fallback even though a strong one is preferred. It takes many extra handshakes, so it’s opt-in per scan (?ciphers=1 on the API).

Scans run in order. On Team, your scans go ahead of others’ in a priority queue.

Every scan is kept with its full result, so a domain’s page shows its grade and score over time — and exactly which scan a change appeared in.

Plan History kept
Free 30 days
Pro 1 year
Team, Founder unlimited
  • Grade and score — see Web TLS grading for every rule.
  • Per-address results — when a name has several addresses, each one’s protocols and cipher are listed. The grade uses the worst one.
  • Fixes — each with a severity (high, medium, low), a title such as Disable TLS 1.0, and the reason. Fix from the top.