Below are guidelines for entering URLs when configuring policies or settings in the admin portal.
- Enter URLs in lowercase letters only (type www.safemarch.com, and not www.Safemarch.com).
- The URL must not contain the protocol schema (that is, do not type http://www.safemarch.com; instead, just type www.safemarch.com).
- A leading period (“.”) functions as a wildcard to the left of the named URL up to five subdomain levels deep, meaning that the same policies will be applied to the subdomains. Thus, the entry .example.com also applies to:
- whitelists atlanta.example.com and serv3.serv2.serv1.atlanta.example.com
In the absence of a leading period, the stated domain/subdomain entry must match exactly.
- The node will always look for a specific match.
Consider the following example with two custom categories:
-Category 1: .domain.com
-Category 2: .cloud.domain.com
Accessing cloud.domain.com will result in the Category 2 policies being applied since there is a specific match for this URL. Domain.com and its subdomains will remain in Category 1.
- Wildcard characters (such as an asterisk) addressing the right side of a stated URL are not explicitly used; they are always assumed. Thus the URL entry “www.safemarch.com” will apply to:
However, if you want to categorize a specific file or directory under the root domain (for example, “mydomain.com/resources/” or “mydomain.com/resources/ftp.htm”), please note the following:
- www.mydomain.com/resources/ftp.htm (with no trailing forward-slash) will match the exact string.
- www.mydomain.com/resources/ (with trailing forward-slash) will match any file or directory underneath it.
Do not use an asterisk ("*") as a wildcard character.