Understand the alert.
Know what to do next.

Forgot your password, missed your invitation, or never completed your first login? Use the same account recovery form.

1. Enter the email address used for your 777pinger account.
2. If you receive an invitation with a temporary password, use the newest one on the Set your password page, then continue to sign in.
3. If you receive a six-digit code, enter it on the recovery form with your new password. An unverified email address needs confirmation first; the form will guide you through a second code if needed.
4. Allow a few minutes for delivery, check junk or quarantine, and contact support if nothing arrives. Repeated requests are temporarily limited.

Recovery does not change your plan, team access, or optional MFA. Never share your password or email code with support.

What it means: The website responded, but 777pinger did not find enough of the six recommended browser protections. An older alert such as “Security headers: 0/6 present” means none were visible in that response. It does not mean the site was hacked or offline.

What to do

1. Run the check again to confirm the result.
2. Ask your web host or developer to review HSTS, Content-Security-Policy, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, and clickjacking protection.
3. Add headers at the web server, application, load balancer, or CDN—wherever public responses are created.
4. Test important pages after the change, especially login, payment, embedded-content, and admin pages.

Content-Security-Policy can break legitimate scripts when added too aggressively. Have the person who manages the website introduce and test it carefully.

What it means: The site timed out or returned an HTTP response outside the successful 200–299 range.

What to do

1. Open the exact monitored address in a browser.
2. Run the check again and note the HTTP code or timeout message.
3. Review your hosting status, application logs, and recent deployments.
4. If only one page fails, check that page’s route, redirects, and permissions.

What it means: The HTTPS connection could not be trusted, the certificate did not match the hostname, or the site did not respond correctly over HTTPS.

What to do

1. Open the HTTPS address and inspect the browser’s certificate warning.
2. Confirm the certificate covers the exact hostname, including www or other subdomains.
3. Renew or reinstall the certificate through your host, CDN, or load balancer.
4. Run the check again after the updated certificate is publicly available.

What it means: The first website response took longer than the monitor’s current two-second limit. This is server response time, not a full browser performance score.

What to do

1. Run the check again to see whether the slowdown was temporary.
2. Review server load, database calls, external APIs, and recent releases.
3. Enable appropriate caching and check CDN behavior.
4. Watch the history before changing the limit so a real trend is not hidden.

What it means: The address responded, but the result did not look like a complete page. It may be an error page, redirect, login screen, or partial deployment.

What to do

1. Open the exact monitored address in a private browser window.
2. Confirm the page is available without signing in.
3. Check redirects and make sure the final page contains a normal title and body.
4. Review application logs if the page is blank or incomplete.

What it means: The endpoint returned an unsuccessful HTTP code, timed out, or did not provide valid JSON.

What to do

1. Call the health endpoint using the same public address.
2. Review the returned HTTP code and response body.
3. Check API, dependency, and database logs for the alert time.
4. Use a small public health endpoint that does not require secrets in its URL.

What it means: The public resolver could not complete the lookup, the hostname did not exist, or it returned none of the supported DNS records. Subdomains do not need their own NS records to pass.

What to do

1. Confirm the hostname and the domain’s nameservers at the registrar.
2. Review the relevant A, AAAA, CNAME, MX or NS records with your DNS provider.
3. Check for recent changes and allow time for cached answers to expire.
4. Review the latest check details and try again after public resolvers update.

DNS health is separate from website uptime. A valid DNS response does not prove the website or mail server is available.

What it means: DNS history starts automatically for public hostnames used by your monitors. Business and Enterprise include it; Pro offers a $10/month paid add-on. Monitors using the same hostname share one history, without using an extra monitor slot. Basic DNS health checks remain available without the add-on.

What to do

