Domain verification failing due to "unsupported content type"

I’m getting this error every time I try to verify my domain

Your domain could not be verified: Unsupported content type: ‘application/octet-stream’. This API method only accepts ‘application/json’ requests, but you specified the header ‘Content-Type: application/octet-stream’. Please try again with a supported content type.

I have done these:

  1. Add the TXT record to my DNS provider (Cloudflare)
  2. Use “@” as the name and the content provided by OpenAI in the TXT record
  3. Wait more than 24 hours
  4. Tried on multiple browsers (Chrome and Firefox). Even tried on a fresh browser profile
  5. Tried on multiple devices, desktop, mobile, tablet, Windows and macOS
  6. Cleared cache, restarted devices

Contacted support, but haven’t received any feedback from them. Pretty sure this is a bug on OpenAI’s side.

Please help

Hey, @akmalmzamri, welcome to the community!

Does the domain load normally in a browser?

Yes. Both the apex and www load in the browser. DNSChecker also show the OpenAI verification content already available in all regions

Hrm. Odd. Yeah, might be a bug.

I’d reach out to support if you can, but I’ll pass this along.

Thanks for reporting. Hope you stick around. We’ve got a great community here.

Thanks. Already contacted support yesterday, but haven’t heard anything so far T_T

I wonder if it’s a CloudFlare issue?

Hopefully support gets back with you soon.

Might try searching here too, though I don’t recall this specific problem before.

Couldn’t find a similar issue here. Seems like mine is the first with this error. Not sure if Cloudflare has a compatibility issue with others, but Google verification works (for OAuth, same TXT method)

Hello,
I have exactly the same problem. I’ve tried virtually everything I can think of, but I still haven’t been able to verify my domain. I’ve checked the TXT record multiple times, and everything appears to be correct. I also verified the TXT record using command-line tools and several online DNS checking services, all of which confirm that the record is present and correct.
What should I do next? Is there any alternative way to verify the domain?
My domain is registered with wedos.com⁠ (formerly VEDOS)
Thank you.

Its been a few days. Still havent heard anything from supports. I’ve upgraded my acc to Plus just to publish a Custom GPT but havent been able to do that T_T

Just to add to this, ive tried verifying another domain from another DNS provider (Namecheap), in another ChatGPT account, and still facing the same issue

This looks like a request formatting issue rather than a DNS problem. The domain verification endpoint is receiving Content-Type: application/octet-stream, but it only accepts application/json, which usually means the client or request layer is sending a binary payload or incorrect headers. It would be worth checking the API call (or SDK config) to ensure the verification request is explicitly set to JSON with proper Content-Type: application/json and that no middleware or proxy is overriding headers.

I would like to buy a subscription too (I don’t have one now). I’m still waiting to see if there will be a solution - this situation is discouraging me for now.

The API call and SDK config are both in OpenAI server. Theres no way for us to check that…

I’m seeing the same issue here. The TXT record is publicly resolvable and the value matches, but clicking Check still returns:

Unsupported content type: application/octet-stream

I also tried a clean browser session and different network, with the same result. This looks like an issue with the verification request rather than DNS.

I’ve been trying to verify my domain but i keep getting the below error. I’ve double checked that everything is setup correctly, attempted on different devices, incognito, variations of the urls etc. I see other posts here with the similar issue any fixes?

Your domain could not be verified: Unsupported content type: ‘application/octet-stream’. This API method only accepts ‘application/json’ requests, but you specified the header ‘Content-Type: application/octet-stream’. Please try again with a supported content type.

Same problem here, and I think I’ve found the root cause. It’s a bug in the ChatGPT web client, not anyone’s DNS or registrar.

First, a useful data point for the “is it Cloudflare?” question. Between this thread we now have three different DNS setups all failing the same way: @akmalmzamri on Cloudflare, bartz on wedos com, and me with a domain registered at Namecheap and DNS hosted at WPX. Different registrars, different DNS providers, exact same error. So it isn’t provider specific.

I captured the network traffic (HAR) while clicking “Check” in Settings > Account > Builder profile. Here is what is actually happening.

The button fires a POST to /backend-api/accounts/{account_id}/domains/{domain_id}/check, and the browser sends that request with an empty body (content-length: 0) and no Content-Type header at all. With no Content-Type set, the server treats it as the default application/octet-stream, and a validator that only accepts JSON rejects it. That is the exact “Unsupported content type: ‘application/octet-stream’… only accepts ‘application/json’” message we are all seeing.

The key implication is that this request is rejected at the HTTP layer before the DNS/TXT record is ever checked. The domain name isn’t even in the failing request, because the body is empty. That is why none of the usual fixes work, and it is why changing domains does nothing. I tested a second, unrelated domain and got the identical error. So “review your domain configuration” or “try another domain” cannot resolve this. The request never reaches the stage where the domain matters.

The fix has to come from OpenAI. Either the web client needs to send Content-Type: application/json on this call (with an empty JSON body), or the endpoint needs to accept a POST with no body.

@PaulBellow, thank you for saying you’d pass this along earlier in the thread. Could you escalate it directly to the engineering team this time? Several of us have gone through official support and only received templated replies, and we are now being redirected back here to the forum, so we are going in circles. I have a full HAR capture and a request_id on file from my support ticket that engineering can use to correlate the failing call in their server logs. Happy to share those with whoever picks this up.

This looks like a regression in the client that affects multiple users, and a single deploy fixing that header would resolve it for everyone in this thread.

The only question is whether anyone from @OpenAI_Support is paying attention to this. It seems like the issue has been going on for at least a few weeks now.

I’m in the same situation. I’m managing my DNS through Cloudflare, and even though I added the TXT record, I’m still getting the same error.

i too have the same issue, and my dns provider is also cloudflare.