Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 25 Apr 2026, 14:37 UTC
Duration 6.3s
Version v26.47.06
Integrity 0143ce229201bd7530156c3835b42b00e8330170b00b5dd4d73f2b31c067f7b0b4db5b18bc76071bb9b0ae4af11508fb52e993dceeacf899f65dfa724b23c633
Subject Domain
cloudflare.com

Engineer's DNS Intelligence Report

cloudflare.com
25 Apr 2026, 14:37 UTC · 6.3s ·v26.47.06 · SHA-3-512: 0143✱✱✱✱ Verify ·Archived ·Cross-Referenced
Executive Topology
Recon Mode Snapshot Re-analyze New Domain
Footprint 9 SaaS Services
DNS Security & Trust Posture
Risk Level: Low Risk
7 protocols configured, 2 not configured Why we go beyond letter grades
Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.
Accuracy 56% Currency 70/100 Maturity consistent
Limiting factor: Resolver agreement is low for this scan — some protocols returned inconsistent results across resolvers
Currentness Excellent TTL Compliance Excellent Completeness Degraded Source Credibility Excellent TTL Relevance Stale
ICuAE Details
DNS data shows some aging or gaps — consider re-scanning for critical decisions

The following DNS record TTLs deviate from recommended values. Incorrect TTLs can cause caching issues, slow propagation, or unnecessary DNS traffic.