1. Add your normal website, SSL, DNS or other public-hostname monitor. No separate DNS-history monitor is needed. example.com and www.example.com have separate histories; different URLs on the same hostname share one.
2. Open any monitor for that hostname to view DNS records and changes. Automatic snapshots run about every 15 minutes on Business and Enterprise, or hourly with the Pro add-on, while at least one reference is active. Allow a short delay for the first result. Earlier records cannot be reconstructed.
3. Expand a change to compare added and removed records. Refresh saved records reloads the view without running another lookup. Confirm unexpected changes with your DNS provider.
4. History stays while any monitor references that hostname, including paused monitors. Deleting or changing the last reference shows a warning: continuing removes that hostname’s saved records and history from the workspace. Adding it again starts fresh. Backups expire under the backup-retention policy.

Captures A, AAAA, CNAME, MX, NS, TXT and CAA for the exact hostname, including returned aliases—not a complete zone or every subdomain. IP addresses, heartbeat addresses and private-agent targets are excluded; private names are never sent to the public DNS resolver. Up to 20 changes are retained within 30 days, subject to storage limits. Old snapshots expire too. TTL countdown and record order are ignored; failed or incomplete lookups preserve the previous snapshot. DNS changes do not affect website uptime or send outage emails.

What it means: Import monitors adds a pasted list or CSV in one reviewed batch. It works with or without dashboard filters; it adds new monitors and does not edit existing ones.

What to do

1. Choose Import monitors next to Add monitor. Paste one target per line, or select a CSV with a Target column. Name, Check type and Interval (minutes) are optional columns.
2. Select the checks to create for each target. A CSV row with a Check type overrides this selection. Use HTTPS URLs for websites, IPv4 addresses for private ping, and host:port for private service checks.
3. Choose a frequency and optional groups. Private targets require an active private agent and permission to manage it. Public checks use your workspace locations.
4. Review the preview. Duplicates are skipped, invalid rows must be fixed, and frequencies are raised to the applicable plan or check-type minimum.
5. Confirm Add monitors. The entire new batch must fit your remaining plan slots. A workspace change may require a fresh preview; no partial batch is added.

Up to 1,000 checks and 128 KB per import, within your existing plan limits. Each check uses one monitor slot. Imports do not buy add-ons or upgrade your plan. Allow a short delay for scheduling and first results. Only import systems you own or are authorized to monitor.

What it means: 777pinger could not find both an SPF record and a DMARC policy for the email domain.

What to do

1. Confirm there is exactly one SPF TXT record at the root domain.
2. Confirm a DMARC TXT record exists at _dmarc.yourdomain.com.
3. Check that included mail services and reporting addresses are correct.
4. Send a test message and review its authentication results after DNS updates.

Changing SPF, DKIM, or DMARC can affect mail delivery. Use the exact values supplied by your email provider.

What it means: The public registry date shows that the domain is approaching renewal.

What to do

1. Sign in to the registrar that holds the domain.
2. Confirm auto-renewal is enabled and the payment method is current.
3. Verify the registrant email can receive renewal notices.
4. Renew early when the domain is important to websites or email.

What it means: 777pinger did not receive the expected success signal from a backup, import, or scheduled task on time.

What to do

1. Check whether the job ran and completed successfully.
2. Review its logs for an error or unusually long run.
3. Confirm the job calls its unique 777pinger ping URL only after success.
4. Adjust the expected schedule if the job legitimately needs more time.

A private agent is a small program you run on an always-on computer inside your office or private network. It can check whether a selected service accepts a connection on its expected port, such as a server on port 443. The Windows agent can also ping a single IPv4 address, such as your router, using agent version 0.3.0 or newer. It does not inspect page content or prove that an application is working correctly after connecting.

Why a separate agent for each location?

Each agent checks from that network’s point of view. An Ohio office agent can reach Ohio’s private servers without exposing them to the internet, and a separate data-center agent helps you tell a local problem from a wider outage. One per separate network is a good starting point. Additional agents are not automatic failover; each monitor uses its assigned agent.

Signed Windows 11 x64 installer

Download the signed Windows installer and read its requirements. It includes Node.js, saves the local connection encrypted, and adds a startup task. Extract the whole ZIP, verify publisher 777 Easy LLC, and follow START-HERE.md for installation and the separate startup-safeguard step. Use a new location’s token only in the hidden local prompt. Confirm Connected and fresh saved results afterward.

