At its homepage, resy.com is protected by Imperva (Incapsula), Google reCAPTCHA. Typical approach to reach it reliably: Browser automation + proxy rotation. Difficulty is per-URL, so deep pages — profiles, listings, search — are usually harder.
IP-reputation and JS-challenge weighted (reese84); behavioral weight is lower.
Typical access
Headless browser that runs JavaScript
Detected vendors
CAPTCHA detected
Evidence
Detection confidence: high · vendor present but served clean (passive edge, not an active challenge)
Homepage-level, datacenter-IP snapshot, June 12, 2026.
This is a passive, homepage-level snapshot and can be inaccurate or out of date — anti-bot vendors update their models continuously, deep pages are usually more protected than the homepage, and a datacenter IP sees more challenges than a residential one. Treat it as a directional signal, not a guarantee.
The homepage is the open front door. On a food & delivery site the valuable pages behave differently — here's the plan to characterise resy.com before you build.
Product detail
JS renderUsually open or JS-rendered, but readily CAPTCHA-gated on rapid or referer-less hits.
Search / category listing
CAPTCHA-proneThe most-scraped surface — the first to throw a CAPTCHA or rate-limit.
Cart / checkout
login wallHighest friction: usually login + WAF; not a public surface.
Find a real deep URL cheaply from the site’s robots.txt and sitemap.xml, then run each through the anti-bot checker. This is an advisory based on the category and resy.com’s homepage result — detect the wall, never try to pass a login.