Identity
37
D
cloudflare-dns.com
Posture Score: 63/100
Scanned May 27, 2026 at 12:00 PM UTC
Score History
Attack Surface
51
Reputation
100
Identity Findings
No SPF record found
The domain has no SPF record, allowing anyone to send email as this domain.
💡 Publish an SPF TXT record (e.g. "v=spf1 include:_spf.google.com -all").
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.cloudflare-dns.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@cloudflare-dns.com").
No MX records found
The domain has no MX records and cannot receive email.
💡 Publish MX records pointing to your mail server(s).
Does not meet bulk sender requirements
Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: Neither SPF nor DKIM is configured (at least one required); No DMARC record published (required since Feb 2024); SPF not published (recommended alongside DKIM)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
No DKIM records found
No DKIM records were found after probing 56 common selectors. The domain may use a custom selector not discoverable via external scan.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.cloudflare-dns.com
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-dns.com/.well-known/mta-sts.txt
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-dns.com").
ARC check skipped — no MX records
Cannot assess ARC support without MX records.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
IPv6 readiness is good
IPv6 records are present and properly configured.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
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.
DANE check skipped — no MX records
Cannot check DANE/TLSA without MX records.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open relay check skipped — no MX records
Cannot test for open relay without MX records.
SMTP compliance check skipped — no MX records
Cannot test SMTP compliance without MX records.
Port exposure check skipped — no MX records
Cannot scan ports without MX records.
STARTTLS downgrade check skipped — no MX records
Cannot test STARTTLS without MX records.
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
FCrDNS check skipped — no MX records
Cannot perform FCrDNS without MX records.
SOA record parameters
Serial: 2404992037, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Authorized certificate authorities
CAA records restrict certificate issuance to: comodoca.com, letsencrypt.org, pki.goog; cansignhttpexchanges=yes, digicert.com; 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 ns1.cloudflare-dns.com: 2400:cb00:2049:1::a29f:21
The subdomain ns1.cloudflare-dns.com resolves to 2400:cb00:2049:1::a29f:21 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2400:cb00:2049:1::a29f:21 is operational or remove the DNS record for ns1.cloudflare-dns.com.
Non-responsive IP for ns2.cloudflare-dns.com: 2400:cb00:2049:1::a29f:121
The subdomain ns2.cloudflare-dns.com resolves to 2400:cb00:2049:1::a29f:121 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2400:cb00:2049:1::a29f:121 is operational or remove the DNS record for ns2.cloudflare-dns.com.
Non-responsive IP for staging.cloudflare-dns.com: 2803:f800:53::6
The subdomain staging.cloudflare-dns.com resolves to 2803:f800:53::6 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2803:f800:53::6 is operational or remove the DNS record for staging.cloudflare-dns.com.
Non-responsive IP for staging.cloudflare-dns.com: 2a06:98c1:52::6
The subdomain staging.cloudflare-dns.com resolves to 2a06:98c1:52::6 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2a06:98c1:52::6 is operational or remove the DNS record for staging.cloudflare-dns.com.
Non-responsive IP for test.cloudflare-dns.com: 2606:4700:4700::1111
The subdomain test.cloudflare-dns.com resolves to 2606:4700:4700::1111 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:4700::1111 is operational or remove the DNS record for test.cloudflare-dns.com.
Non-responsive IP for test.cloudflare-dns.com: 2606:4700:4700::1001
The subdomain test.cloudflare-dns.com resolves to 2606:4700:4700::1001 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700:4700::1001 is operational or remove the DNS record for test.cloudflare-dns.com.
Non-mail domain has no SPF record
This domain has no MX records (does not receive mail) but also has no SPF record. Without "v=spf1 -all", attackers can spoof this domain in phishing emails.
💡 Publish "v=spf1 -all" to explicitly declare this domain sends no mail.
No NSEC/NSEC3 records found
Neither NSEC nor NSEC3 records were found. Authenticated denial of existence is not configured.
💡 Configure NSEC3 records for authenticated denial of existence while preventing zone enumeration.
No MX records — A-record fallback active
The domain has no MX records but has an A record. Per RFC 5321, mail servers will attempt delivery to the A record IP. This domain may be silently accepting mail without SPF/DKIM/DMARC protection.
💡 If this domain should not receive mail, publish a Null MX record (RFC 7505): "0 ." as the MX. If it should receive mail, add proper MX records.
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.
4 subdomain(s) discovered for cloudflare-dns.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for cloudflare-dns.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
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
HSTS enabled with preload on cloudflare-dns.com
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
security.txt present
Found security.txt at https://cloudflare-dns.com/.well-known/security.txt.
TLS certificate valid for 208 days
Certificate for cloudflare-dns.com expires on 2026-12-21.
Certificate issued by SSL.com SSL Intermediate CA ECC R2
The certificate for cloudflare-dns.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha384
The certificate for cloudflare-dns.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for cloudflare-dns.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for cloudflare-dns.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on cloudflare-dns.com.
Domain valid for 2496 days
Domain cloudflare-dns.com expires on 2033-03-27.
Domain transfer and delete locks enabled
Domain cloudflare-dns.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for cloudflare-dns.com do not match known disposable email provider patterns.
Domain is 2982 days old
Domain cloudflare-dns.com was registered 2018-03-27.
No wildcard MX records
No wildcard MX records detected for cloudflare-dns.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
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.
No abuse contacts resolved
Could not resolve abuse contact information for MX IPs via abusix.org.
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-dns.com
HTTPS request to https://webmail.cloudflare-dns.com failed or timed out.
WHOIS registration data
Registrar: Cloudflare, Inc. | Created: 2018-03-27 | Expires: 2033-03-27 | Updated: 2023-03-28
WHOIS privacy protection enabled
Domain cloudflare-dns.com has WHOIS privacy/redaction enabled.
Bulletproof Hosting Detection — API key required
Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.
Threat Intelligence Feeds — API key required
Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).
Typosquat detected: cloudfare-dns.com, cloudflaredns.com, cloudflare-ns.com
3 registered lookalike domain(s) that could be used for phishing against your brand. Domains with MX records can send and receive email, making them high-risk phishing vectors.
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record missing
→
DMARC Policy
DMARC policy missing
⚠️ SPF record is missing. DMARC relies on SPF to verify sender authorization. Without SPF, DMARC alignment will fail, reducing email deliverability and brand protection.
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 missing
⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
TLS not verified or unsupported
→
MTA-STS Policy
MTA-STS not configured
⚠️ TLS support could not be verified. MTA-STS requires TLS to enforce encrypted connections. Without TLS, MTA-STS cannot function.
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC not enforced (p=none or missing)
→
BIMI Record
BIMI not configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
TLS not verified or unsupported
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS support could not be verified. TLS-RPT reports on TLS connection failures, but without TLS support, there's nothing to monitor. You need working TLS encryption before TLS-RPT can provide value.
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-dns.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan cloudflare-dns.com Again