SWPanel

SWPanel bots

SWPanelBot-Uptime

Checks that the website responds and alerts the owner if it goes down or runs slow.

User-Agent Mozilla/5.0 (compatible; SWPanelBot-Uptime/1.1; +https://www.swpanel.com/bots/uptime)

Feature: Availability monitoring Operator: DeepThink Software SLU Contact: [email protected] Version: 1.1 Reviewed on: October 17, 2026

Technical sheet

Everything SWPanelBot-Uptime does

Taken from the module's code. If the bot changes what it does, this sheet and its version change.

Identity

Name
SWPanelBot-Uptime. It is also its name for robots.txt.
Family
SWPanelBot: the common name of all SWPanel bots.
Version
1.1, the one in the User-Agent. The changes in each version are below.
Type
Direct: run and controlled by SWPanel, always on behalf of the service owner.
Category
Monitoring
Operator
DeepThink Software SLU, owner of SWPanel. Legal information.
Contact
[email protected]
Previous names
SWPanel-Uptime/1.0 (+https://www.swhosting.com)

When and how much

When it visits
Always, on services that have availability monitoring.
Frequency
About four times a day per website. It goes through all services in batches of about 200 every 5 minutes, and a full round takes about 6 hours.
Opening hours
24 hours, every day.
Per pass
A GET to the home page. If it fails, it repeats after 1.5 seconds; if there is no response over HTTPS, it tries HTTP.
Per month
About 120 requests if the website responds well.
In parallel
Never. One request after another.

How it requests

What it requests
The home page, https://your-domain/, and http://your-domain/ if the first doesn't answer.
Methods
GET. It also opens a connection to the mail (25 or 587) and FTP (21) ports to read the server's greeting, without logging in.
From where
From SWPanel's probe in Barcelona.
Redirects
It follows them: a redirect to HTTPS or to www counts as a correct response.
Certificate
It doesn't check it: an expired certificate doesn't count as an outage. Security 360 takes care of the certificate.
Cookies and JavaScript
No.
Waits
5 seconds to connect and 8 for the response. If it takes more than 5 seconds, it counts as slow.
How it classifies
2xx, 3xx and 404: responds. 401, 403 and 429: degraded. 5xx or no response: down.
Origin
In preparation From SWPanel's servers. We're reserving some outgoing IPs just for the bots; once they exist, we'll publish them here in a JSON file.
Reverse DNS
In preparation Each IP will have a name under bots.swpanel.com that resolves back to the same IP.

Standards it applies

robots.txt
Exempt, with justification It doesn't consult it. It's a single request to the home page commissioned by the owner, like any availability monitor.
Which websites it visits
Compliant It only visits websites of active SWPanel services and stops as soon as the service is cancelled: it checks before every request.
If the website asks to slow down
Compliant On 429 or 503 it doesn't retry after 1.5 seconds: it notes the website as degraded and returns in the next round.
HTTP cache
Not applicable It must see the website as it is right now.
Signature
Compliant It signs every request with Web Bot Auth (RFC 9421, Ed25519): Signature, Signature-Input and Signature-Agent headers. The public key is at https://www.swpanel.com/.well-known/http-message-signatures-directory.
Contact in the request
Compliant It carries From: [email protected], as RFC 9110 asks of automated clients.

What it does with the data

What it reads
The response code and how long it takes. It doesn't read the page content.
What it stores
Only the status changes: when an outage or slowdown started and ended, the reason and the response time. When all is well it stores nothing about the website, only one record per batch that the probe measured.
How long
24 months.
What for
To alert the owner and show them the service's availability history.
Privacy
SWPanel's general privacy policy.

How it works

One pass, step by step

  1. Takes the batch

    Every 5 minutes it takes the next services in order, about 200, and wraps around on reaching the end.

  2. Requests the home page

    A GET to https://your-domain/ and, if it doesn't answer, to http://your-domain/.

  3. Retries if it fails

    Once more, after 1.5 seconds, so as not to declare a website down because of a one-second glitch.

  4. Classifies

    Responds, degraded or down, according to the code and the response time.

  5. Checks email and FTP

    Opens the connection, reads the server's greeting and closes it, without logging in.

  6. Alerts

    If the status changes, it opens or closes the incident and alerts the owner.

In your logs

This is how SWPanelBot-Uptime looks

An example in Apache and Nginx combined format. The IP and domain are for documentation: yours will be different.

203.0.113.20 - - [17/Oct/2026:04:05:12 +0200] "GET / HTTP/1.1" 200 48211 "-" "Mozilla/5.0 (compatible; SWPanelBot-Uptime/1.1; +https://www.swpanel.com/bots/uptime)" 203.0.113.20 - - [17/Oct/2026:10:07:40 +0200] "GET / HTTP/1.1" 200 48211 "-" "Mozilla/5.0 (compatible; SWPanelBot-Uptime/1.1; +https://www.swpanel.com/bots/uptime)" 203.0.113.20 - - [17/Oct/2026:16:03:55 +0200] "GET / HTTP/1.1" 200 48211 "-" "Mozilla/5.0 (compatible; SWPanelBot-Uptime/1.1; +https://www.swpanel.com/bots/uptime)" 203.0.113.20 - - [17/Oct/2026:22:06:21 +0200] "GET / HTTP/1.1" 200 48211 "-" "Mozilla/5.0 (compatible; SWPanelBot-Uptime/1.1; +https://www.swpanel.com/bots/uptime)"

A request to the home page about four times a day, at times that vary according to the batch.

Verify

Is it really SWPanelBot-Uptime?

A User-Agent can be copied. That's why it must be checked together with everything else. The examples use a documentation IP.

Reverse DNS In preparation

$ host 203.0.113.10 10.113.0.203.in-addr.arpa domain name pointer crawl-203-0-113-10.bots.swpanel.com. $ host crawl-203-0-113-10.bots.swpanel.com crawl-203-0-113-10.bots.swpanel.com has address 203.0.113.10

The IP must resolve to a bots.swpanel.com name, and that name to the same IP. If only the first part holds, it isn't ours.

IP list In preparation

$ curl -s https://www.swpanel.com/bots/ips.asp {"formatVersion": "1.0", "creationTime": "…", "prefixes": [{"ipv4Prefix": "203.0.113.0/28", "service": "SWPanelBot"}]}

A JSON file in the JAFAR format proposed by the IETF, linked from this page.

Request signature Available

Signature-Agent: "https://www.swpanel.com" Signature-Input: sig1=("@authority" "signature-agent"); created=1792224000;expires=1792224300; keyid="…";alg="ed25519";tag="web-bot-auth" Signature: sig1=:…:

Web Bot Auth headers. The public key is at /.well-known/http-message-signatures-directory on www.swpanel.com: with it, any firewall that understands Web Bot Auth verifies the request is ours.

What it requests Available

Compare what you see with the sheet: the paths, the frequency and the volume. A bot called SWPanelBot-Uptime that does something else isn't ours.

If you doubt a visit, write to us at [email protected] with the domain, the time with its time zone, the IP and the log line, and we'll check it.

Stopping it

The owner requests it. The owner turns it off.

Our bots only visit websites of active SWPanel services, only for the functions their owner has active, and stop visiting as soon as the service is cancelled.

If you are the owner

Disable the service's availability monitoring in your SWPanel.

If you are not

If the domain is no longer in SWPanel you shouldn't receive any scheduled visit. If you do, write to us at [email protected] and we'll stop it.

In the firewall

To let it through, use the name together with the IP or the signature, not just the name. Watch out for generic rules: a pattern like “bot” also matches SWPanelBot.

If you block it

Monitoring will report the website as down or degraded when it isn't.

robots.txt doesn't stop it: we explain this in Standards. Its owner stops it, from SWPanel.

Standards

What the standards ask for, and how SWPanelBot-Uptime is doing

Our situation on each point, without embellishment.

What the standards ask for, and how SWPanelBot-Uptime is doing
A proper name in the User-Agent, with the address of its page RFC 9110, 10.1.5, and IETF draft “Crawler best practices”, 2.2 Compliant
A valid name for robots.txt: letters, hyphens and underscore RFC 9309, 2.2.1 Compliant
Visit only websites of active SWPanel services, and stop as soon as the service is cancelled SWPanel's own commitment Compliant
Read and respect robots.txt RFC 9309 and “Crawler best practices”, 2.1. The draft allows documented exemption for crawlers that work on commission. The owner requests it and it is a one-off check. Exempt, with justification
Don't hinder the website: one request at a time, page and time limits, and short waits “Crawler best practices”, 2.3 Compliant
Slow down if the website answers 429 or 503 “Crawler best practices”, 2.3, and RFC 9110, 15.6 Compliant
Respect the HTTP cache “Crawler best practices”, 2.4, and RFC 9111. It needs the current response. Not applicable
A contact in the request: From header RFC 9110, 10.1.2 Compliant
Publish the outgoing IPs in JSON, linked from this page “Crawler best practices”, 2.5, with the JAFAR format In preparation
Reverse DNS that can be confirmed Practice of Google, Bing and Cloudflare for verifying bots In preparation
Sign requests (Web Bot Auth) IETF draft “HTTP Message Signatures for Bots”, September 2026 Compliant
Public page with what it does, what it stores, contact, how to stop it and the exemptions “Crawler best practices”, 2.6 Compliant

Partially: compliant with a caveat, explained in the row. In preparation: depends on the network, such as dedicated IPs and their reverse DNS. Pending: no date yet.

Versions

What has changed

The version goes in the User-Agent. When the bot changes what it does, the version and this sheet change.

What has changed
1.0 12-10-2026 New name, SWPanelBot-Uptime, with the link to the bots page. Replaces SWPanel-Uptime.
1.1 17-10-2026 Links to this sheet. Doesn't retry if the website answers 429 or 503, signs requests, carries the From header and only visits active services.

Frequently asked questions

Questions about SWPanelBot-Uptime

Because from Barcelona it did not answer within 8 seconds twice in a row, or it returned a 5xx error. If you have a firewall that blocks by country or by bot, check that it lets SWPanelBot-Uptime through.

Because the website responds. It is usually a firewall blocking the bot, so we mark it as degraded for you to review.

No: it does not run JavaScript. It is only visible in the server logs.

It does not read it, like other uptime monitors: it is a single request to the homepage made on the owner's behalf. To stop it, the owner turns off monitoring.

The other bots

Each one, with its own sheet