MONITORING PRICING
Free domain signals. Pay-as-you-go website monitoring.
Start with free WebSec monitoring for important domain-control signals, then add HTTP(S) website monitoring on ostr.io's usage-based pricing. No subscription is required to begin.
$0/mo. No monthly fee. Pay as you go.
pricing model
WebSec domain signals form the baseline; HTTP(S) and SMS follow current terms.
Free WebSec monitoring
ostr.io presents WebSec domain-protection capabilities as free for users on all plans:
- WHOIS record monitoring.
- DNS record monitoring.
- SSL/TLS certificate monitoring.
- Domain and certificate expiration reminders.
Monitoring detects signals for owner review; the responsible provider or owner completes any required change. That means you can keep an eye on the domain-control signals that quietly break a business without committing to a paid plan first.
For a small business, free WebSec is the baseline layer: it watches the domain signals that are easy to forget because they do not change every day. WHOIS records, DNS records, certificate state, and renewal deadlines sit behind the website and email customers use. When one of those signals moves, the value is not that monitoring fixes it; the value is that the right person finds out while there is still a clear review path.
Use the free layer for every important business domain before deciding how many HTTP(S) checks to add. That order keeps the pricing decision practical: domain-control awareness runs in the background, while paid website monitoring is reserved for the public pages where a wrong response affects revenue, leads, bookings, or trust.
pricing model
WebSec domain signals form the baseline; HTTP(S) and SMS follow current terms.
Usage model
Usage-based monitoring and notifications
HTTP(S) website monitoring is part of ostr.io's usage-priced monitoring offering, and SMS notification usage follows current ostr.io terms. This site deliberately does not reproduce detailed rate tables, because pricing and product labels change. For anything price-sensitive, use the official source while you set up your account.
| What you monitor | How it is priced |
|---|---|
| WHOIS / DNS / SSL/TLS signals (WebSec) | Free domain-protection capabilities |
| Expiration reminders | Included with free WebSec |
| HTTP(S) website monitoring | Usage-based |
| SMS notifications | Current ostr.io terms |
usage metering
Free WebSec domain signals stay the baseline; HTTP(S) checks and SMS are metered.
How to think about a pay-as-you-go footprint
Usage-based pricing rewards monitoring what matters rather than everything you can. A focused setup - the handful of customer-facing endpoints where a wrong response costs money, plus the free WebSec domain signals running in the background - keeps cost predictable and alerts meaningful. You can always widen coverage later once you have confirmed the early alerts are useful. Because WebSec domain-control monitoring is presented as free, you can begin watching WHOIS, DNS, and certificate signals at no cost and add HTTP(S) checks only where they earn their place.
| Business asset | Practical monitoring choice | Why it matters |
|---|---|---|
| Homepage | HTTP(S) response and timing | Customers need to know the business is reachable. |
| Checkout, booking, or lead form | HTTP(S) response plus content review where relevant | A wrong response directly affects revenue or inquiries. |
| Primary domain | Free WebSec WHOIS, DNS, SSL/TLS, and expiration reminders | Domain-control signals can affect website and email at once. |
| Important secondary domains | Free WebSec first, HTTP(S) only where a public endpoint matters | Not every domain needs paid website checks. |
This is the cleanest way to explain pay-as-you-go monitoring to a non-technical owner: monitor the pages where customers experience the business, and monitor the domain layer that keeps those pages reachable. Everything else can wait until there is a clear operational reason.
owner checklist
Assets, providers, recipients, and escalation routes are written down first.
What to check before you start
- Which website endpoints actually need HTTP(S) monitoring.
- Which domain, DNS, or certificate signals need WebSec coverage.
- Who receives email notifications, and whether any signal warrants SMS.
- The current pricing and product labels ostr.io shows at the time of setup.
- Whether each monitored signal has a named responder and backup.
- Whether any endpoint is seasonal, campaign-specific, or safe to monitor only during active use.
Frequently asked questions
Is there a monthly fee to start?
ostr.io presents a pay-as-you-go model with no monthly fee and free WebSec domain-protection capabilities. Confirm the current wording on the official pricing page at signup.
Why does this page not list exact prices?
Pricing and labels change. We link to the official source so you always make price-sensitive decisions against current figures.
What is free versus usage-priced?
WebSec WHOIS, DNS, SSL/TLS monitoring and expiration reminders are presented as free. HTTP(S) website monitoring and SMS follow usage-based pricing.
How should a small business estimate its monitoring footprint?
Start with the customer-facing endpoints where a wrong response matters, then add free WebSec coverage for each important domain. Review SMS only for signals that need attention outside email.
Should every page on a website be monitored?
Usually no. Monitor the homepage, revenue or lead paths, login pages, and critical API endpoints first. Add lower-value pages only when they have a clear business impact.
Start on ostr.io
Choose the signals you need, assign recipients, and review current official pricing while you set up your account.
domain-protection.info is an official monitoring information property by ostr.io. About this site