Mail domain report: zapier.com

SPF

pass

SPF record published

Found

Record: v=spf1 include:_spf.google.com include:mailgun.org include:7462085.spf03.hubspotemail.net include:mail.zendesk.com include:_spf.qualtrics.com -all
DNS lookups: 9 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✓ 9 of 10 DNS lookups #2

SPF record needs 9 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.zapier.com)

Found

Record: v=DMARC1; p=reject; pct=100; rua=mailto:re+imuzho2gzgl@dmarc.postmarkapp.com,mailto:dmarc_agg@dmarc.everest.email; ruf=mailto:dmarc_fr@dmarc.everest.email; sp=reject; aspf=r; adkim=r;
Found at: _dmarc.zapier.com
External report address: mailto:re+imuzho2gzgl@dmarc.postmarkapp.com (authorized)
External report address: mailto:dmarc_agg@dmarc.everest.email (authorized)
External report address: mailto:dmarc_fr@dmarc.everest.email (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
sp	reject	Subdomain policy
pct	100	Percentage of mail the policy applies to
rua	mailto:re+imuzho2gzgl@dmarc.postmarkapp.com,mailto:dmarc_agg@dmarc.everest.email	Aggregate report addresses
ruf	mailto:dmarc_fr@dmarc.everest.email	Failure report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)

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:re+imuzho2gzgl@dmarc.postmarkapp.com, mailto:dmarc_agg@dmarc.everest.email
✓ 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: google, pm, s1, s2

Found

Selectors: google, pm, s1, s2
_domainkey: NXDOMAIN

Selector	Key	Flags
google	RSA 2048 bits
pm	RSA 1024 bits
s1	RSA 2048 bits
s2	RSA 2048 bits

Checks

✓ Keys found: google, pm, s1, s2 #7

DKIM keys found for this domain with selectors: google, pm, s1, s2
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: pm (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

7 mail servers

Found

Priority	Host	Records	Reverse DNS
1	aspmx.l.google.com	A 142.251.127.27 AAAA 2a00:1450:4001:c21::1b	lcfrai-in-f27.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
5	alt1.aspmx.l.google.com	A 142.250.147.26 AAAA 2a00:1450:4025:c01::1a	rd-in-f26.1e100.net ✓ rd-in-f26.1e100.net ✓
5	alt2.aspmx.l.google.com	A 172.253.152.27 AAAA 2a00:1450:4010:c22::1b	yulpptr-in-f27.1e100.net ✓ yulpptr-in-f27.1e100.net ✓
10	alt3.aspmx.l.google.com	A 192.179.20.27 AAAA 2404:6800:4000:1027::1a	ncboms-in-f27.1e100.net ✓ ncboms-in-f26.1e100.net ✓
10	alt4.aspmx.l.google.com	A 192.178.158.26 AAAA 2404:6800:4013:813::1b	lcdels-in-f26.1e100.net ✓ lcdels-in-f27.1e100.net ✓
10	ms74255568.msv1.invalid	(does not resolve)
10	noreply.qemailserver.com	A 98.97.252.159 A 98.97.252.158 A 98.97.252.157 A 98.97.251.157 A 98.97.251.158 A 98.97.251.159	no PTR no PTR no PTR no PTR no PTR no PTR

Checks

✓ 7 MX records #9

Found 7 MX records for this domain.
!

Hosts without IP addresses

The following MX hosts could not be resolved to IP addresses: ms74255568.msv1.invalid

#10
!

Hosts without IPv6

The following MX hosts could not be resolved to IPv6 addresses: ms74255568.msv1.invalid, noreply.qemailserver.com

#11
✓ Redundant MX hosts #12

Found 7 MX records, which provides redundancy for email delivery.
!

More than 5 MX records

Found 7 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.

#13
✓ 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.
!

Addresses without reverse DNS

These MX addresses have no PTR record, which many receivers treat as a spam signal: 98.97.252.159 (noreply.qemailserver.com), 98.97.252.158 (noreply.qemailserver.com), 98.97.252.157 (noreply.qemailserver.com), 98.97.251.157 (noreply.qemailserver.com), 98.97.251.158 (noreply.qemailserver.com), 98.97.251.159 (noreply.qemailserver.com). Ask your hosting provider to set one.

#30

TLS

warn

MTA-STS testing · TLS-RPT · DANE on 0 of 7 MX hosts

Found

MTA-STS record: v=STSv1;id=1585839705087;
Policy URL: https://mta-sts.zapier.com/.well-known/mta-sts.txt
Mode: testing
Allowed MX: aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com
Max age: 604800 seconds
TLS-RPT record: v=TLSRPTv1; rua=mailto:mta-sts@zapier.com;

DANE (TLSA records)

MX host	TLSA	DNSSEC
aspmx.l.google.com	none	-
alt1.aspmx.l.google.com	none	-
alt2.aspmx.l.google.com	none	-
alt3.aspmx.l.google.com	none	-
alt4.aspmx.l.google.com	none	-
ms74255568.msv1.invalid	none	-
noreply.qemailserver.com	none	-

Checks

✓ Record published #32

MTA-STS record found with id 1585839705087.
!

Policy in testing mode

With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.

#33
!

MX hosts missing from policy

These MX hosts are not listed in the MTA-STS policy (mx: aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com): ms74255568.msv1.invalid, noreply.qemailserver.com. This will break delivery once the policy is enforced.

#34
✓ Reports enabled #35

TLS reports are sent to: mailto:mta-sts@zapier.com
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

warn

https://cdn.zapier.com/storage/files/4913356ce8fc5df09a9a1aaba7d0e5bb.svg

Found

Record: v=BIMI1; l=https://cdn.zapier.com/storage/files/4913356ce8fc5df09a9a1aaba7d0e5bb.svg;
Found at: default._bimi.zapier.com
Logo: https://cdn.zapier.com/storage/files/4913356ce8fc5df09a9a1aaba7d0e5bb.svg

Checks

!

No certificate (a=)

The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.

#38
✓ DMARC meets BIMI requirements #39

DMARC is enforced on all mail, as BIMI requires.