A Security monitor scans one URL on a schedule for malware and for common security problems of the site behind it. Every scan asks Google Web Risk whether the URL is flagged for malware, phishing or unwanted software. It then runs the other check groups that are due: software versions, security headers, TLS settings, email authentication, page content, DNS records, mail encryption and MTA-STS. Each problem it finds is a finding with a severity, and findings at your alert level open an incident. Spam blacklists such as Spamhaus and SpamCop are a separate family, covered in Blacklist Monitoring.
Security monitors were called Virus monitors before Uptimia 6.5.0. Old /cp/monitors/virus links redirect to /cp/monitors/security, and the API keeps the /api/v2/virus path and the type virus.
Before You Start #
- Security monitors are not available on Free. Basic includes 1, Professional 10 and Enterprise 100; the trial includes 50. See Plan Limits and Quotas.
- Every monitor needs at least one alert recipient. Saving one with no recipients is refused.
- The URL must be a public address. localhost and private or reserved IP addresses are refused, because the scanner can never reach them.
- Scans fetch your page with the user agent Mozilla/5.0 (compatible; UptimiaSecurityMonitor/1.0; +https://www.uptimia.com/bot). If a firewall or WAF blocks it, the checks that read the page cannot finish, or judge only what the error response shows, and a check that cannot finish reads Unknown.
What a Security Monitor Checks #
The Web Risk lookup runs on every scheduled scan and cannot be switched off. The other eight groups are switchable per monitor, all on by default, and run at most once a day.
| Check | What it looks at | Runs |
|---|---|---|
| Malware and phishing | Google Web Risk lookup for malware, social engineering (phishing) and unwanted software | Every scan |
| Software versions | End-of-life (EOL) and unpatched releases the server discloses in the Server, X-Powered-By and X-AspNet-Version headers and in the WordPress, Drupal or Joomla generator tag | At most once a day |
| Security headers | HSTS, the browser protection headers and the Secure and HttpOnly cookie flags | At most once a day |
| TLS settings | Retired TLS 1.0 / 1.1 (and SSL 3.0), weak ciphers and the HTTP to HTTPS redirect | At most once a day |
| Email authentication | SPF and DMARC records that stop mail spoofing | At most once a day |
| Page content | Insecure page resources (http:// scripts, iframes and stylesheets on an https page), scripts from new sources and JavaScript libraries with known flaws | At most once a day |
| DNS records | CAA records that limit who can issue certificates, and DNSSEC signing | At most once a day |
| Mail encryption | Whether your mail servers accept encrypted connections (STARTTLS) | At most once a day |
| MTA-STS | A published policy that makes sending servers require encryption | At most once a day |
The page checks read one copy of your page per scan, up to 2 MB, following at most 5 redirects. The email, DNS and mail checks judge the registrable domain without a leading www.. They read Not checked for an IP-address URL or a host on a shared platform such as github.io, because there is no domain of yours to judge. Uptimia runs these checks from its own servers, so a Security monitor has no location selection.
Severities #
Every finding carries one of four severities. Some examples:
| Severity | Examples |
|---|---|
| Critical | Web Risk flags the URL for malware, phishing or unwanted software; the server discloses an end-of-life version (such as PHP 7.4) |
| High | Unpatched software below its secure release; the server accepts TLS 1.0 or 1.1; an SPF record that ends in +all; a mail server without STARTTLS |
| Medium | Weak cipher suites; no SPF record; no DMARC record; mixed content; a script from a new source |
| Low | Weak security headers (grade D, E or F); no HSTS; a disclosed version number; DMARC at p=none; no CAA record; no DNSSEC; no MTA-STS record |
A version from a Linux distribution build, which may carry backported fixes, counts one level lower.
Creating a Security Monitor #
- Go to Monitoring → Security.
- Click Create Security Monitor.
- Enter a Monitor Name and the URL to scan.
- On the Checks card, keep the default checks or switch groups off, and choose Alert on.
- Set Check frequency and Alert delay on the Notification Settings card.
- Pick the contacts to alert on the Alerting card.
- Click Save Monitor. The first scan is queued immediately and runs within a minute.
With one or more Security monitors already saved, Monitoring → Security opens one of them instead of the create page. Use Add Monitor in the monitors panel and pick the Security type.
To create several at once, switch the target field to Add Bulk and paste one URL per line, with an optional name after a comma. Every setting applies to the whole batch. Open each monitor afterwards to give it its own name and notes. You can also reuse a finished monitor: open its detail page, choose Save as Template from the action menu, then create the next one from that template.
Settings Reference #
| Field | What it does | Default | Limits |
|---|---|---|---|
| Monitor Name | The label used on the dashboard, in alerts and in reports. | — | Must be unique among your Security monitors; upper and lower case count as the same |
| URL | The address that is scanned. | — | Must be a valid, public URL |
| Checks | Which check groups run. See the next section. | All on | Malware and phishing is always on |
| Alert on | Which findings open an incident and send alerts: Critical issues only or High and critical. | Critical issues only | — |
| Check frequency | How often the monitor scans. Slider labels: Scan every hour, every 2 hours, every 3 hours, every 6 hours, every 12 hours, every day, every 2 days, every 3 days, every week. | Scan every day | 1 hour to 1 week |
| Alert delay | How long a finding must stand before the first alert goes out. The incident is confirmed when it elapses. | 5 minutes | 0–30 minutes |
| Alert when the issues are resolved | Sends a recovery alert when the incident closes. | On | On / off |
| Alerting | The contacts paged when an incident opens, or an escalation policy that pages them step by step. | All at once | At least one recipient |
| Groups | Monitor groups this monitor belongs to. | None | — |
| Notes | A free-text note that travels with the monitor onto incidents, alert emails and webhooks. | Empty | 500 characters |
| Email Branding Style | The branding theme applied to this monitor's alert emails. | Account default | — |
The editor has three tabs: Main, Advanced and Groups. Name, URL, the Checks card and the alerting cards are on Main; Advanced holds only Notes and Email Branding Style. There is no Locations tab and no Outage confirmation control.
Once your account has at least one escalation policy, the Alerting card gains an All at once | Escalate over time switch. Set it to Escalate over time and pick a policy. With no policies saved yet, the card links you to where you create one (see Escalation Policies).
The Checks Card #
The Checks card bundles the groups into three tiers, each named for the worst issue its groups can raise:
- Critical risks: Malware and phishing (always on) and Software versions.
- Important: TLS settings, Email authentication, Mail encryption and Page content.
- Hardening: Security headers, DNS records and MTA-STS.
Each tier has one switch and a count such as "All 4 on" or "2 of 4 on". Choose checks opens the tier's list with a switch per group. A tier with only some of its groups on opens by itself when you load the editor.
Under the tiers, Alert on sets which findings alert. Issues below the level show on the monitor page only. Medium and Low issues never send alerts at either setting. Some newer High and Critical checks show on the monitor page only for now: open ports, subdomain takeover, directory listings, cross-origin settings, a mail server without STARTTLS and vulnerable JavaScript libraries.
Switching a group off closes its open findings in the same save.
Save-Time Validation #
- A check frequency under 1 hour is rejected with "Security monitors require a minimum check interval of 1 hour". A save that leaves the frequency out is raised to 1 hour rather than failing.
- A URL on localhost or a private or reserved IP address is rejected. Names are not resolved at save time.
- A name already used by another of your Security monitors is rejected as a duplicate; names used by your other monitor types do not conflict.
- A save with no alert recipients is rejected.
Scan Cadence and Re-Scanning After Cleanup #
The Web Risk lookup runs as often as Check frequency says. The other groups run at most once a day inside those scans, so a weekly monitor runs them weekly. There are these exceptions:
- While a finding that alerts is open, the monitor re-scans that group every hour regardless of the setting. A site you clean at 10:00 clears within the hour. Once the incident closes, the normal frequency resumes.
- A check that could not finish (a timeout, a block, a probe error) is retried an hour later, up to 3 times in a row, then at the next regular scan. A failed check never counts as clean: its earlier findings stay open.
- When Web Risk cannot be reached, the malware check reads Unknown and is retried after 5 minutes, 15 minutes and 1 hour, then at the monitor's cadence. The other checks run as normal. A failed lookup is never logged as clean, and it cannot close a malware incident.
If you save a change to a monitor setting, the monitor is scanned again straight away. Saving the form without changing anything, or changing only its recipients or groups, does not start a new scan. Changing the URL closes every open finding and starts again from a fresh scan of the new site.
Check Now #
After a fix, click Check now in the Checks card header or in the page's Actions menu. Every switched-on check, Web Risk included, runs on the next scan instead of waiting for its daily turn. Results usually arrive within a minute or two, and your regular schedule does not move. You can check one monitor once every 5 minutes, and your account 20 times an hour. The button is hidden on paused, suspended and in-maintenance monitors, and for roles that cannot edit monitors.
Alerts and Incidents #
An incident opens when a finding at or above your Alert on level is open, and closes when none is left. The monitor holds one incident at a time, named after its worst finding. If a worse finding appears while it is open (a Web Risk flag, or a higher severity), the incident is replaced by a new one and the alert goes out again.
- An automatic Security incident reads Warning, in amber, on the monitor page, the dashboard and in alerts. A Web Risk flag reads Infected in alert headlines.
- Nothing was down, so a Security incident adds no downtime: uptime figures, reports and status page bars are not affected.
- Every alerting finding, High or Critical, is labelled CRITICAL in alerts.
- The recovery alert reads HEALTHY only when the scan came back fully clean: no issue open, none marked as expected, every check switched on and every check reaching a verdict. Otherwise it reads ISSUE CLOSED: the issue that opened the incident is gone, but other issues may still be open or a check could not finish.
- A public status page or Statuspage never shows what a Security check found. It shows a generic line instead.
Security monitors that existed before Uptimia 6.5.0 got one baseline scan when the new checks were added. What that scan found shows on the page labelled No alert and sends no alert unless it becomes more severe. New monitors alert from their first scan.
Reading the Detail Page #
The detail page is one scrolling stack of cards, not a set of tabs.
Header. The monitor name, its URL and a status badge: Up, Warning (an open incident), Unknown (no check reached a verdict), Maintenance, Paused or Suspended. When a maintenance window is running, a line under the URL reads "Under maintenance until end time · window name", and that line links to the maintenance page. Status vocabulary across all families is in Monitor Statuses.
Stat strip. Four cells:
| Cell | What it shows |
|---|---|
| Current Status | The status badge, with how long it has held and since when |
| Scan Result | The number of open issues, the worst severity and how many are at your alert level; or No issues with how many checks passed; or how many checks are unknown. Before the first scan it reads Not scanned yet |
| Incidents | Incidents in the selected date range, with the most recent one's start time |
| Last Scan | How long ago the last scan ran, or "Not yet" before the first one, and when the full checks run again |
Suspended means the monitor is over your plan's Security allowance after a downgrade and is not being scanned at all.
Open issues card. Every open finding, worst first. Each row shows the severity badge, the title, the check group, whether it alerts at your level (Alerts, No alert or Page only) and since when it has been open. Expand a row to see What we found (the evidence, such as the header and version) and How to fix. The header reads Alerts on: with your level and a Change link to the editor.
Mark as expected. An expanded finding has a Mark as expected button. It stops that issue counting or alerting on this monitor, and you can undo it from the Marked as expected section under the list. If the same issue later comes back at a higher severity, it opens again. Web Risk flags cannot be marked as expected. Marks and undos share an allowance of 60 an hour per account, and each one is recorded in the audit log.
Checks card. One row per check group with Result, Last run and Next run. A result reads the issue count and worst severity, No issues, Not run yet, Switched off, Not checked (the check does not apply to this URL, with the reason), Pending (a check that covers a few items each day) or Unknown with the reason in words. An Unknown check never counts as passed.
Advanced checks card. Owner-only checks for a domain you prove you own: open ports, directory listings, subdomain takeover, cross-origin settings and insecure forms on linked pages. They run at most once a day and need the Professional plan or higher (the trial included). Verification itself is open on every plan:
- Click Verify ownership.
- On the DNS record (recommended) tab, add the TXT record shown, uptimia-verification=<token>. Or, on the File on your website tab, publish that same line at https://<domain>/.well-known/uptimia-verification.txt.
- Click Verify now. Both methods are checked each time.
A verification covers the domain and all its subdomains. Uptimia re-checks verified domains daily, and the third failed check in a row marks the domain Lost, which locks the checks again. A user limited to some monitor groups cannot verify a domain; the account owner or an Admin does it.
Timeline. The shared status bar across the selected range. Its legend lists only the states present in that range, such as Up, Warning, Maintenance, Paused and Unknown. On a monitor with no incident all range it reads only Up.
Incidents card. One row per incident with its start, end and duration, for example "Warning for 3 hours" with the finding on the line below. Clicking a row opens the incident's own page, where the What we found card lists the finding that opened the incident and every other alerting finding open during it, each with its evidence and how to fix it.
Check log card. The scan history, newest first, in three columns: When, Malware and phishing (Clean, Infected or Unknown) and Other checks (one badge per scan, such as "2 issues", No issues, Unknown, Not run or Not checked). There is no probe or response-time column. Click a row to open the check drawer, which lists every check of that scan with its result and the findings open right after it. View all logs opens the same rows in the account-wide Monitoring Logs page, filtered to this monitor.
Limits and Plan Availability #
| Monitor type | Free | Basic | Professional | Enterprise | Trial |
|---|---|---|---|---|---|
| Security | 0 | 1 | 10 | 100 | 50 |
| Advanced checks (verified domain) | — | No | Yes | Yes | Yes |
Free accounts cannot create a Security monitor. If a downgrade puts you over the allowance, the excess monitors are suspended rather than deleted. They stop being scanned, and they start alerting again once you are back inside the limit. A downgrade below Professional locks the advanced checks and closes their open findings at the next scan.
After an Infection #
- Fix the cause, not the symptom. Most infections arrive through an out-of-date CMS or a vulnerable plugin, so update everything and remove what you do not use. The Software versions and Page content checks show what the site discloses as outdated.
- Check server access logs for unauthorized access, then rotate every credential involved: FTP, SSH, database and CMS admin.
- Click Check now once the fix is live, and leave the monitor running. It re-scans hourly while the incident is open, and the recovery alert is your confirmation that Google no longer flags the URL.
- Create one monitor per public hostname. A monitor knows only about the URL it was given, so a flagged subdomain is invisible to a monitor pointed at the apex domain.