Allow Platebreaker Bot on Your Website
Platebreaker indexes recipe metadata (JSON-LD) to help users discover recipes by nutritional content. We never reproduce your full content — users are always directed to your original recipe page. If our bot is being blocked by your firewall, the instructions below will help you allow it through.
Bot Identification
Platebreaker/1.0 (+https://www.platebreaker.com/bot) IP Address 18.223.218.0 Reverse DNS indexer-1.bot.platebreaker.com IP List (JSON)
www.platebreaker.com/indexerips.json
Verification
Web Bot Auth (HTTP Message Signatures)
Firewall Instructions
Select your firewall provider below for step-by-step allowlisting instructions.
Cloudflare
Platebreaker is a Cloudflare Verified Bot. If you use Cloudflare's default Bot Management settings, our requests are automatically allowed — no action is needed.
If you have custom rules blocking aggregators or verified bots, you can add an exception:
Option 1: Verified Bot Exception
Add this expression to your custom rules to allow Platebreaker through:
(cf.bot_management.verified_bot and http.user_agent contains "Platebreaker") → Allow Option 2: IP Access Rule
- Go to Security → WAF → Tools
- Create an IP Access Rule: Allow
18.223.218.0
Option 3: WAF Custom Rule
- Go to Security → WAF → Custom Rules
- Create a rule: Skip all remaining rules when IP equals
18.223.218.0
Wordfence (WordPress)
Wordfence requires IP-based allowlisting (User-Agent allowlisting is not supported for security reasons).
- Go to Wordfence → Firewall → All Firewall Options
- Find "Whitelisted IP addresses that bypass all rules"
- Add on a new line:
18.223.218.0 - Click Save Changes
Platebreaker respects Wordfence rate limits (well under 120 req/min) and will not trigger brute-force protections during normal operation.
Sucuri
Sucuri may automatically recognize Platebreaker via Forward-Confirmed Reverse DNS (FCrDNS). If you are still seeing blocks:
- Go to your Sucuri WAF Dashboard → Access Control
- Under "Whitelist IP Address", add:
18.223.218.0 - Click Save
AWS WAF
AWS WAF supports Web Bot Auth natively. If you have Bot Control enabled, Platebreaker's signed requests are automatically allowed as a verified bot.
If you need to add a manual exception:
- Go to AWS WAF Console → IP Sets
- Create an IP Set containing
18.223.218.0/32 - In your Web ACL, add a rule to Allow traffic matching that IP Set
- Set the rule priority above (lower number than) your Block rules
Fastly
Platebreaker is registered in Fastly's Known Bots list, so no action is needed with default settings.
If you have custom rules that block known bots, you can add a manual exception with a VCL snippet:
if (client.ip == "18.223.218.0") {
set req.http.X-Bot-Verified = "true";
} Or use an IP-based allowlist in your Fastly service configuration.
Other Firewalls
For any firewall or WAF not listed above:
- Add
18.223.218.0to your IP allowlist - Or add a User-Agent exception for
Platebreaker
The full list of our crawler IPs is published at indexerips.json.
Verify a Request is from Platebreaker
You can confirm a request is genuinely from Platebreaker using any of these methods:
- Reverse DNS: Run
host 18.223.218.0— it should resolve toindexer-1.bot.platebreaker.com. Then verify the forward record:host indexer-1.bot.platebreaker.comshould resolve back to the same IP. - IP Range Check: Compare the source IP against our published list at indexerips.json.
- Web Bot Auth: Verify the
SignatureandSignature-Inputheaders against our public key at .well-known/http-message-signatures-directory.
Prefer to Block Indexing?
Platebreaker fully respects robots.txt directives. If you prefer to block our bot from indexing your site, add the following to your robots.txt:
User-agent: Platebreaker
Disallow: / You can also allow indexing of specific paths only:
User-agent: Platebreaker
Disallow: /
Allow: /recipes/ Need Help?
If you are having issues with Platebreaker's bot or need assistance with allowlisting, contact us at creators@platebreaker.com.