Mail domain report: proud2bme.nl

SPF

pass

SPF record published

Record: v=spf1 a mx ip4:37.97.134.143 include:_ironport.cegeka.be include:spf.protection.outlook.com a:server1.proud2bme.nl include:sendgrid.net ~all
DNS lookups: 7 of 10
Void lookups: 0 of 2

✓ No deprecated ptr mechanism #1

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

SPF record needs 7 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.

warn

p=reject (_dmarc.proud2bme.nl)

Tag	Value	Meaning
v	DMARC1	Version
p	reject	Policy

✓ Policy: reject #4

DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
✓ 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.
!

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
✓ Subdomain policy: reject #20

Subdomains are covered by policy 'reject'.

warn

Selectors: mail

Selector	Key	Flags
mail	RSA 1024 bits

info

DNS query for proud2bme.nl failed: read udp 46.225.38.91:35987->8.8.8.8:53: i/o timeout

warn

1 mail server

Priority	Host	Records	Reverse DNS
0	proud2bme-nl.y-v1.mx.microsoft	A 52.101.209.153 A 52.101.68.29 A 52.101.91.159 A 52.101.209.28 AAAA 2a01:111:f403:c967::a AAAA 2a01:111:f403:ca04::f AAAA 2a01:111:f403:ca04::d AAAA 2a01:111:f403:ca21::8	mail-cpjpr04cu00101.inbound.protection.outlook.com ✓ mail-dbapr03cu00105.inbound.protection.outlook.com ✓ mail-matpr04cu00207.inbound.protection.outlook.com ✓ mail-cpjpr05cu00104.inbound.protection.outlook.com ✓ mail-cpjpr05cu00102.inbound.protection.outlook.com ✓ mail-db7pr03cu00507.inbound.protection.outlook.com ✓ mail-db6pr03cu00105.inbound.protection.outlook.com ✓ mail-matpr04cu00100.inbound.protection.outlook.com ✓

✓ 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.

warn

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

MX host	TLSA	DNSSEC
proud2bme-nl.y-v1.mx.microsoft	3 1 1 803f7447cc75b208… 3 1 1 54883cc5f1849331… 2 0 1 c1ad7778796d20bc… 3 1 1 cfd68bde4129c00a… 2 0 1 ea7a25255d111fc3…	Yes

!

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
!

Not configured

MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".

#35
✓ DANE on all MX hosts #36

All 1 MX host publish DNSSEC-validated TLSA records.

info

No BIMI record