Frequently Asked Questions
Find answers to common questions about aioflare
aioflare is a productivity layer on top of Cloudflare, designed for managing multiple accounts and zones efficiently — especially at scale.
No. aioflare works on top of Cloudflare APIs and focuses on bulk operations, automation, and multi-account workflows — not full feature parity.
All sensitive data is encrypted server-side using strong encryption (AES-256-GCM). Each user has isolated encryption keys, and data is encrypted before being stored.
Encryption is fully handled server-side using secure workers. Users do not need to manage encryption keys manually.
Generic system logs and sharing invite emails are not encrypted. All sensitive operational data is encrypted.
aioflare uses Cloudflare’s official APIs to perform all operations. Every action reflects directly on your Cloudflare account.
No. API rate limits and platform restrictions from Cloudflare still apply.
You can: Add and delete zones (single or bulk) Move zones between accounts (with DNS & redirect rules preserved) Manage DNS records (add, edit, delete, bulk operations) Apply filters (by account, record type, or content)
Yes. aioflare is built for scale, with pagination, filtering, and bulk actions designed to handle hundreds of zones.
Common Cloudflare settings are supported, including: SSL/TLS mode Always Use HTTPS Security level Cache level Browser cache TTL
aioflare supports bulk operations such as: Add zones Delete zones Add/edit/delete DNS records Edit IP addresses Toggle proxy settings Purge cache (multiple modes)
All bulk actions are processed through a queue system. Server-side processing (recommended) Browser-based fallback Results can be reviewed in the queue history after execution.
Yes. Some operations generate detailed results, which are stored securely and can be accessed from the queue history.
aioflare uses a queue processor with: Server-side workers (primary execution) Client-side processing (fallback / secondary) Server-side processing ensures tasks continue even if you close your browser.
Record templates allow you to define reusable DNS configurations with multiple records in one template.
Zone profiles combine: Record templates Target account Collection This allows you to add new zones instantly without manual configuration.
Yes. Templates support placeholders like {{zone}}, which automatically resolve to the actual domain name.
Yes. You can: Use prebuilt redirect templates Create custom templates Apply redirects in bulk
aioflare supports: Purge Everything Purge by URL Purge by Prefix Purge by Tag Purge by Host Bulk purge (Purge Everything) is also available.
Collections help you organize zones into logical groups for easier management and bulk operations.
Yes. aioflare supports collection-based sharing.
The owner generates an invite code The invited user verifies using that code Access is granted based on assigned role
Read DNS Write Admin (zone + user management)
Yes. Every action is recorded in the activity log, including the executor’s identity.
aioflare provides: Requests over time Bandwidth usage Threats blocked Cache hit ratio
Yes, including: Jump between zones without leaving the page Zone notes for internal tracking Quick Google Site verification (via DNS record modal)
Yes. The system is designed for scale with: Queue processing Pagination Bulk operations Server-side execution