custom url category with non http and https port.

Showing results for 
Show  only  | Search instead for 
Did you mean: 

custom url category with non http and https port.

L2 Linker



I Have created custom URL category e.g  category name (* Now I want to create inbound rule like below.


Source zone :- Internet 

Destination Zone :- LAN

Destination IP :- Any

Port :- 389 , 4172

URL Categary :- 'Custome category'

Security Profile : Any


My doubt is will this work on port 389 and 4172 port or this will work only on http and https port



Dhananjay Bhakte




Accepted Solutions

Hi @DhananjayBhakte 

Custom URL categories only work for http and TLS traffic - not only for apps web-browsing and ssl as there are quite a few more that are based on http/tls traffic - but at least for ssh you cannot use a custom URL category. 

View solution in original post


L2 Linker



could you please clarify what you are trying to achieve here? The application and the service are independend of each other. You can easily create a rule allowing SSL and Web-Browsing on port 389 and 4172.

Kind regards,
// If you like my answer force commit it.

HI Rene,


I have requirement from customer to open port 389 and 4172 for eg *.xyz domain.

So I created custom category * and have to create rule by calling this category into rule and will allow only 389 and 4172 ports.

As far my understanding url category work only for ssl and web-browsing traffic, so just wanted to know if I keep url category in rule for port port 389 and 4172 will that rule work?






ok now I got you. So you are correct URL filtering is working with http/https only. Futhermore it is kind of uncommon to have URL filtering active in inwards direction. So I saw the request for port 389 which is basically LDAP, dont know for 4172. However please make yourself familiar with the conecpt of an "application firewall" - we do not open ports anymore. But in term of customers request you are right, this is not going to work.

Kind regards,
// If you like my answer force commit it.

Hi @DhananjayBhakte ,


It sounds like you need FQDN not URL. 

You can use FQDN object as source or destination address in the policy. Firewall will query the DNS server and use this fqdn to resolve it to IP address. The received IP will be cached for configured amount of time (probably 30min was the default, but not sure). 

Given the port from your description it sound be more reasonable to use FQDN instead of URL filtering. 


To be more precise URL custom category  will work with web-based application. If you think for a bit it is logical - firewall needs to know which part of the traffic is the URL, so it doesn't matter what port you are using

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!