Guides13 min read

Domain redirect: point a .si (or any second domain) at your site

How to redirect a second domain, such as a .si twin of your .ai, with a clean 301 that keeps the path and works on HTTPS. Includes copy-paste nginx, Apache and Cloudflare config, an email lockdown and a curl test, plus what we found testing real .si redirects on October 17, 2026.

Orbit graphic with 301 at the center and apex, www and HTTPS around it, the three things every domain redirect must cover

A domain redirect is an HTTP response, usually a 301 or 308, that sends every request for one domain to another. DNS alone can’t do it: a DNS record only points a name at a server, and something on that server has to answer with the redirect. Done right, it keeps the visitor’s path and works over HTTPS.

In October 2026, AI companies paid aftermarket prices for .si names they only use as redirects. According to Domain Name Wire on October 15, 2026, plasma.si sold for $20,000 and gab.si for $3,988. We tested those redirects and a few big-brand ones on October 17, 2026. Most dropped the visitor’s path, one relied on a temporary 302, and two served the wrong HTTPS certificate.

.si is Slovenia’s country-code domain. For AI companies it reads as SuperIntelligence. That is why some teams on .ai now hold the matching .si and point it at the main site. In our check of 50 AI companies whose main site runs on .ai, only 2 had a .si twin that pointed to their own site: plasma.si and gab.si.

The guide covers status codes, real failures, copy-paste config for nginx, Apache and Cloudflare, an email lockdown and a curl test. If you are still choosing the main domain itself, start with our guide to the best domain for an AI startup.

What a domain redirect is (and why DNS alone can’t do it)

A domain redirect happens at the HTTP layer, not in DNS. DNS tells the browser which server to contact, and that server has to reply with a 3xx status code and a Location header that names the new address.

Here is the sequence. A browser looks up example.si, gets an IP address, connects and asks for a path such as /pricing. A redirect server answers with 301 Moved Permanently and Location: https://example.com/pricing. The browser then repeats the request at the new address.

A CNAME record can’t do this job. It only makes one hostname an alias of another during the DNS lookup. The browser still asks for example.si, so the target server must accept that name and hold a certificate for it. If it doesn’t, the visitor sees an error or the wrong site.

Registrar “URL forwarding” looks like a DNS setting, but it works because the registrar runs a small web server that answers on your behalf. Google’s guide to redirects and Google Search says: “we recommend that you use a permanent server-side redirect whenever possible.” Server-side redirects also run first. MDN notes that HTTP redirects execute before JavaScript redirects and meta refresh tags, and those two need a hosted page anyway.

301, 302, 307 or 308: which redirect code to use

Use 301 for a second domain that should always point to your main site, or 308 if the domain also receives form posts or API calls. Keep 302 and 307 for genuinely temporary moves and for testing.

RFC 9110, the HTTP standard, says a 301 points to “a new permanent URI,” while a 302 means the resource “resides temporarily under a different URI” for now. Both carry a historical quirk: a browser may turn a POST request into a GET. The 307 and 308 codes exist so the method and body stay unchanged.

CodePermanent?Method kept?Google treats it asUse when
301 Moved PermanentlyYesNot guaranteed (POST may become GET)Permanent: signal that the target is canonicalDefault for a second domain
302 FoundNoNot guaranteed (POST may become GET)Temporary: no canonical signalTesting, short campaigns
307 Temporary RedirectNoYesTemporary: no canonical signalTemporary moves of forms or APIs
308 Permanent RedirectYesYesPermanent: same effect as 301Permanent moves that must keep POST requests

Google Search groups redirect codes by permanence, not by number. “All permanent redirection methods have the same effect on Google Search,” according to Google’s guide to consolidating duplicate URLs. A 301 or 308 tells Google the target should be canonical, and a 302 or 307 does not. RFC 9110 adds one caveat: 308 dates from June 2014 and “might not be recognized everywhere,” so 301 stays the safe default for ordinary web traffic.

Watch the defaults. Some registrar forwarders create a temporary redirect unless you open an advanced setting and choose 301. Our test below found temporary codes on live .si domains.

What we found testing real .si redirects

Of the six redirects we tested on October 17, 2026 (plasma.si, gab.si, salesforce.si, recursive.si, microsoft.si and ai.gov), only plasma.si and microsoft.si kept the visitor’s path. Both salesforce.si and recursive.si had a broken HTTPS setup on the .si name. Only microsoft.si got the apex right in a single hop, and even its www variant failed our four-variant check.

Method: buysidomains.si requested /test-path?q=1 on the http and https versions of each domain with curl -I and curl -IL at about 16:30 UTC. We also looked up registration data in Register.si RDAP. Observed October 17, 2026; setups change.

