<p>Yeh - under <code>Settings -&gt; Spam Settings</code> you'll find <code>Block Keywords</code>:</p>
<p><a href="https://i.sstatic.net/fs5AV.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/fs5AV.png" alt="enter image description here" /></a></p>
<p>Adding <code>http://*</code> and <code>https://*</code> should work.</p>
<p>If you get hit with the same spammers throw their domain in there and it should effectively block 'em.</p>
<p>As an aside, the honeypot (and/or) Captcha is pretty effective too since most of the form submissions that contain URLs are garbage.</p>

CC BY-SA 4.0
2021-12-06T21:20:35.837Z
Thank you RiiterKnight! I will try adding this pattern to the "block keywords" field 
Roger Glenn
CC BY-SA 4.0
2021-12-06T22:02:05.573Z
@RogerGlenn: excellent let me know if it works for you, and if so, mark this as the accepted answer if it helped.
RitterKnight
CC BY-SA 4.0
2021-12-06T17:52:45.300Z
2021-12-06T17:52:45.300Z
RitterKnight
<p><code>Craft CMS: 3.5.x</code>
<code>Freeform Lite: 3.11.3</code></p>
<p>Is there a way to flag submissions as spam (or block altogether) when the message field contains hyperlinks?</p>

<plugin-freeform><solspace><spam>
Freeform: disallow hyperlinks in message field
# Freeform: disallow hyperlinks in message field

(Asked by: username_0 on 2021-12-06)

`Craft CMS: 3.5.x`
`Freeform Lite: 3.11.3`

Is there a way to flag submissions as spam (or block altogether) when the message field contains hyperlinks?

**Tags:** plugin-freeform, solspace, spam

---

## 1 answers

### Answer by username_1 on 2021-12-06. Score: 1

Yeh - under `Settings -> Spam Settings` you'll find `Block Keywords`:

[![enter image description here](https://i.sstatic.net/fs5AV.png)](https://i.sstatic.net/fs5AV.png)

Adding `http://*` and `https://*` should work.

If you get hit with the same spammers throw their domain in there and it should effectively block 'em.

As an aside, the honeypot (and/or) Captcha is pretty effective too since most of the form submissions that contain URLs are garbage.

> **Comments:**
> **username_0**: Thank you RiiterKnight! I will try adding this pattern to the "block keywords" field   
> **username_1**: @RogerGlenn: excellent let me know if it works for you, and if so, mark this as the accepted answer if it helped.  

---

