tussenhaakjes.nl

Checked 22 October 2026, 16:41 UTC · via 8.8.8.8
✗Problems found
12 passed 3 warnings 2 failed 1 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

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
27695
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

pass

3 mail servers

Found

PriorityHostRecordsReverse DNS
100mx1.bit.nlA 213.136.12.237 AAAA 2001:7b8:3:5::25:5mx.lb.network.bit.nl ✓ mx.bit.nl ✓
200mx2.bit.nlA 213.136.12.237 AAAA 2001:7b8:3:5::25:5mx.lb.network.bit.nl ✓ mx.bit.nl ✓
300mx3.bitnl.euA 213.136.12.235 AAAA 2001:7b8:3:5::25:8mx3.lb.network.bit.nl ✓ mx3.bit.org ✓

Checks

  • ✓ 3 MX records #9
    Found 3 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 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 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 6 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.bit.nl3 0 1 7af199fd9f1f984d… 3 0 1 9a2e6c42e329ca46… 3 1 1 1505554503c35fe7… 3 1 1 754131f10c5997a6…Yes
mx2.bit.nl3 0 1 9a2e6c42e329ca46… 3 1 1 754131f10c5997a6… 3 1 1 1505554503c35fe7… 3 0 1 7af199fd9f1f984d…Yes
mx3.bitnl.eu2 1 1 b3fb5d00e994cddf… 2 1 1 51aaa87d984b559a… 2 1 1 2e8307068b6db620… 2 1 1 6ebcefb4210b0886… 2 1 1 a698a20824be04e4… 2 1 1 9d637b3d27a9e570…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 3 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