Identity
72
C
bluevoyant.com
Posture Score: 71/100
Scanned May 8, 2026 at 5:18 PM UTC
Attack Surface
48
Reputation
92
Identity Findings
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.
MTA-STS policy file unreachable
The MTA-STS policy file at https://mta-sts.bluevoyant.com/.well-known/mta-sts.txt could not be fetched.
💡 Host the MTA-STS policy file at the well-known URL over HTTPS.
ARC support not detected
No evidence of ARC (Authenticated Received Chain) support on MX servers. Forwarded messages may lose authentication.
💡 Consider enabling ARC signing on your mail servers to preserve authentication through forwarding.
Shared IP 170.10.128.221 used by multiple MX servers
The IP 170.10.128.221 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 170.10.132.141 used by multiple MX servers
The IP 170.10.132.141 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 170.10.128.242 used by multiple MX servers
The IP 170.10.128.242 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 170.10.128.141 used by multiple MX servers
The IP 170.10.128.141 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 170.10.132.221 used by multiple MX servers
The IP 170.10.132.221 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 170.10.132.242 used by multiple MX servers
The IP 170.10.132.242 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Very low TTL on MX records: 285s
2 MX records have a TTL of 285s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 15s
30 TXT records have a TTL of 15s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 15s
The SPF record has a TTL of 15s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 285s
The DMARC record has a TTL of 285s 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 (~7185s) 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.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
MX records are valid
All MX records are properly configured.
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.
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.
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.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on us-smtp-inbound-1.mimecast.com
Detected open mail-related ports: 25, 587
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: 2403651171, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Authorized certificate authorities
CAA records restrict certificate issuance to: comodoca.com, digicert.com, globalsign.com, godaddy.com, letsencrypt.org, pki.goog
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.bluevoyant.com: 2606:4700::6812:886
The subdomain www.bluevoyant.com resolves to 2606:4700::6812:886 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:886 is operational or remove the DNS record for www.bluevoyant.com.
Non-responsive IP for www.bluevoyant.com: 2606:4700::6812:986
The subdomain www.bluevoyant.com resolves to 2606:4700::6812:986 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:986 is operational or remove the DNS record for www.bluevoyant.com.
Non-responsive IP for portal.bluevoyant.com: 2606:4700::6812:886
The subdomain portal.bluevoyant.com resolves to 2606:4700::6812:886 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:886 is operational or remove the DNS record for portal.bluevoyant.com.
Non-responsive IP for portal.bluevoyant.com: 2606:4700::6812:986
The subdomain portal.bluevoyant.com resolves to 2606:4700::6812:986 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:986 is operational or remove the DNS record for portal.bluevoyant.com.
Non-responsive IP for dev.bluevoyant.com: 2606:4700::6812:986
The subdomain dev.bluevoyant.com resolves to 2606:4700::6812:986 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:986 is operational or remove the DNS record for dev.bluevoyant.com.
Non-responsive IP for dev.bluevoyant.com: 2606:4700::6812:886
The subdomain dev.bluevoyant.com resolves to 2606:4700::6812:886 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:886 is operational or remove the DNS record for dev.bluevoyant.com.
Non-responsive IP for api.bluevoyant.com: 2606:4700::6812:886
The subdomain api.bluevoyant.com resolves to 2606:4700::6812:886 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:886 is operational or remove the DNS record for api.bluevoyant.com.
Non-responsive IP for api.bluevoyant.com: 2606:4700::6812:986
The subdomain api.bluevoyant.com resolves to 2606:4700::6812:986 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6812:986 is operational or remove the DNS record for api.bluevoyant.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.
4 subdomain(s) discovered for bluevoyant.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 bluevoyant.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 bluevoyant.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
HSTS enabled with preload on bluevoyant.com
Strict-Transport-Security: max-age=15552000; preload
security.txt present
Found security.txt at https://bluevoyant.com/.well-known/security.txt.
TLS certificate valid for 73 days
Certificate for bluevoyant.com expires on 2026-07-21.
Certificate issued by WE1
The certificate for bluevoyant.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha256
The certificate for bluevoyant.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for bluevoyant.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for bluevoyant.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on bluevoyant.com.
Domain valid for 84 days
Domain bluevoyant.com expires on 2026-08-01.
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.bluevoyant.com
HTTPS request to https://webmail.bluevoyant.com failed or timed out.
WHOIS registration data
Registrar: Tucows Domains Inc. | Created: 2016-08-01 | Expires: 2026-08-01 | Updated: 2025-07-31
WHOIS privacy protection enabled
Domain bluevoyant.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: quarantine
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: quarantine
⚠️ 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: us-smtp-inbound-1.mimecast.com
PTR record proves mail server legitimacy
MX: us-smtp-inbound-1.mimecast.com
Mail server at 170.10.128.221
→
PTR Record
Reverse DNS: us-smtp-inbound-2.mimecast.com
Mail Server Identity: us-smtp-inbound-2.mimecast.com
PTR record proves mail server legitimacy
MX: us-smtp-inbound-2.mimecast.com
Mail server at 170.10.132.242
→
PTR Record
Reverse DNS: us-smtp-inbound-2.mimecast.com
Mail Server Reputation: us-smtp-inbound-1.mimecast.com
RBL check ensures server is not blacklisted
MX: us-smtp-inbound-1.mimecast.com
Mail server at 170.10.128.221
→
RBL Status
Not blacklisted
Mail Server Reputation: us-smtp-inbound-2.mimecast.com
RBL check ensures server is not blacklisted
MX: us-smtp-inbound-2.mimecast.com
Mail server at 170.10.132.242
→
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: quarantine
→
BIMI Record
BIMI not configured
⚠️ BIMI record is missing. Even with DMARC enforcement, you need to configure BIMI to display your brand logo in supported email clients.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS failure reporting configured
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/bluevoyant.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan bluevoyant.com Again