Record Type Observed TTL Typical TTL Severity Context
NS 6 hours (21600s) 1 day (86400s) medium NS TTL is below typical — observed 6 hours (21600s), typical value is 1 day (86400s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 86400 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
TXT 5 minutes (300s) 1 hour (3600s) high TXT TTL is below typical — observed 5 minutes (300s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
CAA 19s 1 hour (3600s) high CAA TTL is below typical — observed 19s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
MX 213s 1 hour (3600s) high MX TTL is below typical — observed 213s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
SOA 5 minutes (300s) 1 hour (3600s) high SOA TTL is below typical — observed 5 minutes (300s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
Provider Note: Cloudflare manages SOA timers automatically. Free/Pro/Business plans cannot modify SOA values. Observed TTL (5 minutes (300s)) is set by Cloudflare, not the zone administrator. See RFC 1912 §2.2 for recommended SOA timer values.
AAAA 5 minutes (300s) 1 hour (3600s) high AAAA TTL is below typical — observed 5 minutes (300s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
Provider Note: This TTL (5 minutes (300s)) matches Cloudflare's fixed proxied-record TTL. If this record is proxied (orange cloud), the TTL is enforced by Cloudflare and cannot be changed. Disable proxying (gray cloud) to regain TTL control, at the cost of losing Cloudflare's DDoS protection and CDN.
A 5 minutes (300s) 1 hour (3600s) high A TTL is below typical — observed 5 minutes (300s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
Provider Note: This TTL (5 minutes (300s)) matches Cloudflare's fixed proxied-record TTL. If this record is proxied (orange cloud), the TTL is enforced by Cloudflare and cannot be changed. Disable proxying (gray cloud) to regain TTL control, at the cost of losing Cloudflare's DDoS protection and CDN.

Big Picture Questions

  • How often do you actually change this record? If it hasn’t changed in months, a short TTL is generating unnecessary DNS queries without any benefit.
  • Are you preparing for a migration or IP change? Short TTLs make sense temporarily — but should be raised back to 1 hour (3600s) once the change is complete.
  • Every DNS lookup adds 20–150ms of latency. With a 60s TTL, returning visitors trigger a fresh lookup every minute. With 3600s, they get cached responses for an hour — faster page loads, no extra infrastructure needed.
  • Google runs A records at ~30s because they operate a global anycast network and need to steer traffic dynamically. For a typical website without that infrastructure, copying those TTLs increases query volume with zero upside.
Tune TTL for cloudflare.com
Reference: NIST SP 800-53 SI-7 (Information Integrity) · RFC 8767 (Serve Stale) · RFC 1035 §3.2.1 (TTL semantics) DNS provider detected: Cloudflare — provider-specific RFC compliance notes are shown inline above where applicable.
Primary NS ns3.cloudflare.com
Serial 2401983296
Admin dns.cloudflare.com
Provider Cloudflare
Timer Value RFC 1912 Range
Refresh10000s1,200–43,200s (20 min – 12 hrs)
Retry2400sFraction of Refresh
Expire604800s1,209,600–2,419,200s (14–28 days)
Minimum (Neg. Cache)300s300–86,400s (5 min – 1 day)
Expire: SOA Expire is 7 days (604800s). RFC 1912 §2.2 recommends 1,209,600–2,419,200 seconds (14–28 days). If the primary nameserver becomes unreachable, secondary nameservers will stop serving this zone after only 7 days (604800s). Cloudflare's anycast architecture reduces the practical risk, but this value departs from the RFC recommendation.
RFC 1912 §2.2

Independent RFC compliance assessment for Cloudflare. Each finding cites the specific RFC section and reports what the engineering community consensus is. We report honestly — if a provider deviates from standards, we explain what they did differently and what the RFCs actually say.

SOA Expire below RFC 1912 recommendation RFC 1912 §2.2

Cloudflare sets SOA Expire to 604,800 seconds (7 days). RFC 1912 §2.2 recommends 1,209,600–2,419,200 seconds (14–28 days). This means secondary nameservers stop serving the zone sooner if the primary becomes unreachable. Cloudflare's position is that their anycast architecture makes traditional zone transfer semantics less relevant. SOA timers are not editable on Free, Pro, or Business plans.

Below RFC recommendation
Proxied record TTLs fixed at 300s RFC 2181 §5.2

Cloudflare overrides the zone administrator's TTL to 300 seconds for all proxied (orange-cloud) records. RFC 2181 §5.2 requires TTL uniformity within an RRset but does not mandate a specific value. As the authoritative server, Cloudflare is technically within its rights, but the administrator loses TTL control. This can affect ACME DNS-01 challenges and automation workflows that depend on rapid propagation.

Technically compliant, but overrides administrator intent
Non-standard SOA serial format RFC 1912 §2.2

RFC 1912 recommends YYYYMMDDNN format for SOA serial numbers (e.g., 2026022501). Cloudflare uses a proprietary serial number format that does not encode the date. RFC 1035 only requires the serial to increment on changes, so this is compliant with the mandatory standard but breaks the convention relied on by monitoring tools.

Compliant with RFC 1035, deviates from RFC 1912 convention
Negative cache TTL delays new records RFC 2308 §5

Cloudflare's SOA MINIMUM (negative cache TTL) is 1,800–3,600 seconds (30–60 minutes). This controls how long resolvers cache NXDOMAIN responses. Newly created DNS records — including ACME DNS-01 challenge TXT records for Let's Encrypt — may be invisible for up to 1 hour even after creation. This causes certificate issuance failures for automation tools like cert-manager and Traefik. Workaround: pre-create placeholder records before they're needed. This is RFC-compliant but aggressive compared to the 300–900 seconds common at other providers.

RFC-compliant, but causes real-world automation failures
Historical RFC 2181 §5.2 violation: TTL mismatch in CNAME RRsets RFC 2181 §5.2

In February 2022, Cloudflare's resolver (1.1.1.1) returned CNAME responses with mismatched TTLs within the same RRset — including cases where one TTL was zero and another was non-zero. RFC 2181 §5.2 explicitly states: 'the TTLs of all RRs in an RRSet must be the same.' systemd-resolved (used by Arch Linux, Ubuntu, Fedora, and most modern Linux distributions) correctly rejected these responses per the RFC, causing widespread DNS resolution failures. Cloudflare acknowledged the issue and it appears to have been fixed, but it demonstrated that Cloudflare's DNS infrastructure can deviate from RFC requirements in ways that break compliant resolver implementations.

Was a documented RFC violation — appears resolved
This assessment is based on RFC specifications, provider documentation, and documented incidents from DNS engineering communities. DNS Tool does not have a commercial relationship with any provider listed.
Email Spoofing
Protected
Brand Impersonation
Protected
DNS Tampering
Protected
Certificate Control
Configured
Configured
SPF (hard fail), DMARC (reject), DKIM, BIMI, DANE, DNSSEC, CAA
Not Configured
MTA-STS, TLS-RPT
Priority Actions Achievable posture: Secure
Low Add TLS-RPT Reporting

Your domain has DNSSEC + DANE — the strongest email transport security available. TLS-RPT (TLS Reporting) sends you reports about TLS connection failures when other servers try to deliver mail to your domain.

TLS-RPT sends you reports about TLS connection failures to your mail servers.
TypeTXT
Host_smtp._tls.cloudflare.com (SMTP TLS reporting record)
Valuev=TLSRPTv1; rua=mailto:tls-reports@cloudflare.com
RFC 8460
Low Deploy MTA-STS

MTA-STS enforces TLS encryption for inbound mail delivery, preventing downgrade attacks on your mail transport.

MTA-STS tells sending servers to require TLS when delivering mail to your domain.
TypeTXT
Host_mta-sts.cloudflare.com (MTA-STS policy record)
Valuev=STSv1; id=cloudflare.com
RFC 8461
Open Remediation Workspace — Copy-Paste Ready Records
Registrar (RDAP) OBSERVED LIVE
Cloudflare, Inc.
Where domain was purchased
Email Service Provider
Unknown
Strongly Protected
Web Hosting
Unknown
Where website is hosted
DNS Hosting OBSERVED
Cloudflare
Where DNS records are edited
Email Security Methodology Can this domain be impersonated by email? No SPF and DMARC reject policy enforced

SPF Record RFC 7208 §4 Consistent

Does this domain declare who may send email on its behalf? Yes
Success -all 6/10 lookups

SPF valid with strict enforcement (-all), 6/10 lookups

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
RFC 7489: -all may cause rejection before DMARC evaluation, preventing DKIM from being checked
RFC 7208 Conformant — This SPF record conforms to the syntax and semantics defined in RFC 7208 §4.
RFC Failure Mode: Unlike DMARC (where unknown tags are silently ignored per RFC 7489 §6.3), SPF with unrecognized mechanisms produces a PermError per RFC 7208 §4.6 — the record fails loudly rather than silently.
Related CVEs: CVE-2024-7208 (multi-tenant domain spoofing), CVE-2024-7209 (shared SPF exploitation), CVE-2023-51764 (SMTP smuggling bypasses SPF)
SPF hard fail (-all): compliance-strong, but can short-circuit DMARC. RFC 7489 notes that -all can cause some receivers to reject mail during the SMTP transaction — before DKIM is checked and before DMARC can evaluate the result. A message that would pass DMARC via DKIM alignment may be rejected prematurely. For most domains, ~all + DMARC p=reject is the strongest compatible posture — it allows every authentication method (SPF, DKIM, DMARC) to be fully evaluated before a decision is made.
DMARC is set to reject — enforcement is strong. However, some receivers may still reject messages on SPF hard fail before DKIM alignment is checked. Switching to ~all + p=reject would provide the same enforcement with full DMARC compatibility.

DMARC Policy RFC 7489 §6.3 Consistent

Are spoofed emails rejected or quarantined? Yes — reject policy
Success p=reject

DMARC policy reject (100%) - excellent protection

v=DMARC1; p=reject; pct=100; rua=mailto:rua@cloudflare.com,mailto:cloudflare@dmarc.area1reports.com; ruf=mailto:cloudflare@dmarc.area1reports.com
Alignment: SPF relaxed DKIM relaxed
No np= tag (DMARCbis) — non-existent subdomains inherit p= policy but adding np=reject provides explicit protection against subdomain spoofing
Forensic reporting (ruf) is configured, but most major providers do not send forensic reports. RFC 7489 §7.3 warns that forensic reports can expose PII (full message headers or bodies). Google, Microsoft, and Yahoo do not honour ruf= requests. The DMARCbis draft (draft-ietf-dmarc-dmarcbis) has formally removed ruf= from the specification. Consider removing this tag to simplify your record. RFC 7489 §7.3 — Forensic Reports
RFC 7489 Conformant — DMARC record conforms to RFC 7489 §6.3 with full enforcement.
DMARCbis (Pending): draft-ietf-dmarc-dmarcbis will elevate DMARC to Standards Track, obsolete RFC 7489, replace pct= with t= (testing flag), add np= (non-existent subdomain policy), and mandate DNS tree walk for policy discovery instead of the Public Suffix List.
Related CVEs: CVE-2024-49040 (Exchange sender spoofing), CVE-2024-7208 (multi-tenant DMARC bypass)

DKIM Records RFC 6376 §3.6 Consistent

Are outbound emails cryptographically signed? Yes — verified
Found 2048-bit

Found DKIM for 6 selector(s) with strong keys (2048-bit)

SPF authorizes Google Workspace servers, but MX records point to self-hosted infrastructure. The Google Workspace SPF include likely supports ancillary services (e.g., calendar invitations, shared documents) rather than primary mailbox hosting.
k1._domainkey 2048-bit Adequate
k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i89sA2guU0ta4UX1Xzm06XIU6iBP41VwmPwBGRNofhBVR+e6WHUoNyIR4Bn84LVcfZE20rmDeXQblIupNWBqLXM1Q+VieI/eZu/7k9/vOkLSaQQdml4Cv8lb3PcnluMVIhQIDAQAB;
mandrill._domainkey MailChimp (Mandrill) 2048-bit Adequate
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB
s1._domainkey 2048-bit Adequate
k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA1m74n5R+xcz+ICbNBWRIlQeHI65Hjp67+P59XSe71jItafrcJ4/5y/UvU+uNg7KNeOcEsotGo7QvLN87hqZSZqfzVyyGnQuEUXoKPdKokD6Pa5KmJSqbA5Y/f977HpikU9Xtd7Orc7ctRLK6H5QFvGwRi+oC9NRkgNB55UUnLbbkKK+LGeTw4Ghmr5gupw7iYzFXZ1qlFNqV6s9Pmgb+b7oDv+OfQxB/MJyUzQ5eWdKlJWfmW3s77J3fHFfysUbKKUBxEXPxNiMFRG1ClllZ4+AYRh1jrFpjbvZ5j43kqahKXeHDNkF+Gpptd7ufWIevAPTQDSVdKB9vyJQN6wfcQQIDAQAB
smtpapi._domainkey SendGrid 2048-bit Adequate
k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDPtW5iwpXVPiH5FzJ7Nrl8USzuY9zqqzjE0D1r04xDN6qwziDnmgcFNNfMewVKN2D1O+2J9N14hRprzByFwfQW76yojh54Xu3uSbQ3JP0A7k8o8GutRF8zbFUA8n0ZH2y0cIEjMliXY4W4LwPA7m4q0ObmvSjhd63O9d8z1XkUBwIDAQAB
zendesk1._domainkey Zendesk 2048-bit Adequate
v=DKIM1;t=s;n=core;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9IqdLrO3Zr2/56MHt8oQVCQorP0Bl2Fz9sM2tFBnJCdB/HogQmuudEg2xAovCN2PYpw44UijIvPuBoT9vxiv6ZCBJTLJXa82r6ke5rE4tbe9NKFIrVIb9S306cJDrnKFMDb8p0dU/Su0+eUR5gVAOtCuz2L8HAzs5edvsEvD/Fb4ny1RLNSEPZkIQLfGhVxQeWANm3+1Jwb/OBVXV9k0nKpWrpgqcmO7NzroJirp014RQY7rGi60JLUubc6XhvoFQBQrtOAdVlZC5wvfS1bgpq5kQpdP7cajIqWCeqxPTeo0ZUpey2ZcaygEsZz0Z3Gs5wDzyuqd7/ADpr2jNF7ozwIDAQAB
zendesk2._domainkey Zendesk 2048-bit Adequate
v=DKIM1; t=s; n=core; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmiSFNkgXrO3I8aOaPONDZWHv027rkiGIwb838OyXPgvFDEkCV/qGcdXSjZnaVAadrTm/oKnL8WOltP9zB1FLEuKt0fTi5zRyKPE4oIYCnEzXwrGqzjUcCABQBawQVqvXjDOaYh9Lhp8W5PYOLo905vRW7ipyIMDhuzBOJls91/WWXnNK0OwP3RghiisZjA3K2KqtRwf7w6GjNeNuAMNhvcmgAN15d/mhK+dev/hcRbal66RoYyTD8c0F0isahWH0envEX8aj+SBhheNk0/U37dGE+4nFaY5yP9CUlYjFKDSIKZgHzG4Hci3t/RubU58pi6BCrQQdAFvIOeDFeCZ0ywIDAQAB
RFC 6376 Conformant — DKIM keys and signatures conform to RFC 6376 §3.6 (Internet Standard).
Known Vulnerabilities: DKIM l= tag body length vulnerability (attacker appends unsigned content to signed mail), weak key exploitation (keys below 1024-bit are cryptographically breakable per RFC 6376 §3.3.3), DKIM replay attacks (re-sending legitimately signed messages at scale)

MTA-STS RFC 8461 §3 Consistent

Can attackers downgrade SMTP to intercept mail? Not prevented
Warning

No MTA-STS record found

MTA-STS policy enforcement is evaluated in Mail Transport Security below.

TLS-RPT RFC 8460 §3 Consistent

Will failures in TLS delivery be reported? No reporting
Warning

No TLS-RPT record found

DMARC External Reporting Authorization RFC 7489 §7.1

Are external report receivers authorized? Yes — all authorized
Success

All 1 external reporting domains properly authorized

External Domain Authorization Auth Record
dmarc.area1reports.com Authorized v=DMARC1
DANE / TLSA Consistent Recon Methodology Can mail servers establish identity without a public CA? Yes
RFC 7672 §3 RFC 6698 §2 4/4 MX

DANE configured — TLSA records found for all 4 MX hosts

MX Host Usage Selector Match Certificate Data
mxa-canary.global.inbound.cf-emailsecurity.net 3 DANE-EE (Domain-issued certificate) Public key only (SubjectPublicKeyInfo) SHA-256 9122be3be7bcc604fd296255f5783c3d945b4aab46418f87d029ebf74db191e1
mxb-canary.global.inbound.cf-emailsecurity.net 3 DANE-EE (Domain-issued certificate) Public key only (SubjectPublicKeyInfo) SHA-256 9122be3be7bcc604fd296255f5783c3d945b4aab46418f87d029ebf74db191e1
mxb.global.inbound.cf-emailsecurity.net 3 DANE-EE (Domain-issued certificate) Public key only (SubjectPublicKeyInfo) SHA-256 7fed38b4b0b86d8a5834e5a1aeabbb34a5a04159a281d62ff42d6a7bde310f36
mxb.global.inbound.cf-emailsecurity.net 3 DANE-EE (Domain-issued certificate) Public key only (SubjectPublicKeyInfo) SHA-256 96c2b0229b798135d733e41d6e5817c67e853dbb0a70b2cfe22f462a1d085751
mxb.global.inbound.cf-emailsecurity.net 3 DANE-EE (Domain-issued certificate) Public key only (SubjectPublicKeyInfo) SHA-256 9122be3be7bcc604fd296255f5783c3d945b4aab46418f87d029ebf74db191e1
mxb.global.inbound.cf-emailsecurity.net 3 DANE-EE (Domain-issued certificate) Public key only (SubjectPublicKeyInfo) SHA-256 e8a50fb03ed780a45bca47a36af2dca2bc13ad4be117b296285ed8754d7350cb
mxa.global.inbound.cf-emailsecurity.net 3 DANE-EE (Domain-issued certificate) Public key only (SubjectPublicKeyInfo) SHA-256 e8a50fb03ed780a45bca47a36af2dca2bc13ad4be117b296285ed8754d7350cb
mxa.global.inbound.cf-emailsecurity.net 3 DANE-EE (Domain-issued certificate) Public key only (SubjectPublicKeyInfo) SHA-256 9122be3be7bcc604fd296255f5783c3d945b4aab46418f87d029ebf74db191e1
mxa.global.inbound.cf-emailsecurity.net 3 DANE-EE (Domain-issued certificate) Public key only (SubjectPublicKeyInfo) SHA-256 96c2b0229b798135d733e41d6e5817c67e853dbb0a70b2cfe22f462a1d085751
mxa.global.inbound.cf-emailsecurity.net 3 DANE-EE (Domain-issued certificate) Public key only (SubjectPublicKeyInfo) SHA-256 7fed38b4b0b86d8a5834e5a1aeabbb34a5a04159a281d62ff42d6a7bde310f36
Email Transport Security

Two mechanisms protect email in transit. DANE is the primary standard; MTA-STS is the alternative for domains that cannot deploy DNSSEC:

  • DNSSEC + DANE (RFC 7672) — Cryptographic chain of trust from DNS root to mail server certificate. Eliminates reliance on certificate authorities. No trust-on-first-use weakness. Requires DNSSEC.
  • MTA-STS (RFC 8461) — HTTPS-based policy requiring TLS for mail delivery. Works without DNSSEC but relies on CA trust and is vulnerable on first use (§10). Created for domains where “deploying DNSSEC is undesirable or impractical” (§2).
This domain uses DNSSEC + DANE — the strongest cryptographic transport security. DANE binds TLS certificates to DNSSEC-signed DNS records, creating a verifiable chain of trust from root to mail server (RFC 7672 §1.3). MTA-STS could complement this for senders that don't validate DNSSEC, but DANE alone provides the highest level of protection available.

Industry trend: Microsoft Exchange Online enforces inbound DANE with DNSSEC (GA October 2024), and providers like Proton Mail and Fastmail also support DANE. Google Workspace does not support DANE and relies on MTA-STS. Both mechanisms coexist because DANE is backward-compatible — senders skip the check if the domain isn't DNSSEC-signed (RFC 7672 §1.3).

Brand Security Can this brand be convincingly faked? No DMARC reject policy enforced (RFC 7489 §6.3), BIMI brand verification active (BIMI Spec), and certificate issuance restricted by CAA (RFC 8659 §4) — all three brand-faking vectors addressed

BIMI BIMI Spec Consistent Success VMC SVG

Is the brand identity verified and displayed in inboxes? Yes

BIMI with VMC certificate (from Verified CA)

VMC certificate accessible (from Verified CA) - logo displays in Gmail, Apple Mail, and all major providers.
v=BIMI1; l=https://www.cloudflare.com/cloudflare_1171114652.svg; a=https://www.cloudflare.com/cloudflare_1171114652.pem
BIMI Logo
Logo validated (SVG) View full logo

CAA RFC 8659 §4 Consistent Success IODEF

Does this domain restrict who can issue TLS certificates? Yes

CAA configured - only DigiCert, Sectigo, cansignhttpexchanges=yes, ssl.com, Let's Encrypt can issue certificates (wildcard issuance: Let's Encrypt, cansignhttpexchanges=yes, DigiCert, Sectigo, ssl.com per RFC 8659 §4.3)

Authorized CAs: DigiCert Sectigo cansignhttpexchanges=yes ssl.com Let's Encrypt
0 iodef "mailto:tls-abuse@cloudflare.com"
0 issue "digicert.com; cansignhttpexchanges=yes"
0 issue "comodoca.com"
0 issuewild "pki.goog; cansignhttpexchanges=yes"
0 issuewild "digicert.com; cansignhttpexchanges=yes"
0 issue "pki.goog; cansignhttpexchanges=yes"
0 issue "ssl.com"
0 issuewild "comodoca.com"
0 issuewild "ssl.com"
0 issue "letsencrypt.org"
0 issuewild "letsencrypt.org"
Since September 2025, all public CAs must verify domain control from multiple geographic locations (Multi-Perspective Issuance Corroboration, CA/B Forum Ballot SC-067). CAA records are now checked from multiple network perspectives before certificate issuance.
Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Partial RFC 9116

security.txt found with issues

Contact

https://hackerone.com/cloudflare
https://www.cloudflare.com/abuse/

Expires

Missing (required by RFC 9116 §2.5.5)

Policy

https://www.cloudflare.com/disclosure/
en Canonical URL Hiring
Source: https://cloudflare.com/.well-known/security.txt
Missing required Expires field (RFC 9116 §2.5.5)
AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? Yes

AI governance signals observed

llms.txt llmstxt.org
Is this domain publishing AI-readable brand context? Yes
llms.txt found — domain provides structured context for LLMs View llms.txt
AI Crawler Governance (robots.txt) RFC 9309 IETF Draft
Are AI crawlers explicitly allowed or blocked? Not blocked
No AI crawler blocking observed — no blocking directives found in robots.txt View robots.txt
Content-Usage Directive IETF Draft
Does the site express AI content-usage preferences? Not Configured
No Content-Usage directive detected. The IETF AI Preferences working group is developing a Content-Usage: directive for robots.txt that lets site owners declare whether their content may be used for AI training and inference. This is an active draft, not yet a ratified standard.
Example: Add Content-Usage: ai=no to robots.txt to deny AI training, or Content-Usage: ai=allow to explicitly permit it. Without this directive, AI crawler behavior depends on individual crawler policies and User-agent rules.
AI Recommendation Poisoning
Is this site trying to manipulate AI recommendations? No
No AI recommendation poisoning indicators found
Hidden Prompt Artifacts
Is hidden prompt-injection text present in the source? No
No hidden prompt-like artifacts detected
Evidence Log (2 items)
TypeDetailSeverityConfidence
llms_txt_found llms.txt file found providing structured LLM context info Observed
robots_txt_no_ai_blocks robots.txt found but no AI-specific blocking directives low Observed
Public Exposure Checks Are sensitive files or secrets exposed? No

No exposed secrets detected in public page source — same-origin, non-intrusive scan of publicly visible page source and scripts.

No exposed secrets, API keys, or credentials were detected in publicly accessible page source or scripts.
What type of scan is this?

This is OSINT (Open Source Intelligence) collection — we check the same publicly accessible URLs that any web browser could visit. No authentication is bypassed, no ports are probed, no vulnerabilities are exploited.

Is this a PCI compliance scan? No. PCI DSS requires scans performed by an Approved Scanning Vendor (ASV) certified by the PCI Security Standards Council. DNS Tool is not an ASV. If you need PCI compliance scanning, engage a certified ASV such as Qualys, Tenable, or Trustwave.

Is this a penetration test? No. Penetration testing involves active exploitation attempts against systems with authorization. Our checks are passive observation of publicly accessible resources — the same methodology used by Shodan, Mozilla Observatory, and other OSINT platforms.

DNS Server Security Hardened

No DNS server misconfigurations found on ns7.cloudflare.com — Nmap NSE probes for zone transfer (AXFR), open recursion (RFC 5358), nameserver identity disclosure, and DNS cache snooping.

Check Result Detail
Zone Transfer (AXFR) Denied Test inconclusive
Open Recursion Disabled Test inconclusive
Nameserver Identity Hidden Test inconclusive
Cache Snooping Protected Test inconclusive

Tested nameservers: ns7.cloudflare.com, ns6.cloudflare.com, ns5.cloudflare.com, ns4.cloudflare.com, ns3.cloudflare.com

Delegation Consistency 6 Issues

Delegation consistency: 6 issue(s) found — Parent/child NS delegation alignment: DS↔DNSKEY, glue records, TTL drift, SOA serial sync.

Findings:
  • In-bailiwick NS ns3.cloudflare.com has no glue records at parent — resolution may fail
  • In-bailiwick NS ns4.cloudflare.com has no glue records at parent — resolution may fail
  • In-bailiwick NS ns5.cloudflare.com has no glue records at parent — resolution may fail
  • In-bailiwick NS ns6.cloudflare.com has no glue records at parent — resolution may fail
  • In-bailiwick NS ns7.cloudflare.com has no glue records at parent — resolution may fail
  • Could not retrieve NS TTL from parent zone

DS ↔ DNSKEY Alignment Aligned

DS Key TagDS AlgorithmDNSKEY Key TagDNSKEY Algorithm
2371 13 2371 13

Glue Record Completeness Incomplete

NameserverIn-BailiwickIPv4 GlueIPv6 GlueStatus
ns3.cloudflare.com Missing
ns4.cloudflare.com Missing
ns5.cloudflare.com Missing
ns6.cloudflare.com Missing
ns7.cloudflare.com Missing

NS TTL Comparison Drift

Child TTL: 86400s Drift: 0s

SOA Serial Consistency Consistent

ns3.cloudflare.com: 2.401983296e+09
ns4.cloudflare.com: 2.401983296e+09
ns5.cloudflare.com: 2.401983296e+09
ns6.cloudflare.com: 2.401983296e+09
ns7.cloudflare.com: 2.401983296e+09
Nameserver Fleet Matrix Healthy

Analyzed 5 nameserver(s) for cloudflare.com — Per-nameserver reachability, ASN diversity, SOA serial sync, and lame delegation checks.

Nameserver IPv4 IPv6 ASN / Operator UDP TCP AA SOA Serial
ns5.cloudflare.com 162.159.2.9
162.159.9.55 		2400:cb00:2049:1::a29f:209
2400:cb00:2049:1::a29f:937 		AS13335
Cloudflare, Inc. 		2401983296
ns6.cloudflare.com 162.159.5.6
162.159.3.11 		2400:cb00:2049:1::a29f:30b
2400:cb00:2049:1::a29f:506 		AS13335
Cloudflare, Inc. 		2401983296
ns3.cloudflare.com 162.159.7.226
162.159.0.33 		2400:cb00:2049:1::a29f:21
2400:cb00:2049:1::a29f:7e2 		AS13335
Cloudflare, Inc. 		2401983296
ns7.cloudflare.com 162.159.6.6
162.159.4.8 		2400:cb00:2049:1::a29f:408
2400:cb00:2049:1::a29f:606 		AS13335
Cloudflare, Inc. 		2401983296
ns4.cloudflare.com 162.159.1.33
162.159.8.55 		2400:cb00:2049:1::a29f:121
2400:cb00:2049:1::a29f:837 		AS13335
Cloudflare, Inc. 		2401983296
Unique ASNs
1
Unique Operators
1
Unique /24 Prefixes
10
Diversity Score
Fair

1 ASN(s), 10 /24 prefix(es) — consider adding diversity

DNSSEC Operations Deep Dive 1 Issue

DNSSEC operational notes: 1 item(s) to review — KSK/ZSK differentiation, RRSIG expiry windows, NSEC/NSEC3 analysis, and rollover readiness.

Findings:
  • CDS/CDNSKEY automation present but only single KSK — pre-publish second KSK before rollover

DNSKEY Inventory 2 Keys

RoleKey TagAlgorithmKey Size
ZSK 34505 ECDSA P-256/SHA-256 256 bits
KSK 2371 ECDSA P-256/SHA-256 256 bits

RRSIG Signatures 0 Signatures

No RRSIG records found.

Denial of Existence NSEC

NSEC records expose zone contents via ordered names (zone walking). Consider NSEC3 for zone enumeration protection.

Rollover Readiness Partial

Multiple KSKs:
CDS Published:
CDNSKEY Published:
Automation: full
Mail Transport Security Beta Is mail transport encrypted and verified? Yes DANE/TLSA provides cryptographic transport verification

All 3 server(s) verified: encrypted transport confirmed via direct SMTP probe and DNS policy

Policy Assessment Primary
  • DANE/TLSA records published — mail servers pin TLS certificates via DNSSEC (RFC 7672)
Telemetry
TLS-RPT not configured — domain has no visibility into TLS delivery failures from real senders
Live Probe Supplementary
MX Host STARTTLS TLS Version Cipher Certificate
mxb.global.inbound.cf-emailsecurity.net TLSv1.3 TLS_AES_128_GCM_SHA256 Valid
Expires: 2026-08-11 (108 days)
Issuer: DigiCert Inc
mxb-canary.global.inbound.cf-emailsecurity.net TLSv1.3 TLS_AES_128_GCM_SHA256 Valid
Expires: 2026-08-11 (108 days)
Issuer: DigiCert Inc
mxa.global.inbound.cf-emailsecurity.net TLSv1.3 TLS_AES_128_GCM_SHA256 Valid
Expires: 2026-08-12 (109 days)
Issuer: DigiCert Inc
Multi-Vantage Probe Results
Unanimous: TLS verified 2 probes, 1 responded
US-East (Boston) observed
All servers support TLS
France - EU skipped
3.045197726s
Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

Resolved 1 unique ASN(s) across 4 IP address(es)

ASNNameCountry
AS13335 Cloudflare, Inc. US
IPv4 Mappings:
104.16.132.229 → AS13335 (104.16.128.0/20)
104.16.133.229 → AS13335 (104.16.128.0/20)
IPv6 Mappings:
2606:4700::6810:84e5 → AS13335 (2606:4700::/44)
2606:4700::6810:85e5 → AS13335 (2606:4700::/44)

Edge / CDN Success

Domain appears to use direct origin hosting

SaaS TXT Footprint Success 9 services

9 SaaS services detected via DNS TXT verification records

Detects SaaS services that leave DNS TXT verification records (e.g., domain ownership proofs). Does not detect all SaaS platforms — only those indicated by DNS.

ServiceVerification Record
Microsoft 365 MS=ms70274184
Apple apple-domain-verification=DNnWJoArJobFJKhJ
Atlassian atlassian-domain-verification=WxxKyN9aLnjEsoOjUYI6T0bb5vcqmKzaIkC9Rx2QkNb751G3LL...
Canva canva-site-verification=oOyaVnHC-OiFoR1BPvetNA
Cisco Umbrella cisco-ci-domain-verification=27e926884619804ef987ae4aa1c4168f6b152ada84f4c8bfc74...
Facebook / Meta facebook-domain-verification=h9mm6zopj6p2po54woa16m5bskm6oo
Google Workspace google-site-verification=C7thfNeXVahkVhniiqTI1iSVnElKR_kBBtnEHkeGDlo
Miro miro-verification=bdd7dfa0a49adfb43ad6ddfaf797633246c07356
Stripe stripe-verification=5096d01ff2cf194285dd51cae18f24fa9c26dc928cebac3636d462b4c692...
Domain Security Methodology Can DNS responses be tampered with in transit? No DNSSEC signed and validated, cryptographic chain of trust verified

DNSSEC RFC 4033 §2 Consistent Signed ECDSA P-256/SHA-256 Modern

DNSSEC fully configured and validated — AD (Authenticated Data) flag set by resolver 8.8.8.8 confirming cryptographic chain of trust from root to zone (RFC 4035 §3.2.3)

Algorithm Observation: ECDSA P-256/SHA-256 — MUST implement, recommended default (RFC 8624 §3.1)
All current DNSSEC algorithms use classical cryptography. Post-quantum DNSSEC standards are in active IETF development (draft-sheth-pqc-dnssec-strategy) but no PQC algorithms have been standardized for DNSSEC yet.
Chain of trust: Root → TLD → Domain. DNS responses are cryptographically authenticated and tamper-evident.
AD Flag: Validated - Resolver (8.8.8.8) confirmed cryptographic signatures
DS Record (at registrar):
2371 13 2 32996839A6D808AFE3EB4A795A0E6A7A39A76FC52FF228B22B76F6D63826F2B9

NS Delegation Verified

5 nameserver(s) configured

Nameservers: ns3.cloudflare.com ns4.cloudflare.com ns5.cloudflare.com ns6.cloudflare.com ns7.cloudflare.com
Managed DNS
All 5 nameservers hosted by Cloudflare. Managed DNS provides reliable resolution with provider-maintained infrastructure.
DNS provider(s): Cloudflare
Multi-Resolver Verification Recon: Discrepancy detected - Some resolvers returned different results (1 difference found)
Resolver Differences:
TXT: OpenDNS returned different results: [MS=ms70274184 ZOOM_verify_7LFBvOO9SIigypFG2xRlMA _neqmkgaq1lq9it5s8qmetrhbnu121wb _wkjc0fot0d7qrvrdt78bxkj2e2o67d2 apple-domain-verification=DNnWJoArJobFJKhJ asv=894f6d1f9f83bcf44e4b1bc40bc1c4aa canva-site-verification=oOyaVnHC-OiFoR1BPvetNA docker-verification=c578e21c-34fb-4474-9b90-d55ee4cba10c status-page-domain-verification=r14frwljwbxs]
This may indicate DNS propagation in progress or geo-based DNS routing.

HTTPS / SVCB Records RFC 9460 Success HTTPS HTTP/3

HTTPS records found, HTTP/3 supported

PriorityTargetALPNECHRaw
1 . h3, h2 No cloudflare.com. 300 IN HTTPS 1 . alpn="h3,h2" ipv4hint="104.16.132.229,104.16.133.229" ipv6hint="2606:4700::6810:84e5,2606:4700::6810:85e5"

CDS / CDNSKEY (DNSSEC Automation) RFC 7344 Success CDS CDNSKEY

Full RFC 8078 automated DNSSEC key rollover signaling detected (CDS + CDNSKEY)

Key TagAlgorithmDigest TypeDigest
2371 ECDSAP256SHA256 2
CDNSKEY Records:
FlagsProtocolAlgorithmPublic Key
257 3 ECDSAP256SHA256
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

104.16.132.229
104.16.133.229
Where the domain points for web traffic

AAAAIPv6 Address

2606:4700::6810:84e5
2606:4700::6810:85e5
IPv6 ready

MXMail Servers

10 mxa.global.inbound.cf-emailsecurity.net.
10 mxb.global.inbound.cf-emailsecurity.net.
5 mxa-canary.global.inbound.cf-emailsecurity.net.
5 mxb-canary.global.inbound.cf-emailsecurity.net.
Priority + mail server for email delivery

SRVServices

No SRV records
No service-specific routing configured
Web: Reachable (2 IPv4, 2 IPv6) Mail: 4 servers Services: None
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 426 subdomains discovered
How did we find these?
CT logs unavailable 426 current 0 expired 3 CNAMEs Source: Certificate Transparency + DNS Intelligence
Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.
Subdomain Source Status Provider / CNAME Certificates First Seen Issuer(s)
a.href.cloudflare.com CT Log Current — 2 2026-02-10T19:59:42Z
abuse.cloudflare.com CT Log Current — 8 2026-02-09T08:49:11Z
access.cloudflare.com CT Log Current — 8 2026-01-27T02:30:51Z
accounts-devel.realtime.cloudflare.com CT Log Current — 2 2026-01-28T21:25:42Z
accounts.realtime.cloudflare.com CT Log Current — 4 2026-01-28T21:25:07Z
accounts2.realtime.cloudflare.com CT Log Current — 2 2026-01-28T21:43:58Z
admin-staging.registrar.cloudflare.com CT Log Current — 2 2026-02-01T15:30:55Z
admin.certifications.cloudflare.com CT Log Current — 2 2026-01-27T14:12:31Z
admin.registrar.cloudflare.com CT Log Current — 2 2026-02-01T15:46:27Z
admin.sqlite.cloudflare.com CT Log Current — 12 2026-02-02T02:37:14Z
advertisements.indexer-staging.ipfs.cloudflare.com CT Log Current — 2 2026-01-31T22:09:19Z
advertisements.indexer.ipfs.cloudflare.com CT Log Current — 2 2026-02-01T02:23:00Z
agents.cloudflare.com CT Log Current — 4 2026-02-07T09:12:04Z
agents.production.realtime.cloudflare.com CT Log Current — 4 2026-02-09T08:11:03Z
agents.realtime.cloudflare.com CT Log Current — 2 2026-02-17T14:25:02Z
agents.staging.realtime.cloudflare.com CT Log Current — 4 2026-02-12T11:23:51Z
ai-worker.dlp.teams.cloudflare.com CT Log Current — 4 2026-01-30T22:58:58Z
ai.cloudflare.com CT Log Current — 4 2026-02-09T07:46:22Z
aig.cloudflare.com CT Log Current — 8 2026-02-02T23:41:56Z
aim.cloudflare.com CT Log Current — 4 2026-01-26T23:30:12Z
ajax.cloudflare.com CT Log Current — 2 2025-07-22T20:46:24Z
akd-auditor.cloudflare.com CT Log Current — 4 2026-02-05T19:55:46Z
angular-examples.staging.realtime.cloudflare.com CT Log Current — 2 2026-02-09T13:17:22Z
api-devel.realtime.cloudflare.com CT Log Current — 2 2026-02-11T12:47:51Z
api-proxy.notebooks.cloudflare.com CT Log Current — 2 2026-02-16T14:12:30Z
api-silos-devel.realtime.cloudflare.com CT Log Current — 2 2026-02-14T11:04:43Z
api-silos.realtime.cloudflare.com CT Log Current — 2 2026-02-14T07:29:50Z
api-staging.notifications.cloudflare.com CT Log Current — 2 2026-02-11T01:57:59Z
api-staging.notifications.fed.cloudflare.com CT Log Current — 2 2026-02-07T08:49:05Z
api.cloudflare.com CT Log Current — 8 2026-02-05T00:34:17Z
api.notifications.cloudflare.com CT Log Current — 2 2026-02-11T02:09:47Z
api.notifications.fed.cloudflare.com CT Log Current — 2 2026-02-07T08:47:46Z
api.radar.staging.cloudflare.com CT Log Current — 2 2026-02-13T05:26:04Z
api.sqlite.cloudflare.com CT Log Current — 4 2026-02-12T10:51:29Z
api.staging.cloudflare.com CT Log Current — 4 2026-02-17T17:27:44Z
api.workers.cloudflare.com CT Log Current — 8 2026-01-26T04:13:16Z
api.workers.fed.cloudflare.com CT Log Current — 4 2026-01-30T21:02:29Z
api0.devel.realtime.cloudflare.com CT Log Current — 2 2026-02-11T12:26:37Z
api0.realtime.cloudflare.com CT Log Current — 2 2026-02-11T13:07:14Z
apjc-v2.labs.cloudflare.com CT Log Current — 2 2026-01-28T06:25:17Z
apjc.labs.cloudflare.com CT Log Current — 2 2026-01-28T01:33:16Z
apjc.v2.labs.cloudflare.com CT Log Current — 2 2026-01-28T03:40:47Z
app-relay.cloudflare.com CT Log Current — 8 2026-01-29T07:07:22Z
apple-carry-relay.cloudflare.com CT Log Current — 4 2026-02-01T18:44:14Z
apple-relay.cloudflare.com CT Log Current — 2 2026-02-05T16:23:02Z
apwest.labs.cloudflare.com CT Log Current — 2 2026-01-28T01:46:30Z
assets.autorag.ai.cloudflare.com CT Log Current — 2 2026-02-14T00:04:07Z
astriddb.labs.cloudflare.com CT Log Current — 2 2026-01-28T02:23:32Z
aueast.labs.cloudflare.com CT Log Current — 2 2026-01-28T01:37:54Z
auth.cloudflare.com DNS Current cloudflareauth.cloudflareaccess.com 4 2026-01-24 —
autorag.ai.cloudflare.com CT Log Current — 2 2026-02-04T13:41:30Z
aws-flow-logs-federal.cloudflare.com CT Log Current — 4 2026-01-30T22:02:33Z
aws-flow-logs.cloudflare.com CT Log Current — 4 2026-02-07T18:42:15Z
beta.gateway.agents.cloudflare.com CT Log Current — 2 2026-02-14T10:42:01Z
billing.support.cloudflare.com CT Log Current — 9 2025-09-10T16:53:45Z
bindings-staging.mcp.cloudflare.com CT Log Current — 2 2026-02-07T23:43:54Z
bindings.mcp.cloudflare.com CT Log Current — 2 2026-02-07T23:44:23Z
blocked.teams.cloudflare.com CT Log Current — 2 2026-02-10T14:58:00Z
blog-staging.cloudflare.com CT Log Current — 8 2026-01-28T00:00:00Z
blog.cloudflare.com DNS Current — 4 2026-01-24 —
bot-api.developers.cloudflare.com CT Log Current — 4 2026-02-11T07:21:07Z
cac.cloudflare.com CT Log Current — 8 2026-02-03T01:25:58Z
canary.one.dash.cloudflare.com CT Log Current — 2 2026-02-17T13:41:53Z
cdn.em2.cloudflare.com CT Log Current — 1 2025-06-02T00:00:00Z
cdn.labs.cloudflare.com CT Log Current — 7 2026-02-13T05:59:31Z
certifications.cloudflare.com CT Log Current — 4 2026-01-27T13:55:38Z
certvalidate-staging.cloudflare.com CT Log Current — 4 2026-02-10T23:15:43Z
certvalidate.cloudflare.com CT Log Current — 4 2026-02-14T20:58:24Z
ces.dlp.teams.cloudflare.com CT Log Current — 4 2026-02-09T11:42:19Z
challenge-api.teams.cloudflare.com CT Log Current — 2 2026-02-14T01:24:29Z
challenge.docs.cloudflare.com CT Log Current — 2 2026-02-13T22:45:42Z
challenges-staging.cloudflare.com CT Log Current — 4 2026-02-05T06:39:05Z
challenges.fed.cloudflare.com CT Log Current — 6 2026-01-26T09:32:22Z
client.sso.labs.cloudflare.com CT Log Current — 2 2026-01-28T02:18:49Z
cml-sso-proxy-orig.labs.cloudflare.com CT Log Current — 2 2026-01-28T06:38:39Z
cml-sso-proxy.labs.cloudflare.com CT Log Current — 2 2026-01-28T01:25:24Z
cms-api.labs.cloudflare.com CT Log Current — 2 2026-02-01T03:41:04Z
cms.labs.cloudflare.com CT Log Current — 2 2026-01-28T02:55:03Z
cms2.labs-staging.cloudflare.com CT Log Current — 2 2026-02-14T23:19:48Z
cobol.demos.cloudflare.com CT Log Current — 2 2026-02-04T15:32:38Z
community.cloudflare.com CT Log Current — 8 2026-01-27T16:18:01Z
containers-staging.mcp.cloudflare.com CT Log Current — 2 2026-02-13T22:58:07Z
containers.cloudflare.com CT Log Current — 6 2026-02-11T19:19:41Z
content.cloudflare.com DNS Current mkto-ab130037.com 4 2026-01-24 —
content.labs.cloudflare.com CT Log Current — 5 2026-01-28T01:28:14Z
content.v2.labs.cloudflare.com CT Log Current — 2 2026-01-28T01:49:46Z
cor-staging.registrar.cloudflare.com CT Log Current — 2 2026-01-30T10:23:04Z
cor.registrar.cloudflare.com CT Log Current — 2 2026-01-30T10:23:15Z
cp-testing.cloudflare.com CT Log Current — 4 2026-01-31T16:46:18Z
cp10.cloudflare.com CT Log Current — 1 2025-08-30T00:00:00Z
cp11.cloudflare.com CT Log Current — 8 2026-02-01T02:31:27Z
cp2.cloudflare.com CT Log Current — 2 2025-06-30T00:00:00Z
cp3.cloudflare.com CT Log Current — 1 2025-06-30T00:00:00Z
cp4.cloudflare.com CT Log Current — 5 2025-06-30T00:00:00Z
cp5.cloudflare.com CT Log Current — 2 2025-06-30T00:00:00Z
cp6.cloudflare.com CT Log Current — 3 2025-06-30T00:00:00Z
cp7.cloudflare.com CT Log Current — 1 2025-06-18T00:00:00Z
cp8-staging.cloudflare.com CT Log Current — 2 2026-02-09T02:00:33Z
cp9.cloudflare.com CT Log Current — 3 2025-12-09T17:10:22Z
crl.cloudflare.com DNS Current — 4 2026-01-24 —
croissant.pat-issuer.cloudflare.com CT Log Current — 4 2026-01-31T09:05:53Z
csp-reporting.cloudflare.com CT Log Current — 8 2026-01-25T00:00:00Z
custom-inside-tunnel.h3.speed.cloudflare.com CT Log Current — 4 2026-02-14T04:34:19Z
custom-outside-tunnel.h3.speed.cloudflare.com CT Log Current — 4 2026-02-14T11:42:37Z
custom-t0.speed.cloudflare.com CT Log Current — 8 2026-02-15T00:30:43Z
custom-t1.speed.cloudflare.com CT Log Current — 4 2026-02-15T07:48:39Z
custom-t2.speed.cloudflare.com CT Log Current — 8 2026-02-15T13:53:49Z
custom-t3.speed.cloudflare.com CT Log Current — 4 2026-02-15T09:13:34Z
custom-t4.speed.cloudflare.com CT Log Current — 4 2026-02-15T00:20:09Z
cv2-logprovider.research.cloudflare.com CT Log Current — 4 2026-02-16T16:44:57Z
dap.cloudflare.com CT Log Current — 4 2026-02-08T23:31:39Z
dash.cloudflare.com CT Log Current — 12 2026-02-04T22:09:35Z
dash.key-transparency.cloudflare.com CT Log Current — 2 2026-02-14T01:51:14Z
dash.staging.cloudflare.com CT Log Current — 2 2026-02-08T02:17:02Z
data.em2.cloudflare.com CT Log Current — 4 2025-06-27T00:00:00Z
datasets.research.cloudflare.com CT Log Current — 5 2026-02-03T23:59:10Z
davos.cloudflare.com CT Log Current — 4 2026-02-13T00:00:00Z
db-migrator.staging.realtime.cloudflare.com CT Log Current — 2 2026-02-12T05:13:10Z
dbs-in-dbs.sqlite.cloudflare.com CT Log Current — 2 2026-02-14T08:14:08Z
default-page.registrar.cloudflare.com CT Log Current — 2 2026-02-09T16:49:28Z
demo-api.labs-staging.cloudflare.com CT Log Current — 4 2026-01-26T01:42:08Z
demo-api.labs.cloudflare.com CT Log Current — 4 2026-01-27T20:10:14Z
demo-app-dyte-realtime-migration.realtime.cloudflare.com CT Log Current — 2 2026-02-16T17:29:01Z
demo-devel.realtime.cloudflare.com CT Log Current — 6 2026-01-25T08:56:40Z
demo-pat.issuer.cloudflare.com CT Log Current — 4 2026-02-14T23:51:31Z
demo-pat.research.cloudflare.com CT Log Current — 2 2026-01-26T11:09:32Z
demo-preprod.realtime.cloudflare.com CT Log Current — 3 2026-01-28T06:53:34Z
demo.devel.realtime.cloudflare.com CT Log Current — 2 2026-02-17T10:55:52Z
demo.realtime.cloudflare.com CT Log Current — 4 2026-01-29T12:09:24Z
demos.cloudflare.com CT Log Current — 4 2026-01-29T04:01:48Z
dev-devel.realtime.cloudflare.com CT Log Current — 2 2026-01-28T22:20:07Z
dev.ai-worker.dlp.teams.cloudflare.com CT Log Current — 2 2026-01-30T22:58:58Z
dev.akd-auditor.cloudflare.com CT Log Current — 4 2026-02-09T21:02:36Z
dev.dash.staging.cloudflare.com CT Log Current — 4 2026-01-28T23:15:23Z
dev.demo-pat.issuer.cloudflare.com CT Log Current — 4 2026-02-14T23:51:31Z
dev.realtime.cloudflare.com CT Log Current — 2 2026-01-28T21:57:57Z
dev.scan.dlp.teams.cloudflare.com CT Log Current — 2 2026-02-14T16:39:19Z
dev.validation-worker.dlp.teams.cloudflare.com CT Log Current — 2 2026-01-31T01:27:12Z
devel-demo.realtime.cloudflare.com CT Log Current — 2 2026-02-17T10:44:54Z
devel.demo.realtime.cloudflare.com CT Log Current — 4 2026-02-17T10:42:02Z
developer.cloudflare.com CT Log Current — 2 2026-02-15T10:44:18Z
developers.cloudflare.com CT Log Current — 8 2026-01-25T22:54:07Z
dex.cloudflare.com CT Log Current — 4 2026-02-17T00:00:00Z
dns.cloudflare.com CT Log Current — 4 2026-02-08T14:17:37Z
dns2.cloudflare.com DNS Current — 4 2026-01-24 —
docs-vectorize-staging.mcp.cloudflare.com CT Log Current — 4 2026-01-30T17:55:07Z
docs-vectorize.mcp.cloudflare.com CT Log Current — 2 2026-01-30T17:53:45Z
docs.cloudflare.com CT Log Current — 20 2026-01-29T11:12:28Z
docs.mcp.cloudflare.com CT Log Current — 4 2026-01-30T18:08:47Z
docs.realtime.cloudflare.com CT Log Current — 2 2026-02-04T14:17:04Z
docshare.plugins.realtime.cloudflare.com CT Log Current — 2 2026-02-11T13:21:41Z
domains.cloudflare.com CT Log Current — 4 2026-02-15T01:33:57Z
edge-staging.admin.sqlite.cloudflare.com CT Log Current — 2 2026-02-08T16:26:48Z
edge.admin.sqlite.cloudflare.com CT Log Current — 2 2026-02-08T16:27:31Z
editor-staging.cloudflare.com CT Log Current — 4 2026-01-31T02:56:03Z
editor.cloudflare.com CT Log Current — 4 2026-01-31T02:55:09Z
email.cloudflare.com DNS Current — 4 2026-01-24 —
es.cloudflare.com DNS Current — 4 2026-01-24 —
escalations.discord.cloudflare.com CT Log Current — 6 2026-02-10T12:40:05Z
ethereum.cloudflare.com CT Log Current — 8 2026-01-25T00:00:00Z
eunorth.labs-staging.cloudflare.com CT Log Current — 2 2026-02-17T08:19:17Z
eunorth.labs.cloudflare.com CT Log Current — 2 2026-02-17T07:25:50Z
euwest.labs.cloudflare.com CT Log Current — 2 2026-01-27T20:51:42Z
events.cloudflare.com CT Log Current — 8 2026-02-14T20:56:32Z
events.www.cloudflare.com CT Log Current — 1 2026-02-16T15:50:07Z
examples.notebooks.cloudflare.com CT Log Current — 2 2026-02-03T23:11:23Z
examples.staging.realtime.cloudflare.com CT Log Current — 2 2026-02-09T13:16:33Z
feedback.docs.cloudflare.com CT Log Current — 2 2026-02-12T19:39:09Z
fieldmarketing.www.cloudflare.com CT Log Current — 1 2026-02-16T15:13:52Z
firebolt.realtime.cloudflare.com CT Log Current — 2 2026-02-15T06:56:22Z
fonts.static.dash.cloudflare.com CT Log Current — 2 2026-01-26T15:20:34Z
fortran.demos.cloudflare.com CT Log Current — 4 2026-02-01T12:18:59Z
fpw-staging.gateway.agents.cloudflare.com CT Log Current — 2 2026-02-11T09:45:06Z
gates.cloudflare.com CT Log Current — 4 2026-02-09T00:00:00Z
gateway-beta.ai.cloudflare.com CT Log Current — 6 2026-02-02T00:00:00Z
gateway-control.cloudflare.com CT Log Current — 8 2026-01-28T00:00:00Z
gateway-privacy.cloudflare.com CT Log Current — 4 2026-01-29T17:53:09Z
gateway.agents.cloudflare.com CT Log Current — 16 2026-02-03T12:36:34Z
gateway.ai.cloudflare.com CT Log Current — 14 2026-01-26T04:57:09Z
gateway.api.staging.cloudflare.com CT Log Current — 2 2026-02-17T16:41:04Z
geoglyph.cloudflare.com CT Log Current — 4 2026-02-08T00:00:00Z
gh-code.developers.cloudflare.com CT Log Current — 4 2026-02-16T11:42:31Z
goldilocks-ent.research.cloudflare.com CT Log Current — 8 2026-02-09T00:00:00Z
goldilocks-free.research.cloudflare.com CT Log Current — 2 2026-02-13T00:02:26Z
goldilocks-pro.research.cloudflare.com CT Log Current — 4 2026-02-13T00:58:30Z
grafana.cloudflare.com DNS Current — 4 2026-01-24 —
graphql.cloudflare.com CT Log Current — 6 2026-02-10T22:49:18Z
h3.production.speed.cloudflare.com CT Log Current — 4 2026-02-04T15:49:29Z
h3.staging.speed.cloudflare.com CT Log Current — 8 2026-01-29T18:29:13Z
help.one.cloudflare.com CT Log Current — 2 2026-01-27T20:28:26Z
href.cloudflare.com CT Log Current — 6 2026-02-08T00:00:00Z
html-examples.staging.realtime.cloudflare.com CT Log Current — 2 2026-02-09T13:19:03Z
http-message-signatures-example.research.cloudflare.com CT Log Current — 2 2026-01-29T09:57:45Z
icons.realtime.cloudflare.com CT Log Current — 2 2026-02-10T10:57:13Z
id.cloudflare.com DNS Current — 4 2026-01-24 —
idp-rag.labs.cloudflare.com CT Log Current — 2 2026-01-28T02:29:22Z
idp.labs.cloudflare.com CT Log Current — 2 2026-01-28T01:48:26Z
images.mcp.cloudflare.com CT Log Current — 2 2026-02-13T03:07:37Z
inserter.risk-score.teams.cloudflare.com CT Log Current — 4 2026-02-16T20:44:54Z
instant-logs.logs.fed.cloudflare.com CT Log Current — 4 2026-02-03T02:17:39Z
intel.cloudflare.com CT Log Current — 2 2026-01-29T00:00:00Z
invalid.rpki.cloudflare.com CT Log Current — 8 2026-01-26T14:02:43Z
investors.cloudflare.com CT Log Current — 4 2026-01-27T10:11:55Z
ip-check-perf.radar.cloudflare.com CT Log Current — 2 2026-02-13T02:14:47Z
ip-check-perf.radar.staging.cloudflare.com CT Log Current — 4 2026-02-13T13:21:50Z
ipv4-check-perf.radar.cloudflare.com CT Log Current — 2 2026-02-10T18:25:59Z
ipv4-check-perf.radar.staging.cloudflare.com CT Log Current — 2 2026-02-11T20:26:42Z
ipv6-check-perf.radar.cloudflare.com CT Log Current — 2 2026-02-13T15:55:25Z
ipv6-check-perf.radar.staging.cloudflare.com CT Log Current — 2 2026-02-10T18:24:02Z
isp-staging.cloudflare.com CT Log Current — 10 2026-01-27T00:00:00Z
isp.cloudflare.com CT Log Current — 6 2026-02-17T01:33:50Z
it.cloudflare.com DNS Current — 4 2026-01-24 —
key-transparency.cloudflare.com CT Log Current — 8 2026-01-29T20:37:00Z
keyword-tracker.docs.cloudflare.com CT Log Current — 2 2026-02-12T16:12:38Z
labs-staging.cloudflare.com CT Log Current — 2 2026-01-26T01:42:08Z
labs.cloudflare.com CT Log Current — 12 2026-01-27T20:10:14Z
leader.prio.research.cloudflare.com CT Log Current — 4 2026-01-31T17:32:48Z
learn.cloudflare.com CT Log Current — 6 2026-02-14T18:42:47Z
linkdefender.cloudflare.com CT Log Current — 6 2026-02-01T08:09:30Z
linux.cloudflare.com CT Log Current — 4 2026-02-12T20:17:34Z
live.cloudflare.com CT Log Current — 8 2026-01-26T01:02:05Z
live.staging.cloudflare.com CT Log Current — 2 2026-02-02T00:00:00Z
location-devel.realtime.cloudflare.com CT Log Current — 2 2026-01-27T10:43:15Z
location.realtime.cloudflare.com CT Log Current — 2 2026-01-27T10:14:25Z
logs.cloudflare.com CT Log Current — 4 2026-02-17T00:00:00Z
logs.fed.cloudflare.com CT Log Current — 4 2026-02-03T02:17:39Z
mail.cloudflare.com CT Log Current — 4 2026-02-11T22:27:43Z
maps.cac.cloudflare.com CT Log Current — 2 2026-02-03T16:50:25Z
maps.staging.cac.cloudflare.com CT Log Current — 2 2026-02-03T05:53:01Z
masque-relay.cloudflare.com CT Log Current — 1 2025-11-13T17:02:22Z
mcp.cloudflare.com CT Log Current — 36 2026-01-30T17:53:45Z
mcp.developers.cloudflare.com CT Log Current — 4 2026-02-17T17:17:10Z
media-hub-devel.realtime.cloudflare.com CT Log Current — 2 2026-02-07T11:25:08Z
media-hub-preprod.realtime.cloudflare.com CT Log Current — 2 2026-02-07T11:57:09Z
media-hub-production.realtime.cloudflare.com CT Log Current — 2 2026-02-07T11:26:13Z
media-hub.realtime.cloudflare.com CT Log Current — 2 2026-02-14T09:39:39Z
media.labs.cloudflare.com CT Log Current — 2 2026-01-28T01:50:40Z
meta.hpke-keys.privacy-gateway.cloudflare.com CT Log Current — 6 2026-02-11T17:03:44Z
middlecache-housekeeping.developer.cloudflare.com CT Log Current — 2 2026-02-15T10:44:18Z
migp.cloudflare.com CT Log Current — 4 2026-02-17T00:00:00Z
nel.cloudflare.com CT Log Current — 4 2026-02-03T20:03:52Z
netdollar.cloudflare.com CT Log Current — 4 2026-01-25T06:13:37Z
notebooks.cloudflare.com CT Log Current — 9 2026-02-14T01:40:06Z
notifications.cloudflare.com CT Log Current — 4 2026-02-11T01:57:59Z
notifications.dash.staging.cloudflare.com CT Log Current — 4 2026-02-04T00:57:07Z
notifications.fed.cloudflare.com CT Log Current — 4 2026-02-07T08:47:46Z
notify.cloudflare.com DNS Current — 4 2026-01-24 —
ns.cloudflare.com DNS Current — 4 2026-01-24 —
ns1.cloudflare.com DNS Current — 4 2026-01-24 —
ns2.cloudflare.com DNS Current — 4 2026-01-24 —
ns3.cloudflare.com DNS Current — 4 2026-01-24 —
ns4.cloudflare.com DNS Current — 4 2026-01-24 —
ns5.cloudflare.com DNS Current — 4 2026-01-24 —
ns6.cloudflare.com DNS Current — 4 2026-01-24 —
oai-gateway.cloudflare.com CT Log Current — 5 2025-06-11T00:00:00Z
oauth.pipelines-staging.cloudflare.com CT Log Current — 2 2026-01-28T23:58:42Z
objects.research.cloudflare.com CT Log Current — 2 2026-02-02T01:57:11Z
oblivious-gateway.privacy-gateway.cloudflare.com CT Log Current — 1 2025-06-11T00:00:00Z
observability-staging.cloudflare.com CT Log Current — 4 2026-01-29T19:46:32Z
observability-staging.mcp.cloudflare.com CT Log Current — 2 2026-02-07T23:14:09Z
observability.cloudflare.com CT Log Current — 8 2026-01-28T17:43:00Z
observability.fed.cloudflare.com CT Log Current — 2 2026-01-30T19:47:28Z
observability.mcp.cloudflare.com CT Log Current — 2 2026-02-07T23:44:10Z
ocsp.cloudflare.com DNS Current — 4 2026-01-24 —
ohttp-issuer-staging.cloudflare.com CT Log Current — 4 2026-02-14T13:43:14Z
ohttp-issuer.cloudflare.com CT Log Current — 4 2026-02-14T17:40:10Z
onboarding-guide-staging.dash.staging.cloudflare.com CT Log Current — 2 2026-02-03T08:43:56Z
one.cloudflare.com CT Log Current — 6 2026-01-27T20:28:26Z
one.dash.cloudflare.com CT Log Current — 8 2026-01-31T08:25:43Z
one.dash.fed.cloudflare.com CT Log Current — 2 2026-01-31T17:30:21Z
one.dash.staging.cloudflare.com CT Log Current — 8 2026-01-31T18:54:00Z
pages.cloudflare.com CT Log Current — 8 2026-01-27T09:08:18Z
parking-staging.registrar.cloudflare.com CT Log Current — 2 2026-02-02T11:21:00Z
parking.registrar.cloudflare.com CT Log Current — 2 2026-02-02T10:56:40Z
partnerdemandcenter.cloudflare.com CT Log Current — 4 2026-01-29T17:08:07Z
partners.cloudflare.com DNS Current — 4 2026-01-24 —
partnertest.cloudflare.com CT Log Current — 10 2026-01-27T00:00:00Z
pdw.dlp.teams.cloudflare.com CT Log Current — 12 2026-01-30T00:00:00Z
peering.cloudflare.com CT Log Current — 8 2026-01-28T00:00:00Z
pepe-debug.research.cloudflare.com CT Log Current — 3 2026-02-13T20:09:15Z
performance.radar.cloudflare.com CT Log Current — 2 2026-02-10T21:44:56Z
performance.radar.staging.cloudflare.com CT Log Current — 4 2026-02-15T05:47:46Z
phishfilet.cloudflare.com CT Log Current — 2 2026-02-10T18:26:17Z
phishnet.fed.cloudflare.com CT Log Current — 6 2026-01-26T13:32:17Z
pipelines-staging.cloudflare.com CT Log Current — 2 2026-01-28T23:58:42Z
pipelines.cloudflare.com CT Log Current — 4 2026-02-13T00:00:00Z
pkg-beta.try.cloudflare.com CT Log Current — 2 2026-02-10T18:23:46Z
platform.dash.staging.cloudflare.com CT Log Current — 4 2026-02-08T18:28:51Z
platform.dash.staging.fed.cloudflare.com CT Log Current — 4 2026-02-12T15:33:25Z
playground.platform.dash.cloudflare.com CT Log Current — 10 2026-01-31T19:41:14Z
plexi-dev.key-transparency.cloudflare.com CT Log Current — 4 2026-02-17T00:00:00Z
plexi.key-transparency.cloudflare.com CT Log Current — 4 2026-02-13T08:16:25Z
polygon.cloudflare.com CT Log Current — 4 2026-01-25T12:30:51Z
pp-attester-google-account-dev.research.cloudflare.com CT Log Current — 2 2026-02-10T19:42:22Z
pp-attester-turnstile-dev.research.cloudflare.com CT Log Current — 2 2026-02-13T06:58:05Z
pp-attester-turnstile.research.cloudflare.com CT Log Current — 4 2026-02-12T17:17:18Z
pp-issuer-dev.research.cloudflare.com CT Log Current — 4 2026-02-13T04:37:33Z
pp-issuer-production.research.cloudflare.com CT Log Current — 2 2026-02-12T01:39:45Z
pp-issuer-public.research.cloudflare.com CT Log Current — 2 2026-02-15T04:43:01Z
pp-origin-dev.research.cloudflare.com CT Log Current — 2 2026-02-11T02:11:31Z
preview.developers.cloudflare.com CT Log Current — 2 2026-01-27T10:53:40Z
preview.docs.cloudflare.com CT Log Current — 2 2026-02-04T14:13:44Z
privacy-auditability.cloudflare.com CT Log Current — 4 2026-02-14T03:07:58Z
privacy-relay.cloudflare.com CT Log Current — 4 2026-02-15T21:02:47Z
production.ai-worker.dlp.teams.cloudflare.com CT Log Current — 2 2026-02-01T20:14:27Z
production.pdw.dlp.teams.cloudflare.com CT Log Current — 4 2026-02-13T11:38:55Z
production.speed.cloudflare.com CT Log Current — 10 2026-02-04T15:05:44Z
profile.platform.dash.cloudflare.com CT Log Current — 6 2026-02-14T00:45:34Z
public-pat.issuer.cloudflare.com CT Log Current — 4 2026-02-03T00:00:00Z
public.labs.cloudflare.com CT Log Current — 2 2026-02-03T06:46:58Z
r2-calculator.cloudflare.com CT Log Current — 7 2026-02-10T01:43:33Z
r2-staging.rpki.cloudflare.com CT Log Current — 2 2026-02-13T01:42:51Z
r2.labs.cloudflare.com CT Log Current — 2 2026-01-28T01:11:34Z
radar-staging.mcp.cloudflare.com CT Log Current — 2 2026-02-13T15:19:59Z
radar.cloudflare.com CT Log Current — 14 2026-01-29T14:34:38Z
radar.mcp.cloudflare.com CT Log Current — 2 2026-02-13T14:41:09Z
radar.staging.cloudflare.com CT Log Current — 18 2026-01-30T00:00:00Z
raio2025h2b.ct.cloudflare.com CT Log Current — 2 2026-01-29T23:47:09Z
rdap-staging.registrar.cloudflare.com CT Log Current — 2 2026-02-09T15:22:28Z
rdap.registrar.cloudflare.com CT Log Current — 2 2026-02-09T14:59:30Z
react-examples.staging.realtime.cloudflare.com CT Log Current — 2 2026-02-09T13:16:58Z
react-samples.realtime.cloudflare.com CT Log Current — 2 2026-02-03T13:36:31Z
realtime.cloudflare.com CT Log Current — 100 2026-01-25T08:56:40Z
registrar.cloudflare.com CT Log Current — 4 2026-02-07T16:41:14Z
registry.cloudflare.com CT Log Current — 4 2026-02-05T22:16:04Z
research.cloudflare.com CT Log Current — 40 2026-01-26T11:09:32Z
roughtime.cloudflare.com CT Log Current — 4 2026-02-14T00:00:00Z
rpki.cloudflare.com CT Log Current — 4 2026-01-25T09:57:43Z
rtk-devel.realtime.cloudflare.com CT Log Current — 2 2026-02-15T10:42:48Z
rtk-preset.realtime.cloudflare.com CT Log Current — 2 2026-02-05T09:07:05Z
rtk-staging.realtime.cloudflare.com CT Log Current — 2 2026-02-14T06:45:43Z
rtk.realtime.cloudflare.com CT Log Current — 2 2026-02-14T06:44:06Z
run.ai.cloudflare.com CT Log Current — 4 2026-01-25T08:33:31Z
rustpad-backend.plugins.realtime.cloudflare.com CT Log Current — 2 2026-02-11T10:24:13Z
rustpad.plugins.realtime.cloudflare.com CT Log Current — 2 2026-02-11T10:38:25Z
saml-auto.labs.cloudflare.com CT Log Current — 2 2026-01-28T08:48:48Z
saml-sso-auto.labs.cloudflare.com CT Log Current — 2 2026-01-28T01:10:20Z
sandbox.cloudflare.com CT Log Current — 10 2026-02-10T16:08:38Z
sandboxes.cloudflare.com CT Log Current — 8 2026-02-10T18:54:15Z
sat-dev.pat-issuer.cloudflare.com CT Log Current — 4 2026-02-13T00:00:00Z
scan.dlp.teams.cloudflare.com CT Log Current — 12 2026-02-13T23:04:17Z
scm.editor-staging.cloudflare.com CT Log Current — 2 2026-01-31T02:56:03Z
scm.editor.cloudflare.com CT Log Current — 2 2026-01-31T02:55:09Z
select-config.cloudflare.com CT Log Current — 4 2026-01-27T12:35:47Z
sieve.demos.cloudflare.com CT Log Current — 2 2026-02-07T21:15:51Z
sink.dlp.teams.cloudflare.com CT Log Current — 4 2026-02-11T02:15:57Z
sl.cloudflare.com CT Log Current — 1 2026-02-12T00:14:24Z
slide.cloudflare.com CT Log Current — 10 2026-02-16T15:38:27Z
socket-devel.realtime.cloudflare.com CT Log Current — 2 2026-01-28T12:28:12Z
socket-edge-devel.realtime.cloudflare.com CT Log Current — 2 2026-02-07T12:26:49Z
socket-edge.realtime.cloudflare.com CT Log Current — 2 2026-02-07T12:11:22Z
socket-edge.staging.realtime.cloudflare.com CT Log Current — 1 2025-07-11T00:00:00Z
socket-hub-workers.realtime.cloudflare.com CT Log Current — 2 2026-01-30T09:55:20Z
socket-hub-workers.staging.realtime.cloudflare.com CT Log Current — 2 2026-01-30T09:05:25Z
socket-preprod.realtime.cloudflare.com CT Log Current — 2 2026-01-31T04:40:20Z
socket.realtime.cloudflare.com CT Log Current — 2 2026-01-31T04:40:43Z
speed.cloudflare.com CT Log Current — 8 2026-01-29T00:00:00Z
sqlite.cloudflare.com CT Log Current — 14 2026-01-25T09:16:54Z
ssf.risk-score.teams.cloudflare.com CT Log Current — 8 2026-02-11T01:57:56Z
sso-auto.labs.cloudflare.com CT Log Current — 2 2026-01-28T05:40:06Z
sso-proxy.labs.cloudflare.com CT Log Current — 2 2026-01-28T01:27:54Z
staging-dash.key-transparency.cloudflare.com CT Log Current — 2 2026-02-13T04:06:30Z
staging.abuse.cloudflare.com CT Log Current — 7 2026-02-02T16:12:37Z
staging.akd-auditor.cloudflare.com CT Log Current — 4 2026-02-10T13:27:28Z
staging.api.sqlite.cloudflare.com CT Log Current — 4 2026-02-12T05:11:38Z
staging.billing.support.cloudflare.com CT Log Current — 1 2026-02-01T20:25:49Z
staging.cac.cloudflare.com CT Log Current — 8 2026-02-03T06:57:25Z
staging.cloudflare.com DNS Current — 4 2026-01-24 —
staging.community.cloudflare.com CT Log Current — 1 2026-02-13T00:01:42Z
staging.cp3.cloudflare.com CT Log Current — 1 2025-06-03T00:00:00Z
staging.cp7.cloudflare.com CT Log Current — 1 2025-06-18T00:00:00Z
staging.developers.cloudflare.com CT Log Current — 4 2026-01-25T22:54:07Z
staging.dex.cloudflare.com CT Log Current — 4 2026-02-02T21:57:15Z
staging.ethereum.cloudflare.com CT Log Current — 8 2026-02-16T04:31:07Z
staging.mail.cloudflare.com CT Log Current — 2 2026-02-14T11:27:41Z
staging.mcp.cloudflare.com CT Log Current — 2 2026-02-10T16:27:21Z
staging.oai-gateway.cloudflare.com CT Log Current — 1 2025-06-11T00:00:00Z
staging.oblivious-gateway.privacy-gateway.cloudflare.com CT Log Current — 1 2025-06-11T00:00:00Z
staging.pdw.dlp.teams.cloudflare.com CT Log Current — 2 2026-02-13T03:56:06Z
staging.realtime.cloudflare.com CT Log Current — 20 2026-01-30T09:05:25Z
staging.sink.dlp.teams.cloudflare.com CT Log Current — 2 2026-02-11T02:15:57Z
staging.sparrow.cloudflare.com CT Log Current — 4 2026-02-06T00:00:00Z
staging.speed.cloudflare.com CT Log Current — 6 2026-01-27T18:54:42Z
staging.ssf.risk-score.teams.cloudflare.com CT Log Current — 2 2026-02-11T01:57:56Z
staging.support.cloudflare.com CT Log Current — 8 2026-02-13T05:16:10Z
staging.time.cloudflare.com CT Log Current — 1 2026-02-17T21:31:50Z
static-canary.dash.staging.cloudflare.com CT Log Current — 8 2026-01-25T00:00:00Z
static.dash.cloudflare.com CT Log Current — 4 2026-02-17T07:14:34Z
static.integrations.cloudflare.com CT Log Current — 2 2026-02-13T06:11:09Z
stg.mail.cloudflare.com CT Log Current — 2 2026-02-13T02:22:57Z
stream.cloudflare.com CT Log Current — 4 2026-01-29T00:00:00Z
streamer.plugins.realtime.cloudflare.com CT Log Current — 2 2026-02-11T14:01:50Z
support.cloudflare.com CT Log Current — 8 2026-01-30T13:12:42Z
teams.cloudflare.com CT Log Current — 4 2026-02-10T14:58:00Z
tech-summit.labs.cloudflare.com CT Log Current — 4 2026-01-29T23:25:19Z
terrasoup.labs.cloudflare.com CT Log Current — 2 2026-01-28T01:33:06Z
test-devel.realtime.cloudflare.com CT Log Current — 2 2026-02-14T05:26:01Z
test.phishnet.fed.cloudflare.com CT Log Current — 4 2026-01-26T13:34:51Z
test.realtime.cloudflare.com CT Log Current — 2 2026-02-12T05:38:05Z
time.cloudflare.com CT Log Current — 1 2026-02-17T21:30:57Z
tools.radar.cloudflare.com CT Log Current — 2 2026-01-29T14:34:38Z
trace.dash.staging.cloudflare.com CT Log Current — 8 2026-01-26T13:58:27Z
trampoline-staging.registrar.cloudflare.com CT Log Current — 2 2026-02-13T12:04:23Z
trampoline.registrar.cloudflare.com CT Log Current — 2 2026-02-07T16:41:14Z
try.cloudflare.com CT Log Current — 2 2026-02-10T18:23:46Z
turn.cloudflare.com CT Log Current — 4 2026-01-29T08:19:41Z
uat2.support.cloudflare.com CT Log Current — 8 2026-01-27T23:41:51Z
universal-gateway.ipfs.cloudflare.com CT Log Current — 10 2026-01-26T23:29:46Z
upload.cdn.labs.cloudflare.com CT Log Current — 4 2026-02-13T17:03:43Z
uscentral.labs.cloudflare.com CT Log Current — 2 2026-01-28T02:19:32Z
uswest.labs.cloudflare.com CT Log Current — 2 2026-01-28T01:32:37Z
validation-worker.dlp.teams.cloudflare.com CT Log Current — 2 2026-01-31T01:27:12Z
video-uploader.labs.cloudflare.com CT Log Current — 4 2026-02-13T03:53:21Z
vpc.aws-flow-logs-federal.cloudflare.com CT Log Current — 2 2026-01-30T22:04:58Z
vpc.staging.aws-flow-logs-federal.cloudflare.com CT Log Current — 2 2026-01-30T22:02:33Z
webhook-dispatch-prod.realtime.cloudflare.com CT Log Current — 2 2026-02-15T10:14:04Z
webhook-dispatch.realtime.cloudflare.com CT Log Current — 2 2026-02-14T09:58:38Z
whiteboard.plugins.realtime.cloudflare.com CT Log Current — 2 2026-02-11T10:24:16Z
whois.cloudflare.com DNS Current rdap.pacloudflare.com 4 2026-01-24 —
worker.staging.sparrow.cloudflare.com CT Log Current — 4 2026-01-25T01:29:37Z
wrangler-tail.observability.fed.cloudflare.com CT Log Current — 2 2026-01-30T19:47:28Z
www.ajax.cloudflare.com CT Log Current — 2 2025-07-22T20:46:24Z
www.cloudflare.com DNS Current — 4 2026-01-24 —
www.masque-relay.cloudflare.com CT Log Current — 1 2025-11-13T17:02:22Z
www.staging.time.cloudflare.com CT Log Current — 1 2026-02-17T21:31:50Z
www.time.cloudflare.com CT Log Current — 1 2026-02-17T21:30:57Z
Export Recon (CSV)
Δ No Propagation Issues: All DNS records are synchronized between resolver and authoritative nameserver.
DNS Intelligence What does DNS look like right now — and what changed over time?
DNS Evidence Diff Side-by-side comparison
Resolver Records (Public DNS cache)
Authoritative Records (Source of truth)
A Synchronized 2 / 2 records
104.16.132.229
104.16.132.229
104.16.133.229
104.16.133.229
AAAA Synchronized 2 / 2 records
2606:4700::6810:84e5
2606:4700::6810:84e5
2606:4700::6810:85e5
2606:4700::6810:85e5
CAA RFC 8659 §4 Synchronized 11 / 11 records
0 issuewild "pki.goog; cansignhttpexchanges=yes"
0 iodef "mailto:tls-abuse@cloudflare.com"
0 issue "digicert.com; cansignhttpexchanges=yes"
0 issue "comodoca.com"
0 issue "comodoca.com"
0 issue "digicert.com; cansignhttpexchanges=yes"
0 issuewild "digicert.com; cansignhttpexchanges=yes"
0 issue "letsencrypt.org"
0 issue "pki.goog; cansignhttpexchanges=yes"
0 issue "pki.goog; cansignhttpexchanges=yes"
0 issuewild "comodoca.com"
0 issue "ssl.com"
0 issuewild "letsencrypt.org"
0 issuewild "comodoca.com"
0 issuewild "ssl.com"
0 issuewild "digicert.com; cansignhttpexchanges=yes"
0 iodef "mailto:tls-abuse@cloudflare.com"
0 issuewild "letsencrypt.org"
0 issue "ssl.com"
0 issuewild "pki.goog; cansignhttpexchanges=yes"
0 issue "letsencrypt.org"
0 issuewild "ssl.com"
DMARC _dmarc.cloudflare.com RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1; p=reject; pct=100; rua=mailto:rua@cloudflare.com,mailto:cloudflare@dmarc.area1reports.com; ruf=mailto:cloudflare@dmarc.area1reports.com
v=DMARC1; p=reject; pct=100; rua=mailto:rua@cloudflare.com,mailto:cloudflare@dmarc.area1reports.com; ruf=mailto:cloudflare@dmarc.area1reports.com
MX RFC 5321 Synchronized 4 / 4 records
10 mxa.global.inbound.cf-emailsecurity.net.
10 mxa.global.inbound.cf-emailsecurity.net.
10 mxb.global.inbound.cf-emailsecurity.net.
10 mxb.global.inbound.cf-emailsecurity.net.
5 mxa-canary.global.inbound.cf-emailsecurity.net.
5 mxa-canary.global.inbound.cf-emailsecurity.net.
5 mxb-canary.global.inbound.cf-emailsecurity.net.
5 mxb-canary.global.inbound.cf-emailsecurity.net.
NS RFC 1035 Synchronized 5 / 5 records
ns3.cloudflare.com.
ns3.cloudflare.com.
ns4.cloudflare.com.
ns4.cloudflare.com.
ns5.cloudflare.com.
ns5.cloudflare.com.
ns6.cloudflare.com.
ns6.cloudflare.com.
ns7.cloudflare.com.
ns7.cloudflare.com.
SOA RFC 1035 Synchronized 1 / 1 records
ns3.cloudflare.com. dns.cloudflare.com. 2401983296 10000 2400 604800 300
ns3.cloudflare.com. dns.cloudflare.com. 2401983296 10000 2400 604800 300
TXT RFC 7208 §4 25 / 0 records
MS=ms70274184
—
ZOOM_verify_7LFBvOO9SIigypFG2xRlMA
—
_neqmkgaq1lq9it5s8qmetrhbnu121wb
—
_saml-domain-challenge.2dc00405-79cd-457b-b288-a119c6f0c7b7.71996d53-d178-4ba9-bef4-7f7e46edab74.cloudflare.com=1c8736fd-84b2-4197-985f-3fb2852f2457
—
_wkjc0fot0d7qrvrdt78bxkj2e2o67d2
—
apple-domain-verification=DNnWJoArJobFJKhJ
—
asv=894f6d1f9f83bcf44e4b1bc40bc1c4aa
—
atlassian-domain-verification=WxxKyN9aLnjEsoOjUYI6T0bb5vcqmKzaIkC9Rx2QkNb751G3LL/cus8/ZDOgh8xB
—
canva-site-verification=oOyaVnHC-OiFoR1BPvetNA
—
cisco-ci-domain-verification=27e926884619804ef987ae4aa1c4168f6b152ada84f4c8bfc74eb2bd2912ad72
—
creatopy-domain-verification=97d2ca50-9b6f-4a21-9bdb-fbb630e4cec7
—
docker-verification=c578e21c-34fb-4474-9b90-d55ee4cba10c
—
drift-domain-verification=f037808a26ae8b25bc13b1f1f2b4c3e0f78c03e67f24cefdd4ec520efa8e719f
—
facebook-domain-verification=h9mm6zopj6p2po54woa16m5bskm6oo
—
google-site-verification=C7thfNeXVahkVhniiqTI1iSVnElKR_kBBtnEHkeGDlo
—
google-site-verification=ZdlQZLBBAPkxeFTCM1rpiB_ibtGff_JF5KllNKwDR9I
—
liveramp-site-verification=EhH1MqgwbndTWl1AN64hOTKz7hc1s80yUpchLbgpfY0
—
logmein-verification-code=b3433c86-3823-4808-8a7e-58042469f654
—
miro-verification=bdd7dfa0a49adfb43ad6ddfaf797633246c07356
—
onetrust-domain-verification=bd5cd08a1e9644799fdb98ed7d60c9cb
—
status-page-domain-verification=r14frwljwbxs
—
stripe-verification=5096d01ff2cf194285dd51cae18f24fa9c26dc928cebac3636d462b4c6925623
—
stripe-verification=bf1a94e6b16ace2502a4a7fff574a25c8a45291054960c883c59be39d1788db9
—
uber-domain-verification=58086039-150a-42a4-a4be-b4032921aa0f
—
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
—
DNS History Timeline BETA
Your key is sent directly to SecurityTrails and is never stored on our servers. Get an API key
DNS History Timeline BETA

When was a record added, removed, or changed — and could that change be the problem?

Analyze Another Domain

Confirm Your Email Configuration

This tool analyzes DNS records, but to verify actual email delivery, send a test email to Red Sift Investigate. Their tool shows exactly how your emails arrive, including SPF/DKIM/DMARC pass/fail results in the headers.

DATA FRESHNESS & METHODOLOGY

All security-critical records (SPF, DMARC, DKIM, DANE/TLSA, DNSSEC, MTA-STS, TLS-RPT, BIMI, CAA) are queried live from authoritative nameservers and cross-referenced against 5 independent public DNS resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) at the time of each analysis. No security verdict uses cached data.

Registrar data (RDAP) is cached for up to 24 hours because domain ownership and registration details change infrequently. Certificate Transparency logs (subdomain discovery via RFC 6962) are cached for 1 hour because CT entries are append-only historical records. Sections using cached data are marked with a CACHED badge; live queries show LIVE.

Intelligence Sources

This analysis used 4 DNS resolvers (consensus), reverse DNS (PTR), Team Cymru (ASN attribution), IANA RDAP (registrar), crt.sh (CT logs), and SMTP probing (transport). All using open-standard protocols.

Full List
Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below

This cryptographic hash seals the analysis data, domain, timestamp, and tool version into a tamper-evident fingerprint. Any modification to the report data will produce a different hash. This is distinct from the posture hash (used for drift detection) — the integrity hash uniquely identifies this specific report instance.

0143ce229201bd7530156c3835b42b00e8330170b00b5dd4d73f2b31c067f7b0b4db5b18bc76071bb9b0ae4af11508fb52e993dceeacf899f65dfa724b23c633
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 25 Apr 2026, 14:37 UTC.
Internet Archive — Permanent Record Wayback Machine Can this analysis be independently verified? Archived

This analysis has been automatically submitted to the Internet Archive's Wayback Machine, creating a tamper-evident, third-party-hosted snapshot of the DNS security posture at analysis time. This archived copy is independent of DNS Tool — it provides an independently verifiable record of the analysis at this point in time. Combined with the SHA-3-512 integrity hash, this creates a verifiable chain of evidence for domain security state.

View Archived Snapshot
Snapshot preserved at https://web.archive.org/web/20260425143715/https://dnstool.it-help.tech/analysis/16192/view/E
Download Raw Intelligence Download Checksum (.sha3) Cross-Reference Verification

Download the intelligence dump and verify its integrity, like you would a Kali ISO or any critical artifact. The SHA-3-512 checksum covers every byte of the download — deterministic serialization ensures identical hashes across downloads.

After downloading, verify with any of these commands:

Tip: cd ~/Downloads first (or wherever you saved the files).

OpenSSL + Sidecar (macOS, Linux, WSL) 
cat dns-intelligence-cloudflare.com.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-cloudflare.com.json
Python 3 (cross-platform) 
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-cloudflare.com.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+) 
sha3sum -a 512 dns-intelligence-cloudflare.com.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/16192/checksum. Hash algorithm: SHA-3-512 (Keccak, NIST FIPS 202).

Every finding in this report is backed by DNS queries you can run yourself. These vetted one-liners reproduce the exact checks used to build this report for cloudflare.com. Our analysis adds multi-resolver consensus, RFC-based evaluation, and cross-referencing — but the underlying data is always independently verifiable. We are intelligence analysts, not gatekeepers.

DNS Records

Query A records (IPv4) RFC 1035 
dig +noall +answer cloudflare.com A
Query AAAA records (IPv6) RFC 1035 
dig +noall +answer cloudflare.com AAAA
Query MX records (mail servers) RFC 1035 
dig +noall +answer cloudflare.com MX
Query NS records (nameservers) RFC 1035 
dig +noall +answer cloudflare.com NS
Query TXT records RFC 1035 
dig +noall +answer cloudflare.com TXT

Email Authentication

Check SPF record RFC 7208 
dig +short cloudflare.com TXT | grep -i spf
Check DMARC policy RFC 7489 
dig +short _dmarc.cloudflare.com TXT
Check DKIM key for selector 'k1' RFC 6376 
dig +short k1._domainkey.cloudflare.com TXT
Check DKIM key for selector 'mandrill' RFC 6376 
dig +short mandrill._domainkey.cloudflare.com TXT
Check DKIM key for selector 's1' RFC 6376 
dig +short s1._domainkey.cloudflare.com TXT
Check DKIM key for selector 'smtpapi' RFC 6376 
dig +short smtpapi._domainkey.cloudflare.com TXT
Check DKIM key for selector 'zendesk1' RFC 6376 
dig +short zendesk1._domainkey.cloudflare.com TXT
Check DKIM key for selector 'zendesk2' RFC 6376 
dig +short zendesk2._domainkey.cloudflare.com TXT

Domain Security

Check DNSSEC DNSKEY records RFC 4035 
dig +dnssec +noall +answer cloudflare.com DNSKEY
Check DNSSEC DS records RFC 4035 
dig +noall +answer cloudflare.com DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035 
dig +dnssec +cd cloudflare.com A @1.1.1.1

Transport Security

Check TLSA record for mxa.global.inbound.cf-emailsecurity.net RFC 7672 
dig +noall +answer _25._tcp.mxa.global.inbound.cf-emailsecurity.net TLSA
Check TLSA record for mxb.global.inbound.cf-emailsecurity.net RFC 7672 
dig +noall +answer _25._tcp.mxb.global.inbound.cf-emailsecurity.net TLSA
Check TLSA record for mxa-canary.global.inbound.cf-emailsecurity.net RFC 7672 
dig +noall +answer _25._tcp.mxa-canary.global.inbound.cf-emailsecurity.net TLSA
Check TLSA record for mxb-canary.global.inbound.cf-emailsecurity.net RFC 7672 
dig +noall +answer _25._tcp.mxb-canary.global.inbound.cf-emailsecurity.net TLSA
Verify TLS certificate on primary MX (mxa.global.inbound.cf-emailsecurity.net) RFC 6698 
openssl s_client -starttls smtp -connect mxa.global.inbound.cf-emailsecurity.net:25 -servername mxa.global.inbound.cf-emailsecurity.net 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record RFC 8461 
dig +short _mta-sts.cloudflare.com TXT
Fetch MTA-STS policy file RFC 8461 
curl -sL https://mta-sts.cloudflare.com/.well-known/mta-sts.txt
Check TLS-RPT record RFC 8460 
dig +short _smtp._tls.cloudflare.com TXT

Brand & Trust

Check BIMI record BIMI Draft 
dig +short default._bimi.cloudflare.com TXT
Check CAA records (certificate authority authorization) RFC 8659 
dig +noall +answer cloudflare.com CAA

DNS Records

Check HTTPS/SVCB records RFC 9460 
dig +noall +answer cloudflare.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344 
dig +noall +answer cloudflare.com CDS

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083 
curl -sL 'https://rdap.org/domain/cloudflare.com' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (mxa.global.inbound.cf-emailsecurity.net) RFC 3207 
openssl s_client -starttls smtp -connect mxa.global.inbound.cf-emailsecurity.net:25 -servername mxa.global.inbound.cf-emailsecurity.net </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs RFC 6962 
curl -s 'https://crt.sh/?q=%25.cloudflare.com&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20
Check security.txt RFC 9116 
curl -sL https://cloudflare.com/.well-known/security.txt | head -20

AI Surface

Check for llms.txt 
curl -sI https://cloudflare.com/llms.txt | head -5
Check robots.txt for AI crawler rules 
curl -s https://cloudflare.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 104.16.132.229 (Team Cymru) 
dig +short 229.132.16.104.origin.asn.cymru.com TXT
ASN lookup for 104.16.133.229 (Team Cymru) 
dig +short 229.133.16.104.origin.asn.cymru.com TXT
Commands use dig, openssl, and curl — standard tools available on macOS, Linux, and WSL. Results may vary slightly due to DNS propagation timing and resolver caching.
Intelligence Confidence Audit Engine consistent · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Consistent 15106 runs
DKIM
Consistent 14883 runs
DMARC
Consistent 15087 runs
DANE/TLSA
Consistent 14865 runs
DNSSEC
Consistent 15064 runs
BIMI
Consistent 14880 runs
MTA-STS
Consistent 14901 runs
TLS-RPT
Consistent 14916 runs
CAA
Consistent 14913 runs
Maturity: Development → Verified → Consistent → Gold → Gold Master

Appendix: Verification Commands

The core DNS queries behind this report can be independently verified using these standard terminal commands (dig, openssl, curl). DNS Tool adds multi-resolver consensus, RFC-based evaluation, and cross-referencing on top of the raw data shown here.

DNS Records

Query A records (IPv4) (RFC 1035) 
dig +noall +answer cloudflare.com A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer cloudflare.com AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer cloudflare.com MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer cloudflare.com NS
Query TXT records (RFC 1035) 
dig +noall +answer cloudflare.com TXT

Email Authentication

Check SPF record (RFC 7208) 
dig +short cloudflare.com TXT | grep -i spf
Check DMARC policy (RFC 7489) 
dig +short _dmarc.cloudflare.com TXT
Check DKIM key for selector 'k1' (RFC 6376) 
dig +short k1._domainkey.cloudflare.com TXT
Check DKIM key for selector 'mandrill' (RFC 6376) 
dig +short mandrill._domainkey.cloudflare.com TXT
Check DKIM key for selector 's1' (RFC 6376) 
dig +short s1._domainkey.cloudflare.com TXT
Check DKIM key for selector 'smtpapi' (RFC 6376) 
dig +short smtpapi._domainkey.cloudflare.com TXT
Check DKIM key for selector 'zendesk1' (RFC 6376) 
dig +short zendesk1._domainkey.cloudflare.com TXT
Check DKIM key for selector 'zendesk2' (RFC 6376) 
dig +short zendesk2._domainkey.cloudflare.com TXT

Domain Security

Check DNSSEC DNSKEY records (RFC 4035) 
dig +dnssec +noall +answer cloudflare.com DNSKEY
Check DNSSEC DS records (RFC 4035) 
dig +noall +answer cloudflare.com DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) (RFC 4035) 
dig +dnssec +cd cloudflare.com A @1.1.1.1

Transport Security

Check TLSA record for mxa.global.inbound.cf-emailsecurity.net (RFC 7672) 
dig +noall +answer _25._tcp.mxa.global.inbound.cf-emailsecurity.net TLSA
Check TLSA record for mxb.global.inbound.cf-emailsecurity.net (RFC 7672) 
dig +noall +answer _25._tcp.mxb.global.inbound.cf-emailsecurity.net TLSA
Check TLSA record for mxa-canary.global.inbound.cf-emailsecurity.net (RFC 7672) 
dig +noall +answer _25._tcp.mxa-canary.global.inbound.cf-emailsecurity.net TLSA
Check TLSA record for mxb-canary.global.inbound.cf-emailsecurity.net (RFC 7672) 
dig +noall +answer _25._tcp.mxb-canary.global.inbound.cf-emailsecurity.net TLSA
Verify TLS certificate on primary MX (mxa.global.inbound.cf-emailsecurity.net) (RFC 6698) 
openssl s_client -starttls smtp -connect mxa.global.inbound.cf-emailsecurity.net:25 -servername mxa.global.inbound.cf-emailsecurity.net 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record (RFC 8461) 
dig +short _mta-sts.cloudflare.com TXT
Fetch MTA-STS policy file (RFC 8461) 
curl -sL https://mta-sts.cloudflare.com/.well-known/mta-sts.txt
Check TLS-RPT record (RFC 8460) 
dig +short _smtp._tls.cloudflare.com TXT

Brand & Trust

Check BIMI record (BIMI Draft) 
dig +short default._bimi.cloudflare.com TXT
Check CAA records (certificate authority authorization) (RFC 8659) 
dig +noall +answer cloudflare.com CAA

DNS Records

Check HTTPS/SVCB records (RFC 9460) 
dig +noall +answer cloudflare.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344) 
dig +noall +answer cloudflare.com CDS

