Apex, subdomain, or URL. We figure it out.
Results for
ampup.io
Email authentication
Spoofing protection has gaps that need attention.
- 2Pass
- 0Warning
- 1Fail
- 3Not set
SPF
FailAuthorizes which servers may send mail for the domain
SPF is published but misconfigured.
- Policy
- -all
- DNS lookups
- >10 / 10
- Ends in -all (hardfail): unauthorized senders are rejected.
- SPF evaluation needs >10 DNS lookups, over the limit of 10. Receivers return permerror and SPF fails.
v=spf1 a mx include:mailer.chargify.com include:_spf.google.com include:amazonses.com include:mail.zendesk.com include:23808085.spf05.hubspotemail.net include:sendgrid.net include:mailgun.org -allDKIM
PassCryptographically signs outgoing mail (best-effort selector probe)
DKIM key published for 2 known selectors.
- Selectors
- google, k1
- Found a DKIM key at google._domainkey.ampup.io
- Found a DKIM key at k1._domainkey.ampup.io
DMARC
PassTells receivers what to do with mail that fails SPF and DKIM
DMARC is enforced.
- Policy
- p=quarantine
- Coverage
- 100%
- Policy p=quarantine: failing mail is sent to spam.
- Aggregate reports (rua) are configured.
v=DMARC1; p=quarantine; rua=mailto:[email protected]MTA-STS
Not setEnforces TLS for inbound mail and prevents downgrade attacks
No MTA-STS policy. Inbound mail can be delivered without TLS.
TLS-RPT
Not setReceives reports about TLS delivery failures
No TLS-RPT record. You get no reports about failed TLS delivery.
BIMI
Not setDisplays your verified brand logo in supporting inboxes
No BIMI record. No brand logo is published for inboxes.
Checks query live DNS over Cloudflare and the public MTA-STS policy endpoint. DKIM selectors cannot be listed from DNS, so DKIM detection probes common provider selectors only.