Netlify still intercepts my domain m1ssion.com even after removal – URGENT

Hello,
I’m the legal owner of the domain m1ssion.com and I’ve already removed all associations with Netlify.
The domain is now correctly configured to work with Vercel, and DNS records point to the correct A record.

However, when accessing https://m1ssion.com, Netlify still returns a Site Not Found page, blocking my production deployment.

:fire: This is extremely urgent – I need your help to:

  • Fully purge any residual cache or record associated with m1ssion.com
  • Ensure Netlify does not intercept any request to this domain anymore

Example error:
Netlify Internal ID: 01K155T2NT6RKSX056EH11ADJ

Thank you in advance :folded_hands:
— Joseph Mulé – M1SSION™

Hi @wikus77,

This has been automatically escalated to the helpdesk. You should hear back soon.

P.S.: This was an automated message. We use AI to check if someone’s trying to request something that can only be worked on by Netlify-staff. Rest assured, the ticket will be worked on by a human.

Hello Netlify Team,

I’m requesting an urgent and final removal of any association between my domain and the Netlify platform.

  • :white_check_mark: Domain: m1ssion.com
  • :cross_mark: The original Netlify project using this domain has been deleted
  • :white_check_mark: I have already added the TXT record: name: verified-for-netlify

value: https://support.netlify.com/t/remove-m1ssion-dns-routing - :white_check_mark: My DNS is now fully controlled via Cloudflare

  • :white_check_mark: My A records point to 76.76.21.21 (Vercel)
  • :cross_mark: But https://m1ssion.com still shows a Netlify 404 page

This is blocking my production release.

:megaphone: Please purge m1ssion.com from all Netlify CDN layers, cache, routing, and origin config.

The TXT record is live and valid.
Please confirm once the domain is fully removed from Netlify’s backend.

Thank you,
Joseph MULÉ – Owner of m1ssion.com

Hi @wikus77,

This has been automatically escalated to the helpdesk. You should hear back soon.

P.S.: This was an automated message. We use AI to check if someone’s trying to request something that can only be worked on by Netlify-staff. Rest assured, the ticket will be worked on by a human.

Hi, @wikus77. Please stop blaming Netlify for this issue. Netlify has never controlled the DNS for this domain. This has always used external DNS so any incorrectly cache DNS records are completely out of Netlify’s control. This is a domain only you control and only you can fix this issue.

I’ve replied with more detail in the support ticket and this is an ask to stop making false accusations about Netlify. If you want our help, we’ll help you but it doesn’t help anyone to make false accusations and to blame Netlify for an issue that only you have control over.