Is dash.cloudflare.com safe to use as a vendor?

dash.cloudflare.com scored 82/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 9 checks passed, 6 warnings, 0 critical issues across 16 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does dash.cloudflare.com use?

dash.cloudflare.com uses TLSv1.3 with TLS_AES_256_GCM_SHA384. TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Does dash.cloudflare.com have DMARC configured?

Yes. dash.cloudflare.com's DMARC policy is set to 'reject'. SPF record: yes. Strengths: DMARC policy set to reject (strongest); DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 6/10 (within limit); DKIM configured (selectors: s1, k1, krs, mandrill, smtpapi).

Does dash.cloudflare.com have SPF configured?

Yes. SPF record found: v=spf1 ip4:199.15.212.0/22 ip4:173.245.48.0/20 include:_spf.google.com include:s...

Does dash.cloudflare.com have security headers configured?

dash.cloudflare.com has 5 of 5 recommended security headers. Present: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy. All recommended headers present.

Has dash.cloudflare.com been involved in a data breach?

No known breaches found. No known breaches found in public disclosure databases.

Does dash.cloudflare.com have known CVE vulnerabilities?

Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.

MTA-STS & TLS Reporting

Strengths: SMTP TLS Reporting (TLSRPT) configured — delivery failures reported to: mailto:rua@cloudflare.com. Issues: MTA-STS DNS record present but policy file is unreachable (https://mta-sts.cloudflare.com/.well-known/mta-sts.txt) — TLS error, DNS failure, or server down.

dash.cloudflare.com Security Report — Grade B- (82/100)

Q: Does dash.cloudflare.com use HSTS?

Partially. HSTS configured with max-age=86400s (1 days) — below the recommended 180-day minimum (15552000s). Browsers will enforce HTTPS but the policy caches for a short window. Increase max-age to 15552000 or higher.

Q: Is dash.cloudflare.com's SSL certificate valid?

Issues detected. Strengths: Certificate valid, 65 days remaining; Issued by Google Trust Services; 1291 certificates logged in CT. Issues: Certificates issued by 10 different CAs (threshold: 8 for 1291 logged certs) — possible misconfiguration or shadow IT.

Q: Does dash.cloudflare.com have DNSSEC enabled?

No. Strengths: 5 nameservers configured (ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com, ns3.cloudflare.com...); SOA record present and MNAME consistent with NS set; 4 MX record(s) present; DNSSEC enabled: zone signed (DNSKEY present) and chain of trust intact (DS record in parent zone); Zone transfers properly restricted on all nameservers; Address records present: 2 A record(s), 2 AAAA record(s). Issues: All nameservers are from a single provider (cloudflare.com) — a provider outage takes down the domain.

B-

Trust rating

Good · 82/100

Procurement snapshot

No critical findings. The 6 remaining items are configuration gaps, not architectural problems.

Strengths

MX Records & Mail Provider

TLS Configuration

DNS CAA Records

TLS Protocol Support

Questions to ask

Confirm HSTS is enabled and its max-age setting

Estimated remediation effort: 1–2 days

Based on a passive external scan — supplement with vendor-provided attestations, not a replacement.

Trust Score Trend

→ No change 1 scan · Last scanned November 09, 2026

Score

100 75 50 25 0

B-

dash.cloudflare.com

82/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

ISO 27001

Certificate not on file

3rd party · accredited body

GDPR

DPA not on file

Self-reported

CCPA

Self-reported

Incident History

No public breaches on record

Security Posture

6 items need attention

9 passed

Increase how long HSTS stays remembered

HSTS Header

< 30 minutes Medium

This briefly reopens an interception window for returning visitors. HSTS is already turned on for dash.cloudflare.com, which is good — but it's only set to be remembered for 0 day(s), well under the 6-month minimum that's considered safe. A short duration means a returning visitor's browser "forgets" the HTTPS-only rule quickly, briefly reopening the same risk HSTS is meant to close.

PCI-DSS 4.0Req 6.4.1

Application security header configuration

How to fix this

1Update the existing header to the value below (same place you originally added it). You're using Cloudflare in front of this site — add it there, see https://developers.cloudflare.com/rules/transform/response-header-modification/create-dashboard/.

Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

2Confirm it's live: search "http header checker" and enter dash.cloudflare.com.

HSTS guide

Report unlocked.

View all 9 passed checks

MX Records & Mail Provider

TLS Configuration

DNS CAA Records

TLS Protocol Support

DMARC / Email Security

Cookie Security

Known Breaches

CVE Exposure

Subprocessors & Tech Stack

Couldn't check: Malware / Phishing Blocklist — the check didn't complete (the site blocked or timed out our scanner, or a data source was unavailable), so this isn't counted in the score.

Company Signals

Operational risk

Last funding

Employees

Trust Resources

Claim profile →

Trust Center

Not detected

DPA (Data Processing Agreement)

Subprocessors List

Similar companies

Appears in

Vendors graded B

826 companies · LynxRadar ranking

Medium Priority

Not enabled

HSTS configured with max-age=86400s (1 days) — below the recommended 180-day minimum (15552000s). Browsers will enforce HTTPS but the policy caches for a short window. Increase max-age to 15552000 or higher.

Likelihood: ★★☆☆☆

Impact: ★★☆☆☆

Not enabled

Strengths: 5 nameservers configured (ns5.cloudflare.com, ns6.cloudflare.com, ns7.cloudflare.com, ns3.cloudflare.com...); SOA record present and MNAME consistent with NS set; 4 MX record(s) present; DNSSEC enabled: zone signed (DNSKEY present) and chain of trust intact (DS record in parent zone); Zone transfers properly restricted on all nameservers; Address records present: 2 A record(s), 2 AAAA record(s). Issues: All nameservers are from a single provider (cloudflare.com) — a provider outage takes down the domain.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Warn

Strengths: SMTP TLS Reporting (TLSRPT) configured — delivery failures reported to: mailto:[email protected]. Issues: MTA-STS DNS record present but policy file is unreachable (https://mta-sts.cloudflare.com/.well-known/mta-sts.txt) — TLS error, DNS failure, or server down.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Best Practice

5/5 present

All headers configured.

Likelihood: ★★☆☆☆

Impact: ★☆☆☆☆

Warn

No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆

Issues

Strengths: Certificate valid, 65 days remaining; Issued by Google Trust Services; 1291 certificates logged in CT. Issues: Certificates issued by 10 different CAs (threshold: 8 for 1291 logged certs) — possible misconfiguration or shadow IT.

Likelihood: ★★☆☆☆

Impact: ★★☆☆☆