# Domain Verification Alternatives **URL:** \ **Category:** HubSpot Ideas\ **Tags:** developer-tools\ **Created:** [April 16, 2021, 3:32pm UTC](https://community.hubspot.com/t/domain-verification-alternatives/35660 "2021-04-16T15:32:53Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![LitmusMark](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/litmusmark/32/44643_2.png) [@LitmusMark](https://community.hubspot.com/u/LitmusMark)\ **Post date:** [April 16, 2021, 3:32pm UTC](https://community.hubspot.com/t/domain-verification-alternatives/35660/1 "2021-04-16T15:32:53Z")
In your documentation,[your domain verification process](https://developers.hubspot.com/docs/api/developer-identity) requires setting up a signature in the root domain TXT record. As your technical team is probably aware, that record is needed for an SPF record. And that means every time that record is queried by a receiving mail server everything in that record gets sent to them. Further, it doesn’t take much to exceed the payload limitation for a UDP packet, and sadly way too many organizations don’t even support switching to TCP for queries, and a lot of mailserver configurations won’t support TCP anyway. So this requirement can quickly be a deal-breaker for even doing business with an organization for the sake of protecting their mail delivery. Please follow the lead of other technical organizations and either support an https-hosted file for this or at least use a TXT record like setup like DMRC or DKIM does, with a proper LHS value. Such as, make the LHS \_hubspot, and then the RHS the unique verification value. ---
**Author:** ![dennisedson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dennisedson/32/28044_2.png) [@dennisedson](https://community.hubspot.com/u/dennisedson)\ **Post date:** [April 16, 2021, 9:22pm UTC](https://community.hubspot.com/t/domain-verification-alternatives/35660/2 "2021-04-16T21:22:59Z")
Hey @LitmusMark Adding this to the ideas board.