Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/web-subdomain-takeoverWeb and bug bounty

web-subdomain-takeover

⁨Claim a dangling DNS record pointing to a deprovisioned service (subdomain takeover). Load after subdomain enum, on CNAMEs to cloud services, "NoSuchBucket"/"404 there isn't a GitHub Pages site here", or dangling A/CNAME. Signals: CNAME → S3/GitHub/Heroku/Azure/Fastly with a fingerprint error page.⁩

v2026.10.14-ee0e0c52 installs+2 in 7 days27 StarsMITsynced 23 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/web-subdomain-takeover

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
08ihLNlHAf…fxZsC9AA==The CLI checks the SHA-256 and the signature before it writes a file.
Packagef08ae1ce…19e925a3
f08ae1ce27ea…ca6319e925a31 file · ⁦1.3 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-subdomain-takeover@ee0e0c5

When it applies

A subdomain's DNS still points (CNAME/A) to a third-party service that no longer has the resource provisioned, so you can register it and serve content on the victim's subdomain.

Why it works

The org deleted the S3 bucket / GitHub Pages / Heroku app but left the DNS record. The provider now serves that hostname to whoever claims the resource next — you. You control content on a trusted subdomain (phishing, cookie theft on the parent domain, OAuth redirect_uri allowlist).

Method

  1. Find candidates: from subdomain enum, resolve CNAMEs (dig CNAME sub.target.com) and look for third-party targets with a "not claimed" fingerprint (nuclei -t takeovers, subjack).
  2. Confirm the fingerprint: the provider's specific unclaimed-resource error (e.g. S3 NoSuchBucket, GitHub Pages 404, Heroku "no such app").
  3. Claim it: register the exact resource name on that provider (bucket/app/pages repo) and serve a proof file — do NOT phish; a harmless proof page is the report.
  4. Assess chained impact: cookie scope on parent domain, OAuth redirect_uri allowlist, CSP script-src including the subdomain, SPF/email.

Gotchas

  • Only some providers are claimable and only with the right fingerprint — a generic 404 isn't takeover.
  • Prove with a benign marker page; don't collect data or run phishing.
  • Note the chained impact (why it matters) — a bare takeover of an unused subdomain may be low without it.

Verify success

You serve attacker-controlled content at the victim's subdomain (proof file loads at sub.target.com), captured with the DNS record + your claimed resource.

References

can-i-take-over-xyz; subjack/nuclei takeover templates; HackerOne takeover reports.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c5f08ae1ceSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login