
Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021



After you register the domain for your website, you might take pride in owning your company’s online address. However, from a legal standpoint, you don’t own it. While you can register it, thieves can hijack it from you. Domain hijacking does not receive a lot of attention, but it is a real threat. Domain hijacking is also very frustrating, as it is relatively easy for thieves to hijack a domain, and once they get control, it can be very difficult and expensive to regain it.
Domain hijackers take advantage of security weaknesses at your domain registrar, your email service, or your own security practices. The technical details are quite lengthy, but basically, thieves get control of your domain by convincing your domain registrar that they are you. Then, the thieves transfer your domain to their own account, usually with a registrar located in a different country. Thieves hijack domains for several criminal reasons, but the usual motive is to take control of your domain and then sell the registration back to you.
Domain hijacking is very costly. According to Symantec, a US-based security software company, the annual cost to firms from domain hijacking is about $400 billion (£310 billion). Many high-profile domains have been hijacked in the past, including Google, Forbes, Twitter, and the New York Times.
If thieves hijack your domain, recovering it can be very difficult. If you think that you have been the victim of domain hijacking, you should immediately notify your domain registrar. In some cases, your registrar can help you regain control of your domain if you can prove to their satisfaction that it has been hijacked. However, in many cases, the only recourse that you will have is a lengthy and costly litigation procedure to try to regain control.
Of course, the best way to deal with domain hijacking is not to have it happen in the first place. There are steps that you can take to minimise the risks:
By taking these steps, you can help avoid the expense and hassle of attempting to recover a hijacked domain in the future.
Share this

3 min read The allure of OpenClaw is undeniable. You deploy a highly autonomous, self-hosted AI agent, give it access to your repositories and inboxes, and watch it reason through complex workflows while you sleep. It is the dream of the ultimate 10x developer tool realized. But as any veteran DevOps engineer will tell you: running an LLM-backed
7 min read There are cloud outages, and then there are us-east-1 outages. That distinction matters because failures in AWS’s Northern Virginia region rarely feel like ordinary regional incidents. They tend instead to expose something larger and more uncomfortable: too much of the modern internet still behaves as though one place is an acceptable concentration point for infrastructure,
7 min read Artificial intelligence is making software easier to produce. That much is already obvious. Code that once took hours to scaffold can now be drafted in minutes. Boilerplate, integration logic, tests, refactors and small internal tools can be generated with startling speed. In some cases, even substantial pieces of implementation can be assembled quickly enough to
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
Find out everything you need to know in our new uptime monitoring whitepaper 2021