My website calls an API address that no longer exists
Updated 2026-10-16
Short answer: if your site's code calls an address (for an API, a form handler, a chat widget) whose domain no longer resolves, that call fails for every single visitor. The page still loads, so nobody notices until a feature quietly stops working.
How to check it yourself
- Open your site with your browser's developer tools on the Network tab.
- Reload and look for failed requests, especially ones marked as a DNS or name-resolution error.
- For each failing address, look it up with
digornslookup. No address means the service or domain is gone. - Point the code at the service's current address, or remove the feature.
What Preventionlabs shows
Every report reads your homepage's code for addresses it calls (fetch, axios, WebSocket) and checks whether each host has an address in DNS. Hosts with none are reported as calls that fail for every visitor. It also lists every outside service your homepage loads files from, and whether those files actually load.
It reads the homepage's code. Addresses built at runtime, or used only on other pages, need the manual steps above.
Price
First report free, no card needed. Then A$50 a month, up to 10 domains.