Mail domain report: dynveo.fr

SPF

fail

SPF record published

Found

Record: v=spf1 ip4:51.83.25.221 ip4:146.88.234.161 ip4:146.88.234.162 include:spf.aweber.com include:mx.ovh.com include:19602560.spf06.hubspotemail.net ~all
DNS lookups: 5 of 10
Void lookups: 1 of 2
Records published: 2
Problem: include:spf.aweber.com does not exist or has no records

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
!

5 of 10 DNS lookups, with problems

SPF record needs 5 DNS lookups (limit is 10). Problems found: include:spf.aweber.com does not exist or has no records.

#2
✓ Ends with ~all #3

SPF record properly uses ~all to restrict unauthorized senders.
✓ Record published #6

SPF record exists for this domain.
✗

Multiple SPF records

Found 2 SPF records. Publishing more than one v=spf1 record causes a permerror; merge them into a single record.

#16
✓ Valid syntax #25

All SPF mechanisms and modifiers are valid.
!

1 void lookup

1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.

#26
✓ No overly broad IP ranges #27

All ip4/ip6 ranges are narrow enough.

DMARC

fail

p=none (_dmarc.dynveo.fr)

Found

Record: v=DMARC1; p=none;
Found at: _dmarc.dynveo.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

No keys found under the checked selectors

Found

Selectors: None found
_domainkey: NOERROR

Checks

!

No key under common selectors

The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.

#7

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
1	smtp.google.com	A 142.251.127.27 A 142.251.127.26 AAAA 2a00:1450:4001:c21::1a AAAA 2a00:1450:4001:c21::1b	lcfrai-in-f27.1e100.net ✓ lcfrai-in-f26.1e100.net ✓ lcfrai-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓

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 4 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
smtp.google.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