Is yummly.com down or not working?

What happened to yummly.com, why did the website go down and not work? Here you can see who else is having the same problem with yummly.com, as well as possible solutions. According to our statistics, the following most often do not work: Website, Login, Account, Mobile App.

Current status: No failures

At the moment, according to our data, yummly.com is working fine, but single failures are possible. If yummly.com does not work for you, then report your problem and write a comment.

Add comment

What to do if the site yummly.com is not available? Try our guide.

yummly.com outage reports in the last 24 hours

yummly.com - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.

No registration required.
Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
Active links in the text of the message are not published, but displayed in plain text.
It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.

Your name:

Message:

Technical information

Main page title:

Attention Required! | Cloudflare

Protocol:

https

Status code:

403

Page size:

5.7 KB

Response time:

0.163sec.

IP:

18.239.69.8

Response headers:

date:	Mon, 30 Sep 2024 21:55:44 GMT
content-type:	text/html; charset=UTF-8
transfer-encoding:	chunked
connection:	close
x-frame-options:	SAMEORIGIN
referrer-policy:	same-origin
cache-control:	max-age=15
expires:	Mon, 30 Sep 2024 21:55:59 GMT
set-cookie:	__cf_bm=Bc3Mn8cCVQ36IZvMznTeFweYwAm9txuR7gt5XpwOh4A-1727733344-1.0.1.1-QhMeeUGpizuhli4H3cI6OoqPfOmtHsuP_lsE1ah688.Sy5azFtc_sHo5azyTeyQ6fSWMT7rKcuFSHRvfpmYE0Q; path=/; expires=Mon, 30-Sep-24 22:25:44 GMT; domain=.yummly.com; HttpOnly; Secure; SameSite=None
server:	cloudflare
cf-ray:	8cb775782f3a1cb0-AMS

DNS records:

A	address	18.239.69.7
A	ttl	60
A	address	18.239.69.18
A	ttl	60
A	address	18.239.69.26
A	ttl	60
A	address	18.239.69.8
A	ttl	60
MX	exchange	aspmx4.googlemail.com
MX	priority	50
MX	exchange	aspmx5.googlemail.com
MX	priority	60
MX	exchange	alt1.aspmx.l.google.com
MX	priority	30
MX	exchange	aspmx2.googlemail.com
MX	priority	70
MX	exchange	alt2.aspmx.l.google.com
MX	priority	20
MX	exchange	aspmx3.googlemail.com
MX	priority	40
MX	exchange	aspmx.l.google.com
MX	priority	10
NS	value	ns-1730.awsdns-24.co.uk
NS	value	ns-1009.awsdns-62.net
NS	value	ns-1040.awsdns-02.org
NS	value	ns-362.awsdns-45.com
TXT	entries	v=spf1 a mx include:_spf.google.com include:spf.dynect.net include:mail.zendesk.com include:shops.shopify.com include:mg-spf.greenhouse.io ~all
TXT	entries	google-site-verification=SgvweroOJ9tTyNDrNz_9fLZXemZk2Jv5XSKJTq2MFAQ
TXT	entries	apple-domain-verification=NHu7FKapznpJhpg8
TXT	entries	google-site-verification=46kHrfLlF3JbIg0B5caIXQh1NIGKEdxoovlNsDUUFjo
SOA	nsname	ns-1009.awsdns-62.net
	hostmaster	awsdns-hostmaster.amazon.com
	serial	1
	refresh	7200
	retry	900
	expire	1209600
	minttl	86400
CAA	critical	0
CAA	issuewild	awstrust.com
CAA	critical	0
CAA	issuewild	digicert.com
CAA	critical	0
CAA	issuewild	pki.goog
CAA	critical	0
CAA	issue	pki.goog
CAA	critical	0
CAA	issuewild	comodoca.com
CAA	critical	0
CAA	issuewild	letsencrypt.org
CAA	critical	0
CAA	issue	comodoca.com
CAA	critical	0
CAA	issue	awstrust.com
CAA	critical	0
CAA	issue	digicert.com
CAA	critical	0
CAA	issue	letsencrypt.org

SEO headers

h1 Sorry, you have been blocked

h2 You are unable to access yummly.com

h2 Why have I been blocked?

h2 What can I do to resolve this?

How to solve problems with yummly.com

Errors on the yummly.com website can be either on the server side or on your side (client side). If there is practically nothing to be done about errors on the server side (it remains only to wait for the site to work again), then with errors on the client side it is possible to solve the problem with the availability of yummly.com on your own.