Skip to content

HTTP/SSL

SSL certificate and TLS connection check

Inspect certificate trust, host names, validity dates, issuer and negotiated protocol.

Run check

Путь URL будет отброшен, а проверка сертификата выполнится для имени хоста.

POST
Examples:

What the check covers

Opens a TLS connection and inspects trust, names, dates, issuer and protocol.

How to read the result

The certificate must be trusted, current and match the requested host.

Limitations

The check covers the selected host and does not audit all application security.

Example

A target you can check

example.com

Use your own public address to get a result relevant to your configuration.

Privacy

What is processed

The check processes the submitted public target on the NexIP server. Do not submit secrets, tokens or private addresses.

Privacy policy

When to use it

Before launch and during incidents

Run the check after a configuration change, when diagnosing an outage, or before publishing a new service.

Questions about this check

What does “expires soon” mean?

NexIP marks a certificate as expiring soon when it has 14 days or fewer left.

Does NexIP store check results?

The CMS stores technical check history in the database so administrators can analyze errors, load and tool usage.

Why can results differ from another service?

Checks run from the server where NexIP is installed. DNS, HTTP, SSL and Whois results can depend on network, cache, region and external service availability.

Need recurring checks and incident history?

Create a monitor and receive notifications when the state changes.

Set up monitoring