explaingit

edoverflow/can-i-take-over-xyz

5,666PythonAudience · developerComplexity · 1/5Setup · easy

TLDR

A community-maintained reference list that tells you whether hundreds of third-party services are vulnerable to subdomain takeover, where an expired DNS record lets an attacker claim your subdomain.

Mindmap

mindmap
  root((Subdomain Takeover))
    What it is
      DNS points to deleted service
      Attacker claims abandoned URL
    Services covered
      Hundreds of providers
      Pass or fail status
    Fingerprints
      Detection patterns
      JSON export
    Use cases
      Bug bounty research
      Security scanning
      Safe PoC demos
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Look up whether a third-party hosting service your company uses is vulnerable to subdomain takeover before decommissioning an account

USE CASE 2

Use the exported JSON fingerprint file to add subdomain takeover detection to your own security scanning tool

USE CASE 3

Follow the safe proof-of-concept guide to correctly demonstrate a subdomain takeover finding in a bug bounty program

USE CASE 4

Contribute a newly discovered vulnerable service by opening a GitHub Issue with the fingerprint and evidence

Tech stack

PythonJSON

Getting it running

Difficulty · easy Time to first run · 5min

In plain English

This repository is a community-maintained reference list for a specific type of security vulnerability called a subdomain takeover. The problem occurs when a website's DNS record points to a third-party service, such as a hosting platform or cloud provider, but that service account has been deleted or cancelled. An attacker can then register a new account on that same service, claim the abandoned address, and effectively control a subdomain of the original website without the owner realising. The project answers the question of whether a given service is vulnerable to this kind of claim. It maintains a large table listing hundreds of services, noting whether each one is currently vulnerable, what text pattern appears on the page when a takeover is possible, and links to discussion threads where researchers have worked through the details. An automated system checks the fingerprints regularly and marks each entry as passing or failing. The README also explains how to safely demonstrate a subdomain takeover if you find one during a security test or bug bounty program. The recommended approach is to claim the subdomain quietly and serve a harmless file at a non-obvious path, rather than posting anything visible on the main page. This lets you prove the vulnerability to the program without causing harm or drawing unwanted attention. Contributing is done through GitHub Issues using a provided template, so researchers who find new vulnerable services can add them to the list for others to benefit from. The fingerprint data is also exported as a JSON file that other tools can consume programmatically. The project is explicitly a research guide, not a guarantee. The maintainers note that accuracy depends on community contributions, and individual bug bounty programs set their own rules about what counts as an acceptable proof of concept. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1
Which services in can-i-take-over-xyz are currently marked as vulnerable to subdomain takeover, and what fingerprint text should I look for when scanning?
Prompt 2
I found a subdomain pointing to an unclaimed Fastly endpoint, how do I safely demonstrate this takeover in a bug bounty program following the can-i-take-over-xyz guidelines?
Prompt 3
Write a Python script that reads the can-i-take-over-xyz JSON fingerprint file and checks a list of my subdomains' HTTP responses for takeover risk
Prompt 4
How do I submit a new vulnerable service to the can-i-take-over-xyz project, what information do I need to include in the GitHub Issue?
Prompt 5
Explain what a subdomain takeover vulnerability is and why deleting a cloud account without removing DNS records creates a security risk
Open on GitHub → Explain another repo

← edoverflow on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.