Mail domain report: viedemerde.fr

SPF

pass

SPF record published

Found

Record: v=spf1 include:mailgun.org include:spf.mailjet.com include:spf.improvmx.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

fail

p=none (_dmarc.viedemerde.fr)

Found

Record: v=DMARC1; p=none;
Found at: _dmarc.viedemerde.fr

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy

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.
!

No aggregate reports (rua)

DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...

#19

DKIM

warn

Selectors: k1

Found

Selectors: k1
_domainkey: NOERROR

Selector	Key	Flags
k1	RSA 1024 bits

Checks

✓ Keys found: k1 #7

DKIM keys found for this domain with selectors: k1
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: k1 (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	mx1.improvmx.com	A 35.181.18.45 A 13.37.195.136 A 15.236.236.160 AAAA 2a05:d012:412:e202:f36:2c1f:1a49:d38a AAAA 2a05:d012:412:e203:373a:f51a:4a85:1d25 AAAA 2a05:d012:412:e201:88aa:e7b9:7a43:12d7	ec2-35-181-18-45.eu-west-3.compute.amazonaws.com ✓ ec2-13-37-195-136.eu-west-3.compute.amazonaws.com ✓ ec2-15-236-236-160.eu-west-3.compute.amazonaws.com ✓ no PTR no PTR no PTR
20	mx2.improvmx.com	A 13.36.107.63 A 15.236.61.92 A 13.36.222.39 AAAA 2a05:d012:412:e201:1f6e:f6e4:8fd7:4678 AAAA 2a05:d012:412:e202:e81e:cc44:3b53:8a3d AAAA 2a05:d012:412:e203:7e33:3d9c:28d7:ee20	ec2-13-36-107-63.eu-west-3.compute.amazonaws.com ✓ ec2-15-236-61-92.eu-west-3.compute.amazonaws.com ✓ ec2-13-36-222-39.eu-west-3.compute.amazonaws.com ✓ no PTR no PTR no PTR

Checks

✓ 2 MX records #9

Found 2 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.
✓ 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.
!

Addresses without reverse DNS

These MX addresses have no PTR record, which many receivers treat as a spam signal: 2a05:d012:412:e202:f36:2c1f:1a49:d38a (mx1.improvmx.com), 2a05:d012:412:e203:373a:f51a:4a85:1d25 (mx1.improvmx.com), 2a05:d012:412:e201:88aa:e7b9:7a43:12d7 (mx1.improvmx.com), 2a05:d012:412:e201:1f6e:f6e4:8fd7:4678 (mx2.improvmx.com), 2a05:d012:412:e202:e81e:cc44:3b53:8a3d (mx2.improvmx.com), 2a05:d012:412:e203:7e33:3d9c:28d7:ee20 (mx2.improvmx.com). Ask your hosting provider to set one.

#30

TLS

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
mx1.improvmx.com	none	-
mx2.improvmx.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