Mail domain report: visitwestvlaanderen.be

SPF

warn

SPF record published

Found

Record: v=spf1 include:servers.mcsv.net include:_mail.level27.eu ?all
DNS lookups: 2 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 2 DNS lookups (limit is 10).
!

Ends with ?all (neutral)

SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.

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

Found

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

Found

Selectors: mail
_domainkey: NOERROR

Selector	Key	Flags
mail	RSA 1024 bits

Checks

✓ Keys found: mail #7

DKIM keys found for this domain with selectors: 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
✓ No problematic flags #24

No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records: Yes (2)
DS at parent: Yes
Algorithms: RSASHA1-NSEC3-SHA1 (7)
Key tags: 47180, 42756
Signatures valid until: 19 June 2029, 11:23 UTC

Checks

✓ Signed, DS published at parent #8

DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
✓ Signatures valid until 2029-06-19 #21

DNSKEY signatures are valid until 2029-06-19T11:23:06Z.

MX

pass

2 mail servers

Found

Priority	Host	Records	Reverse DNS
10	smtp1.level27.eu	A 91.208.211.39 AAAA 2a02:5b40:4:200::39	smtp1.level27.eu ✓ smtp1.level27.eu ✓
20	smtp2.level27.eu	A 194.32.155.58 AAAA 2a02:5b41:4:440::58	smtp2.level27.eu ✓ smtp2.level27.eu ✓

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

warn

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

Found

DANE (TLSA records)

MX host	TLSA	DNSSEC
smtp1.level27.eu	none	-
smtp2.level27.eu	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