Mail domain report: idewe.be

SPF

pass

SPF record published

Found

Record: v=spf1 mx exists:%{i}.spf.hc896-91.eu.iphmx.com ip4:81.246.12.32/27 ip4:87.233.11.35 ip4:87.233.11.36 ip4:87.233.11.37 ip4:87.233.11.50 ip4:85.17.135.147 ip4:85.17.135.148 ip4:95.211.19.59 ip4:95.211.19.60 include:spf.emailsignatures365.com ip4:54.36.158.121 include:spf.protection.outlook.com ip4:51.137.7.62 ip4:23.90.116.244 ip4:23.90.111.243 ip4:185.111.207.180 ip4:185.2.54.136 include:25172126.spf03.hubspotemail.net include:sendgrid.net include:amazonses.com include:_spf.relay.mailprotect.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.idewe.be)

Found

Record: v=DMARC1; p=quarantine; rua=mailto:dmarcadvisor@idewe.be;
Found at: _dmarc.idewe.be

Tag	Value	Meaning
v	DMARC1	Version
p	quarantine	Policy
rua	mailto:dmarcadvisor@idewe.be	Aggregate report addresses

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:dmarcadvisor@idewe.be
✓ Subdomain policy: quarantine #20

Subdomains are covered by policy 'quarantine'.
✓ Report addresses in own domain #29

All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail, mx

Found

Selectors: mail, mx
_domainkey: NOERROR

Selector	Key	Flags
mail	RSA 1024 bits
mx	RSA 1024 bits

Checks

✓ Keys found: mail, mx #7

DKIM keys found for this domain with selectors: mail, mx
!

1024-bit DKIM key

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

2 mail servers

Found

Priority	Host	Records	Reverse DNS
10	mx1.hc896-91.eu.iphmx.com	A 23.90.111.225 A 23.90.116.214	esa2.hc896-91.eu.iphmx.com ✓ esa1.hc896-91.eu.iphmx.com ✓
10	mx2.hc896-91.eu.iphmx.com	A 23.90.111.225 A 23.90.116.214	esa2.hc896-91.eu.iphmx.com ✓ esa1.hc896-91.eu.iphmx.com ✓

Checks

✓ 2 MX records #9

Found 2 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: mx1.hc896-91.eu.iphmx.com, mx2.hc896-91.eu.iphmx.com

#11
✓ 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
mx1.hc896-91.eu.iphmx.com	none	-
mx2.hc896-91.eu.iphmx.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