Connect QuQi Edge

What QuQi Edge does to your site today, the two things it needs from you, the records to add at your DNS provider in the order that keeps the site up, and how to tell it worked.

6 min de lectura Paid plans

QuQi Edge puts QuQi in front of your website. Visitors reach your site through QuQi’s edge, and your server stays exactly where it is and exactly as it is. Today everything passes through untouched — the card calls this proxy only. Serving the pages you optimized from the edge comes in a later release, and nothing you set up now needs redoing for it.

EMPIECE AQUÍ You connect nothing of yours. There is no password, no token and no account to link: you add a few records at your DNS provider, and that is the whole connection. QuQi Edge is on Growth, Scale and Authority, and not during a trial.

The two things it needs

FIELDWHAT TO ENTERWORTH KNOWING

Hostname The name your site is known by — www.example.com or example.com, exactly as visitors and Google know it. QuQi fills it in from your audit. It never changes. QuQi will not ask a site known as example.com to become www.example.com, or the other way round.

Origin address Where your server answers directly: a DNS-only record such as origin.example.com, or the server’s IP address. Never the hostname itself — once that points at QuQi it would point straight back — and never a name that goes through Cloudflare’s proxy.

A site hosted on Cloudflare Pages or Workers has no direct address to give, so it cannot connect for now.

Set it up

Open Integrations

Make sure you are on the right website, then find QuQi Edge under Delivery and press Set up.

Check the hostname, enter the origin address

The hostname is already filled in. Give the address your server answers on directly.

Press Test

QuQi fetches the front page from your server at that address, as if it were a visitor to the hostname, and tells you what it answered. A server that answers for a different name, or not at all, shows here before anything is saved.

Save

QuQi checks the origin address is a public one and not a loop, then prepares the hostname on the edge. The drawer stays open on the records to add.

The records, in this order

The drawer lists them with a copy button on every name and value, and a button that opens your DNS provider’s own page for the domain where QuQi recognises the provider. The order matters: the switch comes last, and only when the certificate is ready.

Add the TXT records

One lets Cloudflare issue the certificate your site will be served with; where a second one is listed, it proves the hostname is yours so it is active before anything moves. Nothing changes for visitors when you add them.

Press Check again until the certificate reads active

It usually takes a few minutes after the TXT record is in place. The drawer’s status line says what to do next at every stage.

Lower the record’s TTL to 300

At your DNS provider, on the record you are about to change. This is what makes the switch quick to undo if you ever need to.

Add the switch record

For www.example.com, a CNAME named www pointing at edge.quqi.io. For a root domain, the record your provider uses to point a root at another name — the drawer names it in your provider’s words. From that moment visitors reach your site through QuQi.

OJO Do not add the switch record before the certificate reads active. A site switched over without its certificate shows visitors a security warning until the certificate lands.

Root domains

A plain CNAME cannot sit at the root of a domain, so example.com can point at QuQi only where your DNS provider can flatten that for you. Cloudflare DNS does so on every plan, and Namecheap, DNSimple, DNS Made Easy, Hostinger, Porkbun, Gandi, Name.com, Google Cloud DNS and Squarespace each have an ALIAS or ANAME record for it. GoDaddy, Amazon Route 53 and Hetzner cannot: for a root-domain site on one of those, the path is moving the domain’s DNS to Cloudflare’s free plan, which changes nothing else about the site. QuQi tells you this when you connect, and it never proposes a redirect to www instead.

After the switch

The card reads proxy only: every request passes through to your server untouched.
Every 15 minutes QuQi fetches a few pages both ways — through the edge and from your server — and compares them. The drawer’s Health line says when it last checked and what it found.
Dry run does the same check for the front page on demand, and says in one sentence whether the edge answers the same as your server.
Details on the card reopens the drawer at any time.
Edge traffic is not metered. Nothing about it counts against your plan.

Undoing it

Point the switch record back at your server first, wait out its TTL, and only then press Disconnect. Disconnecting removes the hostname and its certificate from the edge, so a record still pointing at QuQi at that moment would show visitors an error page. The card says this again before it lets you disconnect.

CONVIENE SABER If your DNS provider later points the origin address somewhere it should not — a private address, or back at QuQi — the health check records it on the card and stops checking that side. Nothing is switched off on its own; the warning is yours to act on.

¿Esta página ha respondido a su pregunta? Sí No del todo

Google Search Console

Plans