DNS & Email Security Report for eset.com

An automated analysis of eset.com's DNS configuration, email authentication (SPF, DKIM, DMARC), DNSSEC chain, IPv6 readiness, and transport security. Last analyzed June 10, 2026.

D59/100
Poor

Weak security, action needed

Overall security score: 59/100 · Grade D (Poor)

This report is a cached snapshot

DNS changes frequently. Run a fresh, interactive scan of eset.com for live records, propagation, and deep checks.

Run a fresh live scan

Detailed check results

DNS

73%warning
  • A record presentcritical

    2 A record(s) found

  • AAAA record presentrecommended

    No AAAA records

  • MX records presentrecommended

    2 MX record(s) found

  • NS records presentcritical

    4 NS record(s) found

  • SOA record presentcritical

    SOA record found

  • Multiple nameserversrecommended

    4 nameservers configured ✓

  • SOA serial formatinfo

    Serial 1647522683 (valid, managed DNS format)

  • SOA timers validinfo

    Refresh: 3600s ✓, Retry: 600s ✓, Expire: 604800s ✓

  • No lame nameserversinfo

    4 NS all responding ✓

  • Glue records presentinfo

    No glue needed

  • WWW record configuredinfo

    CNAME: www-eset-com.trafficmanager.net

  • MX servers have PTR recordsinfo

    2 MX IPs all have PTR records ✓

  • MX servers have FCrDNSinfo

    2 MX IPs have forward-confirmed reverse DNS ✓

DNSSEC

28%fail
  • DNSSEC signedrecommended

    DNSSEC not configured. Enable DNSSEC at your domain registrar to protect against DNS spoofing

  • DNSSEC validation OKcritical

    Not applicable (DNSSEC not enabled)

  • NSEC3 RFC 9276 compliantrecommended

    Not applicable (domain uses NSEC or is not DNSSEC-signed)

  • RRSIG signatures validrecommended

    Not applicable (DNSSEC not enabled)

  • Modern DNSSEC algorithmoptional

    Not applicable (DNSSEC not enabled)

  • DS digest algorithm modernrecommended

    Not applicable (no DS records or DNSSEC not enabled)

  • DNSKEY algorithm secureoptional

    Not applicable (DNSSEC not enabled)

  • RRSIG TTL saferecommended

    Not applicable (DNSSEC not enabled or no RRSIG data)

  • Chain of trust completecritical

    DNSSEC not enabled

IPv6

30%fail
  • Website reachable via IPv6recommended

    No IPv6 for website. Add AAAA record pointing to your IPv6 address

  • Mail servers reachable via IPv6recommended

    0/2 MX servers have IPv6. Add AAAA records for your mail servers

  • Nameservers reachable via IPv6recommended

    4/4 NS server(s) with IPv6 ✓

Email security

75%warning
  • SPF record presentcritical

    v=spf1 a:a.mx.eset.com a:b.mx.eset.com a:smtpout.eset.com a:branchsmtp.eset.com a:mailservices.eset.com ip4:91.228.164.108/30 ip4:50.31.61.240 ?include:sent-via.netsuite.com -all

  • SPF syntax validcritical

    SPF syntax is correct ✓

  • SPF policy strict (-all)recommended

    SPF uses -all (hard fail) ✓

  • DKIM foundrecommended

    DKIM selector: sg ✓

  • DMARC record presentrecommended

    v=DMARC1;p=quarantine;aspf=r;pct=100;rua=mailto:[email protected]

  • DMARC policy quarantine or betterrecommended

    DMARC policy: quarantine ✓

  • DMARC policy rejectoptional

    DMARC policy: quarantine. Set p=reject for maximum protection

  • BIMI record presentoptional

    No BIMI record. Add TXT at default._bimi with logo URL (requires DMARC p=quarantine+)

  • BIMI configuration validoptional

    No BIMI configured

  • MTA-STS record presentoptional

    MTA-STS configured ✓

  • MTA-STS policy enforcedoptional

    MTA-STS mode: enforce ✓

  • MX records validcritical

    2 MX record(s) ✓

  • MX domains use DNSSECrecommended

    0/1 MX domain(s) have DNSSEC. Ask your mail provider to enable DNSSEC

  • MX DNSSEC validation OKrecommended

    DNSSEC not enabled for MX domains

  • Mail servers not blacklistedcritical

    1 MX server(s) checked against 16 blacklists - clean ✓

  • No critical blacklist listingscritical

    No blacklist listings ✓

Web security