Infrastructure Intelligence

RDAP domain registration lookup (RFC 9083) 
curl -sL 'https://rdap.org/domain/cloudflare.com' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (mxa.global.inbound.cf-emailsecurity.net) (RFC 3207) 
openssl s_client -starttls smtp -connect mxa.global.inbound.cf-emailsecurity.net:25 -servername mxa.global.inbound.cf-emailsecurity.net </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs (RFC 6962) 
curl -s 'https://crt.sh/?q=%25.cloudflare.com&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20
Check security.txt (RFC 9116) 
curl -sL https://cloudflare.com/.well-known/security.txt | head -20

AI Surface

Check for llms.txt 
curl -sI https://cloudflare.com/llms.txt | head -5
Check robots.txt for AI crawler rules 
curl -s https://cloudflare.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 104.16.132.229 (Team Cymru) 
dig +short 229.132.16.104.origin.asn.cymru.com TXT
ASN lookup for 104.16.133.229 (Team Cymru) 
dig +short 229.133.16.104.origin.asn.cymru.com TXT

0s

Running Real-Time Scan Telemetry

Most scans complete in less than one minute. Some may take longer.

Markers represent known resolver locations. Anycast routing selects the nearest node — exact routing is internal to each provider.

Pipeline nodes reflect live data as each analysis phase completes.

Telemetry Log 0 polls