Answers that get you moving.

A one-time check shows a website’s state at that moment. Monitoring repeats checks on a schedule, records history and helps spot incidents while you are away.

Check reachability and the HTTP status first, then DNS records and the certificate. If the issue persists, save the time and result for your hosting provider.

Regular public NexIP checks do not require an agent on the target server. They use externally available network and web information, not private internal metrics.

NexIP helps check IP addresses, domains, DNS, Whois, HTTP headers, SSL, robots.txt, sitemap.xml and meta tags.

Public tools work without registration unless the site administrator has limited access.

Checks run from the NexIP installation server, so results depend on network, DNS cache and external service availability.

A monitor can check HTTP/HTTPS reachability, response status, latency and SSL/TLS health. Available signals depend on its type and settings.

The minimum interval is 60 minutes on Free, 10 minutes on Pro and 5 minutes on Business. Actual timing follows your monitor configuration and status.

Not always. A 200 status means the HTTP request succeeded, but the page may still show an application error or unexpected content. Consider a content check when supported by your plan.

A slow site still responds but takes longer than expected; an outage fails the configured check. Latency thresholds, retries and incident confirmation help distinguish them.

Review the monitor’s checks and incident history to compare the failure, confirmation attempts and recovery. Check frequency affects the precision of the recorded time.

In your account, connect Telegram in notification settings and enable it for the relevant monitor. Telegram alerts require Pro or Business; make sure the bot is not blocked.

Check incident confirmation, the enabled delivery channel, monitor assignment and alert suppression rules. Check your spam folder for email, and bot connectivity for Telegram.

Not necessarily. Retries and incident confirmation can reduce false alarms. The result depends on your monitor thresholds, schedule and alert delivery rules.

A webhook forwards monitoring events to another system, such as a team chat or incident processor. Validate the endpoint, failure handling and receiver security.

A maps a hostname to an IPv4 address, while AAAA maps it to IPv6. If a site supports both, check both: a broken IPv6 path can appear as intermittent downtime.

DNS caching, geographic routing, CDNs and different resolvers can return different addresses. After a DNS change, updates do not reach everyone at once.

Check the requested hostname against the certificate SAN, trust chain, and the specific server or CDN configuration. A valid date alone does not guarantee a trusted HTTPS connection.

301 is a permanent redirect, 302 a temporary redirect, 403 forbidden, 404 not found and 500 an internal server error. Also inspect the final URL and redirect chain.

Server IP filtering, geo restrictions, bot protection, DNS, IPv6 and network routes can affect external checks. Compare the exact URL, timestamp, response and firewall rules.

WHOIS shows domain registration details, registrar and domain status. DNS controls where web and email traffic goes. They are different sources used for different diagnostics.

A meta tag check inspects a single page, such as its title, description and canonical. An SEO audit evaluates more technical signals and may crawl multiple pages, subject to settings.

Check the HTTP status, robots.txt, meta robots, canonical and internal links. Even a technically valid page is not guaranteed to be indexed: search engines make the final decision.

A canonical tag suggests the preferred URL for similar content. Pointing it at the wrong page may confuse search engines and influence their selected canonical.

NexIP provides reports and check history. Export formats, limits and available options depend on your plan and check type. Scheduled account reports help with recurring reviews.

Create a key in your account, grant only the necessary permissions and treat it as a password. The full key is shown at creation time: store it securely.

Use the Authorization: Bearer header with your key. X-API-Key remains available for compatibility. Never put API secrets into public JavaScript or repositories.

Request allowances depend on your plan. Reduce request frequency or change plans as needed; handle rate-limit responses and retry with a suitable delay.

MCP lets compatible AI clients invoke published NexIP tools and operations through a common interface. Connection and capabilities depend on the client, authentication and permissions.

Yes. Free has no time limit and does not require a payment card to get started. It includes core checks and one monitor; current limits are listed on the pricing page.

Paid plans raise limits for checks and monitors, allow more frequent monitoring, longer history and additional notifications, reports and API capabilities. Compare the details before upgrading.

Your account shows subscription, limits and billing information. The public plan comparison explains what extra capabilities an upgrade provides.

Include the checked URL, exact time, observed result and expected behavior. Never send passwords, API keys, payment details or other secrets. Contact support@nexip.ru.