Live SSL, domain and vulnerability badges for your README

A README badge is a tiny image that tells a visitor something at a glance: the build passes, the licence is MIT, the package is current. Most badges show the state of your code. These show the state of the things around it that quietly expire.

Three badges

• SSL expiry: days left on the certificate your site presents. Green above 30 days, yellow from 8 to 30, red at 7 or less.
• Domain expiry: days left on the domain registration, with the same colours.
• Vulnerabilities: for an exact npm or PyPI version, none known in green, or the number of known advisories in yellow, or red when one is high or critical.

Add one

Use the badge generator, or write the Markdown yourself:

[![SSL expiry](https://ambolt.dev/badge/ssl/example.com.svg)](https://ambolt.dev/tools/ssl-certificate-checker)
[![Domain expiry](https://ambolt.dev/badge/domain/example.com.svg)](https://ambolt.dev/tools/domain-expiry-checker)
[![Vulnerabilities](https://ambolt.dev/badge/vulns.svg?ecosystem=npm&name=lodash&version=4.17.20)](https://ambolt.dev/tools/npm-vulnerability-checker)

The image is generated on request and cached for a few hours, so embedding it is cheap and the badge follows the real state without any work on your side.

Why a badge for this

An expired certificate or a lapsed domain is an outage you can see coming. A red badge on the README or the status page of an internal tool is a reminder that does not depend on anyone remembering. For dependencies, a vulnerability badge for the version you pin keeps the question in front of the team.

Limits

The badges are informational: no known advisory is not proof of safety. Only public domains and packages are checked, and the number of requests per address is limited. If you need the numbers in code, the same data is available from the SSL and domain expiry API and the vulnerability API.