68%warning
  • CAA records presentrecommended

    No CAA records. Add CAA record to specify allowed certificate authorities

  • CAA policy strictoptional

    CAA not strict. Add CAA 0 issue "letsencrypt.org" (or your CA) to restrict issuance

  • TLSA records (DANE)optional

    No TLSA/DANE records. Add TLSA at _25._tcp.mail for DANE email encryption

  • DANE configuration validoptional

    No DANE configured

  • No sensitive info in TXTcritical

    No sensitive data leaked ✓

  • Verification records reviewedinfo

    5 verification record(s): Atlassian, Google, Apple, Facebook/Meta, Microsoft 365. Consider if all are still needed

  • HTTPS availablecritical

    HTTPS working (status 200) ✓

  • Valid certificatecritical

    Certificate chain is valid and trusted ✓

  • HTTP redirects to HTTPScritical

    HTTP automatically redirects to HTTPS ✓

  • HSTS enabledrecommended

    HSTS enabled (max-age=31536000) ✓

  • HSTS max-age >= 1 yearoptional

    max-age=31536000 (≥1 year) ✓

  • X-Frame-Options headerrecommended

    X-Frame-Options: SAMEORIGIN ✓

  • X-Content-Type-Options headerrecommended

    X-Content-Type-Options: nosniff ✓

  • Content-Security-Policy headerrecommended

    Content-Security-Policy configured ✓

  • Referrer-Policy headerrecommended

    Referrer-Policy: no-referrer-when-downgrade ✓

  • security.txt presentoptional

    No security.txt. Create /.well-known/security.txt with Contact and Expires fields (RFC 9116)

  • security.txt validoptional

    No security.txt configured

  • HTTP/3 (QUIC) supportedoptional

    No HTTP/3 support detected No h3 in Alt-Svc header No HTTPS DNS record (type 65) QUIC probe inconclusive (Inconclusive - no QUIC reply (trigger may be dropped or UDP/443 filtered)) — not a negative signal

  • QUIC UDP reachableinfo

    QUIC probe inconclusive (no reply — trigger may be dropped or UDP/443 filtered). Not a negative signal; h3 is judged from Alt-Svc / HTTPS record

  • HTTPS DNS record (SVCB)optional

    No HTTPS DNS record (type 65). Add HTTPS record for faster HTTP/3 discovery: eset.com IN HTTPS 1 . alpn="h3,h2"

Issues found (5)

DNSSEC not configured

DNSSEC provides extra protection against DNS spoofing

Learn more

No IPv6 (AAAA) records

Your domain is not reachable via IPv6. IPv6 is becoming increasingly important

Learn more

Mail servers have no IPv6

Your mail servers are not reachable via IPv6

Learn more

No CAA records

CAA records determine which Certificate Authorities may issue SSL certificates

Learn more

No HTTP/3 (QUIC) support

HTTP/3 uses QUIC for faster, more resilient connections. Enable it on your web server and open UDP/443 in your firewall

Learn more

Recommendations (5)

Implement DNSSEC

Activate DNSSEC with your domain registrar and add the DS records to your parent zone. This protects against DNS spoofing attacks.

Impact: Significantly increases security and prevents DNS manipulation

Add IPv6 support

Request AAAA records from your hosting provider for your website. IPv6 is becoming increasingly important.

Impact: Makes your website accessible to IPv6-only networks

Add CAA records

Define which Certificate Authorities may issue SSL certificates, for example: "0 issue letsencrypt.org"

Impact: Prevents unauthorized certificate issuance

IPv6 for mail servers

Add AAAA records for your MX servers to support email via IPv6.

Impact: Improves email reachability for IPv6 networks

Enable HTTP/3 (QUIC)

Enable HTTP/3 for faster page loads and improved connection resilience. Nginx: add "listen 443 quic reuseport;" and "add_header Alt-Svc 'h3=":443"; ma=86400'". Caddy: HTTP/3 is enabled by default. Cloudflare: Enable under Speed → Protocol Optimization. Also add an HTTPS DNS record: example.com IN HTTPS 1 . alpn="h3,h2" Ensure UDP port 443 is open in your firewall (QUIC uses UDP, not TCP).

Impact: Faster page loads (0-RTT), better mobile performance, and connection migration between networks

About this report

IntoDNS.AI evaluates eset.com against DNS hygiene, email authentication, and transport-security best practices, scoring each check and rolling them up into an overall grade. Results reflect public DNS as observed on June 10, 2026 and may differ from a live scan if the domain has since changed its configuration.

Want to check your own domain? Scan any domain on the homepage.

Last analyzed: June 10, 2026 · Google Public DNS