Mail domain report: louvre.fr

SPF

pass

SPF record published

Found

Record: v=spf1 a ip4:89.185.38.128/28 ip4:89.185.38.135/32 ip4:89.185.38.200/29 ip4:78.153.243.182/32 ip4:89.185.38.213/32 ip4:89.185.38.212/32 include:spf.mandrillapp.com include:_spf.datapressepremium.com include:spf.mailjet.com include:mail.zendesk.com include:spf.ess.barracudanetworks.com include:de._netblocks.mimecast.com -all
DNS lookups: 7 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 7 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.louvre.fr)

Found

Record: v=DMARC1;p=quarantine;pct=100;adkim=r;aspf=r;rua=mailto:dmarc@louvre.fr;ruf=mailto:dmarc@louvre.fr;fo=0
Found at: _dmarc.louvre.fr

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:dmarc@louvre.fr	Aggregate report addresses
ruf	mailto:dmarc@louvre.fr	Failure report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)
fo	0	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:dmarc@louvre.fr
✓ 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

Found

Selectors: selector1
_domainkey: NOERROR

Selector	Key	Flags
selector1	RSA 2048 bits

Checks

✓ Keys found: selector1 #7

DKIM keys found for this domain with selectors: selector1
✓ Strong keys #23

DKIM keys are strong enough: selector1: 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

2 mail servers

Found

Priority	Host	Records	Reverse DNS
10	de-smtp-inbound-1.mimecast.com	A 194.104.108.22 A 194.104.110.22	de-smtp-inbound-1.mimecast.com ✓ de-smtp-inbound-2.mimecast.com ✓
10	de-smtp-inbound-2.mimecast.com	A 194.104.108.22 A 194.104.110.22	de-smtp-inbound-2.mimecast.com ✓ de-smtp-inbound-2.mimecast.com ✓

Checks

✓ 2 MX records #9

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

All MX records resolve to valid IP addresses.
!

Hosts without IPv6

The following MX hosts could not be resolved to IPv6 addresses: de-smtp-inbound-1.mimecast.com, de-smtp-inbound-2.mimecast.com

#11
✓ Redundant MX hosts #12

Found 2 MX records, which provides redundancy for email delivery.
✓ At most 5 MX records #13

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

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
de-smtp-inbound-1.mimecast.com	none	-
de-smtp-inbound-2.mimecast.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

info

No BIMI record

Checks

i

Not configured

BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.

#38