# IP address data type

**URL:** <https://community.fibery.io/t/ip-address-data-type/5531>\
**Category:** Ideas & Features\
**Created:** [December 13, 2023, 11:49pm UTC](https://community.fibery.io/t/ip-address-data-type/5531 "2023-12-13T23:49:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Absolute](https://avatars.discourse-cdn.com/v4/letter/a/b2d939/32.png) [@Absolute](https://community.fibery.io/u/Absolute)\
**Post date:** [December 13, 2023, 11:49pm UTC](https://community.fibery.io/t/ip-address-data-type/5531/1 "2023-12-13T23:49:30Z")

</div>

Could we have “IP address (v4)” and “IP address (v6)” as either a data type or a formatting option for “Number”?

Thank you!

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [December 13, 2023, 11:55pm UTC](https://community.fibery.io/t/ip-address-data-type/5531/2 "2023-12-13T23:55:03Z")

</div>

How would defining a field as an IP address affect its behaviour?  
Do you mean that the field should not allow a user to type a set of characters that do not represent a valid IP address?  
Or do you want something to happen when a field containing a valid IP address is clicked?

---

<div class="post-metadata">

**Author:** ![Absolute](https://avatars.discourse-cdn.com/v4/letter/a/b2d939/32.png) [@Absolute](https://community.fibery.io/u/Absolute)\
**Post date:** [December 14, 2023, 3:32am UTC](https://community.fibery.io/t/ip-address-data-type/5531/3 "2023-12-14T03:32:50Z")

</div>

@Chr1sG Validation and identification. Perhaps you could automatically format a correct number of characters, but my thought was to enforce valid addresses and identify the purpose of the field.

No need to make it clickable.