1. Introduction
GlobalPing ("we," "us," or "our") provides a globally distributed network diagnostic and monitoring platform accessible at https://www.globalping.net (the "Service"). The Service offers powerful network diagnostic tools, including ICMP Ping, TCP Ping, HTTP/HTTPS Speed Test, MTR Traceroute, DNS Global Query, Port Scanner, CIDR Scanner, and IP Information Lookup.
These tools interact with real network infrastructure and third-party systems worldwide. As such, their use carries inherent responsibilities. This Acceptable Use Policy ("AUP") defines the rules and standards that all Users must follow when using the Service.
This AUP is incorporated into and forms part of our Terms of Service. Capitalized terms not defined in this AUP have the meaning given to them in the Terms of Service.
2. Agreement to This Policy
By accessing or using the Service, you agree to comply with this Acceptable Use Policy in its entirety. If you do not agree with any provision of this AUP, you must not use the Service.
We reserve the right to update this AUP at any time. Your continued use of the Service after any changes constitutes acceptance of the revised AUP.
3. General Use Principles
3.1 Authorized Access Only
You may only use the Service to test, diagnose, and monitor networks and systems that:
- You own or operate.
- You have been explicitly authorized to test by the owner or authorized administrator.
- Are publicly accessible services where the nature of the test does not constitute an unauthorized intrusion or excessive load.
3.2 Lawful Use
All use of the Service must comply with applicable local, national, and international laws and regulations. You are solely responsible for ensuring that your use of the Service is lawful in your jurisdiction and the jurisdiction of the target system.
3.3 No Harmful Intent
You must not use the Service with the intent to harm, disrupt, degrade, or impair the operation of any network, system, service, or device — whether operated by GlobalPing, other Users, or third parties.
3.4 Good Faith
You must use the Service in good faith for legitimate network diagnostic, troubleshooting, performance measurement, educational, or security research purposes.
4. Authorized Use of Network Diagnostic Tools
4.1 Permitted Purposes
You may use the Service's diagnostic tools for the following purposes:
- Network Troubleshooting: Diagnosing connectivity issues, latency problems, and packet loss on networks you are authorized to manage or monitor.
- Performance Monitoring: Measuring network performance metrics such as latency, throughput, DNS resolution time, and route quality for systems you are authorized to test.
- Service Availability Testing: Verifying the availability and responsiveness of web services, servers, and network endpoints you own or are authorized to monitor.
- DNS Configuration Verification: Checking DNS records, resolution paths, and global DNS propagation for domain names you own or manage.
- Network Inventory: Scanning your own network infrastructure to identify active hosts, open ports, and running services.
- Security Assessment: Conducting authorized security assessments and vulnerability scanning on systems where you have written permission from the owner.
- Quality-of-Service Measurement: Measuring and benchmarking network performance, service quality, and reliability metrics against established standards or across different providers and regions.
- Educational Purposes: Learning about network protocols, diagnostic methodologies, and internet infrastructure in a responsible manner.
- Route Analysis: Analyzing network paths, intermediate hops, and routing behavior using traceroute/MTR tools for networks you are authorized to test.
4.2 Authorization Requirement
Before initiating any diagnostic test against a target system, you must ensure that:
- You are the owner or authorized administrator of the target, or
- You have obtained explicit written permission from the owner or authorized administrator to conduct the specific type of test, or
- The test is directed at a publicly accessible service and the nature and volume of the test is consistent with normal, reasonable use and does not constitute an unauthorized scan or attack.
5. Tool-Specific Rules and Limits
The Service enforces technical limits on each diagnostic tool to promote responsible use. These limits are implemented to protect both the Service and third-party systems. You must not attempt to circumvent these limits.
5.1 ICMP Ping
- Supported Protocols: IPv4 and IPv6.
- Modes: Single test and continuous test modes.
- Rules:
- You must not use continuous ping mode to flood or burden a target system.
- You must not target systems that have explicitly opted out of ICMP responses or where such testing is prohibited.
5.2 TCP Ping
- Supported Protocols: IPv4 and IPv6.
- Modes: Single test and continuous test modes.
- Rules:
- You must only test TCP ports on systems you are authorized to test.
- You must not use TCP Ping to enumerate services on unauthorized systems.
5.3 HTTP/HTTPS Speed Test
- Allowed Methods: GET and HEAD only.
- Maximum Response Body: 2 MB (2,097,152 bytes).
- Rules:
- You must only test web services you own or have permission to test.
- You must not use the HTTP Speed Test to generate excessive traffic against a single target.
- You must not attempt to exploit vulnerabilities in the target web service through the speed test tool.
- You must not test targets that include authentication tokens, session cookies, or other credentials belonging to third parties.
5.4 MTR (My Traceroute)
- Maximum Hops: 5 to 64 (default: 20).
- Probe Count: 1 to 10 per hop (default: 3).
- Probe Timeout: 200 ms to 5,000 ms (default: 1,000 ms).
- Default Port: 443 (must be 1–65535).
- Rules:
- You must not use MTR data to target, attack, or compromise intermediate network devices or infrastructure.
- You must not run continuous MTR tests against a single target at a frequency that constitutes a burden on the network path.
- Route and AS/ISP information obtained through MTR must not be used for malicious purposes.
5.5 DNS Global Query
- Allowed Record Types: A, AAAA, CNAME, MX, NS, SOA, TXT, CAA.
- Allowed Protocols: UDP, TCP, DoT (DNS over TLS), DoH (DNS over HTTPS).
- Features: DNSSEC validation, EDNS subnet probing, expected IP anti-hijack detection.
- Rules:
- You must not use the DNS Query tool to enumerate or harvest DNS records for domains you do not own or have permission to query at scale.
- You must not use DNS query results to plan or execute DNS-based attacks (cache poisoning, amplification, etc.).
5.6 Port Scanner
- Maximum Ports: 10 ports per scan request.
- Valid Port Range: 1 to 65,535.
- Maximum Concurrency: 100 (default: 20).
- Features: Service fingerprinting, skip ping option.
- Rules:
- You must only scan systems you own or have explicit written authorization to scan.
- You must not use the Port Scanner to discover vulnerabilities on unauthorized systems.
- You must not scan ports on systems where the owner has explicitly prohibited scanning.
- Private IP addresses are strictly blocked — the Service will not scan private, reserved, or internal IP address ranges (see Section 9).
- You must not attempt to bypass the 10-port-per-scan limit by submitting multiple concurrent scan requests against the same target.
5.7 CIDR Scanner
- Supported Protocol: IPv4 only.
- Allowed Prefix Length: /21 to /32 (default: /24).
- Maximum Concurrency: 256 (default: 128).
- Probe Options: ICMP and TCP probes.
- Auto-Detection: Partial IP addresses are auto-completed to CIDR notation (e.g.,
1.2.3 becomes 1.2.3.0/24).
- Rules:
- You must only scan network ranges you own or have explicit written authorization to scan.
- CIDR scanning has a higher potential impact on network infrastructure. You must ensure that the target network can accommodate the scanning traffic.
- Private CIDR ranges are strictly blocked (see Section 9).
- You must not use CIDR scanning results to build inventories of unauthorized network assets.
- You must not use CIDR scanning for network reconnaissance as part of a planned attack.
5.8 IP Information Lookup
- Supported Protocols: IPv4 and IPv6.
- Data Provided: Geolocation (continent, country, region/province, city, district), ISP information, geographic coordinates, ASN data, time zone, and postal code. Data is approximate and sourced from local geolocation databases.
- Rules:
- IP geolocation data is approximate and must not be used to physically locate or identify individuals.
- You must not use IP information to stalk, harass, or target individuals.
6. API Usage Rules
6.1 API Access
GlobalPing provides a public API for programmatic access to the Service's diagnostic tools. All rules in this AUP apply equally to API usage.
6.2 API-Specific Requirements
- Authentication: API access may require authentication credentials. You must keep your credentials confidential and must not share them with third parties.
- Rate Limits: You must comply with any rate limits imposed by the API. If rate limits are not explicitly documented, you must not submit requests at a frequency that could impair the Service's availability to other Users.
- Fair Use: API usage must follow fair use principles. You must not:
- Submit automated requests at excessive rates.
- Use the API to build a competing product or service without written permission.
- Aggregate, scrape, or mine data obtained through the API for purposes unrelated to legitimate network diagnostics.
- Reverse engineer, decompile, or disassemble the API.
- Token-Based Authentication: The Service uses cryptographic token-based authentication for WebSocket connections and task submission. You must not attempt to forge, replay, or intercept these tokens.
6.3 Automated Tools and Scripts
- You may use automated tools or scripts to access the Service through the documented API, provided such use complies with this AUP and does not place excessive load on the Service or target systems.
- You must not use automated tools to access Service features not exposed through the documented API (e.g., scraping web pages).
- You must implement reasonable delays between automated requests to avoid overloading the Service.
7. Agent Contribution Rules
7.1 Agent Participation
Users who contribute agent nodes to the GlobalPing network must comply with the following rules in addition to the general rules in this AUP. Agent nodes connect to the GlobalPing infrastructure through middleware nodes, which serve as intermediary dispatchers responsible for routing diagnostic tasks to the appropriate agents.
7.2 Agent Operation Standards
- Authorization: You must be the owner or authorized administrator of the hardware and network on which the agent operates.
- Security: You must maintain the security of your agent node and prevent unauthorized access. This includes keeping the agent software up to date.
- Data Integrity: You must not interfere with, modify, tamper with, or falsify diagnostic test operations or results processed by your agent.
- No Data Harvesting: You must not monitor, log, intercept, or collect data about the tests executed through your agent beyond what is necessary for normal operation.
- Compliance: Your agent must operate in compliance with all applicable laws and regulations in the jurisdiction where it is located.
- Honest Reporting: Your agent must report accurate system information (CPU, memory, network capabilities). Falsifying system information is prohibited.
7.3 Agent Restrictions
- You must not use your agent to execute tests that violate this AUP.
- You must not configure your agent to preferentially route, block, or manipulate test traffic based on target, source, or content.
- You must not use your agent to inject malicious content, responses, or data into test results.
- You must not deploy agents on compromised systems or systems infected with malware.
8. Prohibited Activities
The following activities are strictly prohibited when using the Service. This list is non-exhaustive, and we reserve the right to determine, in our sole discretion, whether any activity constitutes a violation.
8.1 Network Abuse
- Unauthorized Scanning: Scanning, probing, or testing any network, system, or device without proper authorization.
- Denial of Service: Launching, facilitating, or contributing to any form of denial-of-service (DoS) or distributed denial-of-service (DDoS) attack, including bandwidth flooding, connection exhaustion, or resource depletion attacks.
- Network Intrusion: Attempting to gain unauthorized access to any system, network, device, account, or data through the use of the Service.
- Traffic Interception: Intercepting, monitoring, or capturing network traffic that does not belong to you without authorization.
- Excessive Testing: Conducting tests at a volume or frequency that places undue burden on target systems, intermediary networks, or the GlobalPing infrastructure.
8.2 Security Violations
- Exploitation: Attempting to exploit, test for, or validate vulnerabilities on systems you are not authorized to test.
- Brute Force: Using the Service to perform brute force attacks against authentication systems, services, or protocols.
- Malware Distribution: Using the Service to distribute, deliver, or facilitate the distribution of malware, ransomware, or other malicious software.
- Bypassing Security: Attempting to circumvent any security measures implemented by the Service, including rate limits, IP blocking, input validation, private IP protections, or access controls.
- Token Abuse: Forging, replaying, intercepting, or improperly obtaining authentication tokens, session credentials, or API keys.
8.3 Data Misuse
- Data Harvesting: Using the Service to collect, aggregate, or mine network intelligence data, IP address information, or infrastructure details at scale for purposes unrelated to legitimate diagnostics.
- Privacy Violations: Using IP geolocation or other data obtained through the Service to identify, locate, contact, or stalk individuals.
- Surveillance: Using the Service for unauthorized surveillance or monitoring of third-party networks or communications.
- Competitive Intelligence: Systematically collecting data about competitors' network infrastructure without authorization.
8.4 Service Abuse
- Resource Abuse: Consuming excessive Service resources (bandwidth, CPU, agent capacity) to the detriment of other Users.
- Circumventing Limits: Attempting to bypass the technical limits enforced by each diagnostic tool (port count limits, CIDR range limits, concurrency limits, etc.).
- Reselling Access: Reselling, sublicensing, or redistributing access to the Service without prior written consent from GlobalPing.
- Impersonation: Misrepresenting your identity or affiliation when using the Service or communicating with target system administrators.
- Automation Abuse: Using bots, scripts, or automated tools to access Service features in ways not intended or documented.
- Third-Party Policy Violations: Violating the acceptable use policies, terms of service, or usage guidelines of any network, system, or service you interact with through the Service.
8.5 Targeting Restricted Systems
- Critical Infrastructure: Targeting government systems, emergency services, healthcare infrastructure, financial systems, power grids, or other critical infrastructure without explicit authorization.
- Military Systems: Targeting military or defense-related networks or systems.
- Educational Institutions: Unauthorized scanning or testing of educational institution networks.
- Third-Party Cloud Services: Scanning or testing third-party cloud hosting providers' infrastructure in ways that violate their acceptable use policies.
8.6 Legal Violations
- Using the Service in violation of any applicable local, national, or international law or regulation.
- Using the Service to violate export control laws, sanctions, or trade restrictions.
- Using the Service to facilitate any form of illegal activity.
9. Private and Reserved IP Address Restrictions
9.1 Blocked IP Ranges
The Service enforces technical protections to prevent scanning and testing of private, reserved, and internal IP address ranges. The following ranges are strictly blocked and cannot be used as diagnostic targets:
| Range | Description |
|---|---|
| 10.0.0.0/8 (10.0.0.0 – 10.255.255.255) | Private network (RFC 1918) |
| 172.16.0.0/12 (172.16.0.0 – 172.31.255.255) | Private network (RFC 1918) |
| 192.168.0.0/16 (192.168.0.0 – 192.168.255.255) | Private network (RFC 1918) |
| 127.0.0.0/8 (127.0.0.0 – 127.255.255.255) | Loopback addresses |
| 0.0.0.0/8 (0.0.0.0 – 0.255.255.255) | Current network |
| ::1 (IPv6) | IPv6 loopback |
| fc00::/7 (fc00:: – fdff:ffff:... ) | IPv6 unique local addresses |
| fe80::/10 (fe80:: – febf:ffff:... ) | IPv6 link-local addresses |
9.2 No Circumvention
You must not attempt to bypass, circumvent, or defeat the private IP blocking protections through any means, including but not limited to:
- Using DNS resolution to redirect public hostnames to private IP addresses.
- Encoding or obfuscating IP addresses to evade detection.
- Exploiting input validation to submit private IP ranges.
- Using intermediary services or proxies to route traffic to private networks.
9.3 Exceptions
If you are the authorized administrator of a private network and need to test internal infrastructure, you must use internal diagnostic tools within your own network. The Service is designed for testing publicly accessible networks and systems only.
10. Security Responsibilities
10.1 Your Responsibilities
As a User of the Service, you are responsible for:
- Ensuring that all diagnostic tests you initiate comply with this AUP and applicable laws.
- Understanding the potential impact of your tests on target systems and intermediary networks.
- Responding promptly and in good faith to any complaints or inquiries from target system administrators.
- Protecting any account credentials, API keys, or authentication tokens associated with your use of the Service.
- Reporting any security vulnerabilities or abuses discovered through the use of the Service to GlobalPing.
10.2 Our Responsibilities
GlobalPing is responsible for:
- Implementing and maintaining technical safeguards to prevent abuse (input validation, private IP blocking, parameter limits).
- Monitoring the Service for signs of abuse or policy violations.
- Taking prompt action to address verified violations of this AUP.
- Maintaining the security and availability of the Service infrastructure.
10.3 Incident Response
If a target system administrator or third party reports that diagnostic tests originating from GlobalPing are causing disruption or concern:
- We will investigate the report and may contact you for clarification.
- We may temporarily restrict the reported test pending investigation.
- If the test is found to be in compliance with this AUP, we will communicate this to the reporting party.
- If the test is found to be in violation, we will take enforcement action as described in Section 11.
11. Enforcement and Consequences
11.1 Monitoring
We monitor the use of the Service to detect violations of this AUP. Monitoring may include:
- Reviewing test patterns for indicators of unauthorized scanning or abuse.
- Analyzing request volumes for excessive or anomalous activity.
- Responding to complaints from third parties regarding tests initiated through the Service.
11.2 Enforcement Actions
If we determine, in our sole discretion, that you have violated this AUP, we may take one or more of the following actions:
- Warning: Issuing a formal warning and requiring you to cease the violating activity.
- Content Removal: Removing any offending content, data, or test results that violate this AUP.
- Temporary Suspension: Temporarily suspending your access to the Service or specific features.
- Rate Limiting: Imposing additional rate limits or restrictions on your use of the Service.
- Permanent Ban: Permanently terminating your access to the Service.
- Agent Removal: Removing contributed agent nodes from the GlobalPing network.
- Legal Action: Referring the matter to law enforcement or pursuing legal action where appropriate.
11.3 Appeals
If you believe that an enforcement action was taken in error, you may appeal by contacting us using the information provided in Section 14. We will review your appeal in good faith and respond within a reasonable timeframe.
11.4 No Liability for Enforcement
We are not liable for any damages resulting from our enforcement of this AUP, including but not limited to loss of access, data, or test results.
12. Reporting Abuse
12.1 Reporting Violations
If you become aware of any violation of this AUP or any misuse of the Service, please report it to us immediately using the contact information provided in Section 14. Please include as much detail as possible, including:
- The nature of the violation.
- The IP address, hostname, or target involved.
- The approximate date and time of the violation.
- Any relevant logs, screenshots, or other evidence.
12.2 Reports from Third Parties
If you are a system administrator or network operator who has received unwanted diagnostic traffic from GlobalPing:
- We take such reports seriously and will investigate promptly.
- Please provide the source IP addresses of the traffic, timestamps, and the nature of the tests observed.
- In many cases, the traffic may have been initiated by a User testing a network they believe they are authorized to test. We will work to resolve the matter with the User.
- If the traffic constitutes a violation of this AUP, we will take appropriate enforcement action.
12.3 Good Faith Reporting
We encourage good faith reporting of potential violations. However, submitting knowingly false or malicious reports is itself a violation of this AUP and may result in enforcement action against the reporter.
13. Changes to This Policy
We reserve the right to modify this AUP at any time at our sole discretion. Changes will be effective immediately upon posting the revised AUP on the Service.
We will make commercially reasonable efforts to notify Users of material changes by:
- Posting the updated AUP with a revised "Last Updated" date.
- Providing a prominent notice on the Service for significant changes.
Your continued use of the Service after any changes to this AUP constitutes acceptance of the revised policy.
14. Contact Information
If you have questions about this Acceptable Use Policy, wish to report a violation, or need to appeal an enforcement action, please contact us:
For abuse reports or urgent security matters, please include "Abuse Report" or "Urgent Security" in the subject line or heading of your communication.
By using GlobalPing, you acknowledge that you have read, understood, and agree to comply with this Acceptable Use Policy.
GlobalPing — https://www.globalping.net
