[akshayrajp]

What if they have regex'd that field?

[sebstefan]

If they use a regex? https://[e-mail]?linkedin.com/

If they do it the proper way? It's all ogre

You shouldn't use regex to parse URLs, you should use the URL handler that comes with your language (ex: https://developer.mozilla.org/en-US/docs/Web/API/URL/URL)

```js

    const linkedin = new URL("https://[e-mail]?linkedin.com/");
    console.log(linkedin.host);
    // => "i-dont-have-linkedin.com"

```

[xdennis]

Neat trick. Firefox does give a warning about it:

> You are about to log in to the site “i-dont-have-linkedin.com” with the username “linkedin.com”, but the web site does not require authentication. This may be an attempt to trick you.

> Is “i-dont-have-linkedin.com” the site you want to visit?

If those sites are even more clever than a regex, they might bin your application for this.

[revx]

Ends in LinkedIn.com so that'll pass some of them at least.

[snapcaster]

Hopefully they just match on linkedin.com