What subdomains should users not be allowed to choose?

We are creating one of those applications that is compatible with the current day, allowing users to choose their own subdomain.

xxx.company.com 

As this becomes commonplace, it would be useful to compile a list of subdomains that should be prohibited for users to select either for technical / security reasons (e.g. www ) or etiquette (e.g. sex ).

This question is a wiki community, so please edit to add your suggestions.

+4
source share
5 answers

Just notice the suggested profanity filtering.

In general, the filter of profanity makes sense only if you are really confident in the native language of the target audience. Otherwise, you can make your international clients angry: there may be words in English that are profanity in another language (there is no way to find them all), and the words you filter out may be perfectly correct words in other languages. When the Sims 3 was released, EA forums filtered out the word β€œdamit,” but they did it in localized forums, and β€œdamit” is a very common German word. It made it difficult to write anything. β€œSex” also means β€œsix” in Swedish.

This may or may not be a problem if it is only about subdomains. I will just be careful and, rather, block words for technical and security reasons (or things like your own trademarks / products or something else).

It may be wise to use a special domain for custom things that do not have any subdomains, and use a different domain for any subdomains that you need. Thus, you will not need to block the subdomain names in the "user" domain at all.

+3
source
 www register mail pop pop3 test beta stage dev http https sex 

And any words considered profanity (not listed here to protect the innocent)

+2
source
 smtp webmail ftp 
+1
source

We have a smart user who has registered localhost . Could be a real security issue.

also dns

+1
source
 abuse admin donate store payment 
0
source

All Articles