ivanti.com

Checked 22 October 2026, 09:22 UTC · via 8.8.8.8
✗Problems found
28 passed 3 warnings 1 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.protection.outlook.com include:_spf1.ivanti.com include:_spf2.ivanti.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

pass

p=reject (_dmarc.ivanti.com)

Found

Record
v=DMARC1; p=reject; fo=1; rua=mailto:3jelue70@ag.dmarcian.com; ruf=mailto:3jelue70@fr.dmarcian.com
Found at
_dmarc.ivanti.com
External report address
mailto:3jelue70@ag.dmarcian.com (authorized)
External report address
mailto:3jelue70@fr.dmarcian.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:3jelue70@ag.dmarcian.comAggregate report addresses
rufmailto:3jelue70@fr.dmarcian.comFailure report addresses
fo1Failure reporting options

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ 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:3jelue70@ag.dmarcian.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: selector1, selector2, s1, s2

Found

Selectors
selector1, selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits
selector2RSA 2048 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: selector1, selector2, s1, s2 #7
    DKIM keys found for this domain with selectors: selector1, selector2, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: 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

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
2371, 34505
Signatures valid until
12 December 2026, 23:46 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • ✓ Signatures valid until 2026-12-12 #21
    DNSKEY signatures are valid until 2026-12-12T23:46:38Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
0ivanti-com.mail.protection.outlook.comA 52.101.194.158 A 52.101.42.64 A 52.101.40.0 A 52.101.11.17 AAAA 2a01:111:f403:f908::3 AAAA 2a01:111:f403:f804::7 AAAA 2a01:111:f403:c927:: AAAA 2a01:111:f403:f807::mail-ch3pr04cu00106.inbound.protection.outlook.com ✓ mail-mw2pr05cu00100.inbound.protection.outlook.com ✓ mail-cy3pr04cu00100.inbound.protection.outlook.com ✓ mail-sn1pr0501cu00301.inbound.protection.outlook.com ✓ mail-bn3pr02cu00103.inbound.protection.outlook.com ✓ mail-co2pr03cu00307.inbound.protection.outlook.com ✓ mail-bn6pr21cu00500.inbound.protection.outlook.com ✓ mail-co1pr02cu00200.inbound.protection.outlook.com ✓

Checks

  • ✓ 1 MX record #9
    Found 1 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 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 8 MX addresss have a PTR record that resolves back to them.

TLS

fail

MTA-STS record without policy · no TLS-RPT · DANE on 0 of 1 MX hosts

Found

MTA-STS record
v=STSv1; id=202409161535Z;
Policy URL
https://mta-sts.ivanti.com/.well-known/mta-sts.txt
Policy error
https://mta-sts.ivanti.com/.well-known/mta-sts.txt returned HTTP 404

DANE (TLSA records)

MX hostTLSADNSSEC
ivanti-com.mail.protection.outlook.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 202409161535Z.
  • ✗
    Policy not reachable
    The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: https://mta-sts.ivanti.com/.well-known/mta-sts.txt returned HTTP 404.
    #33
  • !
    Not configured
    MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #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