Mail domain report: locservice.fr

SPF

pass

SPF record published

Found

Record: v=spf1 a mx include:spf.mailjet.com include:mail.zendesk.com include:_spf.google.com -all
DNS lookups: 5 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 5 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=reject (_dmarc.locservice.fr)

Found

Record: v=DMARC1; p=reject; aspf=r; adkim=r; pct=100; rua=mailto:pierre@gobocom.fr; ruf=mailto:pierre@gobocom.fr;
Found at: _dmarc.locservice.fr
External report address: mailto:pierre@gobocom.fr (not authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy
pct	100	Percentage of mail the policy applies to
rua	mailto:pierre@gobocom.fr	Aggregate report addresses
ruf	mailto:pierre@gobocom.fr	Failure report addresses
adkim	r	DKIM alignment (r = relaxed, s = strict)
aspf	r	SPF alignment (r = relaxed, s = strict)

Checks

✓ Policy: reject #4

DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
✓ 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:pierre@gobocom.fr
✓ Subdomain policy: reject #20

Subdomains are covered by policy 'reject'.
!

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:pierre@gobocom.fr (needs locservice.fr._report._dmarc.gobocom.fr). Ask the report provider to publish the record, or check the address.

#29

DKIM

warn

Selectors: dkim, mail

Found

Selectors: dkim, mail
_domainkey: NOERROR

Selector	Key	Flags
dkim	RSA 2048 bits
mail	RSA 1024 bits	test mode (t=y)

Checks

✓ Keys found: dkim, mail #7

DKIM keys found for this domain with selectors: dkim, mail
!

1024-bit DKIM key

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

#23
!

Key in test mode

These keys have t=y, so receivers treat DKIM failures as a test: mail. Remove t=y once DKIM works.

#24

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
5	mx1.nexylan.net	A 185.233.34.15 AAAA 2a10:de80:1:4091:b9e9:22f:0:1	mx.soverin.net ✓ mx.soverin.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 2 MX addresss have a PTR record that resolves back to them.

TLS

fail

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
mx1.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.

#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