A parked domain usually displays a temporary or provider-supplied page at the domain's own address. A redirected domain sends a visitor toward a different web address, or URL. Both can be useful when a domain is registered but not serving a full site, yet they produce different browser experiences and require different settings.

Both arrangements use the Domain Name System (DNS) to help a browser find a service for the original name. The difference is in the Hypertext Transfer Protocol (HTTP) response: a parking service sends page content, while a redirect tells the browser to request another URL. Pointing a DNS record somewhere does not, by itself, issue a redirect.

What a Parking Page Shows

A parking page is placeholder content displayed when a visitor reaches a domain. A registrar or hosting provider may offer a default page for a newly registered name, or the owner may serve a custom holding page. The page might state that a site is coming soon, provide contact information, or show provider content. Its exact appearance depends on the service and the owner's configuration.

Parking can be a deliberate interim choice when the owner has not launched a website. It can also appear because a default nameserver or hosting configuration remains in place. A parking page shows what the current web destination is serving. It does not establish the registrant's identity, the reason for the configuration, or legitimate ownership of the domain.

Some parking products display advertising, but a domain owner should not infer that parking guarantees revenue. The amount and eligibility depend on the provider and traffic, and some parking pages have no advertisements. A parked page also does not guarantee search indexing or any particular search position.

What a Redirect Does

An HTTP redirect begins when a client requests the original URL and receives a redirect response from a web server or a service in front of it. The response includes a redirect status code and usually a Location header with the destination URL. If the browser follows the redirect, it requests that destination and changes the address shown in the address bar.

For a simple example, an owner may redirect old.example to http://new.example/ after a site move. A permanent redirect indicates an enduring move, while a temporary redirect indicates that clients should keep using the original URL for future requests. GET is commonly used to retrieve a page, and redirect codes differ in how they handle requests using other methods. Choose a code according to the actual use case rather than assuming all redirect responses behave identically.

A redirect can cover a whole domain or selected paths. A blanket redirect to one homepage may not preserve links to old articles or product pages. For a migration, plan destination mappings for important URLs and check that the target pages exist. Avoid loops in which two endpoints repeatedly redirect to each other. A destination that later expires or changes ownership also becomes a risk if the original domain keeps sending traffic there.

DNS Pointing Is Not HTTP Redirection

DNS records can point a name to an address or, in certain cases, another DNS name. An A record gives an Internet Protocol version 4 (IPv4) address, and an AAAA record gives a version 6 (IPv6) address. A canonical name (CNAME) record makes one DNS name an alias of another. A browser uses that information to contact an endpoint for the original hostname. These records do not carry a web URL path, an HTTP status code, or a Location header. A CNAME alias is therefore not an HTTP 301 redirect.

If a registrar panel offers a setting called URL forwarding, it usually arranges for a web service to answer requests and issue a redirect. The panel may hide that extra service behind one control. By contrast, editing only an address record may send the original hostname to a server that has no configuration for it. The browser might then display a default page, report a certificate error on a secure connection, or receive another response instead of a redirect.

HTTPS is the encrypted form of HTTP. To redirect an HTTPS URL, the browser normally must establish a secure connection to the original hostname and accept its certificate before reading the HTTP response. DNS alone cannot skip that step. A domain with separate www and bare hostnames may also need both names configured if visitors use both addresses.

Inspect the Original Response

To determine what is happening, inspect both layers. A DNS lookup can show where the original hostname resolves. Open the browser's network view before navigating, then inspect the original page request's status code and response headers. Looking only at the final page can hide a redirect that happened first.

A simplified HTTP/1.1 response excerpt for a temporary redirect might look like this:

HTTP/1.1 302 Found
Location: http://new.example/

The 302 status and Location header show a redirect instruction from the original service. If a holding page is returned directly with a 200 status, the service has delivered content at that URL. Where several requests are chained together, compare each response with the next requested address rather than classifying the domain from one final screenshot.

Choosing a Use Case and Managing Risks

Choose parking when you want the original domain to display a temporary page and no full site is ready. Choose a redirect when visitors should reach another established URL. For an unused domain, you may instead leave web service unconfigured, but consider whether mail, verification records, or other DNS services still rely on the name. Changing nameservers just to alter a web experience can disturb those unrelated records.

Review the provider behind a default parking page, especially before using the domain in public materials. A provider-branded page may confuse visitors who expected your site. If you use a custom holding page, make its purpose and current status clear. If you set a redirect, confirm the destination is under appropriate control and still serves the intended content.

After a change, test the exact HTTP and HTTPS URLs visitors may enter, including www if used. DNS caches and browser redirect caches can make results appear inconsistent for a while. Record which hostname, path, and response you observed rather than relying on a single screenshot. Repeat the check for any important old paths as well as the homepage.