LobstersWednesday · May 20, 2026FREE

My domain got abused on Github Pages

github-pagessecuritydomain-abusephishing

In a blog post on Meertens.dev, the author details how their personal domain was abused via GitHub Pages. The attacker added the domain to a GitHub Pages site, bypassing the verification step that requires adding a TXT record to the DNS. GitHub's system allowed the domain to be used without proper authorization, resulting in the domain being listed on blocklists for hosting phishing content. This caused the domain's email to be rejected by major providers and the website to be inaccessible. The author notes that GitHub's support was unhelpful, and the issue persisted for weeks. The post highlights a flaw in GitHub's domain verification process, which relies on DNS records that can be manipulated or overlooked. The author suggests that GitHub should require stronger verification, such as confirming ownership via email or a more robust DNS challenge.

// why it matters

GitHub Pages' weak domain verification can let attackers hijack domains, causing reputation damage and service disruption.

Sources

Primary · Lobsters
▸ Read original at meertens.dev

Like this? Get the next digest.

My domain got abused on Github Pages — aigest.dev