Identity
4
F
cloudflare.com
Posture Score: 38/100
Scanned May 8, 2026 at 3:47 PM UTC
Attack Surface
12
Reputation
99
Identity Findings
Weak DKIM RSA key (~1296 bits) for selector 'k1'
RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.
💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.
Weak DKIM RSA key (~1296 bits) for selector 'mandrill'
RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.
💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.
Port 465 open but TLS handshake failed on mxa-canary.global.inbound.cf-emailsecurity.net
Port 465 (SMTPS) is open but does not complete a TLS handshake.
💡 Ensure TLS is properly configured on port 465.
FCrDNS failure: no PTR for 172.65.65.66 (mxa-canary.global.inbound.cf-emailsecurity.net)
The IP 172.65.65.66 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
FCrDNS failure: no PTR for 172.65.65.66 (mxb-canary.global.inbound.cf-emailsecurity.net)
The IP 172.65.65.66 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
FCrDNS failure: no PTR for 172.65.64.78 (mxa.global.inbound.cf-emailsecurity.net)
The IP 172.65.64.78 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
FCrDNS failure: no PTR for 141.101.90.40 (mxb.global.inbound.cf-emailsecurity.net)
The IP 141.101.90.40 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
NS delegation mismatch
The registrar-delegated nameservers do not match the zone NS records.
💡 Update either the registrar NS delegation or the zone NS records to match.
No PTR record for MX IP: 172.65.65.66
The IP 172.65.65.66 (for mxa-canary.global.inbound.cf-emailsecurity.net) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 172.65.65.66
The IP 172.65.65.66 (for mxb-canary.global.inbound.cf-emailsecurity.net) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 172.65.64.78
The IP 172.65.64.78 (for mxa.global.inbound.cf-emailsecurity.net) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 141.101.90.40
The IP 141.101.90.40 (for mxb.global.inbound.cf-emailsecurity.net) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No MTA-STS record found
Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.
💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.cloudflare.com/.well-known/mta-sts.txt
ManageSieve port 4190 open on mxa-canary.global.inbound.cf-emailsecurity.net
Port 4190 (ManageSieve) is publicly accessible. This should typically be restricted.
💡 Restrict port 4190 access to authorized networks via firewall rules.
No TLS-RPT record found
Without TLS-RPT, you will not receive reports about TLS negotiation failures.
💡 Publish a _smtp._tls TXT record (e.g. "v=TLSRPTv1; rua=mailto:tls-reports@cloudflare.com").
Shared IP 172.65.65.66 used by multiple MX servers
The IP 172.65.65.66 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Very low TTL on A records: 287s
2 A records have a TTL of 287s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on AAAA records: 112s
2 AAAA records have a TTL of 112s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 274s
25 TXT records have a TTL of 274s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 274s
The SPF record has a TTL of 274s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 274s
The DMARC record has a TTL of 274s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
NS TTL mismatch between parent and authoritative zone
The NS record TTL in the parent zone (~7174s) differs significantly from the authoritative zone (~86400s).
💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
BIMI record is valid
BIMI is properly configured with a valid logo and DMARC enforcement.
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
IPv6 readiness is good
IPv6 records are present and properly configured.
STARTTLS downgrade resistance is adequate
STARTTLS is supported with modern TLS and protected by MTA-STS and/or DANE.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
DKIM2 not detected
No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
DMARCbis np tag absent
The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.
Deprecated DMARCbis tags found: pct
The DMARC record contains tags deprecated in DMARCbis: pct. Consider removing these for forward compatibility.
DMARCbis psd tag absent
The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.
DANE/TLSA configured for mxa-canary.global.inbound.cf-emailsecurity.net
TLSA records found and TLS certificate is available for verification.
DANE/TLSA configured for mxb-canary.global.inbound.cf-emailsecurity.net
TLSA records found and TLS certificate is available for verification.
DANE/TLSA configured for mxa.global.inbound.cf-emailsecurity.net
TLSA records found and TLS certificate is available for verification.
DANE/TLSA configured for mxb.global.inbound.cf-emailsecurity.net
TLSA records found and TLS certificate is available for verification.
Open mail ports on mxa-canary.global.inbound.cf-emailsecurity.net
Detected open mail-related ports: 25, 110, 143, 465, 587, 993, 995, 4190
RFC 8058 one-click unsubscribe assessment
DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.
MX IP network diversity
MX IPs span 2 different /16 networks, providing good diversity.
SOA record parameters
Serial: 2403395625, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 300s
Authorized certificate authorities
CAA records restrict certificate issuance to: comodoca.com, digicert.com; cansignhttpexchanges=yes, letsencrypt.org, pki.goog; cansignhttpexchanges=yes, ssl.com
Attack Surface Findings
NSEC records enable zone walking
The domain uses NSEC records for DNSSEC authenticated denial of existence. NSEC records can be walked to enumerate all names in the zone, effectively disclosing the entire zone contents.
💡 Switch from NSEC to NSEC3 with opt-out to prevent zone enumeration. Use NSEC3 with a random salt and sufficient iterations.
Domain enumerability: high
The domain is highly enumerable. Zone transfers, NSEC zone walking, or a combination of factors make it easy to discover all DNS records.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
Non-responsive IP for www.cloudflare.com: 2606:4700::6810:7b60
The subdomain www.cloudflare.com resolves to 2606:4700::6810:7b60 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6810:7b60 is operational or remove the DNS record for www.cloudflare.com.
Non-responsive IP for www.cloudflare.com: 2606:4700::6810:7c60
The subdomain www.cloudflare.com resolves to 2606:4700::6810:7c60 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6810:7c60 is operational or remove the DNS record for www.cloudflare.com.
Non-responsive IP for staging.cloudflare.com: 108.162.209.98
The subdomain staging.cloudflare.com resolves to 108.162.209.98 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 108.162.209.98 is operational or remove the DNS record for staging.cloudflare.com.
Non-responsive IP for api.cloudflare.com: 2606:4700:300a::6813:c0b0
The subdomain api.cloudflare.com resolves to 2606:4700:300a::6813:c0b0 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:300a::6813:c0b0 is operational or remove the DNS record for api.cloudflare.com.
Non-responsive IP for api.cloudflare.com: 2606:4700:300a::6813:c01d
The subdomain api.cloudflare.com resolves to 2606:4700:300a::6813:c01d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:300a::6813:c01d is operational or remove the DNS record for api.cloudflare.com.
Non-responsive IP for api.cloudflare.com: 2606:4700:300a::6813:c0af
The subdomain api.cloudflare.com resolves to 2606:4700:300a::6813:c0af which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:300a::6813:c0af is operational or remove the DNS record for api.cloudflare.com.
Non-responsive IP for api.cloudflare.com: 2606:4700:300a::6813:c0ae
The subdomain api.cloudflare.com resolves to 2606:4700:300a::6813:c0ae which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:300a::6813:c0ae is operational or remove the DNS record for api.cloudflare.com.
Non-responsive IP for api.cloudflare.com: 2606:4700:300a::6813:c11d
The subdomain api.cloudflare.com resolves to 2606:4700:300a::6813:c11d which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:300a::6813:c11d is operational or remove the DNS record for api.cloudflare.com.
Non-responsive IP for api.cloudflare.com: 2606:4700:300a::6813:c0b1
The subdomain api.cloudflare.com resolves to 2606:4700:300a::6813:c0b1 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:300a::6813:c0b1 is operational or remove the DNS record for api.cloudflare.com.
Non-responsive IP for blog.cloudflare.com: 2606:4700::6812:1d07
The subdomain blog.cloudflare.com resolves to 2606:4700::6812:1d07 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:1d07 is operational or remove the DNS record for blog.cloudflare.com.
Non-responsive IP for blog.cloudflare.com: 2606:4700::6812:1c07
The subdomain blog.cloudflare.com resolves to 2606:4700::6812:1c07 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:1c07 is operational or remove the DNS record for blog.cloudflare.com.
Non-responsive IP for support.cloudflare.com: 2606:4700::6812:3ba
The subdomain support.cloudflare.com resolves to 2606:4700::6812:3ba which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:3ba is operational or remove the DNS record for support.cloudflare.com.
Non-responsive IP for support.cloudflare.com: 2606:4700::6812:2ba
The subdomain support.cloudflare.com resolves to 2606:4700::6812:2ba which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:2ba is operational or remove the DNS record for support.cloudflare.com.
Non-responsive IP for docs.cloudflare.com: 2606:4700::6812:1704
The subdomain docs.cloudflare.com resolves to 2606:4700::6812:1704 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:1704 is operational or remove the DNS record for docs.cloudflare.com.
Non-responsive IP for docs.cloudflare.com: 2606:4700::6812:1604
The subdomain docs.cloudflare.com resolves to 2606:4700::6812:1604 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:1604 is operational or remove the DNS record for docs.cloudflare.com.
Non-responsive IP for grafana.cloudflare.com: 2606:4700::6810:85e5
The subdomain grafana.cloudflare.com resolves to 2606:4700::6810:85e5 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6810:85e5 is operational or remove the DNS record for grafana.cloudflare.com.
Non-responsive IP for grafana.cloudflare.com: 2606:4700::6810:84e5
The subdomain grafana.cloudflare.com resolves to 2606:4700::6810:84e5 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6810:84e5 is operational or remove the DNS record for grafana.cloudflare.com.
NSEC used instead of NSEC3 (zone enumeration possible)
The domain uses NSEC records for authenticated denial of existence. NSEC allows zone walking.
💡 Migrate from NSEC to NSEC3 to prevent zone enumeration.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
3435 subdomain(s) discovered for cloudflare.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
4978 certificate(s) found in CT logs
Certificate Transparency logs contain 4978 certificate(s) for cloudflare.com and its subdomains. Each certificate reveals subdomain names.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
HSTS enabled but missing preload directive on cloudflare.com
Strict-Transport-Security: max-age=31536000; includeSubDomains
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
security.txt present
Found security.txt at https://cloudflare.com/.well-known/security.txt.
TLS certificate valid for 33 days
Certificate for cloudflare.com expires on 2026-06-10.
Certificate issued by WE1
The certificate for cloudflare.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha256
The certificate for cloudflare.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for cloudflare.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for cloudflare.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on cloudflare.com.
Domain valid for 2477 days
Domain cloudflare.com expires on 2033-02-17.
Domain transfer and delete locks enabled
Domain cloudflare.com has clientTransferProhibited and clientDeleteProhibited locks.
Google Safe Browsing DNS check — no flag detected
DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.
Abuse contact lookup failed
Could not query abuse contact information.
PhishTank — API key required
PhishTank phishing database check requires an API key.
Sender Score — API key required
Sender Score reputation check requires an API key.
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
Could not connect to webmail.cloudflare.com
HTTPS request to https://webmail.cloudflare.com failed or timed out.
WHOIS registration data
Registrar: Cloudflare, Inc. | Created: 2009-02-17 | Expires: 2033-02-17 | Updated: 2024-01-09
WHOIS privacy protection enabled
Domain cloudflare.com has WHOIS privacy/redaction enabled.
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record found and configured
→
DMARC Policy
DMARC policy: reject
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature missing
→
DMARC Policy
DMARC policy: reject
⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.
Mail Server Identity: mxa-canary.global.inbound.cf-emailsecurity.net
PTR record proves mail server legitimacy
MX: mxa-canary.global.inbound.cf-emailsecurity.net
Mail server at 172.65.65.66
→
PTR Record
No PTR record
⚠️ Mail server mxa-canary.global.inbound.cf-emailsecurity.net (172.65.65.66) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: mxb-canary.global.inbound.cf-emailsecurity.net
PTR record proves mail server legitimacy
MX: mxb-canary.global.inbound.cf-emailsecurity.net
Mail server at 172.65.65.66
→
PTR Record
No PTR record
⚠️ Mail server mxb-canary.global.inbound.cf-emailsecurity.net (172.65.65.66) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: mxa.global.inbound.cf-emailsecurity.net
PTR record proves mail server legitimacy
MX: mxa.global.inbound.cf-emailsecurity.net
Mail server at 172.65.64.78
→
PTR Record
No PTR record
⚠️ Mail server mxa.global.inbound.cf-emailsecurity.net (172.65.64.78) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: mxb.global.inbound.cf-emailsecurity.net
PTR record proves mail server legitimacy
MX: mxb.global.inbound.cf-emailsecurity.net
Mail server at 141.101.90.40
→
PTR Record
No PTR record
⚠️ Mail server mxb.global.inbound.cf-emailsecurity.net (141.101.90.40) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation: mxa-canary.global.inbound.cf-emailsecurity.net
RBL check ensures server is not blacklisted
MX: mxa-canary.global.inbound.cf-emailsecurity.net
Mail server at 172.65.65.66
→
RBL Status
Not blacklisted
Mail Server Reputation: mxb-canary.global.inbound.cf-emailsecurity.net
RBL check ensures server is not blacklisted
MX: mxb-canary.global.inbound.cf-emailsecurity.net
Mail server at 172.65.65.66
→
RBL Status
Not blacklisted
Mail Server Reputation: mxa.global.inbound.cf-emailsecurity.net
RBL check ensures server is not blacklisted
MX: mxa.global.inbound.cf-emailsecurity.net
Mail server at 172.65.64.78
→
RBL Status
Not blacklisted
Mail Server Reputation: mxb.global.inbound.cf-emailsecurity.net
RBL check ensures server is not blacklisted
MX: mxb.global.inbound.cf-emailsecurity.net
Mail server at 141.101.90.40
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
Mail servers support TLS encryption
→
MTA-STS Policy
MTA-STS not configured
⚠️ MTA-STS policy is missing. Even with TLS support, you lack the enforcement layer that prevents attackers from stripping encryption (downgrade attacks).
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: reject
→
BIMI Record
Brand logo configured
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS-RPT is not configured. Without TLS reporting, you have no visibility into TLS connection failures that may be impacting email delivery.
Security Checks
MX Records
✓
SPF Record
✓
DKIM Record
✗
DMARC Policy
✓
BIMI Record
✓
CAA Records
✓
DNSSEC
✓
MTA-STS
✗
TLS-RPT
✗
Embed Badge
Display your domain's security grade on your website or README:
<img src="https://scan.ractermx.com/badge/cloudflare.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan cloudflare.com Again