# Custom Domain on forms

**URL:** <https://community.hubspot.com/t/custom-domain-on-forms/30462>\
**Category:** HubSpot Ideas\
**Tags:** forms\
**Created:** [January 20, 2021, 9:42am UTC](https://community.hubspot.com/t/custom-domain-on-forms/30462 "2021-01-20T09:42:42Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![JQuirk](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jquirk/32/99949_2.png) [@JQuirk](https://community.hubspot.com/u/JQuirk)\
**Post date:** [January 20, 2021, 9:42am UTC](https://community.hubspot.com/t/custom-domain-on-forms/30462/1 "2021-01-20T09:42:42Z")

</div>

Hi. It would be great if the URLs for forms could be edited or linked to our domain, rather than the generic hubspot URL that it creates.

Thanks

---

<div class="post-metadata">

**Author:** ![eterobby](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/eterobby/32/63860_2.png) [@eterobby](https://community.hubspot.com/u/eterobby)\
**Post date:** [October 5, 2023, 6:58pm UTC](https://community.hubspot.com/t/custom-domain-on-forms/30462/2 "2023-10-05T18:58:53Z")

</div>

This would be great as we’ve found that several of our client schools have web content filtering that appears to be blocking [hsforms.com](http://hsforms.com), so staff at those schools are apparently unable to submit HubSpot forms, which are necessary for gaining access to private content we host for them. If we could set our custom domain as a CNAME to [forms.hsforms.com](http://forms.hsforms.com), then we would be able to bypass those filters automatically.

**Edit:** I should clarify that, for our use cases, the more important domain to address is the form _ **submission** _ domain ([forms.hsforms.com](http://forms.hsforms.com)), since this domain getting blocked affects all forms whether they are embedded or shared on the generic HubSpot URL. It would similarly be nice to use a custom domain when sharing forms (in place of [share.hsforms.com](http://share.hsforms.com)), but this is a lower priority to us than ensuring that embedded forms work reliably.

---

<div class="post-metadata">

**Author:** ![MClouatre](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@MClouatre](https://community.hubspot.com/u/MClouatre)\
**Post date:** [March 1, 2024, 5:55pm UTC](https://community.hubspot.com/t/custom-domain-on-forms/30462/3 "2024-03-01T17:55:31Z")

</div>

was this request ever addressed?

---

<div class="post-metadata">

**Author:** ![VGustafsson](https://avatars.discourse-cdn.com/v4/letter/v/e19b73/32.png) [@VGustafsson](https://community.hubspot.com/u/VGustafsson)\
**Post date:** [April 8, 2024, 11:59am UTC](https://community.hubspot.com/t/custom-domain-on-forms/30462/4 "2024-04-08T11:59:58Z")

</div>

Any update on this request?

We also have issues with this. We want to add questions and alternatives to a form but I understand it as once published, a form cannot be edited. Then we need to create a new form but the issue is that we have QR codes linking to the **[survey.hsforms.com/](http://survey.hsforms.com/){first\_form}** printed on expensive cubes. Creating a new form would of course have a URL such as **[survey.hsforms.com/](http://survey.hsforms.com/){second\_form}**. Given that we can’t have the form on our company’s domain and that Hubspot don’t support redirects for **[survey.hsforms.com](http://survey.hsforms.com)**-hosted pages leaves us in a catch 22 situation.

Going forward we will always host QR printed URL’s on our own domain but it would be great to have this resolved.

---

<div class="post-metadata">

**Author:** ![glebs](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/glebs/32/202015_2.png) [@glebs](https://community.hubspot.com/u/glebs)\
**Post date:** [June 28, 2024, 11:59am UTC](https://community.hubspot.com/t/custom-domain-on-forms/30462/5 "2024-06-28T11:59:11Z")

</div>

Would be great to be able to use (1) a custom domain, similarly as it’s done for meetign links, and (2) customise the full URL.

(1) e.g. [forms.mywebsite.com](http://forms.mywebsite.com)

(2) e.g. /my-custom-form-name

---

<div class="post-metadata">

**Author:** ![danraywill](https://avatars.discourse-cdn.com/v4/letter/d/3bc359/32.png) [@danraywill](https://community.hubspot.com/u/danraywill)\
**Post date:** [July 7, 2025, 6:06pm UTC](https://community.hubspot.com/t/custom-domain-on-forms/30462/6 "2025-07-07T18:06:01Z")

</div>

This needs more attention. Xfinity and other ISPs are blocking [hsforms.com](http://hsforms.com). We need to be able to set our own domains so we aren’t dragged down by the poor reputation of the host domain.

---

<div class="post-metadata">

**Author:** ![MarcoHuber](https://avatars.discourse-cdn.com/v4/letter/m/7ea924/32.png) [@MarcoHuber](https://community.hubspot.com/u/MarcoHuber)\
**Post date:** [July 14, 2025, 9:10am UTC](https://community.hubspot.com/t/custom-domain-on-forms/30462/7 "2025-07-14T09:10:05Z")

</div>

Same here

---

<div class="post-metadata">

**Author:** ![Austinhc](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@Austinhc](https://community.hubspot.com/u/Austinhc)\
**Post date:** [July 17, 2025, 5:12pm UTC](https://community.hubspot.com/t/custom-domain-on-forms/30462/8 "2025-07-17T17:12:23Z")

</div>

Came here to upvote. Seeing businesses treat hsforms poorly.

---

<div class="post-metadata">

**Author:** ![BStanleyUK](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bstanleyuk/32/42054_2.png) [@BStanleyUK](https://community.hubspot.com/u/BStanleyUK)\
**Post date:** [September 22, 2025, 11:09am UTC](https://community.hubspot.com/t/custom-domain-on-forms/30462/9 "2025-09-22T11:09:42Z")

</div>

Same here please! +1 👍

---

<div class="post-metadata">

**Author:** ![LBeer7](https://avatars.discourse-cdn.com/v4/letter/l/439d5e/32.png) [@LBeer7](https://community.hubspot.com/u/LBeer7)\
**Post date:** [October 7, 2025, 8:37am UTC](https://community.hubspot.com/t/custom-domain-on-forms/30462/10 "2025-10-07T08:37:53Z")

</div>

Upvoting, our forms are now also being blocked by McAfee

---

<div class="post-metadata">

**Author:** ![bsjut](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bsjut/32/101160_2.png) [@bsjut](https://community.hubspot.com/u/bsjut)\
**Post date:** [February 25, 2026, 7:55pm UTC](https://community.hubspot.com/t/custom-domain-on-forms/30462/11 "2026-02-25T19:55:18Z")

</div>

This should be prioritized more. With “Strict Tracking Prevention” in Browsers getting rolled out, embedded Hubspot forms are simply not loaded anymore. The fastest workaround would be to be able to load forms under a custom first party domain

---

<div class="post-metadata">

**Author:** ![SOleyar](https://avatars.discourse-cdn.com/v4/letter/s/87869e/32.png) [@SOleyar](https://community.hubspot.com/u/SOleyar)\
**Post date:** [March 4, 2026, 6:17pm UTC](https://community.hubspot.com/t/custom-domain-on-forms/30462/12 "2026-03-04T18:17:45Z")

</div>

Upvoting, desperately need this option.  
It’s an option with files, why not forms?

---

<div class="post-metadata">

**Author:** ![vRune4](https://avatars.discourse-cdn.com/v4/letter/v/ba9def/32.png) [@vRune4](https://community.hubspot.com/u/vRune4)\
**Post date:** [April 9, 2026, 8:59am UTC](https://community.hubspot.com/t/custom-domain-on-forms/30462/13 "2026-04-09T08:59:44Z")

</div>

My first thought was that this won’t help if all forms are then reachable through my new custom domain.  
But if my user can say “\_this\_ is my domain and **only** my forms should be loadable through this custom domain” then I (and others) won’t have to worry about some rando creating a phishing form on [hsforms.com](http://hsforms.com).  
Quite frankly, if I made a browser or was setting up a blocklist for an ISP, [hsforms.com](http://hsforms.com) would be one of the first targets on my list. And I would completely ignore Ken from Hubspot when he posts “we’ve cleaned the phishing forms now, [hsforms.com](http://hsforms.com) is once again safe!”. (one of the top results in google when I researched this issue -- nothing against Ken, but… Come on..)  
FWIW: The issue that struck us was that several of our users have Edge running with strict tracking prevention. And no, I’m not going to tell them to switch browser.

---

<div class="post-metadata">

**Author:** ![RubyKL](https://avatars.discourse-cdn.com/v4/letter/r/5fc32e/32.png) [@RubyKL](https://community.hubspot.com/u/RubyKL)\
**Post date:** [August 6, 2026, 5:28pm UTC](https://community.hubspot.com/t/custom-domain-on-forms/30462/14 "2026-08-06T17:28:44Z")

</div>

Hey there, I’d really like to edit the HS forms URL to include our own domain because right now as it stands, this breaks tracking of user journeys, i.e. from Google PPC source… Pls tell me whether this has been addressed by HS.

---

<div class="post-metadata">

**Author:** ![SabariRam](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/sabariram/32/30222_2.png) [@SabariRam](https://community.hubspot.com/u/SabariRam)\
**Post date:** [September 24, 2026, 7:12pm UTC](https://community.hubspot.com/t/custom-domain-on-forms/30462/16 "2026-09-24T19:12:51Z")

</div>

_Hi Everyone,_

_Thank you all for taking the time to submit, vote and comment on this Idea._

_I’m Sabari, the PM for HubSpot’s Forms tool._

_At this time there are no plans to develop this Idea. This is not to say that this idea will never be developed, just that there are no plans to do so at this time._

_Regards,_

_Sabari_

---

<div class="post-metadata">

**Author:** ![eterobby](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/eterobby/32/63860_2.png) [@eterobby](https://community.hubspot.com/u/eterobby)\
**Post date:** [September 25, 2026, 12:51pm UTC](https://community.hubspot.com/t/custom-domain-on-forms/30462/17 "2026-09-25T12:51:55Z")

</div>

Thank you for the update. Do you have any feedback on the problem that various ISPs and content blockers are known to the global domain that is currently used? How is this being addressed, short of not using Hubspot forms?
