vwa.nl

Checked 22 October 2026, 17:11 UTC · via 8.8.8.8
!Passed with warnings
29 passed 3 warnings 0 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf.dictu.nl include:amazonses.com -all
DNS lookups
2 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 2 of 10 DNS lookups #2
    SPF record needs 2 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

pass

p=reject (_dmarc.vwa.nl)

Found

Record
v=DMARC1;p=reject;sp=reject;pct=100;rua=mailto:dmarc@dictu.nl;
Found at
_dmarc.vwa.nl
External report address
mailto:dmarc@dictu.nl (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
sprejectSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:dmarc@dictu.nlAggregate report addresses

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:dmarc@dictu.nl
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

pass

Selectors: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2

Found

Selectors
default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
defaultrevoked
dkimrevoked
mailrevoked
emailrevoked
k1revoked
selector1RSA 2048 bits
selector2RSA 2048 bits
googlerevoked
zohorevoked
mxrevoked
keyrevoked
mtarevoked
pmrevoked
dkim-smtprevoked
s1revoked
s2revoked

Checks

  • ✓ Keys found: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2 #7
    DKIM keys found for this domain with selectors: default, dkim, mail, email, k1, selector1, selector2, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector1: RSA 2048 bits; selector2: RSA 2048 bits.
  • ✓ No problematic flags #24
    No test mode or SHA-1-only keys. Revoked keys (empty p=), which is fine after a key rotation: default, dkim, mail, email, k1, google, zoho, mx, key, mta, pm, dkim-smtp, s1, s2.

DNSSEC

warn

Signed, DS published at parent

Found

DNSKEY records
Yes (5)
DS at parent
Yes
Algorithms
RSASHA256 (8), ECDSAP256SHA256 (13)
Key tags
55819, 38949, 6461, 50731, 54684
Signatures valid until
25 October 2026, 20:50 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 expire in 76h0m0s
    DNSKEY signatures expire at 2026-10-25T20:50:16Z (in 76h0m0s). Check that re-signing works.
    #21

MX

pass

4 mail servers

Found

PriorityHostRecordsReverse DNS
10mail02.dictu.nlA 145.12.216.26 AAAA 2a04:9a00:1021:201a::2mail02.dictu.nl ✓ mail02.dictu.nl ✓
10mail04.dictu.nlA 145.69.216.26 AAAA 2a04:9a00:1022:201a::2mail04.dictu.nl ✓ mail04.dictu.nl ✓
20mail01.dictu.nlA 145.12.216.25 AAAA 2a04:9a00:1021:201a::1mail01.dictu.nl ✓ mail01.dictu.nl ✓
20mail03.dictu.nlA 145.69.216.25 AAAA 2a04:9a00:1022:201a::1mail03.dictu.nl ✓ mail03.dictu.nl ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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 4 of 4 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mail02.dictu.nl3 1 1 4e9f867b22723b6c… 2 1 1 957b778a9e65927b… 3 1 1 7625cd24f983e1d6…Yes
mail04.dictu.nl3 1 1 7625cd24f983e1d6… 3 1 1 4e9f867b22723b6c… 2 1 1 957b778a9e65927b…Yes
mail01.dictu.nl2 1 1 957b778a9e65927b… 3 1 1 4e9f867b22723b6c… 3 1 1 7625cd24f983e1d6…Yes
mail03.dictu.nl2 1 1 957b778a9e65927b… 3 1 1 4e9f867b22723b6c… 3 1 1 7625cd24f983e1d6…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 4 MX hosts 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