Identity
48
B
sophos.com
Posture Score: 80/100
Scanned May 8, 2026 at 4:11 PM UTC
Score History
Attack Surface
91
Reputation
100
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.
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.
Generic ISP PTR hostname: ec2-54-155-161-62.eu-west-1.compute.amazonaws.com
The PTR record for 54.155.161.62 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.sophos.com
Generic ISP PTR hostname: ec2-54-171-8-72.eu-west-1.compute.amazonaws.com
The PTR record for 54.171.8.72 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.sophos.com
Generic ISP PTR hostname: ec2-54-154-237-146.eu-west-1.compute.amazonaws.com
The PTR record for 54.154.237.146 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.sophos.com
Generic ISP PTR hostname: ec2-54-155-161-62.eu-west-1.compute.amazonaws.com
The PTR record for 54.155.161.62 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.sophos.com
Generic ISP PTR hostname: ec2-54-171-8-72.eu-west-1.compute.amazonaws.com
The PTR record for 54.171.8.72 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.sophos.com
Generic ISP PTR hostname: ec2-54-154-237-146.eu-west-1.compute.amazonaws.com
The PTR record for 54.154.237.146 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.sophos.com
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"
Shared IP 54.155.161.62 used by multiple MX servers
The IP 54.155.161.62 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 54.171.8.72 used by multiple MX servers
The IP 54.171.8.72 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Shared IP 54.154.237.146 used by multiple MX servers
The IP 54.154.237.146 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: 281s
2 MX records have a TTL of 281s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on A records: 20s
2 A records have a TTL of 20s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on AAAA records: 20s
2 AAAA records have a TTL of 20s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 281s
49 TXT records have a TTL of 281s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 281s
The SPF record has a TTL of 281s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
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.
MX records are valid
All MX records are properly configured.
MTA-STS and TLS-RPT are properly configured
MTA-STS policy is enforced and TLS reporting is configured.
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.
DMARC failure reporting: fo=0:s
Failure reporting option: 0:s
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 mx-02-eu-west-1.prod.hydra.sophos.com
Detected open mail-related ports: 25
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 3 different /16 networks, providing good diversity.
SOA record parameters
Serial: 2020012681, Refresh: 7200s, Retry: 3600s, Expire: 604800s, Min TTL: 3600s
Attack Surface Findings
Domain enumerability: medium
The domain has moderate enumerability. CT logs and DNS records reveal significant information about the domain structure.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
DNSSEC is not enabled
No DNSKEY or DS records were found. DNS responses are not cryptographically authenticated.
💡 Enable DNSSEC by generating DNSKEY records and publishing DS records at the registrar.
DNS ANY query returns 4 record(s)
The DNS server responds to ANY queries with 4 record(s). The low record count limits amplification risk, but ANY responses still aid reconnaissance.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
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.
11 subdomain(s) discovered for sophos.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 sophos.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
HSTS enabled with preload on sophos.com
Strict-Transport-Security: max-age=31536000 ; includeSubDomains ; preload
security.txt present
Found security.txt at https://sophos.com/.well-known/security.txt.
TLS certificate valid for 89 days
Certificate for sophos.com expires on 2026-08-05.
Certificate issued by R12
The certificate for sophos.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for sophos.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for sophos.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for sophos.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on sophos.com.
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.sophos.com
HTTPS request to https://webmail.sophos.com failed or timed out.
WHOIS lookup failed
Could not retrieve WHOIS data for sophos.com.
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: mx-02-eu-west-1.prod.hydra.sophos.com
PTR record proves mail server legitimacy
MX: mx-02-eu-west-1.prod.hydra.sophos.com
Mail server at 54.155.161.62
→
PTR Record
Reverse DNS: ec2-54-155-161-62.eu-west-1.compute.amazonaws.com
Mail Server Identity: mx-01-eu-west-1.prod.hydra.sophos.com
PTR record proves mail server legitimacy
MX: mx-01-eu-west-1.prod.hydra.sophos.com
Mail server at 54.155.161.62
→
PTR Record
Reverse DNS: ec2-54-155-161-62.eu-west-1.compute.amazonaws.com
Mail Server Reputation: mx-02-eu-west-1.prod.hydra.sophos.com
RBL check ensures server is not blacklisted
MX: mx-02-eu-west-1.prod.hydra.sophos.com
Mail server at 54.155.161.62
→
RBL Status
Not blacklisted
Mail Server Reputation: mx-01-eu-west-1.prod.hydra.sophos.com
RBL check ensures server is not blacklisted
MX: mx-01-eu-west-1.prod.hydra.sophos.com
Mail server at 54.155.161.62
→
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
Mode: none
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: quarantine
→
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 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/sophos.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan sophos.com Again