paxforpeace.nl

Checked 22 October 2026, 15:11 UTC · via 8.8.8.8
✗Problems found
25 passed 4 warnings 1 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:autotask.net mx ip4:195.190.28.88 ip4:13.111.68.29 include:spf.greenhost.nl a:malengo.exception.mx include:spf.protection.outlook.com include:_spf.salesforce.com ip4:213.227.146.219 ip4:192.254.119.131 -all
DNS lookups
7 of 10
Void lookups
0 of 2

Checks

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

DMARC

fail

p=none (_dmarc.paxforpeace.nl)

Found

Record
v=DMARC1; p=none; rua=mailto:webmaster@paxforpeace.nl.nl; ruf=mailto:webmaster@paxforpeace.nl; fo=1
Found at
_dmarc.paxforpeace.nl
External report address
mailto:webmaster@paxforpeace.nl.nl (not authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:webmaster@paxforpeace.nl.nlAggregate report addresses
rufmailto:webmaster@paxforpeace.nlFailure report addresses
fo1Failure reporting options

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:webmaster@paxforpeace.nl.nl
  • !
    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:webmaster@paxforpeace.nl.nl (needs paxforpeace.nl._report._dmarc.paxforpeace.nl.nl). Ask the report provider to publish the record, or check the address.
    #29

DKIM

pass

Selectors: selector1, selector2

Found

Selectors
selector1, selector2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits
selector2RSA 2048 bits

Checks

  • ✓ Keys found: selector1, selector2 #7
    DKIM keys found for this domain with selectors: selector1, selector2
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector1: RSA 2048 bits; selector2: RSA 2048 bits.
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (4)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13), RSASHA256 (8)
Key tags
39034, 20202, 14711, 21604
Signatures valid until
5 November 2026, 10:53 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • ✓ Signatures valid until 2026-11-05 #21
    DNSKEY signatures are valid until 2026-11-05T10:53:39Z.

MX

pass

3 mail servers

Found

PriorityHostRecordsReverse DNS
0paxforpeace-nl.mail.protection.outlook.comA 52.101.103.162 A 52.101.68.15 A 52.101.73.123 A 52.101.185.24 AAAA 2a01:111:f403:ca21::c AAAA 2a01:111:f403:ca21::10 AAAA 2a01:111:f403:ca3c::8 AAAA 2a01:111:f403:c967::cmail-miypr03cu00202.inbound.protection.outlook.com ✓ mail-db6pr03cu00107.inbound.protection.outlook.com ✓ mail-am6pr02cu00203.inbound.protection.outlook.com ✓ mail-zrxpr07cu00100.inbound.protection.outlook.com ✓ mail-matpr04cu00204.inbound.protection.outlook.com ✓ mail-matpr05cu00100.inbound.protection.outlook.com ✓ mail-zrxpr05cu00100.inbound.protection.outlook.com ✓ mail-cpjpr05cu00204.inbound.protection.outlook.com ✓
10mx1.greenhost.nlA 195.190.28.42 AAAA 2a00:c6c0:0:111::25mx1.greenhost.nl ✓ mx1.greenhost.nl ✓
10mx2.greenhost.nlA 195.190.28.43 AAAA 2a00:c6c0:0:111::2525mx2.greenhost.nl ✓ mx2.greenhost.nl ✓

Checks

  • ✓ 3 MX records #9
    Found 3 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 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 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 12 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
paxforpeace-nl.mail.protection.outlook.comnone-
mx1.greenhost.nl3 1 1 9f10c09dc0f0fb0e…Yes
mx2.greenhost.nl3 1 1 1ed78825a5073dfb…Yes

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
  • !
    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
  • !
    Not all MX hosts use DANE
    These MX hosts publish no TLSA records, so mail to them is not protected by DANE: paxforpeace-nl.mail.protection.outlook.com.
    #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