Cloudflare

Planned

Planned — not available yet. No Cloudflare connector exists today. This page describes the intended design, and details may change before anything ships.

Know how every Cloudflare zone is configured, without opening each one.

The Cloudflare connector is intended to read how each zone is set up: its DNS records, its TLS and certificate settings, and the security features that are on or off. The aim is a single view of configuration that is otherwise spread across many zones and many accounts.

Email us about Cloudflare All planned connectors

Planned capabilities

DNS record inventory per zone
TLS mode, minimum TLS version and certificate metadata
Security setting summary per zone, such as WAF and HTTPS rewrites
Change visibility between two readings of the same zone

How it will work

The planned connection uses a Cloudflare API token that the account owner creates with read-only permissions for the zones they choose. TSmartConnect reads configuration on a schedule and stores it as normalized metadata.

Security and permissions

Only read permissions are intended, scoped to selected zones. Global API keys are not accepted. The token can be revoked in the Cloudflare dashboard at any time, and the connector is not designed to edit DNS or settings.

Use cases

DNS inventory across clients

An agency managing many client zones sees every record in one place before a provider change.

TLS consistency

Zones still allowing an older minimum TLS version are listed together.

Configuration evidence

Zone settings become structured evidence for a separate security assessment.

Questions

Is the Cloudflare connector available today?: No. It is planned, and no Cloudflare account can be connected yet.
Will it change my DNS?: No. The planned connector reads configuration only and asks for read-only token permissions.
Is this a Cloudflare partnership?: No. It is a planned integration built on Cloudflare's public API. There is no partnership with Cloudflare.

Interested in Cloudflare?

Connector order follows what customers actually run. Tell us what you would connect and how many sites, accounts or repositories are involved.

Email us