Loading profile...
Try Flare53 free for up to 3 months or 100GB total data transfer, whichever comes first.
Usage meter will show real transfer after metering is enabled. No automatic paid charge without choosing a paid plan.
Run a website checkup before setup. After Flare53 is active, compare response time, cache hit signal, and delivery usage.
Run checkupVisitors should use your public website domain through Flare53. Direct access to the origin should be restricted where possible.
Learn the flowStart with the address of your current hosting. Then enter the website address your visitors will use.
Your origin URL is a public address that reaches your website directly at its current hosting.
You can use a hosting-provider address, a server or load-balancer address, or a separate hostname such as origin.example.com that points to the same hosting.
Many website owners do not already have a separate origin address. In that case, ask your hosting provider to create or provide one before you continue.
This is where your website is currently hosted. Flare53 must be able to reach this address before setup can begin.
https://origin.example.com or your hosting provider's public addressEnter the domain that should become faster through Flare53, for example www.example.com.
It must be different from your origin URL. Do not change its DNS yet. Flare53 will tell you when the final DNS change is ready.
This is the website address your visitors type. It stays the same after Flare53 is activated.
www.example.com — do not include https://This is the public address Flare53 uses to reach your current hosting. Use a provider hostname, server address, or a separate hostname such as https://origin.example.com.
This is what visitors type, for example www.example.com. It must be different from the origin URL. Do not change its DNS until Flare53 tells you it is ready.
Flare53 will show CNAME records. Most DNS providers need the short host/name. Use the full host/name only if your provider asks for it.
Do not block the origin before setup is active. After testing, protect the origin using your hosting firewall, server rules, hosting firewall rule, or private S3 origin method.
Update your profile, billing details, and payment status from your profile page.
You can delete your login account only after all websites under this account are deleted. This prevents orphaned Flare53 speed setups and SSL certificates.