Mail domain report: systemed.fr

SPF

warn

SPF record published

Found

Record: v=spf1 mx:vivetic.com include:mediactive.fr include:spf.protection.outlook.com include:de._netblocks.mimecast.com include:_netblocks.systemed.fr a mx ptr -all
DNS lookups: 10 of 10
Void lookups: 0 of 2

Checks

!

Uses deprecated ptr mechanism

The ptr mechanism in SPF records is deprecated due to performance issues and should be avoided.

#1
✓ 10 of 10 DNS lookups #2

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

fail

p=none (_dmarc.systemed.fr)

Found

Record: v=DMARC1; p=none; rua=mailto:dmarc-reports@pluriad.fr
Found at: _dmarc.systemed.fr
External report address: mailto:dmarc-reports@pluriad.fr (not authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
rua	mailto:dmarc-reports@pluriad.fr	Aggregate report addresses

Checks

✗

Policy: none (monitoring only)

DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.

#4
✓ Record published #5

DMARC record exists for this domain.
✓ Valid syntax #17

DMARC record syntax is valid.
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:dmarc-reports@pluriad.fr
!

Report address not authorized

These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc-reports@pluriad.fr (needs systemed.fr._report._dmarc.pluriad.fr). Ask the report provider to publish the record, or check the address.

#29

DKIM

warn

Selectors: default, selector1, s1

Found

Selectors: default, selector1, s1
_domainkey: NXDOMAIN

Selector	Key	Flags
default	RSA 1024 bits
selector1	RSA 2048 bits
s1	RSA 1024 bits

Checks

✓ Keys found: default, selector1, s1 #7

DKIM keys found for this domain with selectors: default, selector1, s1
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits), s1 (1024 bits). Rotate to a 2048-bit key.

#23
✓ 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.110.22 A 194.104.108.22	de-smtp-inbound-2.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