Identity
74
C
claroty.com
Posture Score: 74/100
Scanned May 8, 2026 at 4:25 PM UTC
Attack Surface
56
Reputation
91
Identity Findings
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.claroty.com/.well-known/mta-sts.txt
BIMI logo may not be SVG Tiny PS
The logo URL returns Content-Type: . BIMI requires SVG Tiny PS format.
💡 Ensure the logo is in SVG Tiny PS format.
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: include:%{ir}.%{v}.%{d}.spf.has.pphosted.com
The mechanism include:%{ir}.%{v}.%{d}.spf.has.pphosted.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@claroty.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.
Slow DNS response from ns-232.awsdns-29.com: 2071.3ms
The nameserver ns-232.awsdns-29.com responded in 2071.3ms, exceeding the 500ms threshold.
💡 Investigate network latency or performance issues on ns-232.awsdns-29.com.
Very low TTL on MX records: 37s
2 MX records have a TTL of 37s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on A record: 288s
The A record has a TTL of 288s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 278s
21 TXT records have a TTL of 278s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 278s
The SPF record has a TTL of 278s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 278s
The DMARC record has a TTL of 278s 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 (~7178s) differs significantly from the authoritative zone (~172800s).
💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.
DKIM records are valid
DKIM records found and validated for selectors: google, dkim
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.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
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.
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 mxa-00829901.gslb.pphosted.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: 1, Refresh: 7200s, Retry: 900s, Expire: 1209600s, Min TTL: 86400s
Attack Surface Findings
Non-routable IPv4 in public DNS: grafana.claroty.com → 10.200.26.236
The subdomain grafana.claroty.com resolves to non-routable IP 10.200.26.236, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: grafana.claroty.com → 10.200.130.8
The subdomain grafana.claroty.com resolves to non-routable IP 10.200.130.8, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: kibana.claroty.com → 10.200.26.236
The subdomain kibana.claroty.com resolves to non-routable IP 10.200.26.236, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
Non-routable IPv4 in public DNS: kibana.claroty.com → 10.200.130.8
The subdomain kibana.claroty.com resolves to non-routable IP 10.200.130.8, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
DNS ANY query returns 30 record(s)
The DNS server responds to ANY queries with 30 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.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
8 subdomain(s) discovered for claroty.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 claroty.com and its subdomains. Each certificate reveals subdomain names.
Reputation Findings
TLS certificate expires in 17 days
Certificate for claroty.com expires on 2026-05-26 (17 days).
💡 Renew the TLS certificate soon — it expires within 30 days.
HSTS enabled but missing preload directive on claroty.com
Strict-Transport-Security: max-age=300
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
security.txt present
Found security.txt at https://claroty.com/.well-known/security.txt.
Certificate issued by Certainly Intermediate R1
The certificate for claroty.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for claroty.com uses an acceptable signature algorithm.
RSA key: 2048 bits
The certificate for claroty.com uses an adequate RSA key of 2048 bits.
SCTs present in certificate
The certificate for claroty.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on claroty.com.
Domain valid for 297 days
Domain claroty.com expires on 2027-03-02.
Domain transfer and delete locks enabled
Domain claroty.com has clientTransferProhibited and clientDeleteProhibited locks.
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.claroty.com
HTTPS request to https://webmail.claroty.com failed or timed out.
WHOIS registration data
Registrar: GoDaddy.com, LLC | Created: 2015-03-02 | Expires: 2027-03-02 | Updated: 2024-01-24
WHOIS privacy protection enabled
Domain claroty.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: 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: mxa-00829901.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxa-00829901.gslb.pphosted.com
Mail server at 143.55.146.218
→
PTR Record
Reverse DNS: mx07-00829901.pphosted.com
Mail Server Identity: mxb-00829901.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxb-00829901.gslb.pphosted.com
Mail server at 143.55.149.124
→
PTR Record
Reverse DNS: mx08-00829901.pphosted.com
Mail Server Reputation: mxa-00829901.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxa-00829901.gslb.pphosted.com
Mail server at 143.55.146.218
→
RBL Status
Not blacklisted
Mail Server Reputation: mxb-00829901.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxb-00829901.gslb.pphosted.com
Mail server at 143.55.149.124
→
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
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-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/claroty.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan claroty.com Again