Mail domain report: vlaio.be

SPF

pass

SPF record published

Found

Record: v=spf1 ip4:20.86.147.52/32 ip4:206.164.32.137/32 ip4:208.75.120.0/22 ip4:205.207.104.0/22 include:spf1.vlaio.be include:spf2.vlaio.be include:spf3.vlaio.be include:spf.topdesk.net include:_spf.tem.scaleway.com include:digital-shared.spf.digitbnlabs.be ~all
DNS lookups: 10 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 10 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=quarantine (_dmarc.vlaio.be)

Found

Record: v=DMARC1; p=quarantine; rua=mailto:3wutt46ykr@rua.powerdmarc.com; ruf=mailto:3wutt46ykr@ruf.powerdmarc.com;fo=1;
Found at: _dmarc.vlaio.be
External report address: mailto:3wutt46ykr@rua.powerdmarc.com (authorized)
External report address: mailto:3wutt46ykr@ruf.powerdmarc.com (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
rua	mailto:3wutt46ykr@rua.powerdmarc.com	Aggregate report addresses
ruf	mailto:3wutt46ykr@ruf.powerdmarc.com	Failure report addresses
fo	1	Failure reporting options

Checks

!

Policy: quarantine

DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

#4
✓ 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:3wutt46ykr@rua.powerdmarc.com
✓ Subdomain policy: quarantine #20

Subdomains are covered by policy 'quarantine'.
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: k1, selector1, s1, s2

Found

Selectors: k1, selector1, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
k1	RSA 1024 bits
selector1	RSA 1024 bits
s1	RSA 2048 bits
s2	RSA 1024 bits

Checks

✓ Keys found: k1, selector1, s1, s2 #7

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

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: k1 (1024 bits), selector1 (1024 bits), s2 (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
1	vlaio-be.mail.protection.outlook.com	A 52.101.209.31 A 52.101.103.140 A 52.101.68.27 A 52.101.209.28	mail-cpjpr05cu00207.inbound.protection.outlook.com ✓ mail-miypr02cu00204.inbound.protection.outlook.com ✓ mail-db7pr03cu00503.inbound.protection.outlook.com ✓ mail-cpjpr05cu00104.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.
!

Hosts without IPv6

The following MX hosts could not be resolved to IPv6 addresses: vlaio-be.mail.protection.outlook.com

#11
!

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 4 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

TLS-RPT record: v=TLSRPTv1; rua=mailto:3wutt46ykr@rua.powerdmarc.com

DANE (TLSA records)

MX host	TLSA	DNSSEC
vlaio-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
✓ Reports enabled #35

TLS reports are sent to: mailto:3wutt46ykr@rua.powerdmarc.com
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