DomainFirst responseHopsPath kept?HTTPS on the .siNote
plasma.si302 on http, then 3012YesWorksEnds at www.plasma.ai with path and query
gab.si3011NoWorks, HSTS 30 daysSame 301 on http, https and www
salesforce.si301 on http1NoPort 443 timed out twiceEnds at www.salesforce.com homepage
recursive.si3022NoA certificate issued for the registrar’s own domain302 to recursive.com, then a 301 to www.recursive.com; browsers show a certificate error on https
microsoft.si3011YesWorks, HSTS 1 yearApex lands on microsoft.com/slovenija/ with path and query; https://www.microsoft.si shows a certificate for another hostname
ai.gov → si.gov3013 from httpNoWorks, HSTS 1 yearhttp to https, then www.ai.gov, then www.si.gov

The same faults showed up on big and small brands.

  • Path loss is the most common fault. gab.si, salesforce.si, recursive.si and the ai.gov chain sent our test path to a homepage. A link to a pricing page on the alias lands on the front page instead.
  • HTTPS fails quietly. Over plain http, salesforce.si and recursive.si looked fine. Over https, one timed out and the other presented a certificate for a different domain, which browsers reject.
  • Temporary codes slip in. recursive.si answered with a 302, never a 301. plasma.si started with a 302 on http before its 301, though it still reached the right page.
  • Chains add up. ai.gov needs three redirects from http to reach www.si.gov. Google’s site move guide says to redirect “to the final destination directly.”
  • Clean is possible, on the apex. microsoft.si sends one 301 straight to microsoft.com/slovenija/ with the path and query intact, and sets HSTS for a year. Its www variant shows why you test all four: http://www.microsoft.si redirects to an http address, and https://www.microsoft.si presents a certificate for a different hostname.

Two more big-brand names showed the same habits. amazon.si answered an https request with a 302 to the amazon.de homepage, and nvidia.si took three hops to reach nvidia.com/en-eu/. None of this breaks a brand, but every dropped path sends someone from an old link or a typed URL to the wrong page.

How to redirect a domain: four methods compared

There are four proper ways to redirect a domain: registrar URL forwarding, Cloudflare Redirect Rules, your own web server, or an S3 bucket behind CloudFront. Masked forwarding and DNS-only setups look similar but aren’t real redirects.

Method301/308HTTPS on sourcePath keptCostBest for
Registrar domain forwarding (URL forwarding)Varies; some default to temporaryVaries by registrarVaries; often an optionOften included with the domainQuick setup if 301, path and HTTPS are all supported
Cloudflare Redirect RulesYes (301, 302, 307, 308)Yes, on proxied recordsYes, with a dynamic targetFree plan: 10 Single Redirect rules per zone; Bulk Redirects up to 10,000 URLsMost second domains, especially with no hosting
Web server (nginx, Apache)YesYes, with your own certificateYesA server you already runTeams that run their own servers
S3 website endpointYesNo; needs CloudFront or Amplify in frontDepends on setupAWS usage pricingTeams already on AWS
Masked or frame forwardingNoVariesAddress bar shows the alias onlyOften includedNot recommended
DNS only (A or CNAME)No: not a redirectOnly if the target serves a certificate for the aliasNot applicableFreeNot a redirect

Cloudflare fits a domain with no hosting at all. Its guide to redirecting one domain to another says to add an A record pointing to 192.0.2.1 (or an AAAA record to 100::), proxied. That address “does not route traffic to an origin server,” so the redirect rule answers every request. Redirect Rules only work on proxied records.

AWS states that “Amazon S3 website endpoints do not support HTTPS,” so an S3 redirect needs CloudFront or Amplify in front. Masked forwarding loads your main site inside a frame on the alias. IONOS’s own help pages recommend an HTTP redirect instead when search matters.

nginx

Give the alias its own server block. The $request_uri variable carries the path and query string, so nothing gets lost.

server {
    listen 80;
    listen 443 ssl;
    server_name example.si www.example.si;

    ssl_certificate     /etc/letsencrypt/live/example.si/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/example.si/privkey.pem;

    return 301 https://example.com$request_uri;
}

The nginx docs describe the older if-based pattern as “a wrong, cumbersome, and ineffective way” to do this. The return line also accepts 302, 307 and 308.

Apache

Apache’s Redirect directive appends any extra path to the target, so /pricing goes to https://example.com/pricing. The block below handles http. For https, add a matching <VirtualHost *:443> with the same ServerName, ServerAlias and Redirect lines, plus the SSL certificate directives for example.si.

<VirtualHost *:80>
    ServerName example.si
    ServerAlias www.example.si
    Redirect permanent "/" "https://example.com/"
</VirtualHost>

Without the word permanent, Apache sends a 302, because temporary is the default.

