Why is ChatGPT Business Hub's DNS verification window 30 minutes?
ChatGPT Business Hub limits DNS TXT verification to roughly 30 minutes, far shorter than typical DNS propagation times, which can run from minutes to 48…
ChatGPT Business Hub caps its domain TXT verification at roughly 30 minutes because the record is tied to a single verification session, not because DNS itself moves that fast. Real-world DNS propagation can take anywhere from a few minutes to 24 hours or more depending on your provider and TTL settings, so many businesses see the record expire before it has fully propagated. If that happens, you restart the domain step and try again with a fresh value, which makes it a recoverable setback rather than a dead end.
What the 30-minute DNS verification window is
When you claim a business profile in ChatGPT Business Hub, the platform asks you to add a TXT record to your domain's DNS settings to prove ownership. Spotibo's guide to Business Hub verification says you only have 30 minutes to complete DNS verification once the process starts, and it advises having domain DNS access ready in advance because you'll need to update settings within that window. A separate guide from South Asia Digital confirms the figure: ChatGPT generates a unique value for each verification session, and the record expires roughly 30 minutes after it's issued. That guide also warns the whole flow is single-session, meaning nothing persists as a draft until the full sequence, from domain verification through contact details, is completed in one sitting.
One tester at Botrank measured this directly and found the record expired about 30 minutes after it was generated. That matches the other reports closely enough to treat 30 minutes as the working figure, even if exact session lengths vary slightly.
Why OpenAI set such a short window, and the gap with real DNS propagation times
OpenAI hasn't published its reasoning for the 30-minute limit. A user on the OpenAI Developer Community forum raised this concern directly in a thread titled "Introducing Businesses in ChatGPT in beta," arguing that the window doesn't account for how long DNS propagation actually takes. The poster put it plainly: even if you add the correct DNS record to a registrar like Namecheap immediately, it may not propagate globally within 30 minutes. They proposed extending the window to at least 48 to 72 hours.
This gap matters because OpenAI's own documentation for a related but separate flow, domain verification inside the Admin Console, uses a far more generous window. OpenAI's help article on domain verification states that if a verification attempt expires before you finish, you can start a new attempt within a new 7-day window, and that a completed domain verification doesn't expire at all. That 7-day allowance for a different OpenAI product makes Business Hub's 30-minute cap look tight by comparison, though it isn't evidence that the same rule applies across both systems.
How long DNS propagation actually takes in practice
Registrar guidance varies a lot. In a hands-on test, Frac.tl reported that domain verification can add time while your DNS record takes effect, noting GoDaddy says this usually happens within an hour while Namecheap says about 30 minutes. That tester's own experience ran faster than either estimate: their DNS verification went through within a few minutes.
Other reports show much longer waits for the same TXT flow. m16 Marketing found that a TXT record can take up to 24 hours to be seen. PlanConversion reported propagation can take minutes to 48 hours depending on the provider, and that one agency it spoke with saw its record expire in about a day rather than 30 minutes, which suggests the session length itself may not be perfectly fixed in every case.
For general DNS context beyond Business Hub, Azion's explainer on DNS propagation breaks this down by TTL: a record with TTL 300 seconds typically propagates globally in 5 to 15 minutes, while one with TTL 86400 seconds can take up to 48 hours. GoDaddy's help documentation states the industry standard similarly, usually a few hours but up to 48 hours in some cases. SpeedTestHQ adds that most A, AAAA, CNAME, MX and TXT changes propagate globally within 15 minutes to 2 hours when TTLs sit at typical low values of 300 to 3600 seconds. Put together, a 30-minute window sits at the fast end of what's achievable, and reliably so only if your TTL was already low before you started.
What happens if your record doesn't verify in time
If the DNS record doesn't become visible within the window, the OpenAI Developer Community thread describes the outcome clearly: the attempt expires or fails. It isn't a permanent block. PlanConversion's guide instructs you to return to Business Hub before the record expires, and if it did expire, generate a new one and replace the old value. Hive Digital's step-by-step guide frames it the same way, noting the screen shows when the record expires, so missing the window just means starting the domain step again for a fresh value.
A roundup of early feedback from Geosnap lists this among three common snags early users hit: the tight DNS window, identity checks that fail with no visible reason and can't be resubmitted, and a VAT number field that turned out mandatory even for businesses that don't have one. If you're weighing whether claiming your profile now is worth the hassle, our post on whether you should claim your business now or wait for launch covers that trade-off.
How to beat the window
The most consistent workaround is lowering your TTL before you start. The OpenAI community thread suggests setting DNS TTL to 5 minutes, which lines up with Azion's data showing a 300-second TTL propagates in roughly 5 to 15 minutes globally, well inside a 30-minute session. Hive Digital's troubleshooting table adds a practical fallback: if verification fails because DNS hasn't propagated yet, or because the host was entered with the domain doubled, wait 15 to 30 minutes and retry.
Our view: given how much propagation times vary by registrar, the safest order of operations is to drop your TTL to its lowest setting a day ahead of starting the Business Hub flow, confirm the TXT record is visible with a public DNS checker before clicking verify, and only then begin the 30-minute session. Treat the first attempt as a dry run rather than assuming it will work first time, especially if your registrar tends toward the slower end of the range.
Alternative verification methods if DNS keeps failing
The notes available to us don't detail a separate non-DNS verification path inside Business Hub itself, so we can't confirm what alternatives exist beyond restarting the domain step with a new TXT value. This is a real gap in the evidence. If your DNS keeps failing for reasons unrelated to timing, such as a misconfigured host entry, Hive Digital's table notes a doubled domain entry is a common cause, but we have no confirmation of a fallback method like email or file-based verification for this specific flow.
Other Business Hub verification pitfalls to watch for
DNS timing isn't the only snag. The Geosnap roundup also flags identity checks that fail silently with no option to resubmit, and a VAT number field that's mandatory even where it doesn't apply, which matters if you're based outside the US. If that's you, our guide on whether a non-US business can claim its Business Hub profile walks through what to expect. Once you're verified, it's worth checking whether the listing earns its keep: our analysis of whether Business Hub sends clicks to your website and our separate look at Business Hub clicks and website traffic are useful next reads before you invest more time chasing verification.
Frequently asked questions
How long does ChatGPT Business Hub's DNS verification window actually last?
Multiple independent reports, including Spotibo and Botrank's hands-on test, put the window at roughly 30 minutes from when the TXT record is generated.
What happens if my DNS record doesn't propagate within the window?
The OpenAI Developer Community describes the verification attempt simply expiring or failing. PlanConversion and Hive Digital both confirm you just restart the domain verification step and get a fresh TXT value to add.
Can I speed up DNS propagation before I start?
Yes. The OpenAI community thread suggests setting your DNS TTL to 5 minutes beforehand, and Azion's propagation breakdown shows a 300-second TTL typically propagates globally in 5 to 15 minutes, comfortably inside the 30-minute session.
Is 30 minutes long enough according to registrars themselves?
It depends on the registrar. Frac.tl reports GoDaddy citing up to an hour and Namecheap citing about 30 minutes, while m16 Marketing found TXT records can take up to 24 hours to be seen, so results vary widely by provider.
Does OpenAI use a longer window anywhere else?
Yes, but for a different product. OpenAI's own help documentation for Admin Console domain verification gives a 7-day setup period and states that a completed domain verification does not expire, which is far more generous than the Business Hub's 30-minute session.
Sources
- ChatGPT business hub: How to verify your website
- How to Verify Your Business on ChatGPT: 6-Step Checklist - South Asia Digital
- How to Create Your ChatGPT Business Profile: A Step-by-Step Guide
- Introducing Businesses in ChatGPT in beta - Announcements - OpenAI Developer Community
- Verifying your domain for OpenAI identity
- How To Claim Your Business on ChatGPT: Step-by-Step Guide
- How to Claim and Verify Your Business in ChatGPT (Step-by-Step)
- How to verify your domain for ChatGPT Business Hub with a DNS TXT record
- How DNS Propagation Works
- What factors affect DNS propagation time?
- DNS Propagation Explained: Why DNS Changes Take Time
- How to Claim and Verify Your Business in ChatGPT
- Businesses in ChatGPT is live: how to claim your profile and what it shows
- Troubleshooting authentication
Want more Sited in your Google results?
Add Sited as a preferred source on Google (opens in a new tab)

