imperva.com

Checked 22 October 2026, 09:16 UTC · via 8.8.8.8
!Passed with warnings
23 passed 6 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx include:_spf.thalesgroup.com ip4:52.38.191.241 ip4:82.166.106.195 ip4:168.245.69.22 ip4:168.245.71.146 ip4:198.207.147.224/27 ip4:204.239.0.224/27 include:spf.protection.outlook.com include:_spf.salesforce.com ip4:192.28.150.158 ip4:168.245.42.152/32 ip4:184.106.22.10/32 ip4:207.97.196.197/32 ip4:198.51.94.24 ip4:198.51.94.25 ip4:185.64.8.19 ip4:185.64.8.18 ip4:185.28.196.47 include:mail.zendesk.com exists:%{i}._i.%{d}._d.espf.agari.com include:%{d}.2f.spf-protect.agari.com ~all
DNS lookups
8 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 8 of 10 DNS lookups #2
    SPF record needs 8 DNS lookups (limit is 10).
  • ✓ Ends with ~all #3
    SPF record properly uses ~all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

warn

p=quarantine (_dmarc.imperva.com)

Found

Record
v=DMARC1; p=quarantine; sp=none; fo=1; ri=3600; rua=mailto:imperva@rua.agari.com; ruf=mailto:imperva@ruf.agari.com
Found at
_dmarc.imperva.com
External report address
mailto:imperva@rua.agari.com (authorized)
External report address
mailto:imperva@ruf.agari.com (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spnoneSubdomain policy
ruamailto:imperva@rua.agari.comAggregate report addresses
rufmailto:imperva@ruf.agari.comFailure report addresses
fo1Failure reporting options
ri3600Report interval (seconds)

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:imperva@rua.agari.com
  • !
    Subdomains unprotected (sp=none)
    DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: k1, selector2, google, s1, s2

Found

Selectors
k1, selector2, google, s1, s2
_domainkey
NXDOMAIN
SelectorKeyFlags
k1RSA 1024 bits
selector2RSA 1024 bits
googleRSA 2048 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: k1, selector2, google, s1, s2 #7
    DKIM keys found for this domain with selectors: k1, selector2, google, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits), selector2 (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mx01.thalesgroup.comA 23.90.119.252esa.hc1631-21.eu.iphmx.com ✓
10mx02.thalesgroup.comA 23.90.122.150esa.hc1631-21.eu.iphmx.com ✓

Checks

  • ✓ 2 MX records #9
    Found 2 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mx01.thalesgroup.com, mx02.thalesgroup.com
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 2 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 2 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx01.thalesgroup.comnone-
mx02.thalesgroup.comnone-

Checks

  • !
    Not configured
    MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38