Cloudflare Zero Trust Connector
Have I Been Squatted creates and maintains its own domain list in your Cloudflare Zero Trust account. Rules with the Block in Cloudflare Zero Trust response add the lookalike domains they flag to that list. Entries do not expire. You reference the list from a Gateway policy, and those domains are blocked on your network.
To see which domains your users resolve and which ones Gateway blocked, connect Cloudflare Gateway Network Intelligence. It uses its own read-only token.
What Have I Been Squatted touches
Section titled “What Have I Been Squatted touches”The connector creates one Gateway list and only ever writes to that list. Its
name is haveibeensquatted- followed by a short identifier for your
organization and -noedit, for example haveibeensquatted-a1b2c3d4-noedit.
Leave the name as it is: if the connector has to reconnect, the name is how it
recognizes its own list, and the identifier keeps it apart from lists other
Have I Been Squatted organizations create in the same Cloudflare account. It does not read, modify, or remove any list you
created, and it does not create or change Gateway policies: you stay in control
of what the list actually does.
Every entry it adds carries a description such as
hibs:1;rule=<rule id>;seen=<time> | IOC blocked by a Have I Been Squatted rule.
The hibs: prefix is how the connector recognizes its own entries, and seen
is when a rule last cited the domain, in Unix seconds. Leave the description in
place. An entry without the prefix is treated as yours and is never removed or
counted, even when it names a domain a rule flags.
Entries added before October 2026 carry exp=<expiry> instead of seen, and a
note that says they block until they expire. They no longer expire. The
connector reads them as cited seven days before their exp, and rewrites the
description the next time a rule cites the domain.
- In Cloudflare, go to Manage Account > API Tokens and create a token with the Zero Trust: Write permission for the account you want to protect.
- Copy your Account ID from the overview page of the Cloudflare dashboard.
- In the app, open Connectors > Cloudflare Zero Trust.
- Paste the Account ID and the token value, then click Connect.
- In Cloudflare, create a Gateway policy that references the new list: see Enforcement below.
Add the response to a rule
Section titled “Add the response to a rule”- Create or edit a rule and open the Response tab.
- Select Add action > Block in Cloudflare Zero Trust.
- Select the Gateway list destination.
- Save the rule.
The response needs at least one domain condition in the rule, because only cited lookalike domain records produce entries; the builder does not save it on a rule with only email or canary conditions.
What is added
Section titled “What is added”For each active rule alert that cites lookalike domain records, Have I Been Squatted adds each distinct cited domain to the list, up to 10 domains per alert.
- Only domains from cited domain (lookalike permutation) records are added.
- The monitored domain and its subdomains are never blocked.
- Alerts that are resolved, ignored, or marked as false positives add nothing.
- Email and canary evidence never produce entries.
Each delivery reads the whole list, makes its changes, and reads the list back to confirm every entry it added or moved. A domain already in the list through an entry you added is left alone.
A queue of the most recently cited domains
Section titled “A queue of the most recently cited domains”Entries never expire, because an expiry can unblock a malicious domain just before it is used again. Instead, the connector’s entries form a queue bounded by the list’s capacity:
- A newly cited domain joins the head of the queue.
- When the queue is full, the entry of Have I Been Squatted’s that a rule cited least recently leaves from the tail, one entry per new domain. Nothing is removed for any other reason.
- A domain cited again moves back to the head, so a lookalike that rules keep citing is not the one removed.
- Entries you added are never removed and do not count toward the queue.
New domains are added before anything is removed, so a delivery that stops
partway has unblocked nothing. Moving an entry to the head removes it and adds
it again with a new seen, because Cloudflare cannot edit an entry in place;
the domain is unlisted for the moment between the two requests. To keep these
moves rare, a cited entry moves only when a rule last cited it more than a day
ago, or when it is among the 100 entries next in line to be removed.
Creating the list does not block anything on its own. A Gateway policy has to reference it:
- In Cloudflare, go to Gateway > Firewall policies and create a DNS policy.
- Set the selector to Host, the operator to in list, and choose the haveibeensquatted-…-noedit list.
- Set the action to Block.
The integration page checks for this and reports one of:
| Status | Meaning |
|---|---|
| OK | An enabled policy blocks traffic matching the list. |
| Not enforcing | No policy references the list, the policy is disabled, or its action is not Block. Entries are stored but nothing is blocked. |
| Permission denied | The token cannot read Gateway policies, so enforcement cannot be confirmed. |
Capacity
Section titled “Capacity”Cloudflare allows 1,000 entries per list on Standard plans and 5,000 on Enterprise. The API does not report which applies to your account, so the connector uses 1,000, which is safe on both.
The queue holds at most the list’s capacity less 10, less any entries you added, and never more than 1,000. The 10 free places let a delivery add its domains (at most 10) before it removes the oldest of its own. When entries you added have filled those places, the oldest entries are removed first instead. If every entry of the queue is cited by the same alert, or the list is full of your own entries, the new domain is not added and the delivery records it as skipped. A list sitting at capacity is expected rather than a fault, and the integration page reports it as At capacity.
Limits
Section titled “Limits”- Cloudflare allows 100 Gateway lists per account. Connecting fails if the account is already at that limit.
- Domain lists do not accept wildcards.
example.comis added as an exact hostname; subdomains are listed individually as they are flagged. - Internationalized domains are converted to their Punycode form before being added, because Cloudflare compares entries in that form.
Health checks
Section titled “Health checks”The integration page shows four checks, refreshed when you connect and whenever you click Test connection. Testing the connection reads the list and changes nothing in it:
- Credential: Cloudflare still accepts the stored token for this account.
- Gateway list: the managed list still exists and is still a domain list.
- Capacity: how much of the list is used.
- Enforcement: whether a Gateway policy references the list.
What is recorded
Section titled “What is recorded”For each alert and response, Have I Been Squatted records the delivery status, the domains it added, moved to the head of the queue, found already blocked, or skipped, the entries it removed to make room, and, when a delivery fails, a short error code. The API token and Cloudflare response bodies are not stored.
If a delivery changed the list and then failed, it is recorded as failed with what it changed, including any entry it removed to move and could not add back. Deliveries are not retried.
Disconnecting
Section titled “Disconnecting”Deactivating the integration stops Have I Been Squatted from adding and removing entries. The Gateway list and everything already in it stay in your Cloudflare account, so anything currently blocked stays blocked until you remove it. Nothing expires on its own. Delete the list in Cloudflare if you want the entries removed.