cda.nl

Checked 21 October 2026, 21:00 UTC · via 8.8.8.8
!Passed with warnings
28 passed 4 warnings 0 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 a ip4:54.171.188.117 ip4:54.171.188.119 ip4:192.254.119.131 include:spf.protection.outlook.com include:_spf.mailer.twinfield.com include:_spf.salesforce.com include:spf.mandrillapp.com include:spf.afas.online include:_spf.mailgun.org -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=reject (_dmarc.cda.nl)

Found

Record
v=DMARC1; p=reject; rua=mailto:529df4fd8ffb4bc0bb6bceda33a988f6@dmarc-reports.cloudflare.net,mailto:dmarc@smtpeter.com; fo=0; adkim=r; aspf=r; pct=100; rf=afrf; ri=86400; sp=none
Found at
_dmarc.cda.nl
External report address
mailto:529df4fd8ffb4bc0bb6bceda33a988f6@dmarc-reports.cloudflare.net (authorized)
External report address
mailto:dmarc@smtpeter.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:529df4fd8ffb4bc0bb6bceda33a988f6@dmarc-reports.cloudflare.net,mailto:dmarc@smtpeter.comAggregate report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo0Failure reporting options
rfafrfFailure report format
ri86400Report interval (seconds)

Checks

  • ✓ 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.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:529df4fd8ffb4bc0bb6bceda33a988f6@dmarc-reports.cloudflare.net, mailto:dmarc@smtpeter.com
  • !
    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

pass

Selectors: selector1, google

Found

Selectors
selector1, google
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits
googleRSA 2048 bits

Checks

  • ✓ Keys found: selector1, google #7
    DKIM keys found for this domain with selectors: selector1, google
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector1: RSA 2048 bits; google: 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 (2)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
2371, 34505
Signatures valid until
19 December 2026, 04:46 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-12-19 #21
    DNSKEY signatures are valid until 2026-12-19T04:46:43Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
0cda-nl.e-v1.mx.microsoftA 52.101.209.28 A 52.101.181.153 A 52.101.209.153 A 52.101.185.24 AAAA 2a01:111:f403:ca04::4 AAAA 2a01:111:f403:ca21::a AAAA 2a01:111:f403:ca09::28 AAAA 2a01:111:f403:ca04::cmail-cpjpr05cu00104.inbound.protection.outlook.com ✓ mail-wa4pr04cu00101.inbound.protection.outlook.com ✓ mail-cpjpr04cu00101.inbound.protection.outlook.com ✓ mail-zrxpr07cu00100.inbound.protection.outlook.com ✓ mail-db4pr02cu00204.inbound.protection.outlook.com ✓ mail-maspr04cu00102.inbound.protection.outlook.com ✓ mail-am6pr02cu00300.inbound.protection.outlook.com ✓ mail-db9pr02cu00204.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

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
cda-nl.e-v1.mx.microsoft2 0 1 ea7a25255d111fc3… 3 1 1 54883cc5f1849331… 3 1 1 cfd68bde4129c00a… 3 1 1 803f7447cc75b208… 2 0 1 c1ad7778796d20bc…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
  • ✓ DANE on all MX hosts #36
    All 1 MX host publish DNSSEC-validated TLSA records.

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