Identity
0
F
thecloroxcompany.com
Posture Score: 59/100
Scanned May 17, 2026 at 7:39 PM UTC
Attack Surface
92
Reputation
84
Identity Findings
No DKIM records found
No DKIM records were found for any common selector. Email may not be authenticated.
💡 Configure DKIM signing and publish the public key at <selector>._domainkey.thecloroxcompany.com
No STARTTLS support on reply.clorox-t.mkt5818.com:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mail5220.clorox-t.mkt5818.com:25
The mail server does not advertise STARTTLS, meaning email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on reply.clorox-t.mkt5818.com
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on mail5220.clorox-t.mkt5818.com
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
Nameserver unresponsive:
The nameserver is not responding on port 53.
💡 Verify that is properly configured and accessible.
Nameserver unresponsive:
The nameserver is not responding on port 53.
💡 Verify that is properly configured and accessible.
Nameserver unresponsive:
The nameserver is not responding on port 53.
💡 Verify that is properly configured and accessible.
Nameserver unresponsive:
The nameserver is not responding on port 53.
💡 Verify that is properly configured and accessible.
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.
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.thecloroxcompany.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.
Generic ISP PTR hostname: ec2-52-3-180-22.compute-1.amazonaws.com
The PTR record for 52.3.180.22 appears to be a generic ISP hostname, which can harm deliverability.
💡 Set a meaningful PTR record like mail.thecloroxcompany.com
Insufficient nameserver redundancy
Fewer than two nameservers with resolvable IP addresses were found.
💡 Configure at least two nameservers on different network subnets for redundancy.
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@thecloroxcompany.com").
Very low TTL on NS records: 192s
4 NS records have a TTL of 192s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 192s
The DMARC record has a TTL of 192s 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.
SPF record length OK (29 bytes)
SPF record is within safe DNS packet size limits.
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
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).
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.
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=1
Failure reports generated when any authentication mechanism fails.
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 reply.clorox-t.mkt5818.com
Detected open mail-related ports: 25
RFC 8058 one-click unsubscribe assessment
No DKIM signing detected. RFC 8058 one-click unsubscribe requires DKIM-signed List-Unsubscribe headers.
MX IP network diversity
MX IPs span 2 different /16 networks, providing good diversity.
SOA record parameters
Serial: 1645829055, Refresh: 3600s, Retry: 300s, Expire: 1814400s, Min TTL: 300s
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.
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.
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
3 subdomain(s) discovered for thecloroxcompany.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 thecloroxcompany.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
DMARC reports sent to URL shortener domain
DMARC aggregate or forensic reports contain sensitive authentication metadata. Sending them to URL shortener domains indicates misconfiguration or a compromised record.
💡 Change DMARC rua/ruf addresses to a domain you control.
SMTP banner mismatch: bounce.mkt41.net
The SMTP banner identifies as 'bounce.mkt41.net' but the MX hostname is 'reply.clorox-t.mkt5818.com' and PTR resolves to 'ec2-52-3-180-22.compute-1.amazonaws.com'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.
💡 Configure the SMTP server banner to match the MX hostname or PTR record (reply.clorox-t.mkt5818.com).
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
HSTS enabled with preload on thecloroxcompany.com
Strict-Transport-Security: max-age=31622400; includeSubDomains; preload
security.txt present
Found security.txt at https://thecloroxcompany.com/.well-known/security.txt.
TLS certificate valid for 69 days
Certificate for thecloroxcompany.com expires on 2026-07-26.
Certificate issued by R12
The certificate for thecloroxcompany.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for thecloroxcompany.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for thecloroxcompany.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for thecloroxcompany.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on thecloroxcompany.com.
Domain valid for 488 days
Domain thecloroxcompany.com expires on 2027-09-18.
Domain transfer and delete locks enabled
Domain thecloroxcompany.com has clientTransferProhibited and clientDeleteProhibited locks.
No disposable email provider MX records
MX records for thecloroxcompany.com do not match known disposable email provider patterns.
Domain is 7911 days old
Domain thecloroxcompany.com was registered 2004-09-18.
No wildcard MX records
No wildcard MX records detected for thecloroxcompany.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 (reply.clorox-t.mkt5818.com) uses with cipher including Forward Secrecy.
No registered typosquat domains detected
None of the common typosquat mutations of this domain appear to be registered by third parties.
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.thecloroxcompany.com
HTTPS request to https://webmail.thecloroxcompany.com failed or timed out.
WHOIS registration data
Registrar: SafeNames Ltd. | Created: 2004-09-18 | Expires: 2027-09-18 | Updated: 2025-10-01
WHOIS privacy protection enabled
Domain thecloroxcompany.com has WHOIS privacy/redaction enabled.
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).
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: reply.clorox-t.mkt5818.com
PTR record proves mail server legitimacy
MX: reply.clorox-t.mkt5818.com
Mail server at 52.3.180.22
→
PTR Record
Reverse DNS: ec2-52-3-180-22.compute-1.amazonaws.com
Mail Server Identity: mail5220.clorox-t.mkt5818.com
PTR record proves mail server legitimacy
MX: mail5220.clorox-t.mkt5818.com
Mail server at 74.112.64.219
→
PTR Record
Reverse DNS: mail5220.clorox-t.mkt5818.com
Mail Server Reputation: reply.clorox-t.mkt5818.com
RBL check ensures server is not blacklisted
MX: reply.clorox-t.mkt5818.com
Mail server at 52.3.180.22
→
RBL Status
Not blacklisted
Mail Server Reputation: mail5220.clorox-t.mkt5818.com
RBL check ensures server is not blacklisted
MX: mail5220.clorox-t.mkt5818.com
Mail server at 74.112.64.219
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
TLS not verified or unsupported
→
MTA-STS Policy
MTA-STS not configured
⚠️ TLS support could not be verified. MTA-STS requires TLS to enforce encrypted connections. Without TLS, MTA-STS cannot function.
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
TLS not verified or unsupported
→
TLS-RPT Reporting
TLS-RPT not configured
⚠️ TLS support could not be verified. TLS-RPT reports on TLS connection failures, but without TLS support, there's nothing to monitor. You need working TLS encryption before TLS-RPT can provide value.
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/thecloroxcompany.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan thecloroxcompany.com Again