Mail domain report: merelbeke.be

SPF

fail

SPF record published

Found

Record: v=spf1 a ip4:178.208.40.47 ip4:194.78.97.227 ip4:185.3.217.43 ip4:91.208.211.62 ip4:212.72.62.129/27 ip4:35.157.190.224/27 ip4:18.185.115.192/26 ip4:18.184.203.224/27 ip4:194.78.97.231 include:spf.protection.outlook.com include:spf.hostedwise.nl include:spf.mailjet.com include:spf.ciport.be include:mailgun.org include:sendgrid.net include:_spf.bibliotheek.be include:_spf.relay.mailprotect.be ~all
DNS lookups: 17 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

No ptr mechanism found in SPF record.
✗

17 DNS lookups, over the limit of 10

SPF record needs 17 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.

#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.
✓ 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.merelbeke.be)

Found

Record: v=DMARC1; p=none;
Found at: _dmarc.merelbeke.be

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: email

Found

Selectors: email
_domainkey: NOERROR

Selector	Key	Flags
email	RSA 1024 bits

Checks

✓ Keys found: email #7

DKIM keys found for this domain with selectors: email
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: email (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

1 mail server

Found

Priority	Host	Records	Reverse DNS
0	merelbeke-be.mail.protection.outlook.com	A 52.101.68.12 A 52.101.91.21 A 52.101.68.25 A 52.101.68.10 AAAA 2a01:111:f403:ca3c::a AAAA 2a01:111:f403:ca38::8 AAAA 2a01:111:f403:c967::c AAAA 2a01:111:f403:ca21::a	mail-db9pr02cu00204.inbound.protection.outlook.com ✓ mail-matpr05cu00105.inbound.protection.outlook.com ✓ mail-db8pr02cu00101.inbound.protection.outlook.com ✓ mail-dbbpr03cu00102.inbound.protection.outlook.com ✓ mail-zrxpr07cu00102.inbound.protection.outlook.com ✓ mail-wa4pr04cu00100.inbound.protection.outlook.com ✓ mail-cpjpr05cu00204.inbound.protection.outlook.com ✓ mail-maspr04cu00102.inbound.protection.outlook.com ✓

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 8 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
merelbeke-be.mail.protection.outlook.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