---
title: "Comment by Jason Knight on \"Regex…\" | Hashnode"
description: "This regular expression meets all of those security requirements set by the internet people. Except for lengths. :D"
url: "https://hashnode.com/posts/regex/5c19033a82e2450f7afc6dfb/comment/5c194dde3960ebb0612df5b4"
---

[Discussion](https://hashnode.com/posts/regex/5c19033a82e2450f7afc6dfb)

Comment [Regex…](https://hashnode.com/posts/regex/5c19033a82e2450f7afc6dfb)

[Jason Knight](https://hashnode.com/@cutcodedown)

[Dec 18, 2018](https://hashnode.com/posts/regex/5c19033a82e2450f7afc6dfb/comment/5c194dde3960ebb0612df5b4)

> This regular expression meets all of those security requirements set by the internet people.

Except for lengths. :D

[Sébastien Portebois](https://hashnode.com/@sportebois)

[Dec 20, 2018](https://hashnode.com/posts/regex/5c19033a82e2450f7afc6dfb/comment/5c194dde3960ebb0612df5b4#reply-5c1b8348ce0fd2f92cb365f6)

Definitely. I didn't take the time to battle test it, but when I read `(\.[^<>()\[\]\\.,;:\s@"]+)*)` in the sample above, I started to smell redos opportunities here
