Spam pages on your Magento store’s address: a hack, or a domain that changed hands?
When a Magento store’s address starts serving gambling spam, either the store has been hacked or the domain has lapsed and someone else has registered it, and on our own list of UK Magento stores in 2026 the register dates point to the second for most of the .uk addresses.
721addresses on our UK Magento list serving gambling spamOctober 2026
449of them on .uk addresseschecked on the .uk register
266of those registered after 1st March 2026read 16th November 2026
When the current registration began, 449 .uk addresses
Registered after 1st March 2026266
Earlier in 202613
In 202547
Before 2025123
A registration that recent points to a domain that changed hands this year more than to a shop that was broken into. The 272 addresses that aren’t .uk were not checked.
From our own scan (October 2026) and the .uk register, read on 16th November 2026.
When we rebuilt our list of UK Magento stores in October 2026, 721 of the addresses on it were serving gambling spam pages. Most of the page titles were in Indonesian, advertising online slots and lottery sites. Our scanner had classed each of them as Magento at some point, but many plainly weren’t shops any more, or perhaps ever: a football club, a dental practice and a driving school were among them. The next question was whether any of these had been broken into.
What the .uk register says about them
On 16th November 2026 I checked the .uk register for the 449 .uk addresses among them. 266 had a current registration that began after 1st March 2026. Another 13 were registered earlier in 2026, 47 in 2025 and 123 before 2025. The other 272 addresses aren’t .uk, and I didn’t check them.
A registration that recent means whoever holds the address now registered it this year. For most of those 266, the likeliest story is that the owner let the domain go and someone else picked it up to host spam. For the older registrations both explanations are still open, because a name can change hands without a new registration date, and a site can be broken into. From the outside, we can’t tell which.
Two ways a store’s address ends up selling slots
Google’s spam policies name both. Hacked content is content placed on a site without permission, through a weakness in its security. Expired domain abuse is buying an expired domain and reusing it to manipulate search rankings; one of the policy’s own examples is casino content on a former school’s site.
For a merchant they’re very different problems. A hacked store is still yours and still taking orders, and someone else is using it. Adobe’s security guidance says most compromises aren’t the work of an inventive attacker: attackers often take advantage of existing, unpatched flaws, poor passwords and weak file permissions. A lapsed domain isn’t yours any more. The shop may still exist on its server, but nobody can reach it by its old name.
How to tell which one you’re looking at
Start with the registrar, because it’s quickest. Your registrar account shows the renewal date. Under Nominet’s process a .uk name keeps working for 30 days after it expires, stops resolving after that but can still be renewed up to 90 days, and drops after 95 days, when any registrar can register it.
If the domain is still yours, search Google for site: followed by your domain and look through a few pages of results for addresses you didn’t create. Hacked pages are often cloaked, so you see the normal shop and search engines see spam; the URL Inspection tool in Search Console shows the hidden version. Check the Security issues report and the list of people who own the property in Search Console too. web.dev’s guide says that a notice that someone you don’t know has verified your site means there’s a strong possibility it has been hacked.
If the store was hacked
Take a copy of the files before you change anything, as the web.dev guide advises, and of the database too. Then find how they got in and close it, remove what they added, and bring the store up to date with the security fixes for its release. Once it’s clean, request a review in the Security issues report, which can take from a few days to a few weeks.
If the domain lapsed
There’s no technical fix once someone else holds the name. What I’d do is make sure it can’t lapse quietly: renew for several years at a time, turn on automatic renewal, and check the registrar has a contact address that someone still reads. If the domain was registered by a former agency or employee, move it into an account the business controls.
Sources
Dates, versions and bulletin numbers on this page were checked against each publisher’s own page on . Where a publisher changes its page after that date, its page is the authority.
Our shop looks normal when we visit it. Can it still be hacked?
Yes. Hacked pages are often cloaked, so the site owner sees a normal page while search engines see the spam. A search for your own site in Google, and the URL Inspection tool in Search Console, show what Google sees.
Can we get a lapsed .uk domain back?
If it’s still within the renewal window, yes. Under Nominet’s process a .uk name can be renewed for up to 90 days after it expires, though it stops resolving after 30. Once it drops and someone else registers it, it’s theirs.
How long does a hacked-site warning take to clear?
Once the site is clean, you request a review in Search Console’s Security issues report, and the review can take from a few days to a few weeks.
Does your free health check look for this?
It looks for signs of a hijack, read from the store’s public pages only. Nothing is logged into or tested.
Find out whether your store shows any sign of a hijack, free.
Give us the address and we will read what the store already shows the world: release, support status, PHP, headers, hosting and any sign of a hijack. One page, by email, within two working days. Nothing is accessed or tested.
Magento Open Source, Adobe Commerce and Mage-OS stores
Read from public pages only, and free
Written up by an engineer who read the store
Free store health checkOne page, by email
What you receiveExample report
Magento Security and Upgrade Health Check
example-store.co.ukNeeds attention
Platform
Magento Open Source 2.4.4-p3
Adobe support
ended 12th April 2025
PHP
8.1, end of life
Frontend
Luma
Security headers
2 of 6 present
Hijack indicators
none found
What we would do first. Apply the outstanding security fixes, then plan the upgrade to a supported release.