tassenmuseum.nl

Checked 22 October 2026, 16:30 UTC · via 8.8.8.8
✗Problems found
21 passed 5 warnings 1 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:_custspf.g1i.one a mx ip4:195.211.72.0/22 ip4:141.138.168.0/21 ip6:2a03:3c00:a001::/48 ip6:2a03:3c00:a002::/48 ~all
DNS lookups
3 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=none
Found at
_dmarc.tassenmuseum.nl
TagValueMeaning
vDMARC1Version
pnonePolicy

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.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (1)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
62529
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

4 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1-forward-antagonist-nl.pub.mailpod13-cph3.one.comA 185.10.9.226mx1-forward-antagonist-nl.pub.mailpod13-cph3.one.com ✓
10mx2-forward-antagonist-nl.pub.mailpod13-cph3.one.comA 185.10.9.227mx2-forward-antagonist-nl.pub.mailpod13-cph3.one.com ✓
10mx3-forward-antagonist-nl.pub.mailpod13-cph3.one.comA 185.10.9.228mx3-forward-antagonist-nl.pub.mailpod13-cph3.one.com ✓
10mx4-forward-antagonist-nl.pub.mailpod13-cph3.one.comA 185.10.9.229mx4-forward-antagonist-nl.pub.mailpod13-cph3.one.com ✓

Checks

  • ✓ 4 MX records #9
    Found 4 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mx1-forward-antagonist-nl.pub.mailpod13-cph3.one.com, mx2-forward-antagonist-nl.pub.mailpod13-cph3.one.com, mx3-forward-antagonist-nl.pub.mailpod13-cph3.one.com, mx4-forward-antagonist-nl.pub.mailpod13-cph3.one.com
    #11
  • ✓ 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 4 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
mx1-forward-antagonist-nl.pub.mailpod13-cph3.one.com3 1 1 dc60fbb3c3cad8bf… 3 1 1 be8c554e6a2a9bfe…Yes
mx2-forward-antagonist-nl.pub.mailpod13-cph3.one.com3 1 1 be8c554e6a2a9bfe… 3 1 1 dc60fbb3c3cad8bf…Yes
mx3-forward-antagonist-nl.pub.mailpod13-cph3.one.com3 1 1 dc60fbb3c3cad8bf… 3 1 1 be8c554e6a2a9bfe…Yes
mx4-forward-antagonist-nl.pub.mailpod13-cph3.one.com3 1 1 dc60fbb3c3cad8bf… 3 1 1 be8c554e6a2a9bfe…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