Apex, subdomain, or URL. We figure it out.
Results for
izipay.pe
Email authentication
The basics are in place but can be hardened.
- 1Pass
- 2Warning
- 0Fail
- 3Not set
SPF
WarningAuthorizes which servers may send mail for the domain
SPF is published but could be tightened.
- Policy
- -all
- DNS lookups
- 10 / 10
- Ends in -all (hardfail): unauthorized senders are rejected.
- Uses 10 of 10 allowed DNS lookups. Close to the limit.
v=spf1 ip4:190.102.141.100 ip4:139.138.38.161 ip4:139.138.35.201 ip4:168.121.49.192/26 ip4:200.60.69.16/28 ip4:200.48.102.185 ip4:190.102.141.102 ip4:200.106.49.168 include:_spf.embluemail.com include:_spf.atlassian.net include:spf.protection.outlook.com include:_spf.qualtrics.com include:_spf.google.com include:_spf.recaptchamail.goog include:_spf.salesforce.com -allDKIM
PassCryptographically signs outgoing mail (best-effort selector probe)
DKIM key published for 2 known selectors.
- Selectors
- google, s2
- Found a DKIM key at google._domainkey.izipay.pe
- Found a DKIM key at s2._domainkey.izipay.pe
DMARC
WarningTells receivers what to do with mail that fails SPF and DKIM
DMARC is published but not fully enforcing.
- Policy
- p=none
- Coverage
- 100%
- Policy p=none: DMARC is in monitoring mode only and does not block spoofed mail.
- Aggregate reports (rua) are configured.
v=DMARC1; p=none; 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.