Identity
60
B
lennox.com
Posture Score: 82/100
Scanned May 18, 2026 at 12:03 AM UTC
Attack Surface
88
Reputation
99
Identity Findings
Weak DKIM RSA key (~1296 bits) for selector 'selector1'
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.
MTA-STS policy file unreachable
The MTA-STS policy file at https://mta-sts.lennox.com/.well-known/mta-sts.txt could not be fetched.
💡 Host the MTA-STS policy file at the well-known URL over HTTPS.
FCrDNS failure: no PTR for 52.101.9.17 (lennox-com.mail.protection.outlook.com)
The IP 52.101.9.17 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: 52.101.9.17
The IP 52.101.9.17 (for lennox-com.mail.protection.outlook.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
SOA expire value too short
The SOA expire value is 86400s (<604,800s / 7 days). Secondary nameservers may stop serving the zone prematurely.
💡 Increase the SOA expire value to at least 604800 seconds (7 days).
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.
DKIM key strength indicates modern key management
All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.
All external report destinations authorized
External DMARC report destinations have valid authorization records per RFC 7489 §7.1.
Subdomains protected (sp=reject)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
No deprecated DMARCbis tags present
The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).
TLS-RPT report destinations are reachable
All TLS-RPT rua= URIs point to resolvable domains.
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
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.
DNS TTL values follow best practices
All critical DNS record TTLs are within recommended ranges.
SPF record is 312 bytes (multi-string TXT)
The SPF record exceeds 255 bytes and requires multi-string TXT encoding. Most modern resolvers handle this correctly.
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.
REQUIRETLS not advertised
The primary MX does not advertise REQUIRETLS (RFC 8689). This is an emerging standard — MTA-STS and DANE provide adequate TLS enforcement for most deployments.
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 lennox-com.mail.protection.outlook.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
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 318, Refresh: 900s, Retry: 600s, Expire: 86400s, Min TTL: 3600s
Authorized certificate authorities
CAA records restrict certificate issuance to: entrust.net, sectigo.com, letsencrypt.org, digicert.com
Attack Surface Findings
DNS ANY query returns 33 record(s)
The DNS server responds to ANY queries with 33 record(s), creating significant DNS amplification risk.
💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.
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.
All MX records resolve correctly
No dangling MX records detected — all MX hostnames resolve to valid IP addresses.
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
3 subdomain(s) discovered for lennox.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 lennox.com and its subdomains. Each certificate reveals subdomain names.
Microsoft Autodiscover endpoint detected (authenticated)
The Autodiscover endpoint at autodiscover.lennox.com is active and requires authentication.
Reputation Findings
HSTS enabled but missing preload directive on lennox.com
Strict-Transport-Security: max-age=31536000;includeSubDomains;
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
security.txt present
Found security.txt at https://lennox.com/.well-known/security.txt.
TLS certificate valid for 324 days
Certificate for lennox.com expires on 2027-04-07.
Certificate issued by Sectigo Public Server Authentication CA OV R36
The certificate for lennox.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for lennox.com uses an acceptable signature algorithm.
RSA key: 4096 bits
The certificate for lennox.com uses an adequate RSA key of 4096 bits.
SCTs present in certificate
The certificate for lennox.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on lennox.com.
No disposable email provider MX records
MX records for lennox.com do not match known disposable email provider patterns.
No wildcard MX records
No wildcard MX records detected for lennox.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
DMARC reporting destinations look legitimate
DMARC rua/ruf addresses do not point to known URL shortener services.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (lennox-com.mail.protection.outlook.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner from hosted mail provider
The MX (lennox-com.mail.protection.outlook.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.
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 contacts found for MX IPs
Abuse contact information retrieved via abusix.org DNS lookup.
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.lennox.com
HTTPS request to https://webmail.lennox.com failed or timed out.
WHOIS lookup failed
Could not retrieve WHOIS data for lennox.com.
Could not determine domain age
WHOIS creation date could not be parsed for lennox.com.
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: ennox.com (has MX!), lnnox.com (has MX!), lenox.com (has MX!), lennx.com (has MX!), lenno.com (has MX!)
11 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 11. 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 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: lennox-com.mail.protection.outlook.com
PTR record proves mail server legitimacy
MX: lennox-com.mail.protection.outlook.com
Mail server at 52.101.41.56
→
PTR Record
Reverse DNS: mail-sj0pr21cu00100.inbound.protection.outlook.com
Mail Server Reputation: lennox-com.mail.protection.outlook.com
RBL check ensures server is not blacklisted
MX: lennox-com.mail.protection.outlook.com
Mail server at 52.101.41.56
→
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
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/lennox.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan lennox.com Again