↓Skip to main content

URL Redirect Record

Stands For: URL Redirect Record (also known as Domain Forwarding or Web Forwarding)

Definition: A URL Redirect Record is not a standard type of DNS record defined in IETF standards. Instead, it is a service or feature offered by many domain registrars and DNS providers that allows a user to automatically forward traffic from one domain to a different URL. The underlying mechanism uses standard DNS records to point to a web server that performs an HTTP redirect.

Key Characteristics:

  • How it Works: When you set up a URL redirect, your provider typically creates a standard A record behind the scenes that points your domain to a web server they manage. This server is pre-configured to do only one thing: respond to all incoming requests with an HTTP redirect (e.g., a 301 or 302 status code) that sends the user’s browser to the destination URL you specified.
  • HTTP-Level Redirection: The forwarding happens at the application layer (HTTP), not the DNS layer. This is a key distinction, as it allows for more flexibility than DNS-level redirection (like a CNAME).
  • Types of Redirects Offered:
    • 301 Redirect (Permanent): Tells browsers and search engines that the page has moved permanently. This is the most common type and is best for SEO, as it passes “link equity” to the new URL.
    • 302 Redirect (Temporary): Tells browsers and search engines that the move is temporary. This is used when you plan to move the content back to the original URL.
    • Masked Forwarding (Not Recommended): Uses an HTML frame to display the content of the destination URL while keeping the original domain in the browser’s address bar. This practice is strongly discouraged as it is bad for SEO and can cause usability issues.

Comparison to CNAME/ALIAS:

  • CNAME and ALIAS records redirect a domain name to another domain name at the DNS level. They cannot specify a URL path (like /about-us) or change the protocol (from HTTP to HTTPS).
  • A URL Redirect service forwards a domain name to a full URL, including the protocol and any path, at the HTTP level.

Common Use Cases:

  • Forwarding an old domain to a new one after a rebrand.
  • Redirecting a shorter, more memorable “vanity” domain to a longer URL (like a social media profile or cloud storage link).
  • Ensuring traffic to the root domain (example.com) is redirected to the www subdomain (www.example.com).
  • Automatically redirecting all HTTP traffic to HTTPS.

Usage Note: As of June 2025, URL Redirect services are a convenient feature for simple forwarding needs. For more complex redirection logic or better performance, it is generally recommended to point your domain’s DNS to your own hosting and configure redirects directly on your web server (e.g., via .htaccess, Nginx config, or application code).