Acceptable Use Policy

1. Monitor what is yours

You may create monitors only for websites, hosts and services that you own, operate, or have been authorised to monitor by the person who does. “Authorised” includes your customers, if you are their hosting provider or agency and your agreement with them covers monitoring.

Two limited exceptions exist because the checks involved are light and the targets are public:

• ICMP ping to any public address, at intervals of 60 seconds or more (300 seconds on free usage), with a fleet-wide cap on how often any single address is pinged by all customers together.
• The free tools on our website (“Is it down?”, the Cloudflare check, the TTFB, port and SSL checkers, and the DNS, redirect and domain expiry lookups), which run one check per request from each probe or from our central server, are rate-limited per visitor, and cache results for the same target. The port checker opens a single TCP connection to one port named by the visitor and closes it without sending data; it never checks a range of ports, and any one host can be checked at most once a minute by all visitors together. The SSL checker performs one TLS handshake per probe, plus up to two from our central server to read the certificate chain. The redirect checker requests each page in a redirect chain once from our central server, for at most 10 hops.

The operator of any address can ask us to exclude it from both at abuse@pingwise.com. We act on such requests within one working day and keep a block list that applies across every account.

2. Do not use the fleet against anyone

You must not use the Service to:

• overload, probe for weaknesses, scan ports, enumerate, or otherwise attack any system, including your own;
• get around rate limits, bot protection, authentication or geo-restrictions of a third party’s site, except where that site’s operator has allowed our probes (for example by listing our addresses);
• send custom HTTP requests that change data on a server you do not control, or that carry credentials you are not entitled to use;
• point heartbeat URLs, webhooks or alert channels at systems you do not control;
• repeatedly create and delete monitors, accounts or status pages to avoid a limit, a cap, or the credit system;
• run more than one account to multiply the free monthly credits (one organisation, one account; use invitations and, later, reseller sub-accounts instead).

Technical limits (shortest interval, response size read, request sizes, API and tool rate limits) are part of this policy. The current values are shown in the application.

3. Status pages and notices

• Publish only content you have the right to publish. No illegal content, no content that infringes someone’s rights, no malware or links to it.
• Do not impersonate another company or service. Your branding must be yours or used with permission.
• Email notices go only to people who subscribed to your page themselves and confirmed their address. Do not import lists. Honour unsubscribes; we process them automatically and keep a suppression list.
• Custom domains must be yours and must stay pointed at us while in use.

4. API, probes and the Service itself

• Use API keys only for your own account and keep them secret. Rotate a key you suspect is exposed.
• Do not interfere with the probe fleet, the public probe lists, the application or other customers’ data, and do not try to access data that is not yours.
• Do not resell, white-label or offer the Service to third parties without a reseller agreement with us.
• Do not use the Service in connection with anything illegal under Greek or EU law or the law of the place you are in.

5. How we enforce this

Depending on how serious the problem is, we may warn you, pause the monitor or feature involved, pause the account, remove content, or terminate the agreement under the Terms of Service. We try to warn first and give you a chance to fix things; we act immediately when a third party or the Service itself is at risk. We may notify the operator of a target that was monitored without authorisation, and we cooperate with law enforcement when the law requires it.

6. Reporting abuse

If our probes are causing you trouble, or you believe a customer is breaking this policy, write to abuse@pingwise.com with the target address, the time (with time zone), and anything you have from your logs. The addresses our probes use are published at pingwise.com/probes/ and in machine-readable form, so you can tell our traffic from anyone else’s. We answer within one working day.