Frequently asked questions

An uptime monitoring service. Mon checks your websites, certificates, domains, servers and DNS records on a schedule, from outside your own network, and alerts you the moment one of them stops working - so you hear about it before your customers do.

Yes, for as long as you like, with no card needed: 5 monitors checked every 5 minutes, email, Slack and webhook alerts, and status pages. Commercial use is allowed. Paid plans start at 10 monitors and check every minute.

One thing being watched: a website, a domain's expiry, a certificate, a port, a DNS record and so on. Your plan's size is the number of monitors it can run at once.

Websites and APIs, keywords on a page, page defacement, SSL certificates, domain expiry, ping, open ports and DNS records - all from one account, with the same alerts and dashboard.

No. Mon checks from outside your network, the way your customers reach you, so there are no agents to install and nothing to host. Add what you want watched in your account and the checks start.

Yes. Paste a list - URLs, domains, servers or records, one per line or straight from a spreadsheet - and Mon adds a monitor for each, skipping any you already watch. On Enterprise plans, connect Namecheap, Amazon Route 53 or Azure DNS and Mon imports your domains and DNS zones itself.

Websites, keywords, ports, ping and DNS every minute on any paid plan, and every 5 minutes on the free plan. Certificates and domains once a day, since they change only a few times a year. Defacement checks at most every hour, since each loads the whole page in a browser. You can choose a longer interval for any monitor.

From 7 locations: Virginia, New York, Dallas, California, São Paulo, Frankfurt and Singapore. Mon places each monitor's checks for you, or you can choose the locations yourself.

A check fails when the target doesn't answer within the timeout, answers with a status code you haven't counted as up, or is missing a keyword you asked for. You choose how many failed checks in a row it takes before each contact is alerted, so a single blip doesn't wake anyone.

Mon publishes the IP addresses of every location it checks from. Find them under Locations in your account, and add them to your allowlist.

Yes. A monitor can send any HTTP method with a body, and check the response for the text you expect. On paid plans it can also send its own headers, sign in with basic authentication and count the status codes you choose as up.

Not in JavaScript-based analytics such as Google Analytics: Mon's checks don't run JavaScript, so they are never counted as visits. They do appear in your web server's own logs, like any other request.

By email, in a Slack channel or with a request to your own webhook, and by SMS on paid plans. Each contact chooses what it hears about: a monitor going down, coming back up, an SSL certificate nearing expiry, and a weekly report.

30, 15, 7 or 1 day before it expires - you choose which. Mon also tells you when a certificate stops being trusted: issued for the wrong name, with a chain browsers don't trust, or missing altogether.

You choose: 7, 14, 30 or 60 days before a domain expires. Mon reads each domain's registration once a day, so it also notices when a domain's status or registrar changes.

Yes. A public status page shows how each part of your service is doing, on a Mon address or your own domain, and maintenance windows keep planned work from counting as downtime.

Two on the free plan, with two maintenance windows, and more on paid plans. Each page shows the monitors you choose, with their recent history bar by bar.

By the number of monitors, for one fixed price. Checks, bandwidth, email alerts and history are never charged for; the only extra is SMS beyond your plan's allowance, if you choose to buy more.

Any time, from Billing in your account. A new plan starts as soon as it's paid, and the unused part of your current plan is refunded in proportion to the time left.

Your plan stays active until the end of the period you've paid for, then your account moves to the Free plan. Nothing more is charged; the time already paid for isn't refunded.

Up to 28%, more on larger plans. Turn on annual pricing on the pricing page to see each plan's yearly price.

By card. Payments are handled by Stripe, and every invoice is kept under Billing in your account.

Yes, on Team and Enterprise plans. Mon's REST API lets your own code read your monitors, their events and your contacts, add, change, pause and delete monitors, manage maintenance windows, status pages and domains, and read DNS records, with an access token from your account. The API page in the docs covers authentication, paging, errors and rate limits.

60 a minute on Team plans and 300 a minute on Enterprise, across all of a team's tokens. Over the limit, the API answers 429 with a Retry-After header saying how long to wait.

Open a ticket from Support in your account. It's tied to your account, so we can look into it straight away, and every reply stays in one place.

Yes. Choose Chat at the top of any page on the website or in the docs. A green dot on it means we're online and usually answer in a few minutes; when we're away, leave a message and we'll get back to you.

Usually the same day. Every message is read by the people who build Mon, so there's no first line of support to get past.

No. Support is by chat on our website, email, the contact form and tickets in your account, which lets us look into a problem properly before we answer.

Maxotek LLC, the company behind PingerMan, which has been watching websites, servers and domains for teams since 2021.