CDN Detector: the question this tool answers
CDN Detector answers one focused troubleshooting question: CDN detector. The live result is designed to tell you whether response headers is usable, whether ASN/network agrees with it, and whether DNS aliases exposes a second path that can explain the symptom. A healthy result here is not an all-purpose website score; it only describes the DNS resolution and delegation evidence this tool owns.
- response headers
- ASN/network
- DNS aliases
- edge signatures
- origin visibility confidence
How to read the response headers, ASN/network and DNS aliases evidence
Start with the value that directly controls the failing service, then use the other signals to confirm or challenge that interpretation. A single record or response can look correct while another hostname, IP family, redirect or mail-authentication path still fails. The tool therefore keeps the raw observed value visible and explains how the signals relate.
- Response headers — Record the public status, final URL and relevant response headers. A working DNS answer does not prove that the application is serving a genuine website response.
- ASN/network — Verify ASN/network from the public Internet and compare it with the value the responsible provider says should be live.
- DNS aliases — Verify DNS aliases from the public Internet and compare it with the value the responsible provider says should be live.
- Edge signatures — Verify edge signatures from the public Internet and compare it with the value the responsible provider says should be live.
- Origin visibility confidence — Verify the public endpoint and response before changing DNS. A proxy error can originate from an offline service, blocked proxy ranges, stale origin address or overloaded application.
Common cdn detector failure patterns
The most useful warnings are mismatches rather than isolated missing fields. Response headers can be absent or stale; ASN/network can point somewhere different from the expected provider; and DNS aliases can reveal a second path that behaves differently. If public sources disagree, first decide whether the difference comes from authoritative data, caching, a separate hostname, IPv6, or another protocol layer before editing configuration.
What to change — and what not to change
Change the smallest setting that the evidence proves is wrong. Compare the observed response headers with the current value supplied by the responsible provider, save the existing value, make one correction, and retest. Do not replace nameservers, delete unrelated MX/TXT records, disable TLS controls or remove IPv6 simply because CDN Detector shows a warning in another layer. Broad changes can turn one isolated problem into several independent outages.
How HostWithShery runs CDN Detector
The submitted public input is normalized and validated before any server-side request is made. HostWithShery then obtains response headers and ASN/network using the appropriate public DNS, HTTP, TLS or mail protocol and adds DNS aliases plus edge signatures where it materially changes the interpretation. URL-based checks are restricted to public destinations, and redirect targets are revalidated instead of being trusted automatically.
Example cdn detector interpretation
Example only: suppose response headers returns an expected value, but ASN/network points to an older destination while DNS aliases shows a different result for another hostname or network path. The correct conclusion is not “everything is broken.” It is that one public path still disagrees with the intended DNS resolution and delegation configuration. The live result uses the domain you enter; this example is never presented as evidence about your site.
When a cdn detector result is inconclusive
This is a public-configuration diagnostic. Network filtering, private control-panel settings, split-horizon DNS, provider-internal state and transient routing conditions can limit what can be confirmed from outside the account. Public diagnostics cannot see private control-panel state, unpublished origin addresses, provider account status or split-horizon/internal DNS. If the remote service times out, blocks automated requests or hides a signal, the result stays inconclusive instead of inventing a provider or configuration. That distinction matters when the next step is a potentially disruptive DNS, SSL or mail change.
How to verify the repair
Authoritative DNS should publish the intended record and independent resolvers should converge on that answer as their previous cached TTLs expire. Repeat CDN Detector after the change and compare the same response headers, ASN/network and DNS aliases evidence that exposed the problem. A provider dashboard saying “saved” is not enough when the public Internet still returns the old value.
What to check next if CDN Detector is healthy
If response headers, ASN/network and DNS aliases now agree but the user-facing problem remains, move to the adjacent layer instead of editing the same setting repeatedly. Use the related diagnostics on this page to test the next plausible cause, and keep the previous result as evidence when escalating to a hosting, DNS or email provider.
Technical references
These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.