DNS points to a different host than your build pipeline deploys to

DNS is the system that tells browsers and crawlers which server to fetch your website from when someone types your domain name. This check compares who DNS says is hosting your site against the hosting provider your build and deployment process actually pushes updates to. On this site, those two do not match. Search engines, AI tools, and this audit all see whatever DNS is currently pointing at, not what is sitting in your code repository or the host you think is live. Until the mismatch is corrected, every score and every piece of content being evaluated may be out of date or wrong, regardless of how much work goes into the actual codebase. You or your developer should log into your DNS provider, where your domain's records are managed, and correct the records so they point at the same host your build pipeline deploys to. This is usually a same-day fix once the correct target host is confirmed, though DNS changes can take up to 24-48 hours to fully propagate worldwide.