Migrate from UptimeRobot to DomainCare

Move your UptimeRobot monitors and alert contacts to DomainCare: what maps to a check, what doesn't carry over and how to cut over without a gap.

By DomainCare TeamPublished Updated 9 min read

You picked UptimeRobot because the free plan covered what you needed: up to 50 monitors, each checked every 5 minutes. Then someone edits the SPF record and a client's invoices start landing in spam, or the mail server's IP turns up on a blacklist, and every monitor stays green.

UptimeRobot's monitor types are HTTP(S), keyword, ping, port, UDP, DNS, heartbeat, SSL and domain expiry. None of them validates SPF, DKIM or DMARC records, watches blacklists or grades security headers. DomainCare runs those checks next to uptime and groups them under the domain they belong to.

This guide takes you from a running UptimeRobot account to DomainCare, including the monitors that won't come with you.

What you'll move

  • HTTP(S) and DNS monitors
  • Keyword, ping, port, UDP and heartbeat monitors have no DomainCare equivalent; step 3 covers them
  • Alert contacts (email, Slack, Discord, webhook; SMS doesn't carry over)
  • Maintenance windows

Step 1: List your UptimeRobot monitors

UptimeRobot's API can list every monitor. The call below uses the v2 endpoint, which UptimeRobot now labels legacy next to its v3 API:

curl -X POST "https://api.uptimerobot.com/v2/getMonitors" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "api_key=YOUR_API_KEY&format=json&logs=0" | jq '.monitors[] | {friendly_name, url, type, interval}'

Or open the monitor list in the UptimeRobot dashboard and note, for each monitor:

  • The full URL (e.g. https://example.com/health)
  • The monitor type (HTTP, keyword, ping and so on)
  • The check interval in seconds
  • Which alert contacts it uses

Step 2: Add your domains to DomainCare

DomainCare works per domain, not per URL. You add a domain and every check starts on it, with nothing to pick first.

Domain-first monitoring

One DomainCare entry replaces several UptimeRobot monitors. example.com becomes a single entry that covers uptime, SSL, DNS, email authentication, blacklists and the other checks together.

  1. Sign in to DomainCare (or start the 30-day trial).
  2. Click Add domain.
  3. Paste your domains, one per line. Full URLs work too: DomainCare strips https://, the path, the port and a leading www., then merges duplicates.
  4. Click Add domains. Checks start in the background. A root domain gets all 13 checks; a subdomain gets 10, because the registration, email authentication and nameserver checks only apply to the root.

The trial covers 1 domain. Any further domains need a paid plan.

If several monitors point at paths on the same domain (e.g. https://example.com/ and https://example.com/api/ping), they collapse into one DomainCare entry. The uptime check requests the domain root over HTTPS (falling back to HTTP), and you can't add path-level checks. Keep those path monitors where they are. A path that lives on its own hostname, like api.example.com, can be added as a domain of its own.

See Add your first domain for a full walkthrough.

Step 3: Map UptimeRobot monitor types to DomainCare checks

UptimeRobot typeDomainCare equivalent
HTTP(S)Uptime check, every 60 seconds
KeywordNo equivalent: the uptime check doesn't read the response body
PingUptime check (an HTTP request, not ICMP)
PortNo equivalent: the open-ports check is an exposure scan, not a monitor
DNSDNS check (alerts when records change)
SSL, domain expirySSL check and domain registration (RDAP) check
UDP, heartbeatNo equivalent

HTTP, DNS, SSL and expiry monitors map cleanly. The others don't, because DomainCare watches a domain, not an arbitrary endpoint. In exchange, every domain also gets email authentication, blacklist, security header, open port and site speed checks, which UptimeRobot's monitor types don't cover.

Step 4: Set up notification channels

DomainCare sends alerts by email, Slack, Discord, webhook and browser push. During the trial only email works; the other channels need a paid plan. UptimeRobot contacts map like this:

UptimeRobot alert contactDomainCare channel
EmailEmail recipient
SlackSlack channel (incoming webhook URL)
DiscordDiscord channel (webhook URL)
WebhookWebhook channel (signed POST with a JSON payload)
PagerDutyNo native channel. The webhook sends DomainCare's own JSON, so you need a PagerDuty integration that accepts custom payloads or a small relay in between
SMSNot offered

To add channels:

  1. Go to Settings > Notifications.
  2. Add email addresses under Alert recipients, and Slack, Discord or webhook under Integrations.
  3. Click Send test on each one.

Alerts are routed by severity. High-severity events, such as a site going down or an expired certificate, alert right away. Medium events go to the daily digest, low and info events to the weekly digest. On each domain's settings page you can route severities to other channels. The same page lets you mute or stop a single check and switch off single event types. There's no failure count to set: DomainCare waits for 2 failed checks in a row before it reports a site as down.

See Notification channels for setup details.

Step 5: Replicate maintenance windows

UptimeRobot maintenance windows stop alerts during planned work. DomainCare has one-off windows per domain:

  1. Open the domain and click Settings.
  2. Under Maintenance windows, set a start and end time (in your local time) and, if you like, a reason.
  3. Click Add window.

During a window DomainCare keeps running checks and recording events, but sends no immediate alerts for that domain. Medium and low events from the window can still show up in the next digest. Windows are one-off; there are no recurring schedules. To quiet a single check for longer, mute it (alerts stop, the check keeps running) or stop it (the check doesn't run) from the same settings page.

Step 6: Validate and cut over

Before you cancel UptimeRobot:

  1. Let DomainCare run for at least 24 hours. Every check runs once when you add the domain, and by 24 hours the daily ones (sitemap, site speed, security headers and open ports) have run a second time. Confirm the results look steady.
  2. Trigger a test alert by taking down a staging site for a few minutes, or use Send test on each channel.
  3. Confirm the alert reached every channel you set up.

When you're confident, cancel UptimeRobot from the ellipsis menu under Billing, Plan & Subscription > Cancel Auto-Renewal. The plan stays active until the end of the period you paid for, then the account drops to UptimeRobot's free plan. On the free plan there's no subscription to cancel: pause or delete the monitors you've moved.

Common questions

Does DomainCare have a free trial? Yes. The 30-day trial covers 1 domain with every check running, needs no card and never charges you automatically. Alerts go by email only during the trial; Slack, Discord, webhook, push and API access need a paid plan. See pricing for paid plan details.

Can I import UptimeRobot monitors automatically? There's no import button. You can paste your whole list of URLs into Add domain in one go, and DomainCare reduces them to unique domains. On a paid plan you can also script it with the DomainCare API.

What about teams and user management? Invite your team and give each person a role (owner, admin, member or viewer). DomainCare bills per domain, so adding people doesn't change the price. See Team & permissions.

Will check history transfer? No. DomainCare starts recording from the day you add a domain. Your UptimeRobot history stays in your UptimeRobot account, subject to the log retention of your plan there.

Move your first domain over

Uptime, SSL, DNS, email authentication and blacklists, checked under one domain. 30 days · no card · no auto-charge.

Start the 30-day trial