Keep the PC awake and online. Reboot followed by manual Windows sign-in has been tested; pre-login, signed-out operation and sleep/wake are not qualified. Updates are manual. Review the download page’s maintenance limitation before installation. Do not bypass Windows security warnings or replace an existing working location just to try the installer.

Manual foreground setup

1. Use an active Pro, Business, or Enterprise plan. Open Private agents, name your location, and create its agent.
2. Save the one-time token securely. Download the agent and install Node.js 22 or later on a computer that stays on in that network. No inbound firewall port is needed; allow outbound HTTPS to app.777pinger.com and access to only the services you intend to check.
3. On Windows, use the guided steps in Private agents. Download both the agent and Windows starter into the same folder. The starter checks for Node.js and prompts privately for your token; do not paste the token into a command. It starts a foreground connection test, not an automatic Windows service. Follow your organization’s script policy.
4. Leave the program running. Connection status refreshes while the Private agents page is visible. Look for Connected, then add a Local port or service monitor, choose this location, and enter the host and port, for example server.local:443. Connected means the agent checked in, not that every monitored service is healthy.
5. Allow a short delay after changes. Checks follow your plan’s schedule. The initial command runs only while that computer and program remain running; arrange a supervised service or startup task before relying on it unattended.

The Windows starter runs assigned ping and service-port checks only. It does not enable subnet discovery, install at startup, save the token to disk, or change firewall rules. Keep an existing working service in place; do not start a second copy for the same location. Arrange supervised startup before relying on unattended checks.

Ubuntu 24.04 x64 installer

Download the Ubuntu 24.04 x64 installer and follow its guided setup. It includes Node.js, prompts privately for the token, and creates an encrypted-credential startup service. Verify the archive against the checksum on the official HTTPS page before extracting; the Linux package is not publisher-signed. TCP checks only, with manual updates. Confirm Connected and a fresh saved result afterward.

Router and internet checks

Add a Device or internet ping monitor for your router and another for an internet address you are allowed to check. Choose your Windows agent for both. A reply means that address was reachable from that computer at that time; it does not test DNS resolution, website content, or every internet destination. Ping may be blocked even when a device is working.

Turn on “Alert if this agent stops checking in” for the location. After five minutes without a check-in, the cloud shows a warning and emails the outage recipients selected in Notifications. A reconnect message uses your recovery recipients. Allow a short delay. Existing locations keep this option off until you enable it; it requires active paid private-monitoring access. Connection health does not change device check frequencies or use another monitor slot.

If the PC cannot reach 777pinger, it cannot upload fresh router or internet results. A sleeping PC, stopped agent, lost Wi-Fi, router problem, or internet outage can all cause the same missing check-in. Treat old green device results as historical, not a diagnosis. Check the PC and local network before deciding the router is down. Reconnection clears the connection warning; device results update on their normal schedule.

If a check fails

1. Confirm the agent computer is on and the location is Connected. If the agent itself is offline, new checks cannot run; do not treat an older green result as proof the service is still reachable.
2. Check that the service is running on the expected host and port, and that the local firewall allows the agent to reach it.
3. After restoring the service or network path, wait for the next check. A successful result resolves the open incident. Choose alert recipients under Notifications.

Updating a manual foreground agent? Stop it, download the latest agent (0.3.1), and restart with the same token. Version 0.3.1 adds private token input for the Windows starter; existing 0.3.0 installations do not need to change to keep their current checks running. For an agent installed with the signed package, use its SUPPORT.md and separate Maintenance launcher instead—do not copy program files into the installation. If a token is exposed, revoke the location immediately; this stops its access and pauses its assigned monitors.

What it means: An optional, cookie-free view of which page paths people open, their referrer domain and country, device category, and real page-load timing. It does not save query strings or raw visitor IP addresses.

What to do

