zapier.com

DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.

Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change.

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

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

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

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

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: pm (1024 bits). Rotate to a 2048-bit key.

MX · 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.

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

TLS · 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.

BIMI · 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.