vanguard.com

Checked 22 October 2026, 11:20 UTC · via 8.8.8.8
!Passed with warnings
28 passed 3 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
DNS lookups
1 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 1 of 10 DNS lookups #2
    SPF record needs 1 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.vanguard.com)

Found

Record
v=DMARC1; p=reject; sp=reject; fo=1; pct=100; rua=mailto:email_eda@vanguard.com; ruf=mailto:email_edf@vanguard.com;
Found at
_dmarc.vanguard.com
TagValueMeaning
vDMARC1Version
prejectPolicy
sprejectSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:email_eda@vanguard.comAggregate report addresses
rufmailto:email_edf@vanguard.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:email_eda@vanguard.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

pass

Selectors: s1, s2

Found

Selectors
s1, s2
_domainkey
NOERROR
SelectorKeyFlags
s1RSA 2048 bits
s2RSA 2048 bits

Checks

  • ✓ Keys found: s1, s2 #7
    DKIM keys found for this domain with selectors: s1, s2
  • ✓ Strong keys #23
    DKIM keys are strong enough: s1: RSA 2048 bits; s2: RSA 2048 bits.
  • ✓ 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

4 mail servers

Found

PriorityHostRecordsReverse DNS
100mxa-00031e02.gslb.pphosted.comA 67.231.152.87mx0b-00031e02.pphosted.com ✓
100mxb-00031e02.gslb.pphosted.comA 67.231.152.87mx0b-00031e02.pphosted.com ✓
200mx0a-00031e02.pphosted.comA 208.84.65.72mx0a-00031e02.pphosted.com ✓
200mx0b-00031e02.pphosted.comA 67.231.152.87mx0b-00031e02.pphosted.com ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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: mxa-00031e02.gslb.pphosted.com, mxb-00031e02.gslb.pphosted.com, mx0a-00031e02.pphosted.com, mx0b-00031e02.pphosted.com
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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 4 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mxa-00031e02.gslb.pphosted.comnone-
mxb-00031e02.gslb.pphosted.comnone-
mx0a-00031e02.pphosted.comnone-
mx0b-00031e02.pphosted.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

pass

https://vmc.digicert.com/2abc48d8-15d3-43ef-bb78-89dff39ce05e.svg

Found

Record
v=BIMI1; l=https://vmc.digicert.com/2abc48d8-15d3-43ef-bb78-89dff39ce05e.svg; a=https://vmc.digicert.com/2abc48d8-15d3-43ef-bb78-89dff39ce05e.pem;
Found at
default._bimi.vanguard.com
Logo
https://vmc.digicert.com/2abc48d8-15d3-43ef-bb78-89dff39ce05e.svg
Certificate
https://vmc.digicert.com/2abc48d8-15d3-43ef-bb78-89dff39ce05e.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://vmc.digicert.com/2abc48d8-15d3-43ef-bb78-89dff39ce05e.svg; certificate: https://vmc.digicert.com/2abc48d8-15d3-43ef-bb78-89dff39ce05e.pem
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.