← Retour au blog
tech 19 May 2026

My Domain Abused on GitHub Pages: How to Avoid This Mishap

A developer shares how his domain was hijacked on GitHub Pages, and the lessons you can learn to secure your own domain. Discover the steps to protect your online projects.

Article inspired by the original source
My domain got abused on Github Pages ↗ meertens.dev

Introduction: When Your Domain is Held Hostage

Imagine receiving an email from Google Search Console notifying you that a new owner has emerged for one of your subdomains. This is exactly what happened to Roland Meertens while traveling through Africa. Such a situation may seem unbelievable, but it is very real and can affect anyone using GitHub Pages to host their site.

The Problem: Lack of Control Over Subdomains

GitHub Pages is a fantastic platform for hosting static websites for free. It allows anyone to quickly showcase their projects without worrying about servers or hosting costs. However, this ease of use comes with certain risks. When you configure a custom domain for your GitHub Pages site, you add a DNS record pointing to GitHub's servers. If you use a wildcard record, as Meertens did with *.immersivepoints.com, it opens the door to abuse.

In Meertens' case, someone was able to use the subdomain kafka.immersivepoints.com from a private GitHub repository, making detection and resolution of the issue more difficult.

Why Does This Happen?

The setup for GitHub Pages relies on a CNAME file in your repository, which indicates the custom domain associated with your site. If another user sets up the same domain in their repository, GitHub doesn't necessarily prevent the resolution of that domain, leading to potential confusion and abuse.

Potential Risks

  • Phishing and Scams: A hijacked domain could be used for phishing attacks or to host malicious sites.
  • Reputation Damage: If a malicious site is associated with your domain, you risk tarnishing your online reputation.
  • SEO Impact: Search engines may penalize your domain if they detect undesirable content.

How to Protect Your Domain

  1. Proactive Monitoring: Set up Google Search Console to receive alerts about changes in your domain's ownership.
  2. Strict DNS Configuration: Avoid using wildcard records for your custom domains on GitHub Pages. Define only the necessary subdomains.
  3. Regular Checks: Periodically check your domain's DNS records to detect any unauthorized changes.
  4. Alert Services: Tools like "Can I Take Over XYZ" can help you identify domains vulnerable to similar takeovers.

Conclusion

Roland Meertens' mishap is an important reminder of the risks associated with hosting sites on third-party platforms. By taking a few simple precautions, you can protect your domain and, by extension, your online reputation. The security of your projects is well worth a little extra attention.

Let's discuss your project in 15 minutes.

GitHub Pages Domain Security DNS Configuration Cybersecurity Website Hosting
Deepthix newsletter · 100% AI · every Monday 8am

An AI agent reads tech for you.

Our AI agent scans ~200 sources per week and ships the best articles to your inbox Monday 8am. Free. One click to unsubscribe.

Visit the newsletter page →

Want to automate your operations?

Let's talk about your project in 15 minutes.

Book a call