rijksmonumenten.nl

Checked 22 October 2026, 15:41 UTC · via 8.8.8.8
✗Problems found
10 passed 2 warnings 3 failed 3 info

SPF

fail

No SPF record found

Checks

  • ✗
    No SPF record
    No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6

DMARC

fail

No DMARC record found

Checks

  • ✗
    No DMARC record
    No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5

DKIM

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.rijksmonumenten.nl does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
8877, 39878
Signatures valid until
5 November 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-11-05 #21
    DNSKEY signatures are valid until 2026-11-05T00:00:00Z.

MX

warn

7 mail servers

Found

PriorityHostRecordsReverse DNS
10ASPMX.L.GOOGLE.COMA 142.251.168.27 AAAA 2a00:1450:4001:c21::1bwh-in-f27.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
20ALT1.ASPMX.L.GOOGLE.COMA 192.178.213.26 AAAA 2a00:1450:4013:c1e::1ayugrqzs-in-f26.1e100.net ✓ yugrqzs-in-f26.1e100.net ✓
20ALT2.ASPMX.L.GOOGLE.COMA 172.253.152.26 AAAA 2a00:1450:4001:c21::1byulpptr-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
30ASPMX2.GOOGLEMAIL.COMA 192.178.213.27 AAAA 2a00:1450:4013:c1e::1byugrqzs-in-f27.1e100.net ✓ yugrqzs-in-f27.1e100.net ✓
30ASPMX3.GOOGLEMAIL.COMA 172.253.152.26 AAAA 2a00:1450:4010:c22::1ayulpptr-in-f26.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
30ASPMX4.GOOGLEMAIL.COMA 192.179.20.27 AAAA 2a00:1450:4025:4403::1bncboms-in-f27.1e100.net ✓ yuskelf-in-f27.1e100.net ✓
30ASPMX5.GOOGLEMAIL.COMA 192.178.158.26 AAAA 2404:6800:4013:813::1alcdels-in-f26.1e100.net ✓ lcdels-in-f26.1e100.net ✓

Checks

  • ✓ 7 MX records #9
    Found 7 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 7 MX records, which provides redundancy for email delivery.
  • !
    More than 5 MX records
    Found 7 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • ✓ 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 14 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
ASPMX.L.GOOGLE.COMnone-
ALT1.ASPMX.L.GOOGLE.COMnone-
ALT2.ASPMX.L.GOOGLE.COMnone-
ASPMX2.GOOGLEMAIL.COMnone-
ASPMX3.GOOGLEMAIL.COMnone-
ASPMX4.GOOGLEMAIL.COMnone-
ASPMX5.GOOGLEMAIL.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