Skip to content

HTTP/SSL

HTTP response headers and security signals

Inspect response headers and the presence of common browser security directives.

Run check

Проверка выполняется с сервера NexIP и повторно проверяет адрес после DNS и редиректов.

POST
Examples:

What the check covers

Reads response headers and marks basic security headers.

How to read the result

Evaluate header presence and values in the context of the application.

Limitations

One header set cannot prove that the whole site is secure.

Example

A target you can check

https://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

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