# Not Matching HyperLinks

This feature checks if the text of the link in the user's message matches the actual inserted link and directs to the same website.

## <mark style="color:$primary;">Scam Mechanics.</mark>

If you might know, the links in **Discord** could be exposed like `https://website.com` or non-exposed, i.e., with a URL address (also called a link anchor) hidden behind the text link. This non-exposed type of link can be created with a special **Discord** syntax pattern like this:

&#x20;`[Link text](https://link-anchor.com/target-url)`

Being posted in **Discord** chat, this message will look like this:

<figure><img src="/files/2xHAkBBHlJkPIDbNYqte" alt=""><figcaption></figcaption></figure>

When the link text makes sense, it's okay, because users understand that they are clicking on a text with a hyperlink that can lead them anywhere, and they should be cautious. However, scammers can abuse this **Discord** feature to make the link text look like an exposed link, while hiding the actual link address using this syntax:

&#x20;`[octopeeps.com](https://octopeeps.io)` or  `[www.octopeeps.com](https://octopeeps.io)`

Let's take the first variant (without www):

<figure><img src="/files/JWdPQsOC6i8gDEmlV4HH" alt=""><figcaption></figcaption></figure>

And, being posted in **Discord**, it will look like this:

<figure><img src="/files/5nGejqWCUzzpaTvZU9yc" alt=""><figcaption></figcaption></figure>

You see?! The link text here looks like an absolutely legit website URL, but the link anchor leads to another domain - to <mark style="color:yellow;">**.io**</mark> instead of <mark style="color:yellow;">**.com**</mark>!

A more complex example of this scam message can have this syntax:

`Check the official [octopeeps.com](https://octopeeps.io) website!`

<figure><img src="/files/3U4U6XOMp7b58qnJ6s8a" alt=""><figcaption></figcaption></figure>

Here we see the same picture with a mismatched domain name in the link text and the real URL in the link anchor. However, this time, the message looks even less suspicious because the surrounding text distracts the reader's attention.

## <mark style="color:$primary;">Explanation of the Feature.</mark>

And this is where the <mark style="color:$success;">Not Matching HyperLinks</mark> feature comes into action! It detects if the message contains a text pattern similar to a URL address syntax in the \[square brackets] in link text and checks if it matches the real target URL address, if any, in the following (parentheses), and if it doesn't, blocks the message:

<figure><img src="/files/jLUGilLNxR3fQHNJsdQk" alt=""><figcaption></figcaption></figure>

Depending on your [Guard Settings](/plugins/guard/guard-settings.md), <mark style="color:purple;">**Bocto**</mark> can also post a detailed alert to the <mark style="color:yellow;">**#alerts**</mark> channel it created during the [setup on the server](/getting-started/setup-on-server.md):

<figure><img src="/files/TpNqY4AMJlXeXCBvEvgA" alt=""><figcaption></figcaption></figure>

## <mark style="color:$primary;">Patterns That This Feature Blocks.</mark>

Currently, the <mark style="color:$success;">Not Matching HyperLinks</mark> feature blocks these patterns:

`[https://octopeeps.com](https://octopeeps.io)`

`[www.octopeeps.com](https://octopeeps.io)`

`[octopeeps.com](https://octopeeps.io)`


---

# Agent Instructions: 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://guide.bocto.octopeeps.com/plugins/guard/guard-features/not-matching-hyperlinks.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.