vca.nl

Checked 22 October 2026, 17:00 UTC · via 8.8.8.8
✗Problems found
7 passed 7 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

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

4 mail servers

Found

PriorityHostRecordsReverse DNS
10vmx01.prolocation.netA 94.228.142.130 AAAA 2a00:d01:ff:905:94:228:142:130vmx01.prolocation.nl ✓ vmx01.prolocation.nl ✓
10vmx02.prolocation.netA 94.228.142.131 AAAA 2a00:d01:ff:905:94:228:142:131vmx02.prolocation.nl ✓ vmx02.prolocation.nl ✓
10vmx03.prolocation.netA 94.228.129.7 AAAA 2a00:d00:ff:129:94:228:129:7vmx03.prolocation.net ✓ vmx03.prolocation.net ✓
10vmx04.prolocation.net(does not resolve)

Checks

  • ✓ 4 MX records #9
    Found 4 MX records for this domain.
  • !
    Hosts without IP addresses
    The following MX hosts could not be resolved to IP addresses: vmx04.prolocation.net
    #10
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: vmx04.prolocation.net
    #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 6 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
vmx01.prolocation.net3 1 1 0d5a5c8f3d8aab82… 2 1 1 e1ae9c3de848ece1…Yes
vmx02.prolocation.net2 1 1 e1ae9c3de848ece1… 3 1 1 55cae87df5bfbfc4…Yes
vmx03.prolocation.net2 1 1 e1ae9c3de848ece1… 3 1 1 44858cd78c2d1a04…Yes
vmx04.prolocation.netnone-

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
  • !
    Not all MX hosts use DANE
    These MX hosts publish no TLSA records, so mail to them is not protected by DANE: vmx04.prolocation.net.
    #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