Mail domain report: ssl.com

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:199.102.137.146 include:amazonses.com include:sendgrid.net include:7793904.spf02.hubspotemail.net include:spf.protection.outlook.com -all
DNS lookups: 5 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 5 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

warn

p=quarantine (_dmarc.ssl.com)

Found

Record: v=DMARC1; p=quarantine; pct=100; rua=mailto:abuse@ssl.com; ruf=mailto:abuse@ssl.com; fo=1;
Found at: _dmarc.ssl.com

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:abuse@ssl.com	Aggregate report addresses
ruf	mailto:abuse@ssl.com	Failure report addresses
fo	1	Failure reporting options

Checks

!

Policy: quarantine

DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

#4
✓ 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:abuse@ssl.com
✓ Subdomain policy: quarantine #20

Subdomains are covered by policy 'quarantine'.
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

pass

Selectors: selector1, selector2, s1, s2

Found

Selectors: selector1, selector2, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
selector1	RSA 2048 bits
selector2	RSA 2048 bits
s1	RSA 2048 bits
s2	RSA 2048 bits

Checks

✓ Keys found: selector1, selector2, s1, s2 #7

DKIM keys found for this domain with selectors: selector1, selector2, s1, s2
✓ Strong keys #23

DKIM keys are strong enough: selector1: RSA 2048 bits; selector2: RSA 2048 bits; 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

1 mail server

Found

Priority	Host	Records	Reverse DNS
0	ssl-com.mail.protection.outlook.com	A 52.101.42.170 A 52.101.50.10 A 52.101.10.16 A 52.101.9.11 AAAA 2a01:111:f403:f804:: AAAA 2a01:111:f403:c902::5 AAAA 2a01:111:f403:f903::3 AAAA 2a01:111:f403:c946::18	mail-mw5pr21cu00102.inbound.protection.outlook.com ✓ mail-mw2pr02cu00502.inbound.protection.outlook.com ✓ mail-bn6pr21cu00500.inbound.protection.outlook.com ✓ mail-bl1pr02cu00103.inbound.protection.outlook.com ✓ mail-mw5pr21cu00100.inbound.protection.outlook.com ✓ mail-sj2pr05cu00505.inbound.protection.outlook.com ✓ mail-mn0pr04cu00203.inbound.protection.outlook.com ✓ mail-ch5pr04cu00200.inbound.protection.outlook.com ✓

Checks

✓ 1 MX record #9

Found 1 MX records for this domain.
✓ All hosts resolve #10

All MX records resolve to valid IP addresses.
✓ All hosts have IPv6 #11

All MX records resolve to IPv6 addresses.
!

Single MX host, no backup

Only one MX record found. For better email reliability, consider adding at least one backup MX server.

#12
✓ At most 5 MX records #13

Found 1 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 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
ssl-com.mail.protection.outlook.com	none	-

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://www.ssl.com/vmc_ssl_com_logo.svg

Found

Record: v=BIMI1;l=https://www.ssl.com/vmc_ssl_com_logo.svg; a=https://www.ssl.com/vmc_ssl_com.pem
Found at: default._bimi.ssl.com
Logo: https://www.ssl.com/vmc_ssl_com_logo.svg
Certificate: https://www.ssl.com/vmc_ssl_com.pem

Checks

✓ Logo and certificate published #38

BIMI logo: https://www.ssl.com/vmc_ssl_com_logo.svg; certificate: https://www.ssl.com/vmc_ssl_com.pem
✓ DMARC meets BIMI requirements #39

DMARC is enforced on all mail, as BIMI requires.