cloudflare.com
cloudflare.com describes itself as "Welcome to Cloudflare - Powering the next generation of applications". It was registered in 2009, served from Toronto, Canada. It has a valid HTTPS certificate, 6 of 6 common security headers, 1 tracking script.
What is cloudflare.com about?
The words appearing most often on the homepage, excluding common filler, are a rough indication of subject matter rather than a description of the business:
- cloudflare ×5
- close ×4
- scale ×3
- network ×3
- users ×3
- latency ×3
- build ×2
- under ×2
- attack ×2
- login ×2
Does cloudflare.com publish the usual trust pages?
All four of the pages a established business normally publishes were found: about, contact, privacy and terms. These were checked at conventional paths only, so a site using different URLs may publish them elsewhere.
How does cloudflare.com compare with other domains analysed here?
Measured against the 121 domains in this index. This is a small, self-selected sample — the domains people happened to look up — not a representative sample of the web.
| Response time | Faster than 77% of them (median 790ms) |
|---|---|
| Security headers | More than 98% of them |
| Domain age | Older than 90% of them |
Related domains in this index
Analysed domains sharing the same network (AS13335 Cloudflare, Inc.):
- stackoverflow.com
- npmjs.com
- digitalocean.com
- w3.org
- postman.com
- quikconsole.com
- bettingages.com
- cookiesforlove.com
Sharing a network means sharing a host or CDN. It implies nothing about a relationship between the sites themselves.
Analysed domains built on a similar stack:
Other analysed domains served from the same country:
- banneradsites.com
- realestatefather.com
- cookape.com.in
- cruzdid.com
- techaudi.com
- calculatewhatever.com
- intointent.com
- dateslots.com
When was cloudflare.com registered?
cloudflare.com was registered on 17 February 2009, which makes it about 17 years old.
A registration this old means the domain has been renewed repeatedly, which costs money every year and is not something abandoned or disposable projects tend to do.
The registrar of record is Cloudflare, Inc..
Registration runs until 17 February 2033.
The domain carries 6 registry locks, which blocks unauthorised transfer or deletion.
| Registered | 17 February 2009 |
|---|---|
| Expires | 17 February 2033 |
| Registrar | Cloudflare, Inc. |
| Registry status | client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited |
Where is cloudflare.com hosted?
The first address resolves to infrastructure in Toronto, Canada.
The network is operated by Cloudflare, Inc. (AS13335 Cloudflare, Inc.).
Hosting location describes where the responding server sits, not where the business is. A CDN will report its nearest edge rather than the origin.
What is cloudflare.com running on?
cloudflare.com exposes 2 identifiable technologies: Google Tag Manager, Cloudflare.
Cloudflare sits in front of the origin, so the server header, IP addresses and response timing describe the edge rather than the machine actually running the site.
Visitor tracking is present (Google Tag Manager), so this homepage is not cookie-free.
- Google Tag Manager
- Cloudflare
The page declares a generator of Astro v6.3.7.
How does the homepage respond?
The server answered with HTTP 200 over HTTPS.
At 388ms to first byte this response is unremarkable for a homepage measured from a single European location.
The HTML alone is 1303KB before images, stylesheets or scripts are counted, which is heavy for a document that browsers must parse before anything renders.
The HTML is compressed with gzip.
| Server header | cloudflare |
|---|---|
| Compression | gzip |
| Page size | 1,334,674 bytes |
| Declared language | en |
| Mobile viewport | declared |
What does the homepage say about itself?
The title is 35 characters, inside the range that displays without truncation.
A meta description of 68 characters is present.
All 68 images on the homepage have alt attributes.
| Title | Cloudflare: Build for the agent era (35 chars) |
|---|---|
| Meta description | Welcome to Cloudflare - Powering the next generation of applications (68 chars) |
| H1 | Everything we learned from powering 20% of the Internet—yours by default (1 on the page) |
| Canonical | https://www.cloudflare.com/ |
| Open Graph title | Cloudflare: Build for the agent era |
| Headings / images | 3 H2s, 68 images (0 without alt text) |
Is cloudflare.com served over a valid certificate?
The HTTPS certificate is issued by Google Trust Services and is valid until 2026-12-04, which is 61 days from the date of this check. It covers 5 hostnames.
- cloudflare.com
- ns.cloudflare.com
- *.ns.cloudflare.com
- *.secondary.cloudflare.com
- secondary.cloudflare.com
The certificate has 61 days left to run.
Which security headers does it set?
All 6 headers checked are set, which is uncommon and indicates someone configured them deliberately.
| Header | Set | Value |
|---|---|---|
| HSTS | yes | max-age=31536000; includeSubDomains |
| Content Security Policy | yes | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://static.cloudflareinsights.com https://static |
| X-Content-Type-Options | yes | nosniff |
| X-Frame-Options | yes | SAMEORIGIN |
| Referrer-Policy | yes | strict-origin-when-cross-origin |
| Permissions-Policy | yes | geolocation=(), camera=(), microphone=() |
How is DNS configured for cloudflare.com?
| IP addresses | 104.16.132.229, 104.16.133.229, 2606:4700::6810:85e5, 2606:4700::6810:84e5 |
|---|---|
| Reverse DNS | 104.16.132.229, 104.16.133.229 |
| Name servers | ns6.cloudflare.com, ns7.cloudflare.com, ns3.cloudflare.com, ns4.cloudflare.com, ns5.cloudflare.com |
| Mail (MX) | mxa.global.inbound.cf-emailsecurity.net (pri 10), mxb.global.inbound.cf-emailsecurity.net (pri 10), mxa-canary.global.inbound.cf-emailsecurity.net (pri 5), mxb-canary.global.inbound.cf-emailsecurity.net (pri 5) |
| SPF | v=spf1 ip4:199.15.212.0/22 ip4:173.245.48.0/20 include:_spf.google.com include:spf1.mcsv.net include:spf.mandrillapp.com include:mail.zendesk.com include:stspg-customer.com include:_spf.salesforce.com -all |
| TXT records | 29 |
cloudflare.com resolves to 4 addresses, which indicates load balancing or a CDN rather than a single origin server.
Mail is handled by 4 exchangers.
An SPF record is published, giving receiving servers a rule for which hosts may send as this domain.
Reverse DNS resolves to 104.16.132.229, 104.16.133.229, which usually names the hosting provider.
Who runs DNS and mail for cloudflare.com?
DNS is operated by Cloudflare rather than self-hosted name servers.
Mail exchangers point at hosts that do not match any major provider, which usually means self-hosted or niche-provider mail.
The domain publishes AAAA records and accepts connections over IPv6.
What else is worth noting about cloudflare.com?
1 of 1 externally hosted scripts carry no subresource integrity hash. If one of those hosts were compromised, the replacement script would run with full access to the page.
What has changed on cloudflare.com?
This domain has been checked 2 times. Only checks where something actually moved are recorded, so each row below is a real change rather than a repeat measurement.
| Checked | HTTP | Response | IP | Headers |
|---|---|---|---|---|
| 4 Oct 2026 | 200 | 388ms | 104.16.132.229 | 6/6 |
| 4 Oct 2026 | 200 | 470ms | 104.16.133.229 | 6/6 |
Changes recorded at the most recent check:
- IP address: 104.16.133.229 → 104.16.132.229
- name servers: ns4.cloudflare.com,ns5.cloudflare.com,ns6.cloudflare.com,ns7.cloudflare.com → ns6.cloudflare.com,ns7.cloudflare.com,ns3.cloudflare.com,ns4.cloudflare.com
- mail servers: mxb-canary.global.inbound.cf-emailsecurity.net (pri 5),mxa.global.inbound.cf-emailsecurity.net (pri 10),mxb.global.inbound.cf-emailsecurity.net (pri 10) → mxa.global.inbound.cf-emailsecurity.net (pri 10),mxb.global.inbound.cf-emailsecurity.net (pri 10),mxa-canary.global.inbound.cf-emailsecurity.net (pri 5)
Can cloudflare.com be spoofed in email?
DMARC is set to reject, the strictest setting: mail that fails authentication is refused outright. This is the configuration that actually stops domain spoofing.
CAA records restrict certificate issuance to 6 named authorities (issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com), so no other CA should be able to issue for this domain.
The zone is not DNSSEC-signed. That is still the norm for most domains, but it means DNS answers cannot be cryptographically verified.
What else does cloudflare.com publish?
A security.txt file is published, giving security researchers a documented way to report vulnerabilities. Very few sites bother.
What does robots.txt allow?
robots.txt is 1,099 bytes and names 9 user-agent groups. It does not blanket-disallow general crawlers.
Sitemaps declared:
- https://www.cloudflare.com/sitemap.xml
AI crawler policy
| Crawler | Policy |
|---|---|
| gptbot | allowed |
| perplexitybot | allowed |
| google-extended | allowed |
| ccbot | allowed |
| anthropic-ai | allowed |
1 sitemap is declared in robots.txt, which gives crawlers a direct list of URLs.
Named AI crawlers are explicitly allowed (gptbot, perplexitybot, google-extended, ccbot, anthropic-ai).
What structured data does the homepage publish?
- Organization
- WebSite
- SearchAction
- WebPage
The homepage publishes 4 structured data types: Organization, WebSite, SearchAction, WebPage.
What does cloudflare.com load from third parties?
The homepage pulls resources from 1 third-party host (imagedelivery.net). Each one sees the visitor IP and user agent on every page load.
1 cookie is set before any interaction (__cf_bm).
The page links or refers to X/Twitter, LinkedIn, GitHub.
| Cookie | Secure | HttpOnly | SameSite |
|---|---|---|---|
| __cf_bm | yes | yes | none |
Does cloudflare.com settle on one address?
Plain HTTP redirects to HTTPS, so visitors who type the bare address still land on the secure version.
Both cloudflare.com and www.cloudflare.com answer with 200 and neither redirects to the other. Search engines therefore see two complete copies of the site, and link equity is split between them unless a canonical tag resolves it.
How easily can cloudflare.com be crawled?
A sitemap is served at https://www.cloudflare.com/sitemap.xml listing 916 entries.
The most recent lastmod date is 2026-10-04.
A deliberately invalid URL correctly returns HTTP 404, so missing pages will not be indexed.
What tracking does cloudflare.com run?
1 tracking script detected: Google Tag Manager.
A consent platform is in place (OneTrust), so in the EU and UK these should only fire after the visitor agrees.
How does cloudflare.com look when shared?
All five social preview tags are present, so links shared to social platforms and chat apps will render with a title, description and image.
The page declares 10 hreflang alternates (x-default, es-es, fr-fr, de-de, it-it, pt-br, zh-cn, ja-jp, ko-kr, zh-tw), so it targets more than one language or region.
How are images, fonts and scripts handled?
68 images on the homepage, 1 of them lazy-loaded (1%).
Modern image formats are in use (2 WebP/AVIF references).
No srcset attributes are used, so every device is served the same image size regardless of screen.
The page pulls 4 external stylesheets and 3 external scripts, with 1 carrying defer or async.
Responses carry Cloudflare and Varnish/Fastly edge edge headers, so content is served from a CDN rather than straight from the origin.
Is cloudflare.com accessible and current?
The page uses 4 landmark elements and 249 ARIA attributes.
No skip-to-content link was found, which keyboard users rely on to bypass navigation.
Can search engines index cloudflare.com?
Nothing on the homepage prevents indexing: no noindex is set in the robots meta tag or the X-Robots-Tag header.
The homepage carries 15 internal and 0 external links across 0 outside hosts.
Visible text is only 0.3% of the HTML, which indicates the page is assembled in the browser rather than served as content.
The heading outline skips 1 level, which breaks the document structure screen readers navigate by.
How is cloudflare.com delivered?
The HTML is served with Cache-Control: max-age=10.
HTTP/3 is advertised via alt-svc, so modern browsers will upgrade to QUIC after the first visit.
The TLS certificate also covers 2 subdomains: ns.cloudflare.com, secondary.cloudflare.com.
- ns.cloudflare.com
- secondary.cloudflare.com
Frequently asked questions
Does cloudflare.com set the usual HTTP security headers?
Yes — all 6 headers checked are present.
Does cloudflare.com allow AI crawlers?
robots.txt names no AI crawler specifically, so they fall under the wildcard rule, which does not disallow them.
What is cloudflare.com built with?
The homepage exposes these fingerprints: Google Tag Manager, Cloudflare. A site behind a CDN or rendered server-side may use more than it reveals.
Where does this data come from?
Every figure was measured by our own server on 4 October 2026: DNS lookups, one HTTPS request to the homepage, a TLS handshake and a request for robots.txt. No third-party SEO API is involved.
Is any of this traffic or authority data?
No. Traffic, authority and ranking figures cannot be measured by inspecting a domain, only modelled. Everything here is a direct observation.
I own cloudflare.com and want this page removed.
Email hello@quikconsolecom.net from an address at the domain and the report will be taken down. It only ever shows what the domain already serves publicly.
Analysed 4 October 2026. Analyse another domain →