Features
What Pingsured can check for you: pages, APIs, certificates, feeds and more, from the locations you choose, with an alert when something breaks.
Each page below takes one thing that can go wrong while a server still answers 200 OK, and shows how to catch it: the settings to use, examples you can copy, and the limits stated up front.
- Know your site is down before your users do
Pingsured requests your site at the interval you choose, from up to four locations, and alerts you when it stops answering. What a check does and how it alerts.
- Catch a broken page that still loads
A page can load fine and still show a maintenance banner, an empty template or a noindex tag. How Pingsured checks HTML elements with CSS selectors.
- Know your API answers correctly, not just that it answers
An API can answer 200 OK with an error, an empty list or stale data. How to check JSON fields, counts and timestamps in every response with Pingsured.
- Hear about a certificate before it expires
A TLS check warns days before a certificate expires and fails when the chain, the hostname or the protocol would turn real clients away.
- Notice a stale feed or an empty sitemap before your readers do
A feed that stopped updating and an empty sitemap both answer 200 OK. How Pingsured checks XML content and freshness so you notice before your readers do.
- See your site the way users around the world see it
Pingsured checks your sites from Germany, Finland, the US West Coast and Singapore. How to choose locations, how failures are judged and where data is stored.
- Know your TLS setup still meets current guidelines
A daily test of your server’s TLS configuration against Mozilla, BSI, NIST or NCSC-NL guidelines, graded with one to five locks, so a weakened setup is noticed.
- Catch the deploy that hides your site from search engines
A release can hide a site from search engines while every page still loads. How Pingsured checks robots tags, canonicals, robots.txt and sitemaps on every run.
- Keep old links and http:// addresses landing in the right place
Redirects break quietly: a lost http-to-https rule, a broken migration map, a loop. How Pingsured checks the status and Location header of each redirect.
- Keep the headers that protect your site in place
A proxy change or a new CDN can silently drop the headers that protect your site. How Pingsured checks Content-Security-Policy, HSTS and others on every run.
- Know in seconds whether an outage is yours or theirs
Payments, email, maps, login: when a provider fails, your site fails with it. How Pingsured checks third-party APIs and status pages next to your own.
- Know your servers and network devices still answer
Not everything speaks HTTP. How Pingsured checks that servers, routers and gateways answer an ICMP ping from four locations, and records the round-trip time.
What every check comes with
- Checks every minute, every 5 or 15 minutes or every hour, or every 15 or 30 seconds on the Scale plan.
- Checks from Germany, Finland, the US West Coast and Singapore, each location judged on its own.
- An alert when a ping crosses your threshold, such as 3 of the last 5 checks: by email and in the app, and by webhook on the Team plan and above.
- One ping can combine several checks: status code, content, headers. It passes only when all of them do.
- Monitoring data stored in Germany and Finland, by a German company.