1. Open Integrations, then add the website name and domain under Visitor insights.
2. Copy the generated tracking line and place it in the website header.
3. Visit a page on the website, wait up to five minutes, then press Refresh.
4. Use the website selector to compare one site with the combined view.
5. To provide a privacy opt-out, have your site’s privacy control call pingerInsights.optOut(). Calling pingerInsights.optIn() allows future page views again.

The script automatically skips browsers with Do Not Track or Global Privacy Control enabled. Deleting a tracked website from 777pinger also deletes its collected events. Describe this measurement in your own privacy notice and obtain consent where required.

What it means: Send monitor failures and recoveries to your team’s chosen channel. The Integrations page includes service-specific setup instructions and troubleshooting.

What to do

1. Open Integrations and choose Slack, Discord, Microsoft Teams or Generic HTTPS webhook. Follow the guide to create a private webhook address.
2. For Discord, use a standard text channel. For Teams, use a Workflows incoming webhook allowed by your organization, not an old Office connector; add a co-owner for continuity.
3. Paste the complete private address into the hidden URL field and name the destination. New Discord and Teams destinations start paused.
4. Choose Send test, then check the intended channel for the [TEST] message. An accepted request alone does not prove the message appeared—especially with Teams workflows.
5. Enable the destination. In Monitors, use the alert icons for one monitor or bulk alert-channel controls for several. Discord and Teams start off on existing monitors; enabling a destination does not change those choices.
6. If an address is exposed, pause and delete it here, then replace or revoke it with the provider. Never share webhook addresses with support.

Saved addresses are encrypted and never returned to your browser. Tests can send while a destination is paused, with workspace limits of one per minute and ten attempts per hour. Each enabled destination of a type receives alerts from monitors allowing that type. Existing duplicate/rapid-change safeguards still apply. Network-discovery changes remain email-only, and SMS schedules do not apply to chat integrations.

What it means: Business and Enterprise include SMS access. Pro offers a $10/month text-alert add-on. Access starts only after payment is confirmed; buying access does not verify a phone or consent on its owner's behalf.

What to do

1. Open Settings → Plan and billing to check your access. If needed, review and complete payment for the add-on or plan. Refresh after payment is confirmed.
2. Open Notifications → Text-message alerts. Enter a name and mobile number including the country code. Request a code only with the phone owner's permission; read and confirm the separate permission and privacy notices.
3. Choose 24/7, or custom days and hours in the recipient's time zone. With custom hours, choose whether to skip outside-hours alerts or send them when the next allowed window starts.
4. Select Send verification code, then enter the six-digit code on 777pinger and choose Verify and enable texts. Codes expire after 10 minutes and allow five guesses. Never send the code to support.
5. Choose the recipient's alert categories. On Monitors, use the alert-channel controls for one monitor or select several for a bulk change. The recipient and the monitor must both allow texts.
6. Use Set text hours to change the saved schedule, or pause the recipient to stop alerts. Check the safety allowance in Notifications; long messages and failed attempts can consume multiple reserved units.

Reply STOP to block 777pinger texts. START allows fresh setup but does not restart alerts: request and verify a new code with permission. Resend waits increase from 1 minute to 15 minutes, 1 hour, 24 hours and then 7 days; account and request-source limits also apply. Unchanged outages do not generate repeated reminders. Rapid status changes temporarily pause a monitor's notifications and are shown in the dashboard; checks continue. Delayed texts combine changes per monitor and expire after 8 days. Texts pause at workspace or service-wide safety limits, while configured email alerts can continue. Message and data rates may apply. Network-discovery change notices remain email-only.

What it means: MFA adds a one-time code from an authenticator app after your password. It is optional for each 777pinger account.

What to do

1. Open Settings and find Authenticator MFA.
2. Choose Set up authenticator and scan the QR code with your authenticator app.
3. Enter the six-digit code to confirm setup.
4. Keep your current session open, then test one new sign-in before closing it.
5. Save the authenticator account in your app’s encrypted backup if that option is available.

If you lose the authenticator account, email support@777pinger.com. We will verify account ownership before resetting MFA. A password reset by itself does not remove MFA.