Single-site operators
Verify once and create as many warmers as your plan allows.
← Back to features
Feature
Hostname Verification
Warm only domains you prove you own—abuse protection built in.
Cache Rocket requires hostname verification before warming. That protects third-party sites from abuse and ensures your warmers only target infrastructure you control.
Highlights
- DNS TXT or HTTPS file/meta verification
- Required before warmer entry URLs are accepted
- Clear pending vs verified status in account
- Safer multi-tenant and agency workflows
Why verification matters
An unrestricted warmer could be misused against someone else's origin. Ownership checks are a deliberate product safeguard—not optional friction.
Developer-friendly checks
Choose DNS TXT for classic setups, or an HTTPS verification file/meta tag that fits Next.js and other static/app hosts without FTP access.
How it works
- 1
Add a hostname
Enter the domain you want to warm.
- 2
Complete the challenge
Publish the DNS TXT or HTTPS verification token.
- 3
Verify & warm
Mark it verified, then create warmers for that host.
Where it shines
Agencies
Verify each client hostname inside the right workspace.
Platform teams
Keep a clean inventory of approved hosts.
Frequently asked questions
- Can I warm a hostname I have not verified?
- No. Entry URLs must use a verified hostname.
- What if DNS is slow to propagate?
- Wait for propagation, then click Verify again. HTTPS file verification is often faster for app deployments.
Related features
All featuresReady to try this in your account?
Create a free Cache Rocket account, verify a hostname, and turn this capability on for your site or API.