Mail domain report: netpublic.fr

SPF

warn

SPF record published

Found

Record: v=spf1 ip4:185.153.8.135 include:nexylan.net include:mail.netpublic.fr ~all
DNS lookups: 4 of 10
Void lookups: 1 of 2
Problem: include:mail.netpublic.fr does not exist or has no records

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
!

4 of 10 DNS lookups, with problems

SPF record needs 4 DNS lookups (limit is 10). Problems found: include:mail.netpublic.fr 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.
✓ Single record #16

Exactly one SPF record is published.
✓ 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.netpublic.fr)

Found

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

pass

Selectors: dkim

Found

Selectors: dkim
_domainkey: NXDOMAIN

Selector	Key	Flags
dkim	RSA 2048 bits

Checks

✓ Keys found: dkim #7

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

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

pass

2 mail servers

Found

Priority	Host	Records	Reverse DNS
10	mx1.nexylan.net	A 185.233.34.15 AAAA 2a10:de80:1:4091:b9e9:22f:0:1	mx.soverin.net ✓ mx.soverin.net ✓
20	mx2.nexylan.net	A 185.233.34.143 AAAA 2a10:de80:1:4092:b9e9:228f:0:1	mx.soverin.net ✓ mx.soverin.net ✓

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.
✓ Reverse DNS confirmed #30

All 4 MX addresss have a PTR record that resolves back to them.

TLS

fail

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
mx1.nexylan.net	3 1 1 db9207b026f07cd3…	No
mx2.nexylan.net	3 1 1 db9207b026f07cd3…	No

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
!

Not configured

MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".

#35
✗

TLSA records not DNSSEC-validated

These MX hosts publish TLSA records that the resolver could not validate with DNSSEC, so senders ignore them or, if validation fails, may refuse delivery: mx1.nexylan.net, mx2.nexylan.net.

#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