FOR YOUR TERMINAL / CLI + API · 4 MIN READ

Your Public IP. Your TLS Report.

A terminal request to the home page returns your source IP and one newline. For a certificate snapshot, use the read-only JSON endpoint with one hostname.

No API KeyIPv4 + IPv660 Requests / Minute

curl: Just the Domain

Terminal

curl aboutssl.info

The bare command uses HTTP. Use the encrypted HTTPS version when possible:

Terminal

curl -fsS https://aboutssl.info

A Stable Plain-text Endpoint

Terminal

curl -fsS https://aboutssl.info/ip

/ip always returns plain text. curl -4 or curl -6 chooses your connection family when your network supports it.

PowerShell

(Invoke-RestMethod -Uri 'https://aboutssl.info/ip').Trim()

Public IP as JSON

Terminal

curl -fsS https://aboutssl.info/api/ip

The response contains ip and numeric version. It is the source seen by this request, not a verified device identity or location.

Check a Public TLS Certificate

TLS Report / JSON

curl -fsS "https://aboutssl.info/api/check?target=aboutssl.info"

PowerShell / TLS Report

$report = Invoke-RestMethod -Uri 'https://aboutssl.info/api/check?target=aboutssl.info'
$report.leaf | Format-List subject, issuer, validTo, daysRemaining
$report.checks

Use exactly one target hostname. URLs, ports, IP literals, uploads and private destinations are not accepted. The server resolves public DNS and makes one pinned-address TLS handshake on port 443. It prefers IPv4 when available; the report names the chosen endpoint.

Read the Report Fields

Field	Meaning
`leaf`	Subject, issuer, SANs, dates, remaining days, fingerprint and public-key details.
`checks`	Hostname match, time validity and chain authorization are separate booleans.
`chain`	The path exposed by the TLS library, up to eight certificates.
`endpoint`	Selected public address, family, answer count and DNS resolver.
`protocol / cipher`	What this connection negotiated, not a scan of everything supported.
`status`	`checks-passed`, `renew-soon` (under 30 days), or `review`. Read the booleans and limitations.

Limits and Errors

Each source IP gets 60 HTTP requests per site in any rolling 60 seconds. Pages, assets, plain text, JSON, errors and HEAD requests share that allowance. Upstream certificate checks have a separate 6-unit rolling allowance; one attempted check costs one unit, including failures. Both budgets must permit the request.

HTTP 400 means invalid input, 405 an unsupported method, 429 a request/lookup or concurrency limit, and 502 an incomplete DNS/TLS check. Wait for Retry-After on 429. Do not retry in a tight loop. X-RateLimit-Limit and X-RateLimit-Remaining show the shared HTTP budget.

A 200 certificate report can contain failed certificate checks; inspect the body rather than treating HTTP success as a trusted certificate. Responses are not cacheable. There is no uptime guarantee, API key, certificate issuance or private-key conversion endpoint.

Do the Certificate Work Locally

The OpenSSL, PowerShell, conversion and complete PFX recipes run on your machine. ABOUTSSL never receives those files or passwords.