eset.com

eset.com · Last checked 2026-10-04 02:12 UTC

eset.com

Needs work, with 2 things to fix

eset.com scored 72/100 (grade C). The main issues are no DKIM key found for the common selectors and SPF is close to the 10-lookup limit, plus 1 more.

Checked 2026-10-04 02:12 UTC · fresh check

3 passed2 need attention0 failing3 for information
Fix this firstThe change with the biggest effect

Reduce SPF DNS lookups

Evaluating SPF for eset.com takes 10 DNS lookups including nested includes; receivers stop at 10 and fail SPF. No detected sending service accounts for these includes; remove each one you no longer send through: sent-via.netsuite.com.

TypeTXT
Name / Host
eset.com

Some DNS providers want “@” here instead of the full domain.

Value
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
Replaces
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

How to apply it

  1. Sign in where your domain’s DNS is managed. This is often where you bought the domain, such as Cloudflare, GoDaddy or Namecheap.
  2. Find the existing TXT record with that name and replace its value.
  3. Save, then come back and re-check. DNS changes can take up to a few hours to show.

All checks

MXCan servers find your inbox?No issues foundPass

Nothing to report.

SPFWho may send as you?SPF is close to the 10-lookup limitNeeds attention
  • Warning: SPF is close to the 10-lookup limit

    Evaluating the SPF record for eset.com needs 10 of the 10 allowed DNS lookups. Adding one more service, or a provider growing its own record, will break SPF.

    How to fix this
  • Warning: SPF has too many lookups that return nothing

    Checking mail from eset.com, IPv6 clients would hit 5 void lookups (DNS queries that return no data). RFC 7208 lets receivers fail SPF after 2. Remove includes and mechanisms that point at names that no longer exist, or MX hosts without an address for that family.

DKIMAre your emails signed?No DKIM key found for the common selectorsNeeds attention
  • Warning: No DKIM key found for the common selectors

    None of the 47 selectors probed under eset.com publish a DKIM key. DNS cannot list selectors, so a key under a custom selector may exist: find the s= value in the DKIM-Signature header of a message you sent and check that selector. If DKIM is not set up, enable it at each service that sends mail for eset.com.

DMARCWhat happens to fakes?DMARC policy is quarantine; consider rejectInfo
  • Info: DMARC policy is quarantine; consider reject

    Failing mail goes to spam rather than being refused. When reports show no legitimate failures, reject gives the strongest protection.

    How to fix this
AlignmentDoes it match your From?SPF alignment is unknownInfo
  • Info: SPF alignment is unknown

    The SPF record of eset.com can pass for some senders (those matched before the failing part), but another evaluation path ends in a permanent error (spf.void-lookups). Senders that reach that path fail SPF, so whether your mail aligns through SPF is unknown. Fix the error so every path evaluates.

BIMICan inboxes show your logo?No BIMI recordInfo
  • Info: No BIMI record

    No BIMI record at default._bimi.eset.com. BIMI is optional: it shows your logo next to your mail in supporting inboxes once DMARC is enforced.

    How to fix this
MTA-STSIs mail to you encrypted?No issues foundPass

Nothing to report.

TLS-RPTWill you hear about failures?TLS-RPT is configuredPass
  • Pass: TLS-RPT is configured

    TLS reports will be sent to mailto:3b7225b1@in.mailhardener.com.

Other fixes

Strengthen the DMARC policyTXT

Rejects mail that fails DMARC, the strongest protection against spoofing.

TypeTXT
Name / Host
_dmarc.eset.com

Some DNS providers want just “_dmarc” here.

Value
v=DMARC1; p=reject; rua=mailto:3b7225b1@in.mailhardener.com; adkim=r; aspf=r
Replaces
v=DMARC1;p=quarantine;aspf=r;pct=100;rua=mailto:3b7225b1@in.mailhardener.com

Prepare BIMIinstruction

BIMI shows your logo next to messages in supporting inboxes, but only for mail that passes DMARC under an enforced policy.

Applies to: default._bimi.eset.com

  1. Enforce DMARC first: p=quarantine or p=reject at 100% (no pct below 100). 2. Convert your logo to an SVG Tiny PS file and host it over HTTPS, for example https://eset.com/bimi/logo.svg. 3. For Gmail and Apple Mail, obtain a VMC or CMC certificate for the logo. 4. Publish a TXT record at default._bimi.eset.com with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.