Mail domain report: inno.be

SPF

pass

SPF record published

Found

Record: v=spf1 mx ip4:94.104.162.48/29 ip4:84.199.51.8/29 ip4:81.240.37.23 ip4:84.198.158.170 ip4:160.8.44.66 ip4:185.33.166.124 include:servers.mcsv.net include:spf.ctacloud.net include:spf.protection.outlook.com include:_spf-dc2.successfactors.com include:_spf.odoo.com -all
DNS lookups: 8 of 10
Void lookups: 0 of 2

Checks

✓ No deprecated ptr mechanism #1

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

SPF record needs 8 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.inno.be)

Found

Record: v=DMARC1; p=quarantine; sp=none; rua=mailto:dmarc_agg@vali.email,mailto:dmarc-reports@inno.be; ruf=mailto:dmarc-reports@inno.be; fo=1
Found at: _dmarc.inno.be
External report address: mailto:dmarc_agg@vali.email (authorized)

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
sp	none	Subdomain policy
rua	mailto:dmarc_agg@vali.email,mailto:dmarc-reports@inno.be	Aggregate report addresses
ruf	mailto:dmarc-reports@inno.be	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:dmarc_agg@vali.email, mailto:dmarc-reports@inno.be
!

Subdomains unprotected (sp=none)

DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

#20
✓ External report addresses authorized #29

Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: mail, selector1, selector2, s1, s2

Found

Selectors: mail, selector1, selector2, s1, s2
_domainkey: NOERROR

Selector	Key	Flags
mail	RSA 1024 bits
selector1	RSA 2048 bits
selector2	RSA 2048 bits
s1	RSA 1024 bits
s2	RSA 1024 bits

Checks

✓ Keys found: mail, selector1, selector2, s1, s2 #7

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

1024-bit DKIM key

1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), s1 (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
10	inno-be.mail.protection.outlook.com	A 52.101.185.24 A 52.101.91.159 A 52.101.68.29 A 52.101.91.153 AAAA 2a01:111:f403:ca48::8 AAAA 2a01:111:f403:ca48::12 AAAA 2a01:111:f403:c967::c AAAA 2a01:111:f403:ca09::22	mail-zrxpr07cu00100.inbound.protection.outlook.com ✓ mail-matpr04cu00207.inbound.protection.outlook.com ✓ mail-dbapr03cu00105.inbound.protection.outlook.com ✓ mail-matpr04cu00101.inbound.protection.outlook.com ✓ mail-miypr02cu00100.inbound.protection.outlook.com ✓ mail-miypr05cu00202.inbound.protection.outlook.com ✓ mail-cpjpr05cu00204.inbound.protection.outlook.com ✓ mail-am7pr02cu00302.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

fail

MTA-STS record without policy · TLS-RPT · DANE on 0 of 1 MX hosts

Found

MTA-STS record: v=STSv1; id=2025-10-01
Policy URL: https://mta-sts.inno.be/.well-known/mta-sts.txt
Policy error: https://mta-sts.inno.be/.well-known/mta-sts.txt returned HTTP 403
TLS-RPT record: v=TLSRPTv1; rua=mailto:tlsrpt@inno.be

DANE (TLSA records)

MX host	TLSA	DNSSEC
inno-be.mail.protection.outlook.com	none	-

Checks

✗

Invalid MTA-STS record

Senders ignore the MTA-STS record because of: id "2025-10-01" must be 1 to 32 letters or digits.

#32
✗

Policy not reachable

The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: https://mta-sts.inno.be/.well-known/mta-sts.txt returned HTTP 403.

#33
✓ Reports enabled #35

TLS reports are sent to: mailto:tlsrpt@inno.be
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

fail

https://inno.be/on/demandware.static/-/Library-Sites-Shared-Library-Inno/default/images/logo/logo-bimi.svg

Found

Record: v=BIMI1; l=https://inno.be/on/demandware.static/-/Library-Sites-Shared-Library-Inno/default/images/logo/logo-bimi.svg;
Found at: default._bimi.inno.be
Logo: https://inno.be/on/demandware.static/-/Library-Sites-Shared-Library-Inno/default/images/logo/logo-bimi.svg

Checks

!

No certificate (a=)

The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.

#38
✗

DMARC not strict enough for BIMI

Mail clients will not show the logo. BIMI requires a subdomain policy other than sp=none.

#39