# Wildcard Domain Allow List

**URL:** <https://devforum.zoom.us/t/wildcard-domain-allow-list/99405>\
**Category:** Zoom Apps\
**Tags:** domainvalidation\
**Created:** [December 1, 2023, 9:30pm UTC](https://devforum.zoom.us/t/wildcard-domain-allow-list/99405 "2023-12-01T21:30:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![aneuhold](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/aneuhold/32/54460_2.png) [@aneuhold](https://devforum.zoom.us/u/aneuhold)\
**Post date:** [December 1, 2023, 9:30pm UTC](https://devforum.zoom.us/t/wildcard-domain-allow-list/99405/1 "2023-12-01T21:30:57Z")

</div>

**Zoom Apps Configuration**  
_Share the Zoom Apps configuration (e.x. React, Vanilla JS, Node.js) you’re working with to give relevant context._  
Ruby + React, but this isn’t specific to the framework being used. This is just about the overall configuration in the zoom app portal.

**Description**  
Our company is updating to a micro-services architecture and will need to update the domain allow list. Would it be okay to add something like `*.companydomain.com` to a Zoom App “Domain Allow List”, or does each subdomain need to be added individually? There seems to be mixed responses in the developer forum.

**Error?**  
No error, just a question

**Troubleshooting Routes**  
N/A

**How To Reproduce**  
N/A

---

<div class="post-metadata">

**Author:** ![aneuhold](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/aneuhold/32/54460_2.png) [@aneuhold](https://devforum.zoom.us/u/aneuhold)\
**Post date:** [December 6, 2023, 7:07pm UTC](https://devforum.zoom.us/t/wildcard-domain-allow-list/99405/2 "2023-12-06T19:07:24Z")

</div>

This was resolved in a different chat, it sounds like this is allowed but the ownership needs to be proven on the domain with a wildcard. 🎉