Mail domain report: velleman.be

SPF

warn

SPF record published

Found

Record: v=spf1 mx a ip4:84.198.211.10/29 include:spf.antispamcloud.com include:spf.protection.outlook.com include:spf.EU.exclaimer.net include:servers.mcsv.net ?all
DNS lookups: 6 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 6 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.velleman.be)

Found

Record: v=DMARC1; p=none; rua=mailto:administrator@velleman.eu; ruf=mailto:administrator@velleman.eu; sp=none
Found at: _dmarc.velleman.be
External report address: mailto:administrator@velleman.eu (not authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	none	Policy
sp	none	Subdomain policy
rua	mailto:administrator@velleman.eu	Aggregate report addresses
ruf	mailto:administrator@velleman.eu	Failure report addresses

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.
✓ Aggregate reports enabled #19

Aggregate reports are sent to: mailto:administrator@velleman.eu
!

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:administrator@velleman.eu (needs velleman.be._report._dmarc.velleman.eu). Ask the report provider to publish the record, or check the address.

#29

DKIM

warn

Selectors: k1, selector1

Found

Selectors: k1, selector1
_domainkey: NOERROR

Selector	Key	Flags
k1	RSA 1024 bits
selector1	RSA 1024 bits

Checks

✓ Keys found: k1, selector1 #7

DKIM keys found for this domain with selectors: k1, selector1
!

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits), selector1 (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

pass

2 mail servers

Found

Priority	Host	Records	Reverse DNS
10	mx.cleanmx.be	A 188.93.100.159 A 37.72.162.135 AAAA 2a02:d08:1002:321:370:7216:2135:1 AAAA 2a02:d08:1001:201:1880:9310:159:1	mx.cleanmx.be ✓ se-001.cleanmx.be ✓ se-001.cleanmx.be ✓ mx.cleanmx.be ✓
50	mx.fallback.cleanmx.be	A 37.72.162.136 A 188.93.100.158 AAAA 2a02:d08:1002:321:370:7216:2136:1 AAAA 2a02:d08:1001:201:1880:9310:158:1	mx.fallback.cleanmx.be ✓ se-002.cleanmx.be ✓ mx.fallback.cleanmx.be ✓ se-002.cleanmx.be ✓

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 8 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
mx.cleanmx.be	none	-
mx.fallback.cleanmx.be	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