> For the complete documentation index, see [llms.txt](https://blog.s1rn3tz.ovh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blog.s1rn3tz.ovh/pentest-web/broken-link-hijacking.md).

# Broken Link Hijacking

## Méthodologie

* Rassembler les liens de réseaux sociaux
* Suivre ces liens

Si l'un d'entre eux renvoie vers un compte inconnue (supprimé ou modifié sans avoir été reconfiguré dans la page)

* Créer un compte au nom du lien sur le réseau social en question
* Suivre le lien du site

Si cela fonctionne, le lien redirigera vers le compte que vous avez créé.

## Broken Link Checker

Broken Link Checker ou blc est un outil permettant de vérifier les lien d'un site web à la recherche de broken links.

Exemple d'utilisation:

*`$ blc https://target.com/ -ro`*

ressource: <https://github.com/stevenvachon/broken-link-checker>

## Writeup

<https://mehedishakeel.medium.com/broken-link-hijacking-my-second-finding-on-hackerone-d715b0713fca>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://blog.s1rn3tz.ovh/pentest-web/broken-link-hijacking.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.