Everything here is also shown step by step inside your dashboard, with your own record values filled in. Use this page when you want the whole picture in one place, or to hand the steps to someone who manages your DNS.
Shield guides
Set up Shieldthis page: add a site, prove you own it, route traffic, lock your server
Shield Tunnelyour server has no public address, or your platform blocks a proxy
What Shield does
Blocks AI scrapers
Shield sits in front of your website. Bots that copy your content are stopped, search engines and real visitors pass through untouched.
Nothing to install on your site
You change two DNS records and tell Shield where your site runs. Your code and hosting stay as they are.
You see what it stopped
The Traffic tab shows every visit that was blocked or let through, and why.
Step by step
1
Add your website
In your dashboard choose Add website and type your site's address. Shield reads your DNS, tells you which provider it is on, and shows you the exact records to add.
2
Prove you own the domain
Pick any one of the four proofs below and add it at your DNS provider, or upload the file. Shield checks on its own every minute, or press Check my DNS now. A new registration stays open for 24 hours; if it runs out, choose Add site again for a fresh record.
The four proofs, any one is enough
CNAME record
Type CNAME. Name _alovia-verify. Value the value shown in your dashboard. Works at Cloudflare, Route 53, Namecheap, GoDaddy, Vercel, Netlify and most others.
CNAME without the underscore
Type CNAME. Name alovia-verify. Same value. For the few DNS panels that refuse a name starting with an underscore.
TXT record
Type TXT. Name _alovia-verify. Value alovia-verify= followed by your verification code, exactly as shown.
Upload a file
If you can put a file on your existing site but cannot edit DNS: create a plain text file at the address shown, with the code as its only content.
3
Send your traffic through Shield
Add the routing record your dashboard shows. For a subdomain like www it is a CNAME to shield.aloviaai.net. For a root domain it is an A record at @ pointing at the address shown, and the same on www. Until ownership is proved, your visitors are not affected.
4
Tell Shield where your site runs
This is the last step before your site is live. If your server has a public address, open Point to my server. If it does not, or your platform blocks a proxy in front of it, open Shield Tunnel. Your dashboard picks the right one for where your site is hosted.
After you are live, only Shield should be able to reach your server, or scrapers who find its direct address walk around Shield. Open the Security tab, pick your hosting platform, and paste the snippet. It makes your server accept a verification code that only Shield sends.
If it does not work
Check says the record was not found
Put only _alovia-verify in the Name or Host field. Your provider adds your domain on its own; typing the full name lands the record at the wrong place. New records take a few minutes to show up, check again.
A conflicting record is in the way
Another record already uses that name. Your dashboard names it. Remove or rename it, then check again.
Your provider refuses the underscore
Use the CNAME without the underscore, the TXT record, or the file upload. Any one proof is enough.
The registration expired
Ownership was not proved within 24 hours. Choose Add site again for a fresh record and add that one.
Your domain already points somewhere else
Prove ownership first, then change the routing record. Your visitors keep reaching your site the whole time.
Your server address is your own domain
That points back at Shield in a loop. Enter where your site actually runs: the IP or hostname from your hosting provider.
Moving from another service
From Cloudflare
Shield takes over the job Cloudflare's proxy was doing, so visitors must reach Shield first. Your DNS can stay at Cloudflare: set the record for your domain to DNS only, the grey cloud, and point it at Shield with the record your dashboard shows. Rules you had in Cloudflare are worth writing down first; the Rules tab covers the same ground in plainer terms. Nothing goes offline during the change.
From Vercel, Netlify, Railway, Render, Fly or another host
Your site keeps running where it is. Only the address visitors arrive at changes: point your domain at Shield, and give Shield the address your host gave your app as your server. If your host blocks a proxy in front of it, Railway is the common case, use the Shield Tunnel instead of an address.
From another bot blocker or firewall
Turn it off for this domain once Shield is live, not before, so there is no gap. Two guards in a row make each other's checks fail and turn real visitors away.
What tells you it worked
The dashboard checks your DNS itself and says if the domain still points at the old service, which record to change, and when the certificate is ready. Test my site at the end of setup makes one real visit and reports what it found.
After it is live
Rules
Shield blocks known AI scrapers and lets search engines and real visitors through by default. In the Rules tab you allow or block specific crawlers, and add your own rules by country, network, IP address or browser.
Pause and Panic mode
Pause lets all traffic flow untouched, useful while you debug your own site. Panic mode is the opposite: the strictest checking, for when you are under attack. Both sit in the Danger zone at the bottom of the Settings tab and turn off just as quickly.
Reports
The Traffic tab shows what was blocked and what passed. Export the last 30 days as a CSV file or a PDF report from the same tab.
Your account and data
Exporting your data and deleting your account go through a request today. Email privacy@aloviaai.com and we handle it under the rights in our Privacy Policy.