Identity
52
C
eset.com
Posture Score: 78/100
Scanned May 8, 2026 at 4:59 PM UTC
Attack Surface
92
Reputation
91
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.eset.com
No STARTTLS support on a.mx.eset.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 b.mx.eset.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 a.mx.eset.com
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
No STARTTLS support on b.mx.eset.com
The mail server does not support STARTTLS. All email is transmitted in plaintext.
💡 Enable STARTTLS on the mail server.
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"
Very low TTL on TXT records: 267s
21 TXT records have a TTL of 267s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 267s
The SPF record has a TTL of 267s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 267s
The DMARC record has a TTL of 267s 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 (~7167s) differs significantly from the authoritative zone (~86400s).
💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.
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.
MTA-STS and TLS-RPT are properly configured
MTA-STS policy is enforced and TLS reporting is configured.
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.
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.
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.
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.
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
Open mail ports on a.mx.eset.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
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 1647522683, Refresh: 3600s, Retry: 600s, Expire: 604800s, Min TTL: 86400s
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.
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.
13 subdomain(s) discovered for eset.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 eset.com and its subdomains. Each certificate reveals subdomain names.
Microsoft Autodiscover endpoint detected (authenticated)
The Autodiscover endpoint at autodiscover.eset.com is active and requires authentication.
Reputation Findings
Missing domain locks: clientDeleteProhibited
Domain eset.com is missing protective locks: clientDeleteProhibited.
💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.
HSTS enabled but missing preload directive on eset.com
Strict-Transport-Security: max-age=31536000
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
security.txt present
Found security.txt at https://eset.com/.well-known/security.txt.
TLS certificate valid for 77 days
Certificate for eset.com expires on 2026-07-24.
Certificate issued by R13
The certificate for eset.com is issued by a third-party CA.
Signature algorithm: rsa-sha256
The certificate for eset.com uses an acceptable signature algorithm.
RSA key: 3072 bits
The certificate for eset.com uses an adequate RSA key of 3072 bits.
SCTs present in certificate
The certificate for eset.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on eset.com.
Domain valid for 344 days
Domain eset.com expires on 2027-04-18.
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.eset.com
HTTPS request to https://webmail.eset.com failed or timed out.
WHOIS registration data
Registrar: CSL Computer Service Langenbach GmbH d/b/a joker.com | Created: 2001-04-18 | Expires: 2027-04-18 | Updated: 2026-03-19
WHOIS privacy protection not detected
Domain eset.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
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: a.mx.eset.com
PTR record proves mail server legitimacy
MX: a.mx.eset.com
Mail server at 91.228.165.113
→
PTR Record
Reverse DNS: a.mx.eset.com
Mail Server Identity: b.mx.eset.com
PTR record proves mail server legitimacy
MX: b.mx.eset.com
Mail server at 91.228.167.41
→
PTR Record
Reverse DNS: b.mx.eset.com
Mail Server Reputation: a.mx.eset.com
RBL check ensures server is not blacklisted
MX: a.mx.eset.com
Mail server at 91.228.165.113
→
RBL Status
Not blacklisted
Mail Server Reputation: b.mx.eset.com
RBL check ensures server is not blacklisted
MX: b.mx.eset.com
Mail server at 91.228.167.41
→
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
Mode: enforce
⚠️ 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: quarantine
→
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 failure reporting 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/eset.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan eset.com Again