IP Canonicalization Test

How the Test Works

1. Resolve the IP, your domain is looked up to its A record.
2. Request by IP, our server fetches the site directly by the raw IP.
3. Inspect the response, we check for a redirect to your domain.
4. Report the result, you get a pass or a clear fix recommendation.

Why It Matters

• Dedicated-origin hygiene, a default-host redirect can prevent an origin you control from serving the same public site at a numeric address.
• A narrow duplicate-URL check, a passing result removes one possible alternate homepage address; it does not validate canonical tags or every host and protocol variant.
• Safer interpretation, a failure on shared hosting or a CDN can be normal because the provider routes requests by hostname or TLS SNI.
• A clear next check, use the redirect and canonical tools separately to inspect named URLs, full chains, and page-level canonical signals.

Canonicalization is one of many signals search engines weigh. Our SEO services fix redirects, duplicate URLs, and crawl issues so engines see one clean version of every page.

IP Canonicalization Scenarios Reference

Canonicalization is about making sure each page is reachable at exactly one URL, with every other variant redirecting to it. These are the three scenarios that matter most, what the correct behavior is, and why it helps. The fix in every case is a server-side 301 permanent redirect to the canonical address.

How to set the 301: on Nginx, add a catch-all default server block that issues return 301 https://your-domain.com$request_uri;. On Apache, use a catch-all VirtualHost or a RewriteRule that tests the %{HTTP_HOST} against your canonical domain. On most managed hosts and CDNs, set the canonical domain or a redirect rule in the dashboard. Use 301 (permanent), never 302, so ranking signals consolidate.