Cloudflare Redirect Rules

Add both DNS records as proxied, then create one rule with a dynamic target that rebuilds the URL from the request path.

DNS (proxied)
A     example.si       192.0.2.1
A     www.example.si   192.0.2.1

Redirect rule
If (custom filter expression):
  (http.host eq "example.si") or (http.host eq "www.example.si")
Then: Dynamic redirect
  Expression: concat("https://example.com", http.request.uri.path)
  Status code: 301
  Preserve query string: on

On the Free plan, this rule uses 1 of the 10 Single Redirect rules per zone.

Registrar domain forwarding (URL forwarding)

If you stay with registrar domain forwarding, check three settings: the redirect type is 301, the “include path” option is on, and HTTPS works on the alias. One registrar’s documentation notes that an https to https redirect requires both domains to have SSL certificates. Remove any old A, CNAME or ALIAS records that conflict with the forwarder.

Redirect a domain to another domain in six steps

Pick where the redirect will run, point both the apex and www at it, get a certificate, add one 301 rule, lock down email and test with curl. The order matters, because HTTPS must exist before the rule can serve https requests.

Six-step diagram for a domain redirect: pick a service, point apex and www, get HTTPS, add a 301 rule, lock down email, test with curl
A clean domain redirect needs HTTPS on the alias and one 301 hop that keeps the path. Source: buysidomains.si, based on Google, Cloudflare and GOV.UK documentation, October 2026.
  1. Pick a service. Use Cloudflare if your DNS can move there, your web server if you already run one, and registrar forwarding only if it supports 301, path and HTTPS.
  2. Point apex and www. Create records for both example.si and www.example.si. For a .si, nameserver changes go only through your registrar: Register.si’s General Terms (Art. 3.5) say holder requests can be made “solely via a Registrar.” A .si delegation needs at least two NS records, and those servers must answer on port 53 over UDP and TCP.
  3. Get HTTPS. Issue a certificate that covers both names. Let’s Encrypt doesn’t charge for certificates, and it announced on October 7, 2026 that default lifetimes drop from 90 to 64 days on February 10, 2027. Automate the renewal.
  4. Add a 301 rule. Send every variant to the final HTTPS URL in one hop, with path and query kept. Set it up as a 302 first, because browsers cache a 301 and a mistake can stick. You switch it to 301 in step 6.
  5. Lock down email. Publish records that say the alias sends and receives no mail (next section).
  6. Test with curl. Check http and https on apex and www. When every variant lands on the right URL, change the code to 301 and run the same checks again.

This is not a site move. Moving an existing site with rankings to a new domain is a bigger job. It includes page-by-page mapping and Search Console’s Change of Address tool, whose actions continue for 180 days. Our domain migration SEO guide covers that case. A fresh alias with no history only needs the redirect.

Don’t forget email and HSTS on a redirect-only domain

A redirect-only domain should publish DNS records stating that it sends and receives no email. GOV.UK guidance recommends a null MX record (RFC 7505), SPF “v=spf1 -all” and a DMARC reject policy. A redirect-only domain should send an HSTS header only if certificate renewal is automated, because under RFC 6797 a bad or expired certificate leaves users no way to click through.

Without these records, nothing tells receiving mail servers that mail from the alias is fake. The UK government’s guidance, Protect domains that don’t send email, recommends four records. The DMARC line below is the minimal form; GOV.UK’s version adds strict alignment and a reporting address (rua=mailto:…) if you want reports.

example.si.                 MX   0 .
example.si.                 TXT  "v=spf1 -all"
_dmarc.example.si.          TXT  "v=DMARC1;p=reject;sp=reject"
*._domainkey.example.si.    TXT  "v=DKIM1; p="

The null MX record comes from RFC 7505: “MX 0 .” means the domain has no mail exchanger, and it must not publish any other MX record. GOV.UK notes that some DNS providers don’t support null MX. Check first that the domain truly sends no mail. For example, plasma.si publishes MX records at its registrar’s mail servers, and a null MX would break any mail it receives there.

HSTS tells browsers to use only HTTPS for a domain. MDN notes that browsers ignore the header when it arrives over plain HTTP, so it only counts on the HTTPS response. RFC 6797 explains the risk: once a browser holds the policy, a bad or expired certificate leaves the user no way to click through, and the alias becomes unreachable.

Send HSTS on the alias only when renewal is automated, and skip the preload list unless you are certain. The hstspreload.org site warns that inclusion “cannot easily be undone,” and removal takes months.

Test your domain redirect with curl

Run curl against all four variants of the alias, http and https on both apex and www, with a test path. Each should return one 301 or 308 whose Location header is the final HTTPS URL with the same path and query.

