When a 200 OK isn't enough
A page can respond correctly and still show an error message. The keyword monitor reads the content and checks that it's the right one.
Included in every plan: 5 free monitors checked every 5 min, down to every 1 min on paid plans.
- URL
- https://api.example.com/health
- Keyword
- "database":"ok"
- Condition
- must exist
- Case
- ignore
How it works
Setting up a Keyword monitor takes less than a minute.
- 1
Choose URL and keyword
Set the page and the text that must be there, for example a product name or "status":"ok".
- 2
UptimeAnchor analyses the response
At every check we download the content and search for the keyword, case-sensitive or not.
- 3
Content-based alerts
If the keyword is missing (or appears when it shouldn't), the monitor goes DOWN and you get notified.
Configuration options
Everything you can tune to fit the check to your service.
- Must exist / must not exist
- Alert when the text is missing, or when it appears, for example "Database error".
- Case sensitivity
- Case-sensitive or case-insensitive search, depending on how strict you want to be.
- All HTTP options
- Method, headers, body, authentication and expected codes, just like HTTP monitors.
- JSON responses
- Look for specific values in API responses without writing scripts.
- Multiple regions
- Make sure content is correct behind CDNs and geographic caches too.
- Detailed history
- Every failure records the reason, so you immediately know whether the content or the server changed.
Use cases
Masked error pages
CMSs and frameworks that return 200 even when the database is unreachable.
Defacement
Get alerted if text that shouldn't be there appears on your homepage.
Application health checks
Verify that the /health endpoint really reports every dependency as operational.
Start monitoring with Keyword
Create an account in under a minute and set up your first monitor. The Free plan stays free forever.
No credit card required.