Pingzo Monitoring Bot & Probe Verification
If you are seeing traffic or automated socket handshakes originating from Pingzo in your server access logs, firewalls, or Web Application Firewall (WAF) analytics, a verified customer has configured an uptime, SSL, or network availability check for your domain or API endpoint. Pingzo operates a global fleet of distributed synthetic monitoring probes designed to verify that online services, web servers, and cloud infrastructure remain responsive, healthy, and accessible around the clock. Our monitoring requests are completely benign, read-only, and non-intrusive, designed to measure server latency and HTTP availability.
Our distributed probe network performs periodic lightweight HTTP HEAD and GET requests, TCP socket handshakes, DNS resolution lookups, and SSL/TLS certificate verifications. These synthetic checks evaluate response times, detect transient outages, monitor certificate expiration dates, and alert website owners when their critical applications experience downtime. We never execute automated vulnerability scans, brute-force authentication attempts, or data scraping. All probes respect standard HTTP protocols, consume minimal server bandwidth, and identify themselves clearly with our official user-agent header containing our probe verification URL.
To ensure network transparency and prevent unauthorized spoofing, all legitimate Pingzo probe requests originate from dedicated IP addresses with verifiable Reverse DNS (rDNS) hostnames pointing to probe.pingzoapp.com. System administrators and DevOps engineers can safely allowlist our monitoring IP addresses in firewall rules, Cloudflare, AWS Security Groups, or Fail2ban to prevent false positive alarms. If you manage a server and wish to verify an incoming IP address, inspect our verification records below or use the form to request probe opt-out or support.
Pingzo Monitoring Bot (www.pingzoapp.com/probe)probe.pingzoapp.comBlock Pingzo From Monitoring Your Infrastructure
Network administrators can immediately halt all synthetic probes. Submitting your hostname or IP address adds it to Pingzo's global exclusion table and automatically pauses any active checks.
pingzo-site-verification=...) in your DNS manager.Pingzo Synthetic Monitoring & Probe Architecture
Pingzo operates a globally distributed edge fleet of synthetic monitoring nodes. Our probes perform non-intrusive availability checks, TLS certificate handshakes, and DNS health audits on behalf of registered website owners and DevOps teams.
Non-Intrusive Availability Handshakes
Our synthetic probes never scrape data, inject payloads, or execute vulnerability scans. Probes issue standard HTTP/HTTPS HEAD or lightweight GET requests to measure socket latency, HTTP status codes, and TLS certificate expiration dates. Checks occur strictly at user-configured frequencies (1 to 15 minutes) and automatically respect backoff throttles.
Verifying Authentic Pingzo Probes
To verify whether an incoming request genuinely originates from our monitoring cluster, inspect the client IP via reverse DNS (rDNS). Authentic Pingzo monitoring requests resolve to hostnames ending with .probe.pingzoapp.com. Run host <IP> or dig -x <IP> in your terminal to confirm authentic DNS PTR records.
WAF & Firewall Whitelisting Guidelines
If your server utilizes Cloudflare, AWS WAF, or fail2ban, rate-limiting rules may inadvertently block synthetic health checks, causing false outage alerts. We recommend creating an allowlist rule matching our official User-Agent header Pingzo Monitoring Bot (www.pingzoapp.com/probe) or verified rDNS domain.
Abuse Reporting & Responsible Operations
We maintain zero tolerance for platform abuse. If you believe a Pingzo subscriber has targeted an unauthorized endpoint or if probe frequency exceeds acceptable network limits, use the instant opt-out form above to immediately block all checks, or contact our security team directly at security@pingzoapp.com.