The site is back up, although it now seems to contain exclusively "free" recipes (i.e. coming from CC sites and old books).
IMHO there are ways to make recipe-scraping resistant to copyright claims.
1. hide all scraping actions behind a login page; that makes content private, hence uninfringing.
2. every time a user "publishes" or shares content, present only an extract of the recipe, like the ingredients and first few steps; expanding the extract sends you to the original site (ideally to the specific anchor of the procedure).
Private as in a single user getting stuff and saving it in their own account, not resharing anything. That's not infringement, or rss feed aggregators would be infringing too.
IMHO there are ways to make recipe-scraping resistant to copyright claims.
1. hide all scraping actions behind a login page; that makes content private, hence uninfringing.
2. every time a user "publishes" or shares content, present only an extract of the recipe, like the ingredients and first few steps; expanding the extract sends you to the original site (ideally to the specific anchor of the procedure).