Linux Mint’s Domain Spent Four Hours on a Hosting Company’s Parking Page
For about four and a half hours on 19 November, Linux Mint’s website, forums and update server showed a hosting company’s parking page instead of Linux Mint.
Anyone who opened linuxmint.com got a certificate warning first. Behind it was a Swedish page from Websupport, a hosting company, offering to help you find a domain name. Linux Mint’s own update server, the one every Mint installation checks by default, served the same page, so Update Manager failed with signature errors.
The domain registration was never touched. What changed was the domain’s DNS zone at Linux Mint’s DNS provider: at about 03:45 UTC it started sending every address under linuxmint.com to the parking server, and at 08:09 UTC a new version put Linux Mint’s own records back. At 08:20 UTC the website, blog, update server and mail records worked again. The forums still didn’t resolve.
The first public report we found is a post by It’s FOSS at 05:06 UTC. When we published, Linux Mint hadn’t explained what happened, and we found no news coverage.
What Happened, and When
We followed the domain from three networks, in Romania, the US and a cloud data centre, between 07:40 and 08:20 UTC. All times are UTC.
- About 03:45: every name goes to the parking server. The zone’s serial number, read as a timestamp the usual way, dates the change to 03:45:02, and its DNSSEC signatures were valid from 02:35. linuxmint.com, www, forums, blog, community and packages.linuxmint.com all resolved to 109.235.174.19, and so did a made-up name we invented for the test. The zone held a catch-all record.
- The parking server was Websupport’s. It answered with a page titled, in Swedish, “Websupport, one of Europe’s largest providers of web hosting and domain names”. Over HTTPS it presented a certificate for
*.r103.websupport.se, which is why browsers warned. - No mail server. The parked zone listed no MX record, so email to linuxmint.com addresses had nowhere to go.
- 05:06: first public report, from It’s FOSS, which asked whether Linux Mint had lost its domain.
- 08:09:45: the records come back. A new zone version restores the website and blog behind Sucuri’s firewall, the update server, the Google mail records and the record that confirms Linux Mint’s Bluesky handle. Resolvers can keep old answers for up to ten minutes, so some people saw the parking page a little longer.
- 08:20: the forums still don’t resolve. forums.linuxmint.com returned an error from Google’s public resolver.
One detail matters for anyone wondering about an attack on the way. linuxmint.com is signed with DNSSEC, and the parking records carried valid signatures from the domain’s own key chain. So they really came from Linux Mint’s DNS provider. This wasn’t a poisoned resolver or someone faking DNS answers.
The registration, on the other hand, showed nothing unusual all morning. The domain is with the registrar Ascio, registered in 2006, paid until June 2031, status “active”, last changed in May. No hold, no transfer, no expiry.
Its name servers, ns1 and ns2.loopiagroup.com, are the ones Websupport tells its own customers to use, and DNS history shows Linux Mint on them since February 2024. For four hours the zone on them held none of Linux Mint’s own records, only the provider’s parking default. Then it held them again.
Why, we don’t know. A lapsed or suspended service, a mistake at the provider and someone with access to the account would all look like this from the outside. Websupport’s status page said “everything is working as it should” when we checked at 08:07 UTC, so it doesn’t look like an outage that hit all its customers.
Codeberg Yesterday, Linux Mint Today
It’s FOSS put the two together, and the timing invites it. On 18 November, Codeberg’s domain disappeared after its registrar, NameSilo, put it on hold. codeberg.org resolves again this morning.
The two cases are different, though. Codeberg’s domain was frozen at the registry level, so it simply stopped existing for a few hours. Linux Mint’s domain kept existing and stayed with the same registrar. What went missing was the content of its DNS zone. We see no technical link between them, and nobody has claimed one.
What they share is a lesson projects don’t like. A single account at a domain or DNS company can take a whole project offline, website, forum, mail and update server in one go, however well the servers behind it are run. Registry locks, a second DNS provider and alerts on zone changes cost little compared with that. Two days, two well-known open-source projects. The internet has a strange sense of timing.
What Mint Users Should Check Now
Your Mint installation was safe from this. apt, the system behind Update Manager, only accepts package lists signed with Linux Mint’s key, and a parking page carries no such signature.
We tested it during the outage, at 08:07 UTC. apt fetched the parking page in place of the package list and refused it with “Clearsigned file isn’t valid, got ‘NOSPLIT’ (does the network require authentication?)”, then “The repository … is not signed”. Nothing got installed. At 08:19 UTC the same test fetched Linux Mint’s signed package lists again.
So for most people the only effect was a morning without Mint updates, including Firefox, which Mint ships from its own repository (version 160.0.1 at the moment), and Cinnamon. Ubuntu’s base packages kept coming from Ubuntu’s servers. A few things are still worth checking.
Clearsigned file isn’t valid, got ‘NOSPLIT’: the update server returned a parking page, and apt refused it. Nothing was installed[trusted=yes] to silence the errormint-iso-verify, or the SHA256 sum and GPG signature (fingerprint 27DE B156 44C6 B3CF 3BD7 D291 300F 846B A25B AE09). Delete it if the check failsIf it happens again, switching to a mirror is the quick fix. Open Software Sources, click the server beside “Main”, pick one of the mirrors in the list, then refresh. Linux Mint gave its users the same advice years ago during an overload of its main server. The list of mirrors is stored on your computer, as the mintsources code shows, so this works even with linuxmint.com down. Mirrors serve the same signed packages, and apt checks them the same way.
Downloads were the real risk. With linuxmint.com’s download and verify pages gone, anyone looking for a Mint ISO that morning landed on whatever search results offered. This is not a theoretical risk for this project. In February 2016 attackers broke into the Linux Mint website and pointed its download link to an ISO with a backdoor in it. If you downloaded Mint on 19 November, check the file before you install it. Linux Mint’s installation guide, hosted outside the domain and online throughout, explains how: run mint-iso-verify on an existing Mint system, or compare the SHA256 sum and check the GPG signature of sha256sum.txt against the fingerprint 27DE B156 44C6 B3CF 3BD7 D291 300F 846B A25B AE09. The kernel.org mirror has the ISOs and both checksum files.
We're Contacting Linux Mint and Websupport
We’re asking Linux Mint what happened to its DNS zone, whether anything else was affected and when the forums will be back.
We’re asking Websupport why the zone served its parking page for those four hours, and whether the change was made by the customer, by its own systems or by someone else.
We’ll update this article when either replies.
Our Mission
We believe security online security matters and its our mission to make it a safer place.