Identity
32
F
comfortsystemsusa.com
Posture Score: 56/100
Scanned May 17, 2026 at 7:57 PM UTC
Attack Surface
84
Reputation
51
Identity Findings
No DMARC record found
The domain has no DMARC record, providing no policy for handling unauthenticated email.
💡 Publish a DMARC TXT record at _dmarc.comfortsystemsusa.com (e.g. "v=DMARC1; p=reject; rua=mailto:dmarc@comfortsystemsusa.com").
SPF exceeds 10-lookup limit (11 lookups)
RFC 7208 limits SPF to 10 DNS lookups. Exceeding this causes PermError and SPF failures.
💡 Flatten your SPF record by replacing includes with direct ip4/ip6 mechanisms.
Invalid DKIM syntax for selector 'k1'
The DKIM record is missing the required p= (public key) tag.
💡 Publish a valid DKIM record with the p= tag containing the public key.
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.
Does not meet bulk sender requirements
Google and Yahoo require all bulk senders to have SPF+DKIM, DMARC, and one-click unsubscribe. Issues: No DMARC record published (required since Feb 2024)
💡 Publish SPF, DKIM, and DMARC records. Implement RFC 8058 one-click unsubscribe for marketing mail.
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.comfortsystemsusa.com/.well-known/mta-sts.txt
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"
Void lookup: mx:comfortsystemsusa-com.mail.protection.outlook.com
The mechanism mx:comfortsystemsusa-com.mail.protection.outlook.com returns no records, wasting a DNS lookup.
💡 Remove mechanisms that reference non-existent domains.
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@comfortsystemsusa.com").
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.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.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.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.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.
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.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.
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.
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.
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 344 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.
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 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: 205201676, Refresh: 3600s, Retry: 600s, Expire: 1209600s, Min TTL: 3600s
Attack Surface Findings
Non-routable IPv4 in public DNS: portal.comfortsystemsusa.com → 10.80.0.246
The subdomain portal.comfortsystemsusa.com resolves to non-routable IP 10.80.0.246, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
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 excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
13 subdomain(s) discovered for comfortsystemsusa.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 comfortsystemsusa.com and its subdomains. Each certificate reveals subdomain names.
1 email SRV record(s) found
Email service SRV records expose mail server configuration for automatic client setup.
Reputation Findings
Listed on dnsbl.spfbl.net
170.10.132.221 (us-smtp-inbound-2.mimecast.com) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.4).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl.spfbl.net
170.10.132.242 (us-smtp-inbound-2.mimecast.com) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.4).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Listed on dnsbl.spfbl.net
170.10.132.141 (us-smtp-inbound-2.mimecast.com) is listed on blacklist dnsbl.spfbl.net (response: 127.0.0.4).
💡 Visit the dnsbl.spfbl.net website to request delisting. Investigate the root cause (compromised account, open relay, spam) before requesting removal.
Missing Strict-Transport-Security on comfortsystemsusa.com
The Strict-Transport-Security header is not set on https://comfortsystemsusa.com.
💡 Add the Strict-Transport-Security header with a max-age of at least 31536000 (1 year) and include the includeSubDomains directive.
security.txt present
Found security.txt at https://comfortsystemsusa.com/.well-known/security.txt.
TLS certificate valid for 36 days
Certificate for comfortsystemsusa.com expires on 2026-06-23.
Certificate issued by R12
The certificate for comfortsystemsusa.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for comfortsystemsusa.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for comfortsystemsusa.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for comfortsystemsusa.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on comfortsystemsusa.com.
Domain valid for 116 days
Domain comfortsystemsusa.com expires on 2026-09-11.
Domain transfer and delete locks enabled
Domain comfortsystemsusa.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for comfortsystemsusa.com do not match known disposable email provider patterns.
Domain is 10474 days old
Domain comfortsystemsusa.com was registered 1997-09-12.
No wildcard MX records
No wildcard MX records detected for comfortsystemsusa.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (us-smtp-inbound-2.mimecast.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner from hosted mail provider
The MX (us-smtp-inbound-2.mimecast.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.comfortsystemsusa.com
HTTPS request to https://webmail.comfortsystemsusa.com failed or timed out.
WHOIS registration data
Registrar: MarkMonitor Inc. | Created: 1997-09-12 | Expires: 2026-09-11 | Updated: 2025-08-10
WHOIS privacy protection not detected
Domain comfortsystemsusa.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
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: comfortsystemusa.com (has MX!), comfortsystemsus.com (has MX!)
2 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 found and configured
→
DMARC Policy
DMARC policy missing
⚠️ DMARC policy is missing. Even with SPF configured, you lack the policy layer that tells receiving servers what to do with authentication failures.
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.
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.141
→
PTR Record
Reverse DNS: us-smtp-inbound-1.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.128.221
→
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.141
→
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.128.221
→
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 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
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/comfortsystemsusa.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan comfortsystemsusa.com Again