curl -I "http://example.si/test-path?q=1"
curl -I "https://example.si/test-path?q=1"
curl -I "http://www.example.si/test-path?q=1"
curl -I "https://www.example.si/test-path?q=1"

A good response looks like this.

HTTP/1.1 301 Moved Permanently
Location: https://example.com/test-path?q=1

Then follow the chain with curl -IL. You want exactly two status lines: the 301 from the alias and the destination’s own response. A 404 is normal for a made-up test path; repeat with a real page such as /pricing to see a 200.

curl -IL "http://www.example.si/test-path?q=1"
  • Every variant returns 301 or 308, not 302 or 307.
  • The Location header is the final https URL, not an http address or an extra www hop.
  • The path and query string arrive intact.
  • The https variants complete without the -k flag. If curl reports a certificate error, browsers will too.

Registrar forwarders usually start working within 10–30 minutes, according to their own documentation. DNS changes can take longer while old records expire from caches, so retest before you conclude a setup is broken.

Which domain redirect setup to choose

For most second domains, a Cloudflare Redirect Rule or a 301 on your own web server is the right choice. Use registrar forwarding only when it offers 301, path forwarding and a valid certificate on the alias.

  • No hosting, DNS can move: use a Cloudflare Redirect Rule on proxied records.
  • You already run nginx or Apache: add a server block or virtual host with a single 301.
  • You hold several aliases: track renewals for both the domains and the certificates, as covered in our domain portfolio management guide.
  • You are moving a whole site: follow a full migration plan, not just a redirect.

Keep the redirect running. Google’s site move guidance says to keep redirects “generally at least 1 year,” and for a brand alias that usually means for as long as you hold the domain. A lapsed domain or an expired certificate breaks the redirect overnight.

Disclosure: buysidomains.si sells .si domain names, including nvq.si. For background on registering and using .si names, see our .si domains guide.

Frequently asked questions

What is a 301 or 302 redirect?

A 301 redirect is an HTTP response that says a URL has moved permanently, and a 302 redirect says the move is temporary. RFC 9110 defines both codes. Google treats a 301 as a signal that the target should be canonical; a 302 sends no such signal. For a second domain that should always point to your main site, a 301 redirect is the right choice.

What does a 307 or 308 redirect mean?

A 307 redirect is temporary and a 308 redirect is permanent, and both keep the original request method and body, so a POST stays a POST. The 307 and 308 codes were introduced because browsers may change POST to GET after a 301 or 302, and RFC 9110 now defines all four. Google treats a 308 redirect like a 301. Use 308 when a redirected domain also receives form posts or API calls.

Is there a free domain redirect service?

Yes, a free domain redirect is possible in several ways. Many registrars include URL forwarding with the domain, Cloudflare's Free plan includes 10 Single Redirect rules per zone, and Let's Encrypt issues certificates without a fee. Before relying on any free domain redirect, check that it sends a 301, keeps the path and query, and serves a valid HTTPS certificate on the redirecting domain.

How long does it take for a domain redirect to work?

A domain redirect set up through registrar forwarding usually starts working within 10–30 minutes, according to registrar documentation. DNS changes can take longer while old records expire from resolver caches, depending on their TTL. Test the domain redirect with a temporary 302 first, because browsers cache a 301, and switch to 301 once curl shows the right Location header on every variant.

Can I redirect a domain without changing the URL?

You can keep the alias in the address bar with masked or frame forwarding, which loads your main site inside a frame on the second domain. We don't recommend it: the address bar never shows the real site, and IONOS's own documentation advises an HTTP redirect when search matters. A standard 301 domain redirect changes the URL in the address bar.

Does redirecting a .si to a .ai help SEO?

Redirecting a .si to a .ai does not add rankings by itself. A permanent 301 tells Google the .ai target should be canonical, so signals from links that point at the .si are consolidated on the main site. The practical value of a .si redirect is catching typed visits, protecting the brand and keeping old links working, provided the redirect keeps the path and works over HTTPS.

Sources

  1. Redirects and Google Search — Google Search Central
  2. RFC 9110: HTTP Semantics, Redirection 3xx — IETF / RFC Editor
  3. End-user sales: here comes .si — Domain Name Wire
  4. Redirect one domain to another — Cloudflare
  5. Redirections in HTTP — MDN Web Docs
  6. Site moves with URL changes — Google Search Central
  7. Protect domains that don't send email — GOV.UK
  8. DNS check — Register.si
  9. URL forwarding (Redirect Rules and quotas) — Cloudflare
  10. RFC 7505: A "Null MX" No Service Resource Record — IETF / RFC Editor
  11. RFC 6797: HTTP Strict Transport Security — IETF / RFC Editor
  12. Announcement: 64-day certificate lifetimes (October 7, 2026) — Let's Encrypt