Identity
0
F
recordedfuture.com
Posture Score: 57/100
Scanned May 8, 2026 at 5:16 PM UTC
Attack Surface
80
Reputation
91
Identity Findings
Weak DKIM RSA key (~1296 bits) for selector 'google'
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 's2'
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.
Weak DKIM RSA key (~1296 bits) for selector 'cm'
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 mailstream-central.mxrecord.mx
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.64.78 (mailstream-central.mxrecord.mx)
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 172.65.213.128 (mailstream-east.mxrecord.io)
The IP 172.65.213.128 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.220.210 (mailstream-west.mxrecord.io)
The IP 172.65.220.210 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.
No PTR record for MX IP: 172.65.64.78
The IP 172.65.64.78 (for mailstream-central.mxrecord.mx) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 172.65.213.128
The IP 172.65.213.128 (for mailstream-east.mxrecord.io) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
No PTR record for MX IP: 172.65.220.210
The IP 172.65.220.210 (for mailstream-west.mxrecord.io) 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.recordedfuture.com/.well-known/mta-sts.txt
BIMI logo may not be SVG Tiny PS
The logo URL returns Content-Type: text/html; charset=UTF-8. BIMI requires SVG Tiny PS format.
💡 Ensure the logo is in SVG Tiny PS format.
ManageSieve port 4190 open on mailstream-central.mxrecord.mx
Port 4190 (ManageSieve) is publicly accessible. This should typically be restricted.
💡 Restrict port 4190 access to authorized networks via firewall rules.
STARTTLS without MTA-STS or DANE protection
STARTTLS alone is vulnerable to downgrade attacks. Neither MTA-STS nor DANE is configured to enforce encryption.
💡 Deploy MTA-STS and/or DANE to protect against STARTTLS stripping attacks.
No CAA records found
No CAA records are configured. Any certificate authority can issue certificates for this domain.
💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"
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@recordedfuture.com").
Very low TTL on MX records: 44s
3 MX records have a TTL of 44s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 284s
35 TXT records have a TTL of 284s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 284s
The SPF record has a TTL of 284s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 284s
The DMARC record has a TTL of 284s 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 (~7184s) 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.
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.
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.
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.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
Open mail ports on mailstream-central.mxrecord.mx
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
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 2403420106, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
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.
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.
10 subdomain(s) discovered for recordedfuture.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 recordedfuture.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
Missing domain locks: clientDeleteProhibited
Domain recordedfuture.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
HSTS enabled but missing preload directive on recordedfuture.com
Strict-Transport-Security: max-age=31557600
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
security.txt present
Found security.txt at https://recordedfuture.com/.well-known/security.txt.
TLS certificate valid for 316 days
Certificate for recordedfuture.com expires on 2027-03-20.
Certificate issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1
The certificate for recordedfuture.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for recordedfuture.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for recordedfuture.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for recordedfuture.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on recordedfuture.com.
Domain valid for 146 days
Domain recordedfuture.com expires on 2026-10-02.
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.recordedfuture.com
HTTPS request to https://webmail.recordedfuture.com failed or timed out.
WHOIS registration data
Registrar: Name.com, Inc. | Created: 2009-01-04 | Expires: 2026-10-02 | Updated: 2025-09-10
WHOIS privacy protection enabled
Domain recordedfuture.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 missing
→
DMARC Policy
DMARC policy: reject
⚠️ 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: 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: mailstream-central.mxrecord.mx
PTR record proves mail server legitimacy
MX: mailstream-central.mxrecord.mx
Mail server at 172.65.64.78
→
PTR Record
No PTR record
⚠️ Mail server mailstream-central.mxrecord.mx (172.65.64.78) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: mailstream-east.mxrecord.io
PTR record proves mail server legitimacy
MX: mailstream-east.mxrecord.io
Mail server at 172.65.213.128
→
PTR Record
No PTR record
⚠️ Mail server mailstream-east.mxrecord.io (172.65.213.128) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Identity: mailstream-west.mxrecord.io
PTR record proves mail server legitimacy
MX: mailstream-west.mxrecord.io
Mail server at 172.65.220.210
→
PTR Record
No PTR record
⚠️ Mail server mailstream-west.mxrecord.io (172.65.220.210) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation: mailstream-central.mxrecord.mx
RBL check ensures server is not blacklisted
MX: mailstream-central.mxrecord.mx
Mail server at 172.65.64.78
→
RBL Status
Not blacklisted
Mail Server Reputation: mailstream-east.mxrecord.io
RBL check ensures server is not blacklisted
MX: mailstream-east.mxrecord.io
Mail server at 172.65.213.128
→
RBL Status
Not blacklisted
Mail Server Reputation: mailstream-west.mxrecord.io
RBL check ensures server is not blacklisted
MX: mailstream-west.mxrecord.io
Mail server at 172.65.220.210
→
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/recordedfuture.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan recordedfuture.com Again