cultuurfonds.nl

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

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.protection.outlook.com include:_spf.cobytes.email ip4:85.17.68.30 include:_spf.exonet.nl ip4:135.84.216.0/22 ip4:159.92.157.4 ip4:92.68.219.231 include:_spf.psm.knowbe4.com include:spf.sendinblue.com ip4:185.166.140.16 ip4:184.173.153.208 ip4:66.240.227.0/24 ip4:34.245.210.0/24 ip4:52.200.59.0/24 ip4:74.63.212.0/24 ip4:216.98.158.0/24 ip4:63.143.57.128/25 ip4:63.143.59.128/25 include:_spf.salesforce.com ip4:178.208.58.45/32 ip4:178.208.58.46/31 ip4:178.208.58.48/31 ip4:45.157.174.64/27 ip4:178.208.58.42/31 ip4:178.208.58.44/32 ip4:178.208.58.51/32 ip4:178.208.58.52/30 ip4:178.208.58.56/31 ip4:178.208.58.57 ~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

warn

p=quarantine (_dmarc.cultuurfonds.nl)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:dmarc@vxcompany.uriports.com; ruf=mailto:dmarc@vxcompany.uriports.com; fo=1:d:s
Found at
_dmarc.cultuurfonds.nl
External report address
mailto:dmarc@vxcompany.uriports.com (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:dmarc@vxcompany.uriports.comAggregate report addresses
rufmailto:dmarc@vxcompany.uriports.comFailure report addresses
fo1:d:sFailure reporting options

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

DKIM

warn

Selectors: mail, selector1, selector2, s1, s2

Found

Selectors
mail, selector1, selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
selector1RSA 1024 bits
selector2RSA 2048 bits
s1RSA 2048 bits
s2RSA 2048 bits

Checks

  • ✓ Keys found: mail, selector1, selector2, s1, s2 #7
    DKIM keys found for this domain with selectors: mail, selector1, selector2, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), selector1 (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

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
18786, 60409
Signatures valid until
29 October 2026, 00:00 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-10-29 #21
    DNSKEY signatures are valid until 2026-10-29T00:00:00Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
0cultuurfonds-nl.mail.protection.outlook.comA 52.101.103.162 A 52.101.209.31 A 52.101.209.28 A 52.101.68.12 AAAA 2a01:111:f403:ca21::10 AAAA 2a01:111:f403:ca04::a AAAA 2a01:111:f403:ca3c::8 AAAA 2a01:111:f403:ca09::28mail-miypr03cu00202.inbound.protection.outlook.com ✓ mail-cpjpr05cu00207.inbound.protection.outlook.com ✓ mail-cpjpr05cu00104.inbound.protection.outlook.com ✓ mail-db9pr02cu00204.inbound.protection.outlook.com ✓ mail-matpr05cu00100.inbound.protection.outlook.com ✓ mail-du0pr03cu00102.inbound.protection.outlook.com ✓ mail-zrxpr05cu00100.inbound.protection.outlook.com ✓ mail-am6pr02cu00300.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 0 of 1 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
cultuurfonds-nl.mail.protection.outlook.comnone-

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