Re: Why are Cloudflare checking my browser?

Ben Ramsey <ben@benramsey.com> Thu, 27 February 2020 14:03 UTC

Return-Path: <ben@benramsey.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFD673A0946 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2020 06:03:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=benramsey.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GiKuhZe6r_Pl for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2020 06:03:42 -0800 (PST)
Received: from mail-yw1-xc30.google.com (mail-yw1-xc30.google.com [IPv6:2607:f8b0:4864:20::c30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B23633A0945 for <ietf@ietf.org>; Thu, 27 Feb 2020 06:03:41 -0800 (PST)
Received: by mail-yw1-xc30.google.com with SMTP id n127so3060895ywd.9 for <ietf@ietf.org>; Thu, 27 Feb 2020 06:03:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=benramsey.com; s=google; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=yI/mvWoZrm4EUVfDwsgaNO4cXJK+Umjq5dG/9ARD8NI=; b=NkapjSvAIEZlHZxPdQ3cqK3K9mN63br5MiDbWMH2uB0o0P7IqkxvOSw9tHchu6JP0q gWG6v3jAQMdp/ALHNrkHNR2ANxYXWnY2Mv0QCeD7F4HVyZcuUGd+t9thO00qeSW4ECx6 +wr/P13A7ENoYwYtrN8/Ccmi6zMN335r4+NiG9G+B88VbCUk3Lt4hU+R+8Dg6E9Gv7qG 8+JZiTYAAQyGrbUxCpugmVWy8c2SoTI4GS1t14HcUqCARPqPOdnH5T0TEbSDVcbJNhtm db5kdG4Fu6FmU+p2WG38tEevzCVPZbXIK/JElgPRZYJtNqEFu2Kw8EMMwPsQqATPVviQ I4Gw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=yI/mvWoZrm4EUVfDwsgaNO4cXJK+Umjq5dG/9ARD8NI=; b=X5bES5wzCjBc5jSxRqe6fcBkcOuK7rG62aaSXHR68Fk8eOpWCzLY8l6JlZFu1V1ip0 VDTp/06Ds8Uc48UzWmpuSDrRtfE2mL7WutNHFvQEe8S2e2jW5nlwl2q5AnsA1G0MWXRF Mc5RBjsH2qRZnu7qZBhcnT4gHZb/UD7utWl+lmvfZdDDAh48y8IGSkfjsYT1XQYAC9vz ANs6863ZR8slsv0ZTilPTd9SLgA/sIDzd9zyHrQjuWsGLLpQ7oDZJB4c1SOv7x9UZvQB 4ixkVa6AcfbMSo99V9DJtS7JoJnfBudkzrPwI+ajC8Uz84yHn3ErOxliXVS7T23+6g5L XtbA==
X-Gm-Message-State: APjAAAWPWTBp3tTqDmZfcyB3ml8CkzXWiASDRPjIAdTt9/g9GGjGYqcn G2J6VuYeo5SEKVwb6JEZrs4vXIpUEeMQ7Q==
X-Google-Smtp-Source: APXvYqz2gsbhVs3168qT/DJA3KlYSIZ5aho2tSvJ5zPScDhbPhYUu8eD02jVXSr42QgQwwmny+QuxQ==
X-Received: by 2002:a05:6902:4e4:: with SMTP id w4mr3916140ybs.239.1582812220425; Thu, 27 Feb 2020 06:03:40 -0800 (PST)
Received: from [10.10.42.46] (h96-61-170-50.lvrgtn.dsl.dynamic.tds.net. [96.61.170.50]) by smtp.gmail.com with ESMTPSA id e131sm2448731ywb.81.2020.02.27.06.03.39 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 27 Feb 2020 06:03:39 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Ben Ramsey <ben@benramsey.com>
Mime-Version: 1.0 (1.0)
Subject: Re: Why are Cloudflare checking my browser?
Date: Thu, 27 Feb 2020 08:03:39 -0600
Message-Id: <EE05B8C5-10F6-4E71-A886-61F3D490F27E@benramsey.com>
References: <BC83D18D-7DEF-4769-A788-82D0AC8C888A@sinodun.com>
Cc: IETF Discussion <ietf@ietf.org>
In-Reply-To: <BC83D18D-7DEF-4769-A788-82D0AC8C888A@sinodun.com>
To: John Dickinson <jad@sinodun.com>
X-Mailer: iPhone Mail (17D50)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7S5l5GZNXOmlxI8eCabWavbFS6A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2020 14:03:44 -0000

> On Feb 27, 2020, at 04:27, John Dickinson <jad@sinodun.com> wrote:
> 
> Hi,
> 
> Maybe I missed an announcement but please could someone explain why I am seeing:
> 
> Checking your browser before accessing ietf.org.
> 
> This process is automatic. Your browser will redirect to your requested content shortly.
> Please allow up to 5 seconds…
> DDoS protection by Cloudflare
> Ray ID: 56b9671cdc01e608
> 
> whilst going to an ietf mailman page?
> 
> What is Cloudflare checking for? What is Cloudflare’s privacy policy for this “service”?
> 
> BTW the link https://www.cloudflare.com/5xx-error-landing?utm_source=iuam shown as the text “DDoS protection by Cloudflare” doesn’t provide any explanation.


I’ve noticed this recently on a lot of other Cloudflare-backed websites. I wonder if they’re mitigating a large-scale DDoS attack, or something like that?

Cheers,
Ben