Your company publishes an app in HubSpot’s marketplace, and this record verifies its domain, so HubSpot shows no “not verified” warning when customers install it. HubSpot checks the record regularly: remove it and the warning comes back.
Name: @ (the domain itself) Type: TXT Value: hubspot-developer-verification=ZjUyYzJkNDYtYTM3OC00YjE0LWJmMzQtN2U1YjAxYzlkOGEw
| Added by | HubSpot — verified domain for a public app |
| Can it be deleted? | Keep it — the service checks it again, and removing it undoes the verification |
Look for it on your domain
Enter a domain: we look up its TXT records and say whether this one is there — naming every other record we recognise.
What it is for
A HubSpot developer account can verify one domain, shared by all its public apps. A verified domain removes the warning banner from the app’s install screen.
Why it is on your domain
- A developer in your company verified the domain for a HubSpot app.
Can you delete it?
Keep it. HubSpot says it keeps checking that the record is present, and that the install warning returns if the record is removed or changed.
Questions
What about hubspot-domain-verification?
A separate HubSpot record, which HubSpot’s documentation does not name; it appears to belong to an account-level domain check, such as user provisioning through Okta or Google.
Sources
Checked on 26 September 2026 against these official sources:
- Legacy public apps — developers